AIWorkDex
Product Practice

Record the product outcome, capacity, and exclusions

Give the team a deliberate investment boundary before detailed solution work expands.

Preparation
A short investment discussion before solution shaping.
Difficulty
Moderate
Task
Set the product investment appetite
Back to the Task: Set the product investment appetite

Before you start

Get what you need before you start

  • Bring the problem evidence, current commitments, available people, fixed dates, and obligations that cannot move.
  • Identify the person who owns the capacity decision.

Steps

Work through the method

Use the listed inputs and tools. Check the evidence when you need to verify a step.

  1. State the outcome worth investment

    Describe the product outcome, who needs it, and the evidence that makes the problem worth attention. Keep proposed features outside this statement.

    Why it matters: The team must know what result would justify spending capacity.

    Input
    The product problem, evidence, and current strategy.
    Output
    A concise product outcome and decision rationale.
    Tools in this stepGitHub

    Evidence for this step

  2. Set the capacity boundary

    Choose the maximum people, calendar window, and protected commitments available for the problem. Create a milestone that names the outcome and boundary.

    Why it matters: A visible boundary lets solution work respond to real capacity.

    Input
    Available capacity, fixed obligations, and the desired outcome.
    Output
    A named milestone with capacity, protected work, and decision owner.
    Tools in this stepGitHub

    Evidence for this step

  3. Record what the appetite excludes

    List attractive additions, protected work, and conditions that would force a new investment decision. Keep excluded items outside the milestone.

    Why it matters: The boundary fails when additions enter without showing what they displace.

    Input
    The milestone, current commitments, and proposed additions.
    Output
    An investment record with explicit exclusions and reopen triggers.
    Tools in this stepGitHub

    Evidence for this step

Success checks

Check the result before you finish

  • The outcome and maximum investment are clear.
  • Protected commitments and exclusions are visible.
  • The team knows which condition requires a new decision.

Failure modes

Watch for these problems

  • Do not present the boundary as a delivery estimate.
  • Reopen the decision when a required outcome cannot fit.
  • Escalate when a fixed legal or safety obligation conflicts with the appetite.

Tools

Choose the tools you need

Sources

Read the sources behind this practice

Check what each source supports and where the advice has limits.