Hoppa till innehållet
Peak Atlas

Peak One · Knowledge

A project is work with a start and an end. Project management makes sure the end actually arrives.

A project is a time-bound effort with a specific result. This guide walks through the five steps almost every project needs. The demo shows them as a flow.

Status: Available in Peak One

An example

Website relaunch at Studio Kiel

Example: Anna writes the brief, splits the relaunch into four phases with one milestone each and plans the tasks on the board. Every morning My Day shows her the three most important tasks. After sign-off the team holds a short retrospective.

Example, invented

The sequence

  1. 1. Brief: why and what

    Goal, scope, out of scope, deliverables and people on one page. Without this foundation you plan blind.

  2. 2. Plan: tasks, dates, dependencies

    Break deliverables into tasks, estimate, assign owners and set milestones. Dependencies show what relies on what.

  3. 3. Execution: work in the open

    A board with clear statuses shows what is open, in progress, blocked or done. Blockers are named early, not at the end.

  4. 4. Daily work: a few things first

    Each person knows in the morning which two or three tasks move things most today. The plan becomes the work of the day.

  5. 5. Close: sign off and learn

    Get the result signed off, hand over open items, run a retrospective. Only then is a project really done.

  6. The iron triangle

    Scope, time and resources are linked. If one changes, at least one other has to move, or quality suffers.

Honest limits

  • No cure-all

    Method does not replace decisions. If goal or scope are unclear, even the best tool will not help.

  • What Peak One does today

    Tasks, board, My Day, calendar, goals and milestones are available. Timeline and dependencies are beta, an AI project planner is planned.

  • The demo is an example

    The flow in the demo runs on invented data in your browser and saves nothing.

Frequently asked questions

How is a project different from routine work?

A project has a fixed goal, a start and an end. Routine work repeats without a fixed end.

Do I need a specific method?

No. Classic planning or agile sprints both work. What matters is that goal, ownership and dates are clear.

What is a milestone?

A point in time when an important interim result should be ready. It has no duration; it marks a checkpoint.

How many tasks should a project have?

Enough that each one can be finished in a few days. Very large tasks hide risks.

Five steps, one flow.

If you keep brief, plan, execution, day and close apart, you keep the overview even in busy weeks.

Try the flow