İçeriğe geç
Peak Atlas

Draft · not indexed. Part of what this page describes is not generally available yet.

Peak One · Template

A look back is only as good as the next change. Two concrete actions beat twenty good insights.

The template guides the retrospective in three columns and ends with a few actions that someone owns. In the demo you sort cards on a retro board.

Try the retro
Durum: BetaTemplates exist for boards and workflows; project templates with a timeline are still being built.

Retrospective · sprint 7

Sample data · nothing is saved

Interactive demo with invented sample data. No account, nothing is saved or sent.

How the template is built

  1. What went well?

    What we want to keep. Concrete, with an example.

  2. What did not go well?

    What slowed us down. Talk about processes, not people.

  3. What do we change?

    Two or three actions at most, each with an owner and a date.

  4. Check the last retro

    Start with a quick check: did we carry out last time's actions?

  5. A calm frame

    Fixed time, clear facilitation, every voice counts. Collect first, then discuss.

An example

Project close at Studio Kiel

Example: After the relaunch the team collects eleven cards. Two actions remain: request approvals with a fixed date in future and get copy before design starts. Both become tasks with an owner.

Example, invented

Honest limits

  • No dedicated retro module

    Peak One has no retro board of its own. You create actions as tasks; Peak Task is available for that.

  • As a Peak One project, in beta

    Templates for boards and workflows exist in Peak One as a beta. Project templates with a timeline are still being built, so today you carry part of the structure over by hand.

  • The demo saves nothing

    The template on this page runs in your browser with invented sample data. Nothing is saved and nothing is sent.

Frequently asked questions

When should I run a retrospective?

At the end of every sprint or project, and after larger incidents.

How long does it take?

For one team usually an hour. More important than the length is that actions come out of it.

What if the same points keep coming up?

Then the actions were not carried out or were too big. Pick smaller steps and check them first next time.

Peak One · TemplateSprint planningDraft · not indexedPeak One · Use caseProject recoveryDraft · not indexedPeak One · TemplateMeeting to tasksDraft · not indexed

Learning that sticks.

With a few clear actions, every retro becomes an improvement in the next project.

Try the retro