Gantt or Kanban: picking a view for client projects

Ask what the project's real constraint is. If it is a date, with dependent tasks and a firm deadline, use a Gantt chart. If it is a stream of tasks and the daily question is "what next?", use a Kanban board. Many client projects need both.

Agencies, consultants and small studios often pick a project view by habit. The view then shapes the conversations: a timeline makes people talk about dates, a board makes them talk about flow. Choosing on purpose saves a lot of status meetings.

Gantt and Kanban side by side

Question	Gantt chart	Kanban board
What does it show?	Tasks as bars on a calendar, linked by dependencies	Tasks as cards moving through columns
What does it answer?	Will the project finish on time, and what is in the way?	What is in progress, what is stuck, what comes next?
Planning unit	Dates and durations	Tasks and their status
Fits best	Fixed scope, fixed deadline, many hand-offs	Ongoing work, support, changing priorities
Main risk	A beautiful plan nobody updates	A busy board with no end date in sight
Client view	Easy to share as a timeline	Better kept internal, or simplified

How a Gantt chart works

Each task is a bar that starts and ends on a date. Arrows link tasks that depend on each other; the usual link is finish-to-start, where one task cannot begin until another is done. Milestones mark moments the client cares about, such as design sign-off or launch.

The longest chain of dependent tasks is the critical path. Any delay on it moves the end date; delays elsewhere may not. Knowing which tasks sit on the critical path tells you where an extra pair of hands actually helps.

A Gantt chart is strongest when it mirrors a clear project structure. The guide to a simple project structure of phases, work packages and tasks shows how to break client work into pieces a timeline can hold.

How a Kanban board works

A board has columns for each stage of work, often To do, In progress, Review and Done. Each task is a card that moves right as it progresses. Two ideas make it more than a to-do list:

• Work-in-progress limits. Each column allows a set number of cards. When In progress is full, nobody starts something new; they help finish what is there.
• Pull, not push. People take the next card when they have capacity, instead of having work assigned to an already full plate.

The number to watch is cycle time: how long a card takes from start to done. When it grows, something in the process is getting stuck.

Which view fits your client project

• A website or app build with a launch date. Gantt for the plan and the client conversation, because dependencies such as content, design and approvals drive the date.
• A monthly retainer. Kanban. The work is a stream of requests, and the question each week is what to do next within the hours agreed.
• An event or installation. Gantt, with milestones for every supplier deadline.
• Support and maintenance. Kanban, with a column for waiting on the client so stalled work stays visible.
• A fixed-fee project. Gantt for the scope and dates, plus close tracking of effort, since every overrun comes out of your margin. The guide to fixed fee versus time and materials covers how the pricing model changes the risk.

Using both without double work

1. Plan in the timeline. Set phases, milestones and dependencies once, at the start and whenever scope changes.
2. Run the week on the board. Pull this week's tasks from the plan onto the board and work them through.
3. Let the board update the plan. Task status should be entered once and show in both views. Two separate lists drift apart within a week.
4. Review weekly. Compare progress with the timeline and with the budget, and move dates openly when they slip.

Dates are half the picture; hours and money are the other half. The guide to project budget tracking for small teams explains what to watch alongside the schedule.

Mistakes to avoid

• Drawing a detailed Gantt chart for work nobody can predict, then spending more time updating bars than doing tasks.
• Running a Kanban board with no WIP limits, so In progress becomes a parking lot.
• Showing an internal board to the client, complete with every half-finished card.
• Keeping the plan in one tool and the tasks in another, so neither is ever true.

That last point reaches beyond the project view; the case for keeping clients, projects, time and invoices together is made in running a small agency on one app.

Frequently asked questions

Is Kanban better than Gantt for small teams?

Neither is better in general. Kanban suits small teams handling a steady flow of tasks with shifting priorities. Gantt suits projects with a deadline and tasks that depend on each other. Many small teams use a board day to day and a simple timeline for dated projects.

Can you use Gantt and Kanban together?

Yes. Plan dates and dependencies on the timeline, then run the current week's tasks on a board. The key is that each task's status is kept in one place and shows in both views.

What is a WIP limit?

A work-in-progress limit caps how many cards may sit in a column at once. It stops people from starting too many things and pushes the team to finish work before taking on more.

What does a project timeline view show?

It shows each task or phase as a bar across a calendar, with its start and end dates, the links between dependent tasks, and milestones. It is the quickest way to see whether the plan still meets the deadline.