Peak Command · Guide · Getting started
Your first week with Peak Command
started calmly.
A guide to your first week with Peak Command: read Today, check the sources, record your first decision. Put your starting questions together here.
What should Peak Command answer for you in your first week?
2 questions in the plan. First question: Which decision is on your desk this week?
The first week at a glance
Read Today. Check sources.
Which decision is on your desk this week?
Start with one question, not with every feature.
Peak Command is the management layer of Peak One. It owns no data of its own; it reads your other Peak products: goals from Peak Goals, initiatives from Peak Year, tasks and blockers from Peak Work. Its navigation has exactly four items: Today, Goals, Plan and Decisions. For the first week, one question you have to settle anyway is enough.
From reading to doing
Your starting questions. For your first week.
The next week.
2 questions selected
- Which decision is on your desk this week?
Write it as a question, e.g. “Do we hire in November?”.
- Where do your goals and plans live today?
Command reads Peak Goals and Peak Year directly. Anything that only lives in a spreadsheet is missing from the brief.
What a good
start needs.
A real question from your week, the sources that can answer it, and one person who decides at the end.
Which decision is on your desk this week?
Write it as a question, e.g. “Do we hire in November?”.
A real questionNot a test question: something you have to decide this week anyway.
Know the sourcesPeak Command reads goals, initiatives and tasks from other Peak products. What is missing is shown as missing.
Record an outcomeA decision with a reason and a review date, saved in Peak Log.
The playbook
Three days, three steps.
Read, check,
decide.
Today → Goals → Decisions
- 01
Day 1: read Today.
Open Peak Command and read the Today brief. Every line names its rule and its source. The Top 3 show what matters most today, and why. When nothing needs a decision, it says so.
Example · Nordwind Studio (fictional)Today: 2 milestones overdue, constraint “design capacity”.
First question: do we move campaign B by three weeks? - 02
Day 2: check the sources.
Look at where each number comes from and how fresh it is. Missing data is shown as missing, never as zero. Add missing goals or plans in their own product, not in Command.
Check the sources“Growth: not available”
Not an error: Peak Growth isn't connected, nothing is shown as 0. - 03
Day 3: decide once.
Open Decisions, take a card or create the question yourself, and record the decision with a reason and a review date. It is saved in Peak Log and comes back on the review date.
Record a decision
“Campaign B starts on 2 Dec. Reason: design capacity. Review on 15 Dec.”“Let's see how it goes.”
Your quality check
Did your first week work?
Tick what you have checked. Your selection stays in this view only.
0 of 4 points checked
What this article is based on.
Editorial guide with a fictional example. Today brief, Top 3, source freshness, decisions saved to Peak Log and inherited permissions exist in Peak Command today. Numbers in the example are made up.
- Evidence pending
Editorial guide with fictional companies and numbers. No customer data, no measured values, no customer results.
Start with Today.
Sign in to Peak One and read your first brief. Without an account, the demo shows the same flow with sample data.
Frequently asked questions
What do I need for the first week?
A Peak One account and at least one Peak app with data, such as Peak Goals, Peak Year or Peak Work. Peak Command reads these apps.
Do I have to enter data in Peak Command?
No. Peak Command owns no data of its own. You create goals, plans and tasks in the responsible apps.
How much time does it take a day?
The guide plans a few minutes in the morning for Today and one fixed slot per week for the review.