Read
What do I need to decide this week, and why?
Your questionThis week's decisions
Command reads the Peak products with your permissions. What you may not see there, you do not see here either.
Peak Command · How it works
From your question
to a situation with a source.
Command reads Peak Goals, Year, Work, Plan, Finance, Radar and Constraints, orders them by visible rules and shows what a decision needs. Writing always happens in the product that owns the thing.
Rule-based · fixed examples on this page · no model call
CONTEXT BEFORE DECISIONYour question.
Your question.
A path you can follow.
02 / The visible path3 example steps
This week's decisions
Why: A decision needs context. Command shows every candidate with the reason it is due right now.
- 01Sources: decision candidates, initiatives from Peak Year, capacity from Peak Plan
- 02Rule: deadline, goals affected, how many initiatives depend on it
- 03Result: candidates with a reason; nothing is decided automatically
02 / Read, order, write back
Command reads. The specialist product writes.
That way every task, goal and decision exists exactly once in Peak One.
02 / Visible path
Order
- 01Example step
Sources: decision candidates, initiatives from Peak Year, capacity from Peak Plan
- 02Example step
Rule: deadline, goals affected, how many initiatives depend on it
- 03Example step
Result: candidates with a reason; nothing is decided automatically
Write back
A decision goes to Peak Log, an initiative to Peak Year, a task to Peak Work.
Your review is still open.
These marks decide nothing.Situation and decision stay separate
What happens in the background, and what does not.
No language model in the situation
Brief and ranking are rules, not generated text. The preview here uses fixed examples.
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.Scenarios change nothing
A “what if” calculates with Peak Finance and Peak Year. It is only applied in the owning product.
- Basis
- Rules and sources, no language model
- Permissions
- Inherited from Peak One
Not connected stays visible
If a product is not connected, Command shows “not available” instead of a zero.
SituationDecision
The next step
Open Command with your data.
Sign in to Peak One. Command then shows the situation from the products you already use.
Sign in to Peak OnePeak Command · How it worksFrom Peak One.
Rule-based · fixed examples on this page · no model call
Frequently asked questions
What happens when I open Peak Command?
Command reads Radar, bottleneck, goals, plan and decisions afresh and composes the daily brief, top 3 and tensions from them. None of it is stored.
Does everyone see the same thing?
No. Command reads with the permissions of the signed-in person. What someone may not see in a product, they do not see in Command either.
Does Peak Command act without me?
No. Peak Command suggests and prepares. A decision, a task or a scenario only takes effect when you confirm it in the owning product.
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.