Peak Command · Guide · First decision
Your first management decision
recorded properly.
A guide to one decision from question to review: options, criteria, reason and review date. Put together the questions for your first decision here.
Which decision do you want to make properly first?
2 questions in the plan. First question: What is the question in one sentence, with a date?
One decision at a glance
Question. Options. Decision.
What is the question in one sentence, with a date?
A good first decision is small but complete.
Don't pick a strategy question for the whole year. Pick a question with consequences in the coming weeks, such as a hire, a delay or a budget. In Peak Command, decision cards show candidates from your goals, your capacity and your plan. You record the decision there; it is saved in Peak Log and comes back on the review date.
From reading to doing
Your decision questions. For the first card.
The next decision.
2 questions selected
- What is the question in one sentence, with a date?
“By 15 Nov: do we hire a second designer?”
- Which two or three options really exist?
Always write down “change nothing” and name what it costs.
What a first
decision needs.
A clear question, at least two real options, one criterion you can be measured against later, and a day on which you look back.
What is the question in one sentence, with a date?
“By 15 Nov: do we hire a second designer?”
Two real options“Change nothing” counts as an option. A question with one answer isn't one.
One criterionHow will you know in eight weeks whether it was right?
A review dateWithout a date, a decision quickly turns into a guess.
The playbook
From question to reviewed decision.
Ask, weigh,
record.
Question → Options → Decision → Review
- 01
Derive the question from the numbers.
Start from a tension: plan, capacity and goals don't fit together. Peak Command shows such tensions on Today. Turn it into exactly one question.
Example · Nordwind Studio (fictional)Design plans 205 hours a week, 160 are available.
Question: hire a second designer or stop two initiatives? - 02
Describe options by their consequences.
For each option, write down what it costs, what it brings and what it delays. Use the same units: euros, hours, weeks. A scenario in Command helps, but changes nothing until you apply it in the owning product.
Make options comparable
“Hire: about €5,200 a month. Stop: 2 client projects later.”“Hiring is expensive.” - 03
Record it and set a review date.
Record the decision with its reason, criterion and review date. In Peak Command it is saved in Peak Log. Tasks that follow from it are created in Peak Work, not in Command.
Check before savingReason, criterion and review date in place?
Yes → record. No → complete it.
Your quality check
Is your decision ready?
Tick what you have checked. Your selection stays in this view only.
0 of 4 points checked
What this article is based on.
Editorial guide with a fictional example and made-up numbers. Decision cards, recording to Peak Log, reviews and scenarios exist in Peak Command today; scenarios change nothing until they are applied in the owning product.
- Evidence pending
Editorial guide with fictional companies and numbers. No customer data, no measured values, no customer results.
See how decisions come together in Command.
The decision intelligence page shows cards, candidates and memory in detail.
Frequently asked questions
Which decision is a good start?
One that stalls without you and whose effect you can check within a few weeks.
Do I need Peak Command for this?
No. The method also works on paper. Peak Command records the decision in Peak Log and keeps the review in view.
What belongs in a recorded decision?
What was decided, why, who owns it, by when and how you will know whether it worked.