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 · outcome missions · planned

An outcome instead of a list.
A mission is meant to tie goal, work and decision together.

Planned: from an outcome you want to reach, Peak Command is meant to propose a mission that holds goal, initiatives, tasks and open decisions together. There are no missions today.

Open the interactive demo

Planned feature · example mapping · no connection

Peak GoalsYour outcome
Mission (planned)Part of the mission
Mission (planned) · Example mapping
One mapping in detail
01 / Peak GoalsOutcome
02 / Fictional test valueExample: 20 new retailers by March
03 / Mission (planned)Mission goal

A readable path as an example. No transfer.

View all 5 mappings
Example mapping with fictional values.
Peak GoalsPlace in Mission (planned)
OutcomeMission goal
GoalMeasure
InitiativePart
TaskNext step
DecisionOpen
Example mapping
No transfer
This connection is planned. Nothing is connected or transferred on this page.
One concrete target

How it is meant to work.

Mission (planned)Place in Peak CommandPlanned

The mapping shows a planned connection. It is an example, not a live connection.

02 / How it is meant to work

Outcome. Proposal. Your approval.

A mission is not meant to invent anything new but to connect what already exists in Peak One.

  1. 01 / The outcome

    Name the outcome

    Planned: you state the outcome, for example “20 new retailers by March”.

    What you want to reach.NumberDateOwner
  2. 02 / The parts

    Propose the parts

    Planned: Peak Command is meant to propose fitting goals, initiatives and tasks, each with its source.

    What already exists.GoalsInitiativesTasks
  3. 03 / The approval

    Decide yourself

    You decide what belongs. Writes go only through the owning product.

    You decide.ScopeOrderEnd

Trust needs clarity

Planned means: not here yet.

01 / The existing evidence

This connection is planned

Peak Command has no missions yet. This page creates nothing and connects nothing.

Source / Peak CommandEXAMPLE
Peak GoalsMappingMission (planned)
Mapping
Example
Arrival
Planned

02 / Your check

Built today

Today Peak Command links goals from Peak Goals with initiatives from Peak Year and shows which goals have no initiative.

Account
Not connected here
Status
Not available yet

03 / The clear limit

No date promised

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

  • Adapter
  • Webhook
  • Embed
  • Planned

The next step

Look at coverage today.

The interactive demo shows how Peak Command already brings goals, initiatives and the top 3 together today.

Open the interactive demo
Your mappingPLANNED
Peak Goals→Mission (planned)
Outcome → Mission goal

Until then you use what Peak Command already reads today.

Frequently asked questions

Can I use outcome missions 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 does Peak Command show about goals today?

Goals from Peak Goals with check-ins, which goals are covered by initiatives from Peak Year and a warning when too much runs at once.

Is a mission meant to create things on its own?

No. A proposal is planned. You decide what belongs, and writes go through the owning product.