Draft · not indexed. Part of what this page describes is not generally available yet.
Peak One · Template
A plan shows what depends on what. When one task slips, you see at once what moves with it.
A Gantt plan lays tasks out on a timeline and links the ones that wait on each other. Try in the demo how the end date shifts.
What happens if …?
Sample data · nothing is savedGo-live stays at day 24
Critical path: Concept → Design → Build → Go-live.
Interactive demo with invented sample data. No account, nothing is saved or sent.
How the template is built
Template columns
Phase, task, owner, start, duration in working days, predecessor and milestone yes or no.
Phases as groups
For example concept, build, test, sign-off. Each phase ends with a milestone.
Dependencies
The usual type is finish to start: B starts only when A is done. Only record real dependencies, or the plan becomes rigid.
Critical path
The longest chain of dependent tasks sets the earliest end date. If a task on it slips, the end moves.
Place buffer on purpose
Buffer belongs visibly before important milestones, not hidden in every single estimate.
An example
Product launch at Nordwind Travel Goods
Example: In the demo Mira delays „Approve packaging“ by five days. Because it sits on the critical path, the launch date moves with it. A delay in the social media copy changes nothing about the end.
Honest limits
Timeline and dependencies are beta
The timeline (Gantt), dependencies and the critical path exist in Peak One in Board V2, part of Work V2, not yet in the app catalog.
A scenario simulator is planned
Playing through delays in the demo only calculates in your browser. A simulator for projects is planned.
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 is a Gantt plan worth it?
When there is a fixed date and tasks wait on each other, for example launches, relaunches or events.
How detailed should it be?
Coarse enough to stay current. Tasks from a few days to two weeks are usually a good size.
Are the tasks on the timeline the same as on the board?
Yes. In Peak One a task is one row that board, list, timeline and calendar show. There is no copy to keep in sync.
What exactly is the critical path?
The longest chain of tasks that depend on each other. It determines the earliest possible end date of the project.
See the consequences before they happen.
A plan with real dependencies shows early which delay matters. Try it in the demo, no account needed.
Try the plan