Peak Command
Each line names its rule and its source. When nothing needs a decision, the brief says so.
What needs a decision today?
A dashboard is strong when you want to see metrics and interpret them yourself. Peak Command starts with the question of what needs a decision today, and records it. Here both sides stand next to each other, including where a dashboard is the better choice.
What decides it for you?
What needs a decision today?
Same questions. Two kinds of tool. No winner decided in advance.
01 / The basis for deciding
Pick a focus. Each row asks Peak Command and a typical dashboard the same question. The dashboard side is described in general; you check your own tool yourself.
6 dimensions · Same standard for both options
Each line names its rule and its source. When nothing needs a decision, the brief says so.
What needs a decision today?
A dashboard typically shows the numbers someone set up. What follows from them is up to the viewer.
What needs a decision today?
| The criterion | Peak Command | A dashboard |
|---|---|---|
| What counts todayWhat needs a decision today? | Peak CommandToday brief with Top 3 Each line names its rule and its source. When nothing needs a decision, the brief says so. Backed by codePeak Command features with status “built”: Today brief, Top 3, decisions in Peak Log, scenarios, review agenda, inherited permissions. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one · docs/prd/peak-command-prd.md (PCMD register) | A dashboardNot yet evidenced A dashboard typically shows the numbers someone set up. What follows from them is up to the viewer. Evidence pendingNo statement about a specific product. Tools in this category differ a lot. Check your own tool yourself and note the date and source. General description of a tool category |
| Recording a decisionWhere does it say later what was decided and why? | Peak CommandIn Peak Log, with a review A decision is written to Peak Log with its reasons and can be reviewed and searched later. Backed by codePeak Command features with status “built”: Today brief, Top 3, decisions in Peak Log, scenarios, review agenda, inherited permissions. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one · docs/prd/peak-command-prd.md (PCMD register) | A dashboardNot yet evidenced Dashboards are built for looking. Decisions then usually live in minutes or emails. Evidence pendingNo statement about a specific product. Tools in this category differ a lot. Check your own tool yourself and note the date and source. General description of a tool category |
| Missing dataHow do you see that a number is missing or stale? | Peak CommandMissing stays missing Missing data never shows as zero. Each signal shows how fresh and how reliable its source is. Backed by codePeak Command features with status “built”: Today brief, Top 3, decisions in Peak Log, scenarios, review agenda, inherited permissions. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one · docs/prd/peak-command-prd.md (PCMD register) | A dashboardNot yet evidenced Whether empty values show as zero, a gap or a note is set by the person who builds the dashboard. Evidence pendingNo statement about a specific product. Tools in this category differ a lot. Check your own tool yourself and note the date and source. General description of a tool category |
| Free analysisCan I build my own charts and drill deep into data? | Peak CommandNot what Command is for Peak Command shows a brief, priorities and decisions, not a chart builder of its own. Backed by codePeak Command features with status “built”: Today brief, Top 3, decisions in Peak Log, scenarios, review agenda, inherited permissions. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one · docs/prd/peak-command-prd.md (PCMD register) | A dashboardNot yet evidenced For free analysis, filters and your own charts a dashboard is usually the better choice here. Evidence pendingNo statement about a specific product. Tools in this category differ a lot. Check your own tool yourself and note the date and source. General description of a tool category |
| Data sourcesWhich data goes in? | Peak CommandThe Peak One products Command reads Peak Goals, Year, Work, Plan, Finance, Radar and Constraints. Products not connected show as “not available”. Backed by codePeak Command features with status “built”: Today brief, Top 3, decisions in Peak Log, scenarios, review agenda, inherited permissions. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one · docs/prd/peak-command-prd.md (PCMD register) | A dashboardNot yet evidenced If your numbers come from many systems outside Peak One, a dashboard is often the better choice here. Evidence pendingNo statement about a specific product. Tools in this category differ a lot. Check your own tool yourself and note the date and source. General description of a tool category |
| What ifCan I play through an assumption without changing anything? | Peak CommandScenarios without side effects Scenarios compute with Peak Finance and Peak Year. They change nothing until you apply them in the owning product. Backed by codePeak Command features with status “built”: Today brief, Top 3, decisions in Peak Log, scenarios, review agenda, inherited permissions. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one · docs/prd/peak-command-prd.md (PCMD register) | A dashboardNot yet evidenced Some dashboards offer parameters for assumptions, others don't. Check your own tool. Evidence pendingNo statement about a specific product. Tools in this category differ a lot. Check your own tool yourself and note the date and source. General description of a tool category |
Source code is evidence of implementation. It does not replace a current live test.
This page describes Peak Command only as it is built in Peak One today. It describes dashboards as a category, not a product, and says what a dashboard is better suited for.
Peak Command per its register. The tool category described in general only.
The same question, the same period, the same data for both tools.
For Peak Command only what the register lists as built counts. Planned features are not here.
For free analysis, your own charts and many external sources a dashboard is usually the better choice. The table says so.
02 / From feature to moment
A check turns a list into a concrete trial. Pick the first test for both tools.
The same question in both tools. The protocol prepares the test; it doesn't run it.
Open both tools and answer in writing: which three things need a decision this week?
You know how long it takes you to reach a clear answer.
Peak Command features with status “built”: Today brief, Top 3, decisions in Peak Log, scenarios, review agenda, inherited permissions. A register doesn't replace your own test in your workspace.
Source checked:
Peak-Admin/peak-one · docs/prd/peak-command-prd.md (PCMD register)Task selected. No test run.
Open the interactive demo03 / Before the next step
A table doesn't replace a test. The interactive demo shows Peak Command's flow at the fictional Nordwind Studio: brief, Top 3, one decision. None of it reaches Peak One.
Switching is a separate decision. Prepare it and keep the open evidence in view.
The demo runs locally in your browser and changes nothing.
For analysis and your own charts a dashboard often stays right. For the question of what gets decided today, try Peak Command in Peak One.
Sign in to Peak One and open CommandPeak Command statements per the PCMD register (as of 2026-10-27). The tool category is described in general, with no statement about a specific product.
Often the answer is both, for different jobs.
Not necessarily. For free analysis, your own charts and many external sources a dashboard is usually the better choice. Command answers a different question: what needs a decision today.
The Peak One products, such as Goals, Year, Work, Plan, Finance, Radar and Constraints. Products not connected show in Command as “not available”, never as zero.
The decision is written to Peak Log with its reasons. Later you can search it and check in a review whether it worked.
No. The page describes dashboards as a category, with no statement about a specific product. Individual tools differ a lot; check your own yourself.