Somebody on your team just said “we need a plan,” and now you’re staring at three tabs: a Gantt chart tool, a kanban board, and a blank to-do list. They all promise clarity. They are not interchangeable. Pick the wrong shape and you’ll spend the project fighting your own plan — updating a chart nobody reads, or missing a deadline that a chart would have made obvious in week one.

The good news: choosing is one question, not a personality quiz.

The only question that matters

Does your work have a deadline that other work has to line up against?

That’s it. If yes — things must happen in a certain order, by a certain date, and some tasks can’t start until others finish — your plan has a time dimension, and you want a timeline. If no — the work is a pool of items that get done as capacity frees up, and “when” matters less than “what’s next” — your plan has a flow dimension, and a board or a list will serve you better.

Everything else (team size, tool budget, how much your manager likes colored rectangles) is detail.

What each shape is actually for

A to-do list is a memory. It answers one question: what needs doing? It’s the right shape when the work is yours alone, the items are independent, and nothing is waiting on anything else. Groceries, bug triage, the fifteen small chores of a launch week. The moment one item can’t start until another finishes, the list starts lying to you — it shows “write announcement” and “get legal sign-off” as equals when one of them is quietly blocking the other. A list has no way to say waiting.

A kanban board is a flow meter. It answers: what’s moving, what’s stuck, and what’s next? Work enters on the left, gets pulled through columns, and exits done. It’s the right shape for continuous work with no finish line — support queues, content pipelines, a team shipping improvements every week forever. Boards are honest about capacity (“why are nine cards In Progress?”) and silent about dates. A board cannot show you that the whole thing needs to be done by March 28, because a board doesn’t believe in March 28.

A Gantt chart is a promise made visible. It answers: will we make the date — and if not, which task is to blame? Bars on a calendar, arranged so dependencies are visible and the critical path stands out. It’s the right shape when the project has a beginning, an end, a deadline someone said out loud, and tasks that wait on each other. Launches, events, migrations, renovations, anything with the word “by” in it.

The honest trade-offs

Every shape has a failure mode, and it’s usually the reason people switch:

  • Lists scale down beautifully and up terribly. Twelve items, fine. Sixty items across four people with three deadlines — you’ve built a Gantt chart’s worth of complexity with none of its visibility.
  • Boards hide deadlines until they’re emergencies. “It’s in progress” is a soothing answer right up until someone asks whether it’ll be done by the launch date, and nobody can say, because the board was never asked to know.
  • Gantt charts rot when edits are expensive. A timeline is only as good as its last update. If moving one bar means an afternoon of dragging cells around, the chart freezes into fiction and the real plan retreats into hallway conversations. (This is a tooling problem, not a Gantt problem — more on that below.)

Mixing shapes without making a mess

Real projects usually deserve two shapes at two altitudes. The pattern that works: a timeline for the room, a board or list for the desk. The Gantt chart holds the phases, milestones, and dependencies — the five-to-twelve bars everyone points at in the Monday meeting. The kanban board or to-do list holds the forty tickets inside the “Build” bar — the detail only the builders need. The chart answers “will we make the date”; the board answers “what do I pick up next.” Trouble starts only when one tool is asked to answer both questions at once.

If you landed on “Gantt chart”

The traditional objection is that timelines are expensive to make and worse to maintain — true for spreadsheets, true for heavyweight PM suites, and the reason half the plans that should be charts live in someone’s head instead. It’s also the specific gap ganttchart.ai was built for: describe the plan in plain English — the same sentence you’d say in the meeting — and get back a real chart with tasks, durations, dependencies, and milestones, editable by dragging and shareable as a link, no accounts needed on either end. The ten-minute version of that process, including the paragraph-writing trick that makes the chart draw itself, is in our step-by-step guide, five finished charts with their prompts are in the worked examples, and the story of why we built the tool at all is in the case study.

And if you landed on “board” or “list” — genuinely, use the board or the list. A timeline you don’t need is just a prettier way to be behind schedule. The best shape for a plan is the one your team still believes in three weeks after you drew it.