Planned: the state on 1 April next to today. In between: two decisions, one with a recorded outcome.
Gap visible · then the comparison from the first date
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 · Time machine · planned
Planned: you are meant to call up the situation on an earlier day, such as the start of the quarter, and lay it next to today: goals, plan, bottleneck and the decisions in between. Today you find earlier decisions with reason and outcome in decision memory.
View decision memoryPlanned feature · fictional example · not a product capture
01 / Example value
How much history is there in Peak One?
Gap visible · then the comparison from the first date
Change the example value. The view follows the rule.
Fictional data · nothing saved
Two example values
Schematic example on a scale from 0 (no history) to 10 (a whole year). This is how the feature is meant to work; it is not available yet.
Planned: the state on 1 April next to today. In between: two decisions, one with a recorded outcome.
Gap visible · then the comparison from the first date
Comparison with decisions · what made the difference?
Trust needs clarity
01 / The existing evidence
Calling up the state of an earlier day is planned and not possible today. A look back is never meant to invent data that did not exist then.
02 / Your check
Decision memory finds earlier decisions with reason and outcome; the roadmap shows plan, forecast and reality.
Compare both cases and their rule.
03 / The clear limit
We do not say here when the feature arrives. We name it once it is provably available.
The next step
See how you already find earlier decisions, their reasons and their outcomes today.
View decision memoryPlanned feature · fictional example · not a product capture
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.
Decisions with reasoning in Peak Log and the history of your objects. The decision memory in Command searches them.
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.