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.
- Steps
- 3
- Difficulty
- Moderate
- Task
- Set the product investment appetite
Requires: Bring the problem evidence, current commitments, available people, fixed dates, and obligations that cannot move. Identify the person who owns the capacity decision.
Uses: GitHub
Back to the Task: Set the product investment appetiteBefore you start
Prepare
- 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.
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.
Step details and sources
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 stepGitHubEvidence for this step
Basecamp describes setting an investment appetite before detailed solution work and varying scope within that boundary.
Basecamp: Setting the appetite; Fixed time, variable scopeThis is one software company’s method. Its cycle lengths do not transfer as a default.
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.
Step details and sources
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 stepGitHubEvidence for this step
Basecamp describes setting an investment appetite before detailed solution work and varying scope within that boundary.
Basecamp: Setting the appetite; Fixed time, variable scopeThis is one software company’s method. Its cycle lengths do not transfer as a default.A GitHub milestone can group selected issues and pull requests under a named description and track their completion.
GitHub Docs: Creating a milestone, steps 3–5A milestone records the selected boundary. It does not set capacity or preserve exclusions by itself.
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.
Step details and sources
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 stepGitHubEvidence for this step
Basecamp describes setting an investment appetite before detailed solution work and varying scope within that boundary.
Basecamp: Setting the appetite; Fixed time, variable scopeThis is one software company’s method. Its cycle lengths do not transfer as a default.A GitHub milestone can group selected issues and pull requests under a named description and track their completion.
GitHub Docs: Creating a milestone, steps 3–5A milestone records the selected boundary. It does not set capacity or preserve exclusions by itself.
Success checks
Check the result
- The outcome and maximum investment are clear.
- Protected commitments and exclusions are visible.
- The team knows which condition requires a new decision.
Failure modes
What could go wrong
- 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 tools
GitHub
An issue workspace for recording a software release boundary, milestone, and known dependencies.
Check fit, limits and pricingSources
Check the sources
Check what each source supports and where the advice has limits.
- Basecamp: Set BoundariesPractitioner method documentation · Publication date unavailable
- Hacker News: Ask HN: Co-founder is addicted to new featuresFirst-hand founder and practitioner discussion · Published 16 September 2020
- GitHub Docs: Creating and editing milestones for issues and pull requestsOfficial product documentation · Publication date unavailable