Skip to content
Peak Atlas

Peak Command / Weekly review

Monday, 9 a.m.The agenda is already there.

At Nordwind Studio (fictional) the weekly meeting started with twenty minutes of status reports. Peak Command builds the weekly agenda from what is due: Top 3, tensions between goals, capacity and plan, blockers from Peak Work and decision reviews that are due. Every line names its rule and source.

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

Local draft · no product activation
Prepare the weekly agenda

Local example · nothing is read from Peak One.

Sixty minutes that decide something.

Review / Decision / Follow-up

01Situation02Decide03Follow up
Example / Weekly agenda

Three blocks instead of a status round.

Situation
Top 3 and tensions, each with its rule.
Decide
Decision cards with candidates.
Follow up
Due reviews of earlier decisions.
Example with a fictional company · not the product interface

Your weekly meeting in the example

Three answers, one agenda.

Describe the shift, the decision and the due review. The preview orders them into an agenda and 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 weekly agenda.

Draft · not yet put together

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

One week, one rhythm

Prepare, decide, review.

The weekly meeting gets shorter when the status is visible beforehand and the time stays for decisions.

  1. 01Prepare

    The agenda is ready.

    Situation

    Top 3 and tensions, each with its rule.

    Peak Command reads goals, plan, blockers and capacity from the products and orders them by rules.

    Products → weekly agenda
  2. 02Decide

    Record instead of forget.

    Decide

    Decision cards with candidates.

    A decision is written to Peak Log with its reason, including a date for the review.

    Decision card → Peak Log
  3. 03Review

    What came of it?

    Follow up

    Due reviews of earlier decisions.

    Due reviews appear in the next agenda. In the example only a local note is created.

    Sample artifact → agenda note

From the example to a real meeting

Open the weekly agenda in Peak Command.

In Peak One you open Peak Command and call up the review for the week. The agenda is built from your goals, your plan and your open decisions.

Sign in to Peak One

Peak Command / Your next step

Less status. More decisions.

Build your agenda in the example. Then open the real one for this week.

Prepare the weekly agenda
Local working example

A weekly meeting with an outcome.

Due reviews of earlier decisions.

Frequently asked questions

Where does the agenda come from?

From open decisions in Peak Log, goals from Peak Goals, blockers from Peak Work and initiatives from Peak Year. Besides the week there are monthly and quarterly rounds.

What if nothing needs a decision?

Then Command says so. It does not pad the agenda.

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