---
name: learn-capstone
description: "Capstone project for the PM Foundations Course: act as PM for a product from discovery through launch decision, applying every framework learned across all prior modules in a single integrated case study."
category: learning
complexity: advanced
tags: ["learning", "capstone", "course-completion", "integrated", "case-study", "full-lifecycle"]
---

# Learn: PM Capstone Project

## Purpose
The capstone project is the final module of the PM Foundations Course. It synthesizes everything covered in the prior modules — discovery, strategy, metrics, prioritization, execution, stakeholder management, and modern PM — into a single, integrated product case study. You will act as the lead PM for **Pando**, a new B2B collaboration tool, taking the product from initial research through a go/no-go launch decision. There are no isolated exercises here. Every framework you've learned must work together.

## Domain Context

### What is a Capstone Project?
In education, a capstone project integrates knowledge across an entire curriculum into a single complex challenge. For PM learning, this means:
- No isolated framework exercises — every decision connects to the ones before and after it
- Trade-offs become real: optimizing for one dimension affects others
- You must justify every decision with evidence, reasoning, and PM judgment
- The "right answer" is not always clear — the quality of your reasoning matters more than the conclusion

### The Pando Scenario
**Company**: Pando is an early-stage B2B SaaS startup, 18 months old, with 12 full-time employees.

**Product**: Pando is a team collaboration tool focused on "async-first" communication — it replaces real-time meeting culture with structured, written updates, decision logs, and team check-ins. Think of it as a mix between Notion (structured docs), Slack (team communication), and Loom (async video).

**Current state**:
- 3,200 monthly active users across 140 teams
- Freemium model: free for ≤ 5 users, $12/user/month for larger teams
- Monthly recurring revenue: $28,000 MRR
- 30-day retention: 61% (strong for an early-stage B2B tool)
- Net Promoter Score: 42

**The challenge**: Pando's investors want to see a path to $500K MRR within 18 months. The current growth rate won't get there. As the new PM, you need to identify the growth opportunity, build a strategy, define a roadmap, set metrics, and ultimately present a go/no-go recommendation for a major product bet.

## Learning Format
This is a full-lifecycle case study. You will make real product decisions across six phases, with each phase building on the previous ones. The AI mentor plays multiple roles:
- **Discovery phase**: User research facilitator
- **Strategy phase**: Board advisor
- **Metrics phase**: Data analyst presenting dashboard data
- **Prioritization phase**: Engineering lead presenting trade-offs
- **Execution phase**: PRD reviewer
- **Stakeholder phase**: Skeptical executive in the room

The mentor evaluates decisions holistically, looking for coherence across phases as much as correctness within each phase.

## Prerequisites
- **Required**: Completed or familiar with content from: `learn-foundations`, `learn-user-research`, `learn-discovery`, `learn-strategy`, `learn-metrics`, `learn-prioritization`, `learn-execution`, `learn-stakeholder-management`
- **Recommended**: `learn-ai-pm` for Phase 5 (AI features decision)

## Learning Objectives
By the end of this module, you will be able to:
- Apply the full PM lifecycle (discover → define → deliver → measure → iterate) to a real product scenario
- Make coherent strategic choices that cascade logically from discovery findings to execution plan
- Write a go/no-go recommendation that integrates evidence from discovery, metrics, and stakeholder input
- Demonstrate the ability to defend product decisions under challenge
- Identify the PM skills you've mastered and the gaps that remain for continued growth

## Module Structure

### Phase 1 — Discovery (20–25 min)
The learner reviews 4 interview excerpts from Pando users and must identify the most promising growth opportunity. They build a simplified Opportunity Solution Tree.

**Phase Checkpoint**: 2 questions on opportunity framing and OST structure.

### Phase 2 — Strategy (15–20 min)
The learner makes the five Playing to Win choices for Pando's next 18 months and runs the Coherence Test.

**Phase Checkpoint**: 2 questions on strategic coherence.

### Phase 3 — Metrics (15–20 min)
The learner defines a North Star Metric, 3 input metrics, and 2 counter-metrics for Pando's chosen growth strategy.

**Phase Checkpoint**: 2 questions on metric design.

### Phase 4 — Prioritization (15–20 min)
The learner applies RICE scoring to 5 potential initiatives and selects the top 2 for Q1.

**Phase Checkpoint**: 2 questions on prioritization reasoning.

### Phase 5 — Execution (15–20 min)
The learner writes a concise PRD for the highest-priority initiative, including success metrics and 2 user stories with acceptance criteria.

**Phase Checkpoint**: 2 questions on PRD quality.

### Phase 6 — Stakeholder Presentation & Go/No-Go (20–25 min)
The learner presents their Q1 plan to a skeptical leadership team (simulated) and defends the go/no-go recommendation with integrated evidence from all prior phases.

**Final Debrief**: Comprehensive performance review across all 6 phases with course completion summary.

## Instructions

### Step 0 — Learner Context (do this first)
Before starting, acknowledge the scope of the capstone:

_"Welcome to the PM Capstone Project. This is the most demanding module in the PM Foundations Course — it's designed to be. You'll act as PM for Pando across 6 phases: discovery, strategy, metrics, prioritization, execution, and stakeholder presentation. Each phase builds on the last. This will take 90–120 minutes if done fully. You can pause between phases and pick up where you left off._

_Before we start, two questions:_
1. _Which prior modules have you completed? (Discovery, Strategy, Metrics, Prioritization, Execution, Stakeholder Management)_
2. _Is there any area where you felt less confident and want to practice more in this capstone?"_

**Wait for their response.** Adjust which phases to emphasize based on their self-reported gaps.

---

### Phase 1 — Discovery

**Present the Pando scenario** (see Domain Context above), then present the user interview excerpts:

---

**Interview Excerpt 1 — Jamie, Head of Design, 22-person agency:**
> "Pando is actually pretty great. The async check-ins have cut our daily standup meetings by 80%. But we keep running into problems when we need to make a decision with multiple people. We'll have a conversation in Pando, everyone gives input, but nobody ever moves it to a conclusion. Decisions just… float. We end up having a meeting to make the decision anyway."

**Interview Excerpt 2 — Marcus, VP Engineering, 50-person SaaS company:**
> "Our team tried Pando for 3 months and then went back to Slack. The writing-first culture is hard to change — engineers just don't want to type out updates every day. The tool is great if everyone's on board with async, but if you have even a few people who don't buy in, it creates a two-tier communication system. Half the team is on Pando, half is still in Slack."

**Interview Excerpt 3 — Sofia, Chief of Staff, 15-person consulting firm:**
> "We love the decision log feature. It's the first time we've ever had a real record of why we made choices. But the search is terrible — I'm constantly scrolling to find old decisions. Also, I really wish there was a way to tag people as 'responsible' for following through on a decision. Right now it's just a document."

**Interview Excerpt 4 — Alex, CEO, 8-person startup:**
> "I use Pando as a kind of digital brain for the company. Meeting notes, decisions, weekly updates — it's all there. My problem is that new hires take 3–4 weeks to get up to speed because there's so much to read. I wish there was a smarter way to onboard people to the company's context — like an AI assistant that could answer 'what has the team decided about X?' without them having to dig through 18 months of docs."

---

Ask: _"Based on these four interviews, what growth opportunities do you see? List every unmet need or pain point. Then group them into parent opportunities. Finally, pick the ONE opportunity you think is most likely to unlock Pando's path to $500K MRR — and argue for your choice."_

Evaluate against these reference opportunities:
1. Decision closure — conversations don't reach conclusions (Jamie)
2. Team adoption friction — async culture change is hard (Marcus)
3. Decision search/retrieval — can't find old decisions (Sofia)
4. Decision accountability — no ownership tracking on follow-through (Sofia)
5. New hire onboarding to company context (Alex)
6. AI-powered knowledge retrieval / company memory (Alex)

Expected groupings:
- **Decision quality and accountability**: closure, search, accountability
- **Team adoption and behavior change**: culture friction
- **Organizational knowledge management**: onboarding, AI retrieval

**Strongest opportunity for $500K MRR path**: Either "Decision quality and accountability" (broad, core to Pando's value prop) or "AI-powered knowledge management" (high-value, differentiating, matches where B2B SaaS market is heading).

After the learner picks their opportunity, challenge their reasoning: "Marcus says teams abandon Pando because of culture change friction. If that's happening, does improving decision quality solve the adoption problem — or does it only serve teams who are already bought in?"

**Phase Checkpoint 1:**

**Q1:** "Name the opportunity you chose and the one biggest risk of focusing on it."
**Q2:** "What additional research would you need to do before committing to this direction?"

---

### Phase 2 — Strategy

**Setup:**
_"You've identified your growth opportunity. Now let's build the strategy. Apply Roger Martin's Playing to Win cascade to Pando. Make choices at each of the 5 levels and then run the Coherence Test."_

Present the five cascade prompts one at a time:
1. **Winning Aspiration**: What does winning look like for Pando in 18 months?
2. **Where to Play**: Which market segment, company size, and use case will you focus on?
3. **How to Win**: Cost leadership or differentiation — what is Pando's unique advantage?
4. **Capabilities**: What 3 capabilities must Pando be world-class at to execute this strategy?
5. **Management Systems**: What metrics, processes, or team structures reinforce the strategy?

After the learner completes all five choices, run the Coherence Test:
"Do your Where to Play and How to Win choices reinforce each other? Do your Capabilities match your How to Win? Is there anything that contradicts?"

Common incoherence to surface: If learner says "Where to Play: all company sizes from 5 to 500" AND "How to Win: deep customization for enterprise" — these are in tension. Enterprise customization requires dedicated engineering investment that works against a broad horizontal play.

**Phase Checkpoint 2:**

**Q1:** "What is the biggest strategic risk in your chosen direction? What assumption, if wrong, would break the strategy?"
**Q2:** "Who is your primary competitor for the segment and use case you've chosen — and why is your strategy better than following the same path?"

---

### Phase 3 — Metrics

**Setup:**
_"Your strategy is defined. Now design the metrics system that will tell you if you're winning. Define: (1) your North Star Metric, (2) 3 input metrics, (3) 2 counter-metrics."_

Evaluate against NSM criteria:
- Captures core user value (not revenue)
- Leading indicator of retention and growth
- Measurable, actionable, understandable by the whole team

Strong NSM candidates:
- "Teams with ≥1 decision logged per week" (habit-based, captures core value)
- "Decisions with an assigned owner" (if accountability is the chosen opportunity)
- "Team members who return to Pando at least 3 days/week" (engagement, but less specific)

Weak NSM: "MRR" (lagging, doesn't capture user value), "DAU" (generic, doesn't reflect Pando's specific value)

Input metrics should be leading indicators that move before the NSM:
- New team activation rate (teams that complete their first decision log)
- Onboarding completion rate
- Notification open rate (for async check-in reminders)

Counter-metrics:
- Churn rate (existing subscribers canceling)
- Decision-log-to-meeting conversion (are Pando decisions actually replacing meetings?)

**Phase Checkpoint 3:**

**Q1:** "Your NSM moves up 15% in Month 1 after launching a new feature. Is that enough to know the feature worked? What else would you check?"
**Q2:** "A counter-metric is moving in the wrong direction — your 30-day churn rate went from 9% to 14%. But your NSM is still growing. What's happening and what do you do?"

---

### Phase 4 — Prioritization

**Setup:**
_"You've defined your strategy and metrics. Now you have 5 potential initiatives for Q1. Apply RICE scoring (or ICE if you prefer) and select the top 2 to build. Justify your selections."_

**The 5 initiatives:**

1. **Decision Closure Flow**: A structured workflow that moves a Pando discussion to a formal decision with an assigned owner, a deadline, and a completion status. (Estimated: 6 weeks)

2. **AI Company Memory**: An AI assistant that can answer "What has the team decided about X?" by searching all decision logs and meeting notes. (Estimated: 10 weeks, requires LLM integration)

3. **Slack Integration**: A two-way sync that lets Slack users see and respond to Pando check-ins without leaving Slack, reducing the tool-switching barrier. (Estimated: 8 weeks)

4. **Smart Onboarding**: A personalized onboarding flow that gives new team members a summary of the 10 most relevant recent decisions and context docs for their role. (Estimated: 5 weeks)

5. **Mobile App (iOS + Android)**: Native mobile clients for Pando (currently web-only). (Estimated: 14 weeks)

Ask the learner to apply RICE: Reach, Impact, Confidence, Effort — and explain their top 2 selections.

After their answer, challenge their reasoning:
- If they pick Mobile App: "Mobile has the largest reach but the longest build time. What evidence do you have that mobile is blocking adoption vs. other factors?"
- If they pick AI Company Memory: "This requires integrating an LLM. What are the responsible AI considerations you'd need to address before shipping?"
- If they pick Slack Integration: "This gives Slack users a bridge — but does it solve the culture change problem or just delay it? What's the long-term strategic implication?"

**Phase Checkpoint 4:**

**Q1:** "You scored the initiatives but your top-2 selection doesn't include the Mobile App, and a board member insists mobile is critical for growth. How do you respond?"
**Q2:** "Your engineering lead says the Decision Closure Flow will take 10 weeks, not 6. How does this change your Q1 plan?"

---

### Phase 5 — Execution

**Setup:**
_"You've selected your Q1 initiatives. Write a concise PRD for your #1 priority initiative. Include: problem statement, success metrics, proposed solution (key UX flows), 2 user stories with acceptance criteria, and out-of-scope items."_

Evaluate the PRD against the quality bar from `learn-execution`:
- Problem statement: user-focused, not solution-focused
- Success metrics: tied to the NSM or input metrics defined in Phase 3
- Solution: specific enough to build, but not micromanaging implementation details
- Acceptance criteria: testable (pass/fail), not vague
- Out-of-scope: explicit list that prevents scope creep

**Phase Checkpoint 5:**

**Q1:** "An engineer asks: 'Should a decision be automatically marked closed when the owner marks it done, or when all stakeholders confirm?' How do you answer, and where does this edge case belong?"
**Q2:** "Your designer says the flow you've specced will take 3 extra weeks to make beautiful. You have 1 week of buffer. What do you do?"

---

### Phase 6 — Stakeholder Presentation & Go/No-Go

**Setup:**
_"You're presenting your Q1 plan to Pando's leadership team. In the room: the CEO (focused on path to $500K MRR), VP Engineering (focused on technical debt and team capacity), VP Sales (focused on closing enterprise deals), and a board observer (focused on competitive positioning). Present your plan — then I'll simulate their questions."_

Ask the learner to give a 5–7 sentence summary of their Q1 plan, including:
- The opportunity they chose and why
- The metrics that define success
- The 2 Q1 initiatives
- The go/no-go recommendation (proceed with this plan vs. pivot)

Then simulate stakeholder questions:

**CEO**: "You're betting on Decision Closure. But Marcus's interview showed that adoption is our biggest barrier — shouldn't we fix the Slack integration first to reduce friction?"

**VP Engineering**: "The AI Memory feature is in your Q2 plan. Our team has never built with an LLM before. What's your plan for the responsible AI review and the engineering capability gap?"

**VP Sales**: "We're losing deals because enterprise customers want SSO and admin controls, not decision logging. Why is none of that on your roadmap?"

**Board Observer**: "Notion just announced they're adding AI memory to their product. How does your strategy hold if a competitor ships this before you?"

Evaluate the learner's responses for:
- Composure and clarity under pressure
- Ability to defend with evidence (reference back to discovery, data, metrics)
- Willingness to acknowledge uncertainty and explain how they'll learn
- Strategic coherence (not changing the plan just because someone pushes back)

---

### Final Debrief — Course Completion

After Phase 6, provide a comprehensive capstone debrief:

**Performance summary by phase:**
| Phase | Skill Tested | Score (1–5) | Key Observation |
|-------|-------------|-------------|-----------------|
| Discovery | Opportunity identification, OST | | |
| Strategy | Playing to Win, Coherence Test | | |
| Metrics | NSM design, input/counter metrics | | |
| Prioritization | RICE, trade-off reasoning | | |
| Execution | PRD clarity, acceptance criteria | | |
| Stakeholders | Composure, evidence-based defense | | |

**Overall PM readiness assessment:**
Based on performance, provide one of these characterizations:
- **Ready to lead**: Strong across all phases, coherent strategy, clear communicator — ready to operate as a PM with minimal supervision
- **Nearly there**: Strong in some areas, gaps in 1–2 phases — focus on the specific gaps before taking on a new PM role
- **Growing**: Clear potential with notable gaps — recommend repeating the weaker modules with more deliberate practice

**Top 3 strengths** (with specific examples from the session)

**Top 2 growth areas** (with specific next steps)

**Course completion message:**
_"You've completed the PM Foundations Course. Across [X] modules, you've practiced every core PM skill from first principles — discovery, strategy, metrics, prioritization, execution, and stakeholder management. The Pando capstone connected them all into a coherent product lifecycle._

_PM mastery comes from application, not repetition. Take the frameworks you've practiced here into your real work. When you write your next PRD, use the 6-section structure. When you update your roadmap, attach outcomes. When you walk into a stakeholder meeting, bring evidence, not opinions._

_Your next growth frontier: [specific recommendation based on gaps identified]._

_Congratulations on completing the course."_

### Adaptive Difficulty Rules
- **Strong prior modules performance**: Skip the scaffolding within each phase; evaluate answers with a higher bar; push on strategic coherence across phases more aggressively.
- **Mixed prior performance**: Offer brief framework reminders at the start of each phase; be explicit about what's being tested.
- **First-time learner (no prior modules)**: Acknowledge the challenge; provide more context for each phase; focus on developing instincts over scoring perfection.

### Cross-References
- Prerequisites: All prior `learn-*` modules in `pm-guided-learning`
- Completion of this module marks completion of the PM Foundations Course
- For continued learning: `learn-ai-pm` (if not yet completed), skills in `pm-product-strategy`, `pm-ai-product-management`
- For real-world application: `create-prd`, `product-strategy`, `outcome-roadmap` in their respective plugins