A Gantt chart is a bar chart that looks like a decision. It is a model of sequence and time — useful when dependencies are real, decorative when the bars are fiction. Learn to read one, build a simple one, and stop treating the printout as a contract with Thursday.
What the bars are actually claiming
A timeline shows when work is supposed to happen. A Gantt chart adds duration, start and finish, and — if you are doing the job — predecessors. The bar is not progress. The bar is a forecast. Progress is a separate field you update from reality. A chart that is 80% complete because someone dragged the percent-complete handle is a confidence trick you played on yourself.
Read left to right for sequence, top to bottom for work breakdown, and the connecting lines for dependencies. Finish-to-start is the common one: B cannot start until A finishes. Start-to-start and finish-to-finish exist; misuse them and you will invent a schedule that only the software understands. If you cannot explain a link in a sentence, delete the link. Mystery predecessors are how a one-day slip becomes a three-week mystery.
Milestones are dates with meaning: a decision, a freeze, a release, a regulatory window. They have zero duration. Do not use a milestone as a hiding place for a month of unplanned work. Stakeholders love milestones because they look like commitments. Your job is to attach each one to the work that must be true — and to the owner who will say when it is not.
Build a small, honest schedule
Start from deliverables, not from a tool template with fifty summary rows. List the work packages that must finish, the order they must finish in, and a duration you would defend to the person doing the work. Get the durations from them. A Gantt built entirely by the PM in a quiet hour is a novel. Novels are allowed to have plot holes. Projects are not.
Enter dependencies before you enter dates. Dates are a result of sequence plus capacity, plus any hard constraints (a conference, a legal date, an environment freeze). If you type the end date first and then squeeze the bars to fit, you have produced a sales artefact. It will look excellent in the steering pack. It will also be wrong on day one, which is traditional, and still not a virtue.
Keep it shallow enough to update. A 400-row Gantt that nobody touches after baseline is a museum. For most teams, a two-level view is enough: summary deliverables for leadership, a handful of successor tasks for the people sequencing work. If you need the third level, use it in the working file and show the summary in the meeting. Clarity is a filter, not a lack of rigour.
When a Gantt helps — and when it lies
Use a Gantt when sequence and a date interact: migrations, launches with a freeze, vendor lead times, anything with a genuine critical path. The critical path is the longest chain of dependent work. Slip there and the end date slips. Slip on a task with float and you have used up slack, not the deadline. Knowing which is which is the whole point of the diagram. Pretty bars without that distinction are a timeline in formal wear.
Do not use a Gantt as the daily board for a team that pulls from a backlog. They will not update it. You will chase them. Everyone will hate the chart and still believe it, which is the worst combination. Pair the views: the board for flow this week, a thin timeline for the dates that other teams and vendors must meet. Two views of one plan. Two plans is how you get two truths and a Friday argument.
Re-baseline only when an approved change says so. If the bars have been quietly slid every week so the project is always 'on track,' you are running a video game with god mode enabled. Show the baseline versus the forecast. The gap is the conversation. Hiding the gap is how Gantts earned their reputation as confident fiction.
Summary & next steps
A Gantt is a sequence model, not proof. Enter dependencies before dates, take durations from the people who will do the work, and reserve it for work where order and a deadline actually interact. Update from reality or stop showing it.
Next: collaboration basics — comments, mentions, and the single source of truth that stops your timeline living in six inboxes.