The one bottleneck
Why are we missing our delivery dates right now?
Your questionBottleneck delivery
From Peak Constraints: the point that limits the most right now, with the person responsible and the status.
Peak Command · Bottleneck and radar
What is holding you back
comes first.
Command shows the current bottleneck from Peak Constraints and the most important hints from Peak Radar. It does not re-score them. It places them next to your goals and your plan, so you see what is affected.
In Peak One today · one active bottleneck · radar hints with their source
CONTEXT BEFORE DECISIONYour question.
Your question.
A path you can follow.
02 / The visible path3 example steps
Bottleneck delivery
Why: A late delivery date is the symptom. The bottleneck shows where the work piles up.
- 01Bottleneck from Peak Constraints: quality check before shipping
- 02Blocker from Peak Work: two orders waiting for sign-off for 5 days
- 03Consequence: milestone “Autumn collection launch” in Peak Year at risk
02 / Three sources, one place
Bottleneck, hint, consequence.
Command is where you see whether a problem hits a goal. It gets solved in the product built for it.
02 / Visible path
Hints from the radar
- 01Example step
Bottleneck from Peak Constraints: quality check before shipping
- 02Example step
Blocker from Peak Work: two orders waiting for sign-off for 5 days
- 03Example step
Consequence: milestone “Autumn collection launch” in Peak Year at risk
The consequence for your goal
Which goal, initiative or milestone depends on it? That turns a warning into a decision.
Your review is still open.
These marks decide nothing.Situation and decision stay separate
Clear responsibilities.
One bottleneck, not ten
Command shows the one active bottleneck from Peak Constraints. It is set and solved there.
Your question→Fixed rule→Example steps
The sculpture illustrates the flow. It is not a product interface.
The sculpture illustrates the flow. It is not a product interface.The radar is not recalculated
Hints from Peak Radar keep their rating and their source. Command only puts them in context.
- Basis
- Rules and sources, no language model
- Permissions
- Inherited from Peak One
No alarm from guesswork
If no source reports anything, Command shows nothing, instead of inventing a suspicion.
SituationDecision
The next step
See the bottleneck in context.
The example below shows a morning at the fictional company Nordwind Studio, with bottleneck, radar hints and affected goals.
View the examplePeak Command · Bottleneck and radarWhat limits right now.
In Peak One today · one active bottleneck · radar hints with their source
Example · Find the constraint
Where is your growth stuck right now?
Seven numbers are enough for a first read. The rules are below the result; there are no benchmark values from other companies.
Biggest constraint
Demand
Leads × close rate give fewer new customers than your goal, and fewer than you could deliver for.
How it was calculated
| Customers won per month = leads × close rate | 9 |
|---|---|
| Customers actually starting = smaller of won and capacity | 9 |
| Customers lost per month = active customers × churn | 3.2 |
| Demand ÷ goal | 0.75 |
| Capacity ÷ goal | 0.83 |
| Lost ÷ starting | 0.36 |
Rules in this order: 1. Cash runway under 3 months. 2. The smaller of demand ÷ goal and capacity ÷ goal, if it is under 1. 3. Retention, if lost ÷ starting is at least 0.5. 4. Otherwise no hard constraint.
Example Runs in this browser only · nothing is saved or sent · fictional values
Frequently asked questions
How does Peak Command know the bottleneck?
From Peak Constraints. You set the active bottleneck there; Command shows it and what affects it.
Does Peak Command score Radar signals differently?
No. Command reads Peak Radar through its own scoring and does not re-score the signals.
What if I do not use Peak Constraints?
Then Command shows that no bottleneck is set instead of inventing one. Radar signals still appear.
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.