Write and review one product investment brief
Give decision makers one concise, evidence-linked product bet and preserve their decision.
- Preparation
- A drafting session followed by an asynchronous or live decision review.
- Difficulty
- Moderate
- Task
- Write an investment-ready product brief
Before you start
Get what you need before you start
- Bring the product problem, evidence, appetite, shaped solution, feasibility findings, and decision owner.
- Confirm where sensitive research can be linked safely.
Steps
Work through the method
Use the listed inputs and tools. Check the evidence when you need to verify a step.
Draft the product bet
Create a Confluence page from an approved template. Record the problem, evidence links, investment appetite, solution outline, critical risks, exclusions, and open questions.
Why it matters: A shared brief lets reviewers assess the same product decision.
- Input
- The research finding, appetite, shaped solution, and feasibility review.
- Output
- A concise product investment brief with source links.
Tools in this stepConfluenceEvidence for this step
Basecamp’s pitch method records the problem, appetite, solution, risks, and excluded work for a product investment decision.
Basecamp: The purpose of the pitch; ingredients 1–5; Ready to presentConfluence can preview and apply a selected template when creating a page.
Atlassian Support: Opening instructions; template browserConfluence can aggregate recorded decisions with the Decision report macro.
Atlassian Support: Opening description; Add this macro to your page or live doc
Review evidence and missing decisions
Ask reviewers to mark unsupported claims, conflicting assumptions, missing owners, and conditions for proceeding. Revise the brief without hiding unresolved disagreement.
Why it matters: The brief supports a decision only when its limits remain visible.
- Input
- The draft brief and reviewer comments.
- Output
- A reviewed brief with corrections, open questions, and decision conditions.
Tools in this stepConfluenceEvidence for this step
Basecamp’s pitch method records the problem, appetite, solution, risks, and excluded work for a product investment decision.
Basecamp: The purpose of the pitch; ingredients 1–5; Ready to present
Record the decision and conditions
Record proceed, revise, or stop, the decision maker, date, conditions, follow-up owner, and next review trigger. Add a Decision report where the team needs a cross-space view.
Why it matters: A retrievable decision prevents later work from relying on memory or an outdated draft.
- Input
- The reviewed brief and authorised decision.
- Output
- A dated product decision linked to its brief and conditions.
Tools in this stepConfluenceEvidence for this step
Confluence can aggregate recorded decisions with the Decision report macro.
Atlassian Support: Opening description; Add this macro to your page or live doc
Success checks
Check the result before you finish
- The brief contains problem evidence, appetite, solution, risks, and exclusions.
- Unsupported claims and disagreement remain visible.
- The authorised decision and its conditions are retrievable.
Failure modes
Watch for these problems
- Pause when no authorised decision owner exists.
- Return to feasibility work when a critical dependency lacks review.
- Keep sensitive customer evidence in its approved system and link only what reviewers may access.
Tools
Choose the tools you need
Tool
Confluence
A shared document workspace for structuring a product brief and retrieving recorded decisions.
Check fit, limits and pricingSources
Read the sources behind this practice
Check what each source supports and where the advice has limits.
- Basecamp: Write the PitchPractitioner method documentation · Publication date unavailable
- Atlassian Support: Create a page from a templateOfficial product documentation · Publication date unavailable
- Atlassian Support: Insert the decision report macroOfficial product documentation · Publication date unavailable