Project WBS Mindmap
The code
mindmap
root((Website Launch))
Discovery
Stakeholder interviews
Requirements doc
Design
Wireframes
Visual system
Build
Frontend
CMS integration
Launch
QA pass
Go live checklist
How this template works
A work breakdown structure answers one question: what does done consist of? This mindmap breaks a website launch into four phases — Discovery, Design, Build, and Launch — and then into concrete deliverables like wireframes and a go-live checklist. Unlike a Gantt chart, it makes no promises about dates, which makes it the right artifact for the scoping conversation that happens before scheduling starts.
The syntax is deliberately minimal. mindmap on the first line selects the diagram type. root((Website Launch)) defines the center node, and the double parentheses give it the circular shape that marks it as the root. Each phase name is indented one level beneath the root, and each deliverable is indented one level beneath its phase, so Stakeholder interviews attaches to Discovery purely through its leading spaces. Nothing else is required: no node ids, no arrows, no closing brackets. That is why WBS maps like this one are so easy to maintain in version control alongside the project plan.
The gotcha is scope creep in diagram form. Every new deliverable is one more line, and because adding it takes five seconds, branches grow silently until the map stops fitting on a screen. Set a rule — four to six leaves per branch — and treat a branch that breaks the rule as a signal to split the project into sub-projects. Also keep deliverable names as nouns, since verb phrases blur the line between tasks and outcomes.
To adapt it, rename the phases for your methodology, add an owner leaf under each deliverable, or add a Risks branch for open questions before kickoff. The structure survives any renaming you throw at it.
Related templates that use the same grammar: the product roadmap mindmap for planning horizons, the learning path mindmap for curricula, and the business model mindmap for strategy sketches. The mindmap diagram guide documents the syntax in full.
Variations to try
- Add an owner name as a leaf under each task to turn the WBS into a lightweight assignment board.
- Add a Risks branch with children for open questions and dependencies before kickoff.
- Duplicate the map per phase and link the files from your project wiki for large programs.
