One-Pager Draft

Team 8 (Bumblebees): Alexis Tuchinda · Christian Roy · Efrain Angon-Cruz · Natnael Tadesse

Description: What is it?

Product Hub is one place where stakeholder feedback comes in, gets checked against the agreed scope, and goes to the person who owns that work. A PM sets up a project with requirements and owners. Stakeholders submit feedback in plain language. AI flags feedback that conflicts with the scope, explains why, and suggests an owner for the PM to confirm.

Problem: What problem is this solving?

Feedback often arrives after engineers and designers have started building, and it is spread across Slack, meetings, PRDs, and Jira. None of these connect a new comment to the requirement it changes or to the person building it, so scope shifts mid-build and teams redo work. Jira, Notion, and Glean each hold part of the picture, but none of them sends feedback to the person who owns the work.

Why: How do we know this is a real problem and worth solving?

In 8 PM interviews, 3 told specific stories of losing work to late scope changes: one had a week of design work thrown out, one had a stakeholder add requirements mid-build after reviewing them up front, and one had the last part of a project sent back over design standards nobody had shared. Their usual fix, stakeholder review before work starts, didn’t prevent it.

Market: about 1.5M PMs worldwide (TAM), 562.5K who likely face this problem based on our 3 of 8 rate (SAM), and 5,625 as a first 1% target (SOM). These are early estimates from a small sample.

Success: How do we know if we’ve solved this problem?

  • Fewer review cycles and less redone work per project, compared with the team’s own baseline.
  • Routing accuracy: the share of feedback that reaches the right owner, measured with a “report a wrong route” button.
  • Adoption: at least 70% of invited users complete a core workflow, most come back on their own, and several team members contribute.
  • Guardrails: we don’t count every routed comment as a win, and teams should not feel watched.

Audience: Who are we building for?

Execution-focused PMs who run engineering and design teams on cross-functional projects with changing requirements and frequent stakeholder feedback. Engineers and designers are secondary users: they get notified and feel the cost of late changes most. Stakeholders are the ones submitting feedback.

What: Roughly, what does this look like in the product?

Release 1 (the MVP from our story map):

  • Project setup with requirements, team roles, and an owner for each requirement
  • Stakeholders submit feedback in plain language and confirm which requirement it affects
  • AI scope check that flags conflicts and explains why (this absorbed our earlier Drift Watch idea)
  • AI-suggested owner that the PM confirms or changes
  • Notification to the engineer or designer with the feedback and the affected requirement
  • A “report a wrong route” button

Release 2 adds progress tracking, grouped feedback, and AI next steps. Prototype: cs177-team-bumblebees.vercel.app

How: What is the experiment plan?

We’re testing our riskiest assumptions first: that teams will adopt another tool, keep requirements and feedback documented, and not feel watched.

  • Routing test: run one PM’s real scope, roles, and feedback through the system and check if each item reaches the right owner.
  • Diary study: PMs and team members log how they handle requirements and feedback for a week. We’re right if they already document consistently.
  • Alignment test: teams run a simulated project with and without the dashboard. We’re right if teams with it agree faster with fewer conflicts.
  • Prototype pilot: teams use v0 on a real or simulated project. We’re right if at least 70% complete a core workflow and most return on their own.

When: When does it ship and what are the milestones?

Done: interviews (Weeks 1-2), problem choice and pitch (Weeks 3-4), story map (Week 5), v0 prototype (Week 6), test cards (Week 7).

Next: run the four tests, fix routing, then ship Release 1 to pilot teams. Release 2 follows once routing accuracy holds up.

Reading: Lenny’s template roundup highlights Steve Morin’s 1-pager for its focus on success criteria and risks. We used that in Success, where we pair our metrics with guardrails, and in How, where we test our riskiest assumptions first.

Avatar

About the author

Leave a Reply