Product work is a sequence of cuts

1758. Lesson identity

Module

4.10 — Product management

Lesson

Product work is a sequence of cuts

Academic type

Systems

Order

1

Estimated time

35–45 minutes, including practice

1759. Learning objective

After this lesson, you can rank a constrained backlog using value, risk, dependency, cost, and scope boundaries, then defend the ordering with explicit trade-offs.

1760. Why this matters

A backlog is not a promise to build everything. It is a set of competing claims on limited attention, implementation time, and testing capacity. Without an explicit ordering, the loudest request or most attractive idea tends to become the next task. Product judgment means deciding what earns capacity now, what must wait, and what should be cut.

An AI assistant can compare options, expose possible dependencies, and challenge assumptions, but it cannot supply missing evidence or own the final product boundary. State the objective, constraints, and decision rule before asking for assistance. Treat AI output as a proposal to inspect, not as evidence or an automatic priority order.

1761. Prior knowledge

You should be able to describe a product request, separate a desired outcome from a proposed feature, and distinguish available evidence from an assumption that still needs validation. No particular tool or project file is required.

1762. Core concept

Product prioritization is a sequence of cuts. Each cut asks whether an item has sufficient value, reduces an important risk, has ready dependencies, has an acceptable cost, and fits the current scope boundary. The learner—not a score, stakeholder volume, or AI suggestion—must make the final comparison and explain why selected work deserves capacity before the alternatives.

A priority is not a permanent ranking. It is a decision for a particular work window under particular constraints.

1763. Mental model: the FIVE FILTERS

After applying the filters, make the final cut: choose the smallest set that supports the objective while reserving enough capacity for integration, validation, and correction. A high-value item can wait if a dependency is missing. A lower-visibility item can move earlier if it resolves a major risk. An easy task is not automatically a priority.

A defensible ordering states:

1. The current objective and capacity boundary.
2. The selected items and their order.
3. The cut line separating selected, deferred, and removed work.
4. The risk and consequence attached to each deferred item.
5. A concrete trigger that would reopen each deferred decision.
6. The evidence and assumptions supporting the material judgments.

1764. Evidence versus assumption

Label a judgment EVIDENCE when it comes from an observed result, stated constraint, existing requirement, or verified dependency. Label it ASSUMPTION when it is an estimate, prediction, interpretation, or untested belief.

A score does not turn an assumption into evidence. If support is missing, preserve the uncertainty instead of presenting the judgment as fact.

1765. Concrete example

Assume the work window has capacity for one medium item and one small item.

A defensible order selects the first-time objective clarification, then the failure-message improvement. Cosmetic variants are deferred because they serve the current objective less directly. The inventory category is deferred because its dependency is unresolved and its cost exceeds the remaining boundary.

The ranking could change if the objective changed. That would not make the original decision wrong; it would mean the decision context had changed.

1766. Common mistakes

• Treating stakeholder volume, apparent popularity, or an AI suggestion as sufficient evidence.
• Filling all capacity with feature work and leaving no room for validation or correction.
• Hiding unresolved dependencies inside a numerical score.
• Deferring an item without naming the consequence or a concrete reopen trigger.
• Calling an item “out of scope” without relating that exclusion to the current objective and boundary.

1767. Guided practice

Use the worksheet below. The current objective is make the existing core interaction easier to evaluate. The work window has capacity for two small items or one large item plus validation.

Preformatted prioritization worksheet

Use EVIDENCE or ASSUMPTION in every basis column. Keep entries concise.

Complete the worksheet, then:

1. Draw a visible cut line between selected and deferred or removed work.
2. State how much capacity the selected work uses and what capacity remains for validation.
3. Defend the first two choices in two to four sentences. Cite at least one labeled evidence entry and identify any assumption that materially affects the order.
4. State what is explicitly excluded from the current scope.
5. For every deferred item, record the risk carried, the consequence of waiting, and a specific reopen trigger.
6. Name one condition that could change the overall ordering.

Do not rank an item merely because it appears easy. Explain how it serves the objective or reduces a meaningful risk.

1768. Practical assessment

Submit the completed worksheet and decision defense through Practical assessment: Defend a constrained backlog cut. The assessment evaluates objective alignment, dependency awareness, capacity discipline, evidence-versus-assumption labeling, explicit exclusions, deferred risks, and coherent reopen triggers. The quiz remains a secondary check of the lesson vocabulary and mental model.

1769. Validation

Another developer should be able to reconstruct your decision, identify what entered and left the work window, distinguish evidence from assumptions, see which risks remain open, and know what observable conditions would justify reconsideration.

1770. Key takeaways

• A backlog is a set of competing claims on limited capacity, not a commitment to build everything.
• Prioritization combines value, risk, dependency, cost, and scope.
• A visible cut line is part of the decision, not an omission.
• Deferred work needs a stated consequence and a concrete reopen trigger.
• A ranking is defensible when its evidence, assumptions, exclusions, capacity effects, and change conditions are explicit.

1771. Next lesson

Continue with 4.10 L2 — Record the trade-off, where you will document the reasoning behind a product decision.

1772. Knowledge check