Prepare steps
We have decided to hire a second project lead from January.
Your questionNew role
Planned: the decision turns into a list of steps, each with its product, content and reason.
Planned This capability is specified but not built yet. The page shows the plan with fictional examples. Available today: Today brief, Top 3, decisions with memory, goals, roadmap and scenarios.
Peak Command · Prepared actions · planned
Prepared by Command.
Carried out only after your approval.
Planned: for a decision, Command is meant to prepare the follow-up steps, such as tasks in Peak Work or a change in Peak Year, and carry them out in the owning product only after your approval. Steps with an external effect are meant to need an approval of their own. Today Command writes decisions, initiatives and tasks one at a time through the owning product.
Planned feature · fixed examples · nothing is carried out
CONTEXT BEFORE DECISIONYour question.
Your question.
A path you can follow.
02 / The visible path3 example steps
New role
Why: A hire affects plan, capacity and budget. The steps are meant to be prepared together so none is forgotten.
- 01Planned: record the decision with its reason in Peak Log
- 02Planned: task “Write the role profile” in Peak Work, owner: you
- 03Planned: note capacity from January in Peak Plan as an assumption
02 / How it is meant to work
Prepare. Check. Approve.
A decision often brings several steps with it. They are meant to be prepared together and traceable one by one.
02 / Visible path
Check one by one
- 01Example step
Planned: record the decision with its reason in Peak Log
- 02Example step
Planned: task “Write the role profile” in Peak Work, owner: you
- 03Example step
Planned: note capacity from January in Peak Plan as an assumption
Approve and keep a record
Planned: only after your approval does the owning product carry out the steps; each is visible in the history afterwards.
Your review is still open.
These marks decide nothing.Situation and decision stay separate
Planned means: not here yet.
Preparing actions is planned
Follow-up steps prepared as a bundle are planned. Nothing is ever carried out without approval, and steps with an external effect are meant to need an additional approval.
Your question→Fixed rule→Example steps
The sculpture illustrates the flow. It is not a product interface.
The sculpture illustrates the flow. It is not a product interface.Usable in Command today
Today Command writes a decision to Peak Log, an initiative to Peak Year and a task to Peak Work, each triggered by you.
- Status
- Planned, not available yet
- Today
- Brief, top 3 and decisions usable
No date promised
We do not say here when the feature arrives. We name it once it is provably available.
ProposalExecution
The next step
Today: prepare decisions well.
See how Command already keeps candidates with reasons, scenarios and decision reviews together today.
View decision preparationPeak Command · Prepared actions · plannedWhat has been decided?
Planned feature · fixed examples · nothing is carried out
Frequently asked questions
Can I use prepared actions yet?
No. It is planned and no date is promised. Today Peak Command shows the daily brief, top 3, decisions, goals, initiatives and scenarios from the Peak products.
Will Peak Command run actions on its own?
No. Planned or not: Command prepares, you check and approve. Risky steps are meant to need explicit approval.
What works today?
Today you record decisions in Command and create tasks in Peak Work, both yourself and with your confirmation.
Does Peak Command store data of its own?
No. Peak Command owns no data. It reads the Peak products with your permissions and writes only through the owning product, such as decisions in Peak Log.