コンテンツへスキップ
Peak Atlas

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

Peak One · Template

A good project starts on one page. If you cannot write the goal down, you cannot plan it.

The project brief captures on one page why the project exists, what it delivers and what it does not. In the demo it becomes a first plan, built from fixed rules in your browser.

ステータス: BetaTemplates exist for boards and workflows; project templates with a timeline are still being built.

From brief to project plan

Fixed rules, no AI

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

How the template is built

  1. Goal and reason

    One or two sentences: which problem does the project solve, and how will you know at the end that it is solved?

  2. Scope and out of scope

    What belongs to it and what explicitly does not. The second part prevents most later discussions.

  3. Deliverables

    The concrete outputs, each with a person who signs it off.

  4. Dates and milestones

    A fixed end date or a target window, plus two to four milestones where you check progress.

  5. People and roles

    Who decides, who works on it, who is only kept informed.

  6. Risks and assumptions

    What could hold the project up, and which assumptions must hold for the plan to work?

An example

Website relaunch at Nordwind Travel Goods

Example: Jonas writes the relaunch brief on one page. Under „out of scope“ it says: no new shop, no new product photos. In the demo he presses „Draft plan“ and sees phases, tasks and milestones as a first proposal.

Example, invented

Honest limits

  • The demo uses no AI

    The plan in the demo comes from fixed rules in your browser. An AI planner that drafts a plan from a brief is planned for Peak One, but not built.

  • 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

How long should a project brief be?

As short as possible, usually one page. If it grows longer, the scope is often not clear yet.

Who writes the brief?

Usually the project lead, agreed with the person who signs off the result. For client work, the client is part of it.

Does Peak One draft a plan from the brief?

Not yet. It is planned. The demo shows the idea with fixed rules, without AI.

What happens to my text in the demo?

Nothing. It stays in your browser and is neither saved nor sent.

Write it clearly, then plan.

A one-page brief saves weeks of back and forth. In Peak One you then create the tasks that board, list and calendar share.

Try the brief