01 / Evidence fileExample: deliver the project in-house
Option A
GoalFull control
Example: the team knows the client and can steer at any time.
How well does the option reach the actual goal?
Peak Docs · Decision memosSample data · No real decision
Not the loudest opinion.The reasoned decision.
Many decisions are made in a meeting and forgotten a week later. Here you weigh two sample options with the same questions and see how that becomes a memo with follow-up tasks.
What decides it for you?
How well does the option reach the actual goal?
A decision that holds
Why this option, and what follows?
Two options. The same questions. A decision with a visible reason.
01 / Your first perspectiveOption AExample: deliver the project in-house
02 / Your second perspectiveOption BExample: hire a partner
01 / The basis for deciding
Two options. The same questions.
Pick a focus. Each row asks both sample options the same question. The values are made up and marked as an example.
4 dimensions · Same standard for both options
02 / Evidence fileExample: hire a partner
Option B
GoalFast start
Example: the partner has delivered similar projects before.
How well does the option reach the actual goal?
| The criterion | Option A | Option B |
|---|---|---|
| GoalHow well does the option reach the actual goal? | Option AFull control Example: the team knows the client and can steer at any time. Demo exampleFictional sample data. No real companies, no real numbers, nothing is saved or sent. Sample data on this page | Option BFast start Example: the partner has delivered similar projects before. Demo exampleFictional sample data. No real companies, no real numbers, nothing is saved or sent. Sample data on this page |
| CapacityWho carries the work, and is there enough time? | Option ATeam at capacity Example: two people would have to move other tasks. Demo exampleFictional sample data. No real companies, no real numbers, nothing is saved or sent. Sample data on this page | Option BCoordination needed Example: plan a weekly check-in with the partner. Demo exampleFictional sample data. No real companies, no real numbers, nothing is saved or sent. Sample data on this page |
| RiskWhat can go wrong, and how early would we notice? | Option ADelay Example: without capacity the date slips. Demo exampleFictional sample data. No real companies, no real numbers, nothing is saved or sent. Sample data on this page | Option BDependency Example: the knowledge stays with the partner afterwards. Demo exampleFictional sample data. No real companies, no real numbers, nothing is saved or sent. Sample data on this page |
| ReversibilityHow easily can the decision be changed later? | Option AEasily Example: in-house work can be replanned at any time. Demo exampleFictional sample data. No real companies, no real numbers, nothing is saved or sent. Sample data on this page | Option BWith lead time Example: a contract has a term. Demo exampleFictional sample data. No real companies, no real numbers, nothing is saved or sent. Sample data on this page |
Transparency is part of the comparison.
Source code is evidence of implementation. It does not replace a current live test.
Our standard
No shortcut.Reasons that last.
A good memo shows options, reasons and what is still open. In Peak Docs you record the decision in the decision block.
Traceable decisions
Whoever asks later finds the answer.
Options, reasons and open points live in the same document.
- 01
Same questions
Both options are looked at with the same criteria.
- 02
Reason before result
The decision states why it was made.
- 03
Unknown stays unknown
If information is missing, it appears as an open question.
02 / From feature to moment
Test it with a real decision.
Pick a check and run it with a decision from your work.
Where do you want to start?
Take a decision that is coming up and ask both options the same questions.
Your checkFor both options
The same task
The two options
Write down the two most serious options in one sentence each.
What you check
Everyone on the team understands what is being decided.
Backed by code
Features marked “built” or “partial” in the Peak Docs requirement register. A register doesn't replace your own test in your workspace.
Source checked:
Peak-Admin/peak-one@5f93511 · docs/prd/peak-docs-prd.md (requirement register)Task selected. No test run.
See the steps03 / Before the next step
From the memo to delivery.
In Peak Docs you write the memo with a decision block. Checklist items become tasks; comments can be assigned and resolved.
- 01Write down options and reasons
- 02Record the decision in the decision block
- 03Turn checklist items into tasks
Switching is a separate decision. Prepare it and keep the open evidence in view.
From choice to delivery
Decided means: next steps clear.
Checklists become tasks with owners.
The next sensible step
Your next decision deserves a memo.
Start Peak Docs and record your decision with reasons and follow-up tasks.
Start Peak DocsThe options on this page are made up. Decision block, checklist item to task, comments and versions per the Peak Docs register.
Memory for the team
One decision. One place.
Versions show how the memo evolved.
Frequently asked questions
How do I record a decision?
With the decision block in the document. It sits visibly next to the options and their reasoning.
What happens to open points?
You turn a checklist item or a comment into a task with one click, linked back to the document.
Can I see how the memo changed?
Yes. Versions show the differences and can be restored.