Daily Junction.mobi portalBusiness · January 6, 2024 · Tom Bennett · 6 min
A Gantt chart is a horizontal bar chart that shows a project's tasks against a timeline, making it easy to see what happens when and how tasks depend on each other.
If you have ever seen a project plan made of horizontal bars marching across a calendar, you have seen a Gantt chart. It is one of the oldest and most enduring tools in project management, and for good reason: it turns an abstract list of tasks into a picture of time. At a glance you can see what is happening now, what comes next, and whether everything is on track. This guide explains what a Gantt chart is, the parts that make it work, when to use one and where it falls short.
A Gantt chart is a horizontal bar chart that displays a project's tasks against a timeline, with each bar showing when a task starts, how long it lasts and when it ends. Tasks are listed down the left-hand side; time runs across the top. The position and length of each bar tell you the schedule at a glance.
Named after engineer Henry Gantt, who popularised the format in the early twentieth century, the chart answers the questions every project raises: What needs doing? In what order? By when? And are we on track? That combination of clarity and simplicity is why it remains a staple of project management more than a century later.
A Gantt chart looks simple, but a good one carries a lot of information. The key elements are:
Put together, these turn a flat to-do list into a living schedule. You can see not just what must happen but when and in what sequence, which is exactly the information a plan needs to be useful.
The feature that lifts a Gantt chart above a simple timeline is its ability to show dependencies — relationships where one task cannot proceed until another has reached a certain point. The most common type is finish-to-start: you cannot lay a carpet until the floor is built; you cannot test software until it is written.
Mapping these links reveals something important: the critical path. This is the longest chain of dependent tasks running through the project, and it sets the shortest possible time in which the whole thing can be completed.
If a task on the critical path slips by a day, the project finishes a day late — no matter how far ahead everything else is. Tasks off the critical path have slack and can move a little without harming the deadline.
Knowing the critical path tells a project manager where to focus. Protect those tasks, watch them closely, and you protect the deadline. It also shows where you have flexibility to reassign people or absorb a delay without panic.
Imagine planning a small product launch. A stripped-down version might look like this:
| Task | Duration | Depends on |
|---|---|---|
| Finalise product | 2 weeks | — |
| Build website | 2 weeks | Finalise product |
| Write marketing copy | 1 week | Finalise product |
| Set up email campaign | 1 week | Write marketing copy |
| Launch (milestone) | 1 day | Build website, Set up email campaign |
On a Gantt chart, "build website" and "write marketing copy" can run in parallel because both depend only on the finished product, but the launch waits for the slower branch to complete. Reading the bars, you would quickly see that the website is on the critical path and the marketing copy has a little slack — useful to know if someone falls ill.
Gantt charts shine when a project has a reasonably clear scope and a logical sequence of tasks. Classic examples include construction, event planning, a marketing campaign or a product launch — anything where you can sketch out the steps and roughly how long each will take.
They are also superb communication tools. A single chart can show a stakeholder the whole plan, the deadlines and the current status without a long meeting, which is invaluable when you need to keep busy people aligned.
But they are not universal. Gantt charts struggle when:
For that kind of fast-moving work, lighter agile approaches — boards, sprints and short cycles — often fit better. Many teams sensibly blend the two: a high-level Gantt chart for the overall roadmap and stakeholders, and agile methods for the day-to-day. When a project does have to change direction, the chart becomes a handy reference point for managing that shift, a small slice of change management in action.
You can create a Gantt chart in dedicated software, a project tool or even a spreadsheet. Whatever you use, a few habits keep it valuable:
The chart is only as good as the thinking behind it. The act of building one often surfaces problems — clashes, impossible deadlines, missing steps — before they bite, which is part of its value.
A Gantt chart is a horizontal bar chart that lays a project's tasks along a timeline, showing when each starts, how long it runs and how tasks depend on one another. Its real power lies in making dependencies and the critical path visible, so you know where delays will hurt and where you have slack. It is ideal for projects with a clear scope and sequence and unbeatable for explaining a plan to others, but less suited to highly uncertain work, where agile methods come into their own. Used well, and kept up to date, a Gantt chart turns a daunting list of tasks into a plan you can actually steer.
![[View image]](/img/what-is-a-gantt-chart.jpg){kind=link}