Skip to content

07-prioritization-stack.md

Latest commit

 

History

History
93 lines (56 loc) · 3.42 KB

07-prioritization-stack.md

File metadata and controls

93 lines (56 loc) · 3.42 KB
Raw

Example 07 — Prioritization Stack

Scenario

A PM has more requests than the team can absorb and needs a defendable ranking.

Input

"We have room for only 3 items next quarter: conversation history search, AI answer quality tuning, enterprise admin audit logs, onboarding simplification, team workspace sharing, growth referral flow, and export improvements. Help me prioritize them and explain what should wait."

What good output looks like

A strong pm-workbench response should:

  • anchor on the period objective before ranking items
  • reflect impact, effort, dependencies, and commitments
  • clearly identify what is above and below the line
  • help the PM explain why some work is intentionally not prioritized now

Expected output shape

Prioritization Stack

Example target output

Prioritization Stack

1. Period objective

Next quarter should optimize for activation and trust in the core product, while preserving the minimum enterprise credibility needed for active deals.

2. Constraints

  • Capacity only supports 3 meaningful priorities.
  • CEO wants growth, but growth will be inefficient if activation and core trust remain weak.
  • Sales needs enough enterprise readiness to keep serious deals moving.
  • Support is already seeing onboarding confusion.

3. Prioritization logic

The stack favors work that:

  • reduces immediate user friction
  • strengthens the product's core AI promise
  • prevents enterprise credibility from blocking near-term revenue
  • avoids amplifying a leaky product with premature growth loops

4. Recommended stack

P0 / Must-do

  1. Onboarding simplification This is the fastest path to reducing first-use friction and support drag.

  2. AI answer quality tuning This protects the core product promise. Growth on weak answer quality will be fragile.

  3. Enterprise admin audit logs This supports enterprise credibility for active sales conversations without turning the quarter into a full enterprise roadmap.

P1 / Strong candidates

  • Conversation history search Useful for retention and depth, but less urgent than activation and core answer quality.

  • Team workspace sharing Strategically valuable, but likely stronger after the core first-use and trust problems are tighter.

P2 / Not now

  • Growth referral flow Below the line because referral growth can amplify a weak activation experience.

  • Export improvements Useful, but not as central to the quarter objective as activation, answer quality, or enterprise credibility.

5. Deferred items and why

The below-the-line work is not a forever no. It is a current-period no because the scarcest resource is focused execution. The quarter should not split itself across growth amplification, collaboration depth, enterprise maturity, and core quality all at once.

6. Risks and sequencing notes

  • If enterprise audit logs expand into broader admin controls, the top 3 may no longer fit.
  • If answer quality issues are deeper than tuning, that lane may need more capacity.
  • If onboarding data shows friction is not the main activation bottleneck, the stack should be revisited.

7. Immediate planning next step

Confirm the quarter objective with leadership, then scope each P0 item tightly enough that the team can defend what is in and out of the quarter.

Why this is useful

Prioritization is where PM judgment becomes visible. A good stack makes trade-offs defendable instead of political.