Skip to content
Peak Atlas

Peak Command / Capacity and growth

The new client says yes.Who does the work?

Atelier Morgenrot (fictional) wins projects faster than it can deliver them. Peak Command reads capacity from Peak Plan, puts it next to goals and plan and shows the tension before the team feels it. A scenario computes what a later hire would mean.

Put the goal into words. Add perspectives and timing right below.

Local draft · no product activation
Check capacity in the example

Two sample situations · nothing is read.

More orders, same team.

Goal / Capacity / Tension

01Goal02Capacity03Tension
Example / Capacity check

Goal, load, tension.

Goal
The growth goal from Peak Goals.
Capacity
Load from Peak Plan, read only.
Tension
Where goal and capacity don't fit together.
Example with a fictional company · not the product interface
For growing teamsNew project → Hire → Bottleneck

Your capacity in the example

Goal, team, alternative.

Describe the growth goal, the team affected and the alternative. The preview stores nothing.

Local working example · nothing is saved or sent. Please don't enter personal data.

Peak Command / Start noteLOCAL DRAFT
01 / Your thoughts
02 / Your start noteLocal preview

Three answers. One capacity question.

Draft · not yet put together

Goal
Still open
Capacity
Still open
Option
Still open
Your input appears here right away. With “View the start note” you check the three details locally.

Two typical situations

Where does your growth hit a limit right now?

Pick the situation. Tension, scenario and result follow from it.

A retainer at Atelier Morgenrot (fictional)

A client wants to start next month.

The action
Command shows the tension between the growth goal and the design team's load from Peak Plan.
The intent
A yes with open eyes, or a later start.
Working example / New project

The tension

Goal
Four new retainers (example)
Load
Design team almost fully booked
Tension
Goal needs more than is free
Editorial structure sketch · not a customer reference

The example shows the structure with a fictional company. In Peak Command you read the same question from your own products.

To the next step

Is this for you?

A clear job. Clear limits.

A team that
grows faster than planned.

This is where the example helps.

  • You win projects before it's clear who delivers them.
  • You plan capacity in Peak Plan or want to.
  • You want to weigh hires against start dates.
Local previewPeak Command

Writes in the owning product

What this page doesn't do.

  • This page reads no data from Peak One and stores nothing.
  • Peak Command doesn't decide for you and changes nothing outside the owning product.
  • No health score, no number without a source.

From the example to real capacity

See tensions in “Today”.

In Peak Command tensions between goals, capacity and plan appear as soon as Peak Plan and Peak Goals have data.

Sign in to Peak One

Peak Command / Your next step

Growth needs hands.

Check your capacity in the example. Then look at the tensions in Command.

Check capacity in the example
Local working example

Grow without burning out the team.

Where goal and capacity don't fit together.

Frequently asked questions

Where does capacity come from?

From Peak Plan, read only. Command does not re-plan people and changes no allocation.

What is a tension?

A place where goal, capacity and plan do not fit together. Command names the rule by which it found it.

Are the companies on this page real?

No. The companies and numbers are fictional examples. They show the flow, they prove no effect.

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.

More in Peak Command

All pages in Solutions