# Planning and project

Planning diagrams fail in the same way: they are drawn once for approval, and then the plan changes without them. Everything here is text-first for exactly that reason.

The good ones make one thing visible that a list cannot: dependency, sequence, or slack.

---

## In this section

[Gantt chartTasks, dependencies and a critical date.](https://help.gocapable.com/diagrams/gantt-chart.html)

[TimelineHistory, launches and incident reviews.](https://staging.dev.capable-sites.com/wiki/pages/1410138271)

[PERT and critical pathSlack, and the path that has none.](https://help.gocapable.com/diagrams/pert-and-critical-path.html)

[Work breakdown structureDeliverables decomposed until they are estimable.](https://help.gocapable.com/diagrams/work-breakdown-structure.html)

---

## Everything under here

[Gantt chartCreate a Gantt chart with tasks, durations, dependencies and milestones, and edit it on a canvas.](https://help.gocapable.com/diagrams/gantt-chart.html)[PERT and critical pathDraw a PERT chart, find the critical path and show slack between dependent activities.](https://help.gocapable.com/diagrams/pert-and-critical-path.html)[Work breakdown structureBuild a WBS in Confluence, decomposing deliverables into work packages level by level.](https://help.gocapable.com/diagrams/work-breakdown-structure.html)

---

_A plan you can change is a plan people trust._