Skip to content
Peak Atlas

Peak Command · with Peak Work

What blocks rises to the top.
Tasks stay in Peak Work.

Peak Command reads blockers and tasks from Peak Work and puts them next to goals and initiatives. If you create a task from Command, it is created in Peak Work, not in a second list.

Open the interactive demo

Built in Peak One · example with fictional values

Peak WorkIn Peak Work
Peak CommandIn Peak Command
Peak Command · Example path
One mapping in detail
01 / Peak WorkBlocked task
02 / Fictional test valueExample: photo approval open
03 / Peak CommandTension

A readable path as an example. Peak Command reads, it does not copy.

View all 5 mappings
Example path with fictional values.
Peak WorkLine in Peak Command
Blocked taskTension
SinceDuration
ProjectInitiative
CapacityHint
New taskCreate
Read path
Nothing transferred here
Nothing is connected on this page. In Peak One, Peak Command reads the products you are allowed to see.
One concrete line

Read the source. Show where it came from.

Peak CommandLine in Peak CommandRead only

The path shows where a line in Peak Command comes from. The values are fictional. In Peak One you see your own.

02 / How both work together

Blocked. Seen. Done.

Peak Work stays the place for work. Peak Command shows which work needs a leadership decision right now.

  1. 01 / The blocker

    Blocker in Peak Work

    A task is stuck, for example because an approval is missing.

    Something is stuck.TaskReasonSince when
  2. 02 / The effect

    Visible in Peak Command

    The blocker appears among the tensions and can move into the top 3, with the rule why.

    What it holds up.InitiativeMilestoneGoal
  3. 03 / The step

    Task through Peak Work

    A new task from Command is created in Peak Work, with your permissions there.

    Through Peak Work.TaskAssigneeDue

Trust needs clarity

What Peak Command does not do with tasks.

01 / The existing evidence

No second task list

Peak Command keeps no tasks of its own. Every task is the same one as in Peak Work.

Source / Peak CommandEXAMPLE
Peak WorkPathPeak Command
Read
Built in Peak One
Shown in Command
Not checked here

02 / Your check

No assigning without permission

Whoever may not create tasks in Peak Work cannot do so from Peak Command either.

Account
Peak One sign-in
Permissions
From the source product

03 / The clear limit

No rating of people

Peak Command shows blockers and capacity, no performance scores about individual people.

  • Adapter
  • Webhook
  • Embed
  • Planned

The next step

See blockers next to your goals.

The interactive demo shows how blockers from Peak Work appear in Peak Command. With fictional values.

Open the interactive demo
Your pathREAD ONLY
Peak Work→Peak Command
Blocked task → Tension

In Peak One you see which source stands behind every line.