The "kanban vs Gantt" debate usually isn't really a debate about tools — it's two people answering different questions and assuming they're arguing about the same thing.
They answer different questions
A Gantt chart answers "when." It shows duration, sequence, and overlap on a timeline, and it's the right tool when deadlines and dependencies between dated work are the main constraint — launches, releases, anything with a hard external date.
A kanban board answers "what state is this in right now." It shows flow — what's waiting, what's in progress, what's blocked, what's done — and it's the right tool when the main constraint is throughput and work-in-progress, not calendar dates. Ongoing support work, content pipelines, and most day-to-day team execution fit this better than a timeline does.
The mistake is picking one and forcing everything into it
Forcing date-driven work onto a kanban board loses the sequencing information — you can't see that task C can't start until task A and B both finish three weeks from now. Forcing flow-driven work onto a Gantt chart produces fake precision: assigning calendar dates to support tickets or content drafts that don't actually have hard deadlines just creates a chart everyone learns to ignore.
Same data, different lens — that's the actual answer
The useful pattern isn't "choose kanban or choose Gantt." It's keeping one underlying set of tasks, statuses, and dependencies, and viewing it through whichever lens answers the question you're currently asking. Planning a release timeline? Look at it as a Gantt chart. Running the daily standup? Look at the kanban view of the same items. The data doesn't change — only the lens does.
This only works if both views read from the same underlying board instead of being separately maintained tools, because the moment you maintain a kanban board and a Gantt chart as two different artifacts, they drift apart and someone starts trusting the wrong one.
What to check before you pick
If you find yourself asking "is this on track" — you want Gantt. If you find yourself asking "what's stuck and why" — you want kanban. If you're asking both in the same meeting, you don't have a tool problem, you have a "two views of one dataset" problem, and the fix is structural, not a different chart.