Skip to content
Peak Atlas

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

Where did things stand then,
and what has changed since?

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 memory

Planned feature · fictional example · not a product capture

EXAMPLE / PREVIEW

One situation.
The fitting consequence.

Peak Command / ExampleLOCAL EXAMPLE

01 / Example value

How much history is there in Peak One?

02 / What Command showsPlanned: “Goals before 1 June not recorded.” The look back starts where the data starts.

Gap visible · then the comparison from the first date

Change the example value. The view follows the rule.
Fictional data · nothing saved

One question. Two situations.
The situation
decides what comes first.
Compare both cases below ↓

Two example values

How much history is there in Peak One?

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.

3/ 10Little
See the gap firstEXAMPLE CASE
Planned: “Goals before 1 June not recorded.” The look back starts where the data starts.
Then

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

9/ 10A year
Then next to nowEXAMPLE CASE
Planned: the state on 1 April next to today. In between: two decisions, one with a recorded outcome.

Comparison with decisions · what made the difference?

Trust needs clarity

Planned means: not here yet.

01 / The existing evidence

The time machine is planned

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.

Peak Command / Example casesEXAMPLE
  1. 3/10
    Planned: “Goals before 1 June not recorded.” The look back starts where the data starts.Gap visible · then the comparison from the first date
  2. 9/10
    Planned: the state on 1 April next to today. In between: two decisions, one with a recorded outcome.Comparison with decisions · what made the difference?

02 / Your check

Usable in Command today

Decision memory finds earlier decisions with reason and outcome; the roadmap shows plan, forecast and reality.

4 / 1010 / 10

Compare both cases and their rule.

03 / The clear limit

No date promised

We do not say here when the feature arrives. We name it once it is provably available.

ExampleNothing decided

The next step

Today: memory for decisions.

See how you already find earlier decisions, their reasons and their outcomes today.

View decision memory
Peak Command · Time machine · plannedThe reference date.

Planned feature · fictional example · not a product capture

Frequently asked questions

Can I use the time machine 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.

What can I trace today?

Decisions with reasoning in Peak Log and the history of your objects. The decision memory in Command searches them.

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.