What is a Gantt chart?

A Gantt chart is a horizontal bar chart that maps the tasks of a project against a calendar. Each task is a bar; the bar's position shows when the task starts and ends, and its length shows how long it takes. Stack those bars up, line them against a timeline, and you can see an entire project at a glance: what happens when, what overlaps, and what has to wait for something else to finish.

It is, in other words, a picture of a plan over time. That single idea is why the Gantt chart has outlived a century of project-management fashions and still shows up in everything from a wedding checklist to a satellite launch.

The parts of a Gantt chart

Almost every Gantt chart is built from the same handful of elements. Once you can name them, you can read any chart you meet:

• The task list runs down the left-hand side — one row per piece of work, often grouped into phases.
• The timeline axis runs across the top, marked in days, weeks, or months depending on how far the project stretches.
• The bars are the heart of it. A bar's left edge is the start date, its right edge is the finish date, and its width is the duration.
• Milestones are zero-length events — a launch, an approval, a deadline — usually drawn as a diamond rather than a bar.
• Dependencies are arrows connecting one bar to another, showing that the second task can't proceed until the first reaches a certain point.
• Progress is often shown by shading part of a bar, so a half-filled bar means the task is roughly halfway done.
• The "today" line is a vertical marker on the current date, which makes it instantly obvious whether you're ahead or behind.

How to read one

Reading a Gantt chart is mostly a matter of moving your eye in two directions. Read down the rows to see everything the project involves. Read across a single row to see when that task happens. Then look for three things:

1. Overlap. Bars that sit on top of each other in time are happening at once — that tells you where people will be busy simultaneously, and where you might be over-committed.
2. Sequence. Follow the arrows. They show the order work has to happen in, and which late task will drag others with it.
3. Position relative to today. A bar whose progress shading hasn't reached the today line is running behind. A milestone to the left of today that hasn't been hit is a missed deadline.

A small worked example

Say you're redesigning a website. Your tasks might be: research the current site (5 days), design the new pages (1 week), build them (2 weeks), review (3 days), then launch. Plotted as a Gantt chart, "design" can't start until "research" finishes, "build" follows "design", and "launch" is a milestone at the very end. The moment you draw it, two things jump out that a to-do list would hide: the project is about five weeks long, and the "build" task is the long pole — if it slips, the launch slips with it. That second insight is the whole point. A list tells you what; a Gantt chart tells you when, and what depends on what.

What Gantt charts are good at

• Showing time and overlap. Nothing communicates "these three things all happen in March" faster than three bars stacked over March.
• Making dependencies visible. The arrows turn an invisible web of "this has to come first" into something you can actually see and argue about.
• Spotting the long pole. The chain of tasks that determines the end date — the critical path — stands out once everything is on a timeline.
• Communicating a plan to other people. A stakeholder who would never read a project spreadsheet will understand a Gantt chart in ten seconds.

Where Gantt charts fall short

It's worth being honest about the limits, because reaching for a Gantt chart when you need something else is a common mistake.

• They assume you know the plan. Gantt charts are weak for exploratory or research work where the next step depends on what you just learned. A Kanban board handles that flow better.
• They can get unwieldy. A 400-task chart is hard to read and harder to keep current. The fix is grouping tasks into collapsible phases and resisting the urge to track every tiny item.
• They go stale if no one updates them. A Gantt chart is only as honest as its last edit. A plan drawn once and never revisited is decoration, not management.

A short history

The chart is named after Henry Gantt, an American engineer who popularised it in the 1910s to schedule factory and shipyard work. He wasn't quite first: the Polish economist Karol Adamiecki devised a near-identical "harmonogram" around 1896, but published it in Polish and Russian, so the English-speaking world learned it from Gantt. For decades the charts were drawn and redrawn by hand on paper — which is why, for most of the twentieth century, they were reserved for projects big enough to justify the effort. Software changed that. Today you can build one in a browser in a minute, which is arguably the bigger revolution: the technique finally became cheap enough for everyday plans.

When should you use one?

Use a Gantt chart when at least two of these are true: the project has a deadline, it has more than a handful of tasks, those tasks depend on each other, or you need to explain the plan to someone who isn't in your head. A weekend move, a product launch, a dissertation, a kitchen remodel — all fit. Buying groceries does not. The test is simple: if "when" and "in what order" matter, a Gantt chart will earn its keep.

Frequently asked questions

Is a Gantt chart the same as a project timeline?

They overlap, but a timeline usually just shows when things happen, while a Gantt chart adds task durations, dependencies between tasks, and progress. Every Gantt chart is a timeline; not every timeline is a Gantt chart.

Do I need special software to make one?

No. You can sketch a basic Gantt chart on paper or in a spreadsheet. Dedicated tools just make it far faster to draw, drag, and keep up to date — for example, you can build one free in the browser at ganttchartmaker.app with no signup.

How detailed should my tasks be?

A good rule is that no task should be shorter than the smallest unit you actually track — if you review the plan weekly, tasks under a day add noise without adding control. Group fine detail under collapsible phases instead.

What is the difference between a task and a milestone?

A task has a duration and is drawn as a bar. A milestone is a zero-length marker for a moment that matters — a deadline, an approval, a launch — and is usually drawn as a diamond.