Product

Start with the product decision that is consuming scarce time or capacity, then preserve the assumptions, trade-offs, and evidence behind it.

Jobs to finish

What is getting stuck in Product?

“This is costing me scarce engineering capacity while several concepts still look plausible.”

Several plausible concepts are competing for scarce product and engineering effort after the problem research is complete.

Expected result: Advance one concept with its evidence and unresolved assumption recorded. Keep the reasons for rejecting the others.
Available Practice: One complete method

“This is costing me delivery time while the first release remains too broad or too incomplete to use.”

The proposed first release exceeds the team’s capacity, yet removing more work could leave the core user path incomplete.

Expected result: Set a reviewable boundary around one complete use case and state every material exclusion and consequence.
Available Practice: One complete method

“This is costing me team capacity while an unbounded idea keeps absorbing more work.”

A raw product idea is expanding before the team has decided how much capacity the problem deserves.

Expected result: Set the maximum investment, the outcome worth that investment, and the work that stays outside the boundary.
Available Practice: One complete method

“This could consume scarce team capacity if a critical assumption fails after commitment.”

A shaped solution looks coherent, but an unresolved design, technical, contractual, or regulatory dependency could invalidate it.

Expected result: Answer, isolate, or stop for each critical dependency before the build receives commitment.
Available Practice: One complete method

“This is costing me decision time while reviewers reconstruct the product case from scattered material.”

The product concept lives in conversations and sketches while reviewers need one shared basis for a resource decision.

Expected result: Give every reviewer the same concise product bet and preserve the resulting decision and conditions.
Available Practice: One complete method

“This is costing me delivery focus while urgent requests repeatedly displace existing commitments.”

New requests compete with work already in progress, while every item is described as urgent.

Expected result: Choose a short ordered commitment and show its intended outcome, evidence, trade-offs, and displaced work.
Available Practice: One complete method

“This is costing me product capacity while one requested implementation is treated as the only answer.”

A proposed implementation is being treated as the requirement before the underlying workflow failure is clear.

Expected result: Record a build, defer, decline, or research decision tied to the evidenced workflow problem.
Available Practice: One complete method

“This is costing me analysis time while the release still lacks evidence for a clear product decision.”

The team can ship the change, but it cannot yet tell whether the intended product outcome improved or regressed.

Expected result: Define the intended outcome, baseline, observable measure, decision window, and guardrail before release.
Available Practice: One complete method

“This is costing me release confidence because one failure could reach every user before the team can respond.”

A change is ready for real use, while broad exposure could reveal a product or operational problem too late.

Expected result: Choose the initial audience, stages, health signals, owner, and stop or rollback response before exposure grows.
Available Practice: One complete method

“This is costing me maintenance capacity while the feature’s present value and removal risk remain unclear.”

A shipped feature shows weak use while it still adds maintenance, support, and future product constraints.

Expected result: Choose to keep, simplify, retire, or investigate the feature with user dependency and removal risk visible.
Available Practice: One complete method