Home Resources Working template
Working template · Decision making

A decision brief you can trace

A reusable structure for a product recommendation with source context, limits, and a clear next step.

Use in your next product reviewBy Triyan Arif Wibowo

Read and use the complete guide below. No email required. This resource is original portfolio content for a fictional product.

Inside the guide
  1. Frame the decision in one sentence.
  2. Copy this structure into your working document.
  3. A small synthetic example.
  4. Review the reasoning before polishing the prose.

Frame the decision in one sentence.

A brief is not a storage place for every note. Start with the decision the reader needs to make. State whether you are requesting more discovery, proposing an experiment, or recommending a committed change.

Write a short problem statement without embedding the solution. “Administrators cannot identify the approval owner” keeps more options open than “We need an approval dashboard.”

Copy this structure into your working document.

Replace the prompts with your own evidence. Keep the source references close to the claim they support; a long appendix alone makes review harder.

SectionWriting prompt
Decision requestedWhat should the review group decide now?
Observed problemWho was doing what, and where did they struggle?
EvidenceWhich original records support this interpretation?
Contrasting evidenceWhat does not fit the current explanation?
Scope and limitationsWho or what has not been represented?
Proposed next stepWhat is the smallest useful action and who owns it?
Revisit conditionWhen or why should this decision be reviewed?

A small synthetic example.

Decision requested: investigate whether named ownership improves assisted onboarding. Observed problem: sample interview and ticket excerpts describe waiting at a handoff without knowing who should act.

Evidence: synthetic sources AT-014 and AT-018 describe the same handoff from different channels. Contrasting evidence: AT-020 describes a successful self-service setup. The brief therefore limits its proposal to assisted onboarding.

Next step: review the handoff wording and observe another assisted setup cycle. No implementation date or expected gain is implied by the example.

Evidence supports an interpretation. It does not remove the need for product judgment.

Review the reasoning before polishing the prose.

Ask a colleague to underline every claim that depends on evidence. Can each one be traced? Then ask them to describe the strongest alternative explanation. If the brief cannot accommodate that question, it needs more context.

Keep the final decision beside the brief, including deferrals. Future readers should be able to distinguish an idea that was discussed from work that was approved.

TW
Triyan Arif WibowoPortfolio author

Design and content for this fictional Northstar AI portfolio. These practical articles describe the concept’s approach to customer evidence.

From practice to product

Explore a source-linked evidence workflow.

Explore the platform concept

Give the next decision a clearer foundation.

Explore the fictional Northstar workflow, from source to insight.

Request a concept demo