Draft · not indexed. Part of what this page describes is not generally available yet.
Peak One · Beta
Nothing happens on its own. Some tasks wait until another one is done.
In Work V2 you link tasks that wait for each other and see the critical path. It is in beta and not in the app catalog yet.
An example
No go-live without approval
Example: At Agentur Nordlicht, “Go-live” can only start once “Legal copy approved” is done. If the approval slips by three days, the demo shows the go-live moving too.
Try it
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 it works
Who waits for whom
Set that a task can only start once another one is done.
Critical path
Work V2 shows the chain that sets the end date. If something slips there, the end moves.
Visible in the timeline
Dependencies appear as links in the Board V2 timeline.
A demo to try
Delay one of six sample tasks and see how the end date and critical path change. Only your browser does the math.
Honest limits
Beta, not in the app catalog
Dependencies are part of Work V2. They are built but not switched on for everyone yet.
Scenarios are planned
A simulator that runs “what if …” on real projects is planned. The demo uses sample data only.
Frequently asked questions
Can I set dependencies today?
In Work V2, which is in beta. The existing board without V2 does not have them.
Does Peak move dates automatically?
Work V2 shows you what moves. Whether you change dates is up to you.
What is the critical path?
The chain of tasks without slack. Any delay in it moves the project end.