Templates
About these templates
Projects tend to go wrong in a few predictable places: the work was never fully listed, nobody was clearly responsible, or the plan lived somewhere the team never looked. These templates each cover one of those gaps.
Early on, a work breakdown structure is the most useful thing you can build. Splitting a project into deliverables and then into tasks surfaces the work nobody had thought about yet, which is exactly the work that overruns later. Once the shape is clear, a RACI chart settles ownership before it becomes a problem, and it is worth doing even on small projects where the answer feels obvious. Then, for running the work, a kanban board shows what is actually moving versus what has quietly stalled.
For anything spanning months, a roadmap gives you phases and milestones over time. If dates are still guesses, use now, next and later instead. It communicates sequence honestly without inventing precision you do not have, and it is far easier to update when priorities shift. A process map is the one to use when the sequence itself is the deliverable, such as a handover or an approval path that people keep getting wrong.
The meeting agenda is the smallest template here and probably the most used. A timeboxed agenda everyone can see keeps a status meeting from turning into a discussion about one person's blocker.
Because these are mind maps, plans stay easy to change. Add a branch when scope grows, drag a task to a different owner, and share the map so the team is reading the current version rather than an export from last week.