Project Map
Chart the terrain before you set out.
Chart the terrain before you set out
Project Map connects business objectives to concrete work — with every dependency visible, every estimate grounded, and every deviation tracked. Plan the route. Then navigate it.
Four phases. One continuous flow.
Project Map follows the natural arc of a project — from defining what you want to achieve, through planning how to get there, to navigating the actual work and learning from the result.
Destination
Define strategic goals and business objectives. Link them to milestones — the landmarks that mark real achievement. Set terrain tags to characterise your project's conditions.
Route Planner
Break milestones into work packages and activities. Set estimates by role. Map dependencies. Flag known unknowns as questions. When the plan is ready, lock the baseline.
Navigator
Assign work to people. Track time and progress. When reality diverges from the plan — and it will — re-route dynamically or open a formal re-plan. Deviation from baseline is always visible.
Logbook
Save proven routes as templates. Tag terrain conditions. Use historical data to forecast future projects — grounded in what actually happened, not what someone hoped would happen.
From strategy to hours. Connected.
Plan with roles, execute with people
An Activity defines what needs doing and how long it should take — assigned to a role, not a person. When work begins, a Task is created and assigned to a specific team member. Planning stays clean. Execution stays accountable.
Baseline and re-routing
When the plan is ready, lock the Baseline. After that, every change goes through a Re-route draft — visible to the whole team, committed with a reason. The original plan is never overwritten. Drift is always traceable.
History as a forecasting tool
Every completed milestone feeds a historical record. Future estimates can be grounded in what similar work actually took — matched by role, size, and terrain conditions.
Everything from Milestone down is where the actual planning and execution happens.
What we believe about project planning
The plan is not the work
Planning and execution are different activities requiring different information. An activity belongs to a role. A task belongs to a person. Mixing them creates confusion. Separating them creates clarity.
Deviation is information
Every project drifts from its plan. The question is whether you see the drift while you can still act on it. Project Map shows baseline deviation continuously — not as a report you run on Fridays.
History beats optimism
Reference Class Forecasting uses data from past projects — matched by role, size, and conditions — to ground new estimates in reality. Your next estimate is informed by what actually happened, not what you think will happen.
Dependencies are the plan
A list of tasks is not a plan. The connections between them — what blocks what, what enables what — are where the real planning happens. Project Map makes dependencies visible and central, not an afterthought.
Questions are first-class
Every project has things you don't know yet. Project Map lets you capture these as Questions — linked to the work they block, assigned to the person who can answer, with a deadline. Unknowns become visible and manageable.
Scope is a flag, not a wall
Work doesn't respect agreement boundaries. A project often includes tasks from different budgets, different stakeholders, different agreements. Project Map lets you plan and track all of it — while keeping clear what's in scope and what isn't.
Follow the build
Project Map is under active development. Sign up to follow progress and get early access when the first release is ready.
Join the waitlist