Your project already has a shape

You open a new project and the first thing the tool wants to know is how you’d like to organize. How many columns? What should they be called? Does “Review” come before or after “Testing”? Do you need a “Blocked” lane? Labels? Custom fields? Automation rules?

This is the setup ceremony. It has a certain warmth to it - you’re making decisions, building structure, and the organizing feels like progress. Twenty minutes pass and the structure is ready. The work it was built for hasn’t begun.

The ceremony is so normalized it barely registers as a cost. You watch tutorials for it. You have opinions about it. Underneath the familiarity, though, sits an assumption worth examining: that managing a project means sorting work into parallel stages, and that defining those stages is where you naturally start.

The grid and the line

The kanban board borrows its metaphor from the factory floor. Stations, queues, cards moving left to right. The system’s job is to show you where things are accumulating.

This works well for parallel streams with shared bottlenecks. A product team shipping features across design, engineering, and QA. A support desk triaging tickets. Anywhere the question is “where is this stuck?”

A freelancer redesigning a website is doing something else entirely. Discovery becomes wireframes. Wireframes become design. Design goes to the client. Feedback returns. Revisions happen. Then build. Then ship. One thing becomes the next, carried by the grain of the work itself.

The shape of this work is a line. It always was.

What a chain shows you

Something becomes visible in a sequential view that columns can’t show you. The chain of completion - whether each piece of work grew out of the one before it, or whether something was skipped.

When the chain is intact, the connections between tasks are solid. When something got completed out of order, the break is visible. The chain shows it without judgment - a fact about the sequence, something worth knowing.

Completed work settles. Several done tasks in a row compress into a stack - still present, still accessible, but no longer claiming the space of what’s ahead. You don’t archive things. Finished work recedes on its own, the way it does in your mind.

This is where the thinking kept arriving when we were building Balladic’s flow view. What happens when a tool shows you the shape of your work instead of asking you to build one.

When your work genuinely has parallel stages, columns are there. The quiet surprise, using it ourselves, was how rarely that turned out to be the case. Most projects were lines. The shape was always there. We’d just been too busy building containers to notice.