Gantt or dependency graph? Why we merged the two
You have met both tools. The Gantt chart knows about time but hates change. The dependency graph knows about links but forgets the calendar. Each is half a picture, so we stopped making people choose.
The UnaTask team, Building UnaTask. Jul 6, 2026. 5 min read.
If you have ever planned a project with software, you have probably met the two classic tools, and probably been let down by both in the same week. On one side, the Gantt chart. On the other, the dependency graph. Each one is genuinely good at a thing the other one ignores, which is exactly why neither has ever felt like enough.
What the Gantt gets right, and wrong
The Gantt chart understands time. Tasks are bars on a calendar, longer work looks longer, and you can see the shape of a month at a glance. That part is great. The trouble is that a Gantt is built like a spreadsheet, so the moment reality changes it fights you. One task slips and you are dragging rows and retyping dates, and the links between tasks, if the tool has them at all, are buried in a dialog three clicks deep. It shows you time beautifully and then punishes you for time moving.
What the graph gets right, and wrong
The dependency graph understands relationships. Every task is a node, every link is an arrow, and you can finally see the shape of who is waiting on whom. That part is great too. But a graph floats in no particular calendar. The nodes sit wherever the layout put them, so a task due tomorrow and a task due next month look identical, and the one question everyone actually asks, when will this be done, has no answer on the screen. It shows you order and forgets time.
So you are stuck choosing. Take the Gantt and get time without flexibility. Take the graph and get relationships without a calendar. Most teams end up keeping both, in two tools, which is its own quiet tax.
The synthesis
We did not want to pick a side, so we built the thing in the middle. Tasks are cards, like nodes on a graph, and you draw dependencies by pulling a wire from one to another. But the cards are not floating in nowhere. They live on a real date axis, so where a card sits is when it happens, and how wide it is, is how long it takes. Time and relationships, on the same surface, at the same time.
Two rules keep it honest. You cannot draw a loop, because a plan where A waits for B waits for A is not a plan, it is a paradox, so the canvas refuses it. And a blocker can never end after the task it blocks begins, so when you stretch or move something, everything downstream slides to keep that true. The graph gives you the links. The axis gives you the calendar. The rules keep the two agreeing with each other.
The best tool is often the one that stops making you choose.
We are not claiming to have reinvented planning. Gantts and graphs both got something right, and we borrowed the good half of each. The point was never to add another view to argue about. It was to put time and dependencies in one place, so the plan tells the whole truth instead of half of it.