# What Is a Gantt Chart?

> 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.

*Section: Business — By Tom Bennett (Sports Writer) — Published January 6, 2024 — 6 min read*

Canonical URL: https://dailyjunction.co.uk/business/what-is-a-gantt-chart
Tags: gantt chart, project management, planning, scheduling, productivity

## Key takeaways

- A Gantt chart maps a project's tasks along a horizontal timeline, so each bar shows when a task starts, how long it lasts and when it finishes.
- It makes dependencies visible, showing which tasks must finish before others can begin.
- Milestones mark key checkpoints or deadlines and are usually shown as a diamond rather than a bar.
- The critical path is the chain of dependent tasks that sets the shortest possible project length; delays on it delay everything.
- Gantt charts suit projects with a defined scope and sequence, but can become unwieldy for highly uncertain or fast-changing work.

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.

## What it is

**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](/business/what-is-agile-project-management) more than a century later.

## The anatomy of a Gantt chart

A Gantt chart looks simple, but a good one carries a lot of information. The key elements are:

- **Tasks (or activities)** — the individual pieces of work, listed on the left.
- **The timeline** — the horizontal axis, usually in days, weeks or months.
- **Bars** — each task's duration, drawn to scale; a longer bar means a longer task.
- **Dependencies** — lines or arrows linking tasks that rely on one another.
- **Milestones** — key checkpoints or deadlines, usually shown as a diamond rather than a bar.
- **Progress** — often a shaded portion of each bar, or a percentage, showing how much is done.
- **Owners** — who is responsible for each task.

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.

## Dependencies and the critical path

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.

## A simple worked example

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.

## When to use a Gantt chart (and when not to)

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](/business/what-is-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:

- **The work is highly uncertain** and the plan changes constantly, so the chart is out of date as soon as it is drawn.
- **Scope is fluid**, with requirements emerging as you go.
- **Tasks are tiny and numerous**, making the chart a cluttered mess.

For that kind of fast-moving work, lighter [agile](/business/what-is-agile-project-management) 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](/business/what-is-change-management) in action.

## Building and maintaining one

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:

1. **Break work into sensible tasks** — not so big they hide problems, not so small they create noise.
2. **Estimate durations honestly** — optimistic estimates produce plans that were never achievable.
3. **Map real dependencies** — these drive the critical path, so getting them right matters most.
4. **Update it regularly** — an out-of-date Gantt chart is worse than none, because it gives false confidence.
5. **Mark milestones clearly** — they give everyone shared checkpoints to aim for.

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.

## The bottom line

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.

## Frequently asked questions

### What is a Gantt chart used for?

It is used to plan and track projects over time. By laying tasks out along a timeline as horizontal bars, it shows at a glance what needs to happen, in what order, who is responsible and whether the project is on schedule. Teams use it to coordinate work, spot clashes, communicate the plan to stakeholders and monitor progress against the original dates.

### What is the difference between a Gantt chart and a timeline?

A simple timeline just plots events or dates in sequence. A Gantt chart goes further: each task has a bar showing its duration, and it captures dependencies between tasks, who owns them and how progress is tracking. In short, a timeline shows when things happen, while a Gantt chart shows how the whole plan fits together and where the pressure points are.

### What are dependencies in a Gantt chart?

Dependencies are links between tasks showing that one cannot start, or finish, until another has reached a certain point. The most common is finish-to-start: task B can only begin once task A is done. Mapping dependencies reveals the true order of work and exposes the critical path, the sequence that determines the earliest the project can finish.

### Are Gantt charts still useful?

Yes, for the right work. They remain excellent for projects with a reasonably clear scope and sequence, such as construction, event planning or a product launch. For highly uncertain, fast-changing work, lighter agile tools like boards and sprints often fit better, though many teams blend both, using a Gantt view for the big picture and agile methods day to day.

## Sources

- [Association for Project Management (APM)](https://www.apm.org.uk/)
- [Atlassian: What is a Gantt chart?](https://www.atlassian.com/agile/project-management/gantt-chart)

---
Daily Junction — https://dailyjunction.co.uk/business/what-is-a-gantt-chart