Gantt Chart vs Kanban Board: Which One Your Project Needs

Use a Gantt chart when the project is defined by dates and dependencies: a fixed launch, a contract with milestones, a build where the roof cannot go on before the walls. Use a Kanban board when the project is defined by a steady stream of work whose order changes: bugs, feature requests, support fixes, content. The Gantt chart answers “when will this be done, and what slips if that slips?” The board answers “what is being worked on now, and where is it stuck?” Many small teams need the first question answered a few times a quarter and the second every day, which is why the common answer is a short milestone list plus a board.

What a Gantt chart shows

A Gantt chart is a bar chart laid over a calendar. Each row is a task or a group of tasks, each bar runs from its start date to its finish date, and diamonds mark milestones. NASA’s Schedule Management Handbook↗ (opens in a new tab) describes it that way, with a vertical line for the report date so you can see what should be finished by now.

The same handbook makes a point worth knowing: in its typical form, a Gantt chart does not show task dependencies, “so it is impossible to tell how one task slipping may affect another task.” The chart becomes a schedule only when the bars are linked. Scheduling software does this with dependency types; Microsoft’s guide to linking tasks in Project↗ (opens in a new tab) lists four, finish-to-start, start-to-start, finish-to-finish and start-to-finish, with finish-to-start as the default, and notes that once tasks are linked, every change to a predecessor moves its successors.

• Strength: it shows the whole timeline at once, and with links it tells you which tasks set the finish date. That chain is the critical path, and it is what you protect.
• Strength: it is the format clients, lenders and inspectors expect. A contract with dated milestones is easiest to discuss against a chart of those dates.
• Weakness: it is a forecast, and it goes stale the day reality differs. Someone has to update dates and durations, or the chart describes a project that no longer exists.
• Weakness: it says nothing about how much is in progress at once. Ten bars can overlap on one person and the chart looks fine.

What a Kanban board shows

A Kanban board shows work as cards moving through columns, such as To Do, In Progress and Done. It has no calendar. It shows where each item is, how many items are in each stage, and where they pile up. The idea comes from Toyota’s pull system, which the Toyota Production System↗ (opens in a new tab) describes as “making only what is needed, when it is needed, and in the amount needed,” with each process pulling from the one before.

For knowledge work, Kanban University’s Kanban Guide↗ (opens in a new tab) sets out the practices: visualize the work, limit work in progress, manage flow, make policies explicit, use feedback loops, and improve through experiments. It also names the measures a board makes visible: lead time, delivery rate and work in progress. None of them is a date on a calendar; they are how long work takes and how much is underway.

• Strength: it is always current, because moving a card is the update. There is no separate schedule to maintain.
• Strength: bottlenecks are visible. A column that keeps growing is a problem you can see before anyone reports it.
• Strength: reordering is free. The next item can change until someone starts it, which suits work that arrives unplanned.
• Weakness: it does not answer “will we hit March 15?” You can estimate from how fast cards usually move, but the board does not draw the timeline for you.
• Weakness: dependencies are invisible unless you write them down. Two cards that must happen in order look like any other two cards.

Gantt chart vs Kanban board, side by side

                  Gantt chart                 Kanban board
Main question     When will it be done?       What is happening now?
Shows             Dates, durations,           Status, work in progress,
                  dependencies, milestones    bottlenecks
Time axis         Calendar                    None
Dependencies      Links between bars          Not shown by default
Updated by        Editing dates               Moving cards
Handles change    Replanning the schedule     Reordering the queue
Best for          Fixed dates, contracts,     Ongoing streams: bugs,
                  sequenced builds            requests, support, content
Goes stale when   Nobody updates dates        Nobody moves cards

When a Gantt chart is the right tool

• The date is fixed from outside. A trade show, a regulatory deadline, a school term, a lease. Work backward from it and you need to see the whole chain.
• The work is heavily sequenced. Construction, events, hardware and moves all have steps that cannot start until others finish. A board hides this; linked bars make it obvious.
• Several teams or vendors hand off to each other. The chart shows who is waiting on whom, and when.
• Someone outside the team needs to sign off on the plan. Contracts, grants and client engagements usually expect dated milestones, and a chart is the common language for them.
• Resources are booked. If a crane, a venue or a contractor is available for one week, the plan has to be built around that week.

When a Kanban board is the right tool

• Work arrives continuously and its order changes. Bug reports, feature requests, support escalations, marketing requests.
• Most items are small and mostly independent. Each can be finished without waiting for a long chain of others.
• The team’s problem is too much at once, not a missed date. A board makes work in progress visible so you can limit it.
• You want status without a status meeting. Anyone can look at the board and see what is being worked on.
• AI assistants do part of the work. An assistant can move a card and leave a note far more reliably than it can maintain a schedule, and the board shows its work beside everyone else’s.

If you have chosen a board and are deciding how to run it, with cadences and roles or with continuous flow, that is a separate question, covered in Kanban vs Scrum.

Using both: a milestone list and a board

Most small projects do not need a full Gantt chart. They need to know the handful of dates that matter and what is being done this week. A hybrid that works:

1. Write the milestones as a short list with dates in the project plan: kickoff, design approved, beta, launch. Five to eight lines is typical. Add a dependency line only where one really exists (“beta needs the payment provider’s approval”).
2. Put the work on a board. Every task that moves a milestone is a card, and its note names the milestone it serves.
3. Once a week, compare the two. For each upcoming milestone, look at its open cards. If there are more than the time allows, cut scope, add people or move the date, and say which.
4. Draw a real Gantt chart only for the part that is truly sequenced, such as a vendor handoff or a launch week, and throw it away when that part is done.

The milestone list gives stakeholders the dates they need; the board gives the team the daily picture. A one-page plan with a milestone table, which is a good home for the list, is in the project plan template.

Milestone              Date                Depends on
Content inventory      October 16, 2026    -
Design approved        October 30, 2026    Content inventory
Beta on staging        November 20, 2026   Design approved
Launch                 December 4, 2026    Beta sign-off by client

Where fenbs fits, and where it does not

fenbs is a board, not a scheduler. It has no Gantt view, no due dates and no dependencies between tasks, so if your project is defined by a sequenced timeline, use a scheduling tool for that part. What fenbs does is the board half of the hybrid: four lanes, To Do, Next Up, In Progress and Completed; tasks of three kinds, feature, enhancement and bug; and a priority from 1 to 10, where 1 is the most urgent. A task has a note for the problem and a plan for how it will be done, so the note is the natural place to name the milestone it serves. Related tasks can be linked both ways, but a link records that they belong together; it does not block one on the other or move any dates.

AI assistants join the board over MCP as members with their own role, move cards and add notes, and History records who changed what. For the weekly comparison, Copy as Markdown copies the board so you can paste it next to the milestone list.