10 Years with Kanban: Why Simplicity Still Wins
It’s not a productivity hack. It’s a philosophy about attention in a distracted world.
Originally published on my Blogger site on August 29, 2024. Preserved here on Substack.
Ten years ago, I started using Kanban by accident.
I didn’t read a manifesto. I didn’t get certified. I just felt like I was drowning in invisible work and needed a way to see the surface. So I opened Trello, made three columns, and started dragging cards.
That small act quietly changed how I think about work.
Over the last decade, the tools have changed; from Trello to GitHub Projects to Notion. But the shape has stayed the same. And somewhere along the way, I realized something important: Kanban isn’t really a productivity technique.
It is a philosophy about attention.
In 2024, when speed is mistaken for progress and every app is fighting for your focus, Kanban feels more relevant than ever. It doesn’t promise to make you faster. It promises to keep you honest.
What Kanban Actually Is (Without the Jargon)
At its core, Kanban is a system for managing flow. It originated on the Toyota manufacturing floor in the 1940s to visualize bottlenecks. The word literally translates to “signboard.”
That matters. The system assumes that if you can’t see your work, you can’t manage it.
Strip away the Agile coaching upsells, and you are left with three questions:
What am I working on?
What is next?
What is done?
That’s it. It doesn’t gamify your life. It asks you to confront reality. And frankly, that can be uncomfortable.
The Quiet Constraints
After a decade of using this personally and leading teams with it, I’ve stopped seeing Kanban as a board. I see it as a set of constraints that save us from ourselves.
1. The Power of “Visualizing the Invisible”
When work lives only in your head, everything feels urgent. Everything feels heavy. It’s a nebulous cloud of “stuff I need to do.”
The moment you put it on a board, the physics change. The chaos externalizes. You stop being the system and start observing the system.
You realize you aren’t drowning; you just have eight tasks. That is a solvable problem.
2. The Art of Limiting WIP (Work In Progress)
This is the hardest part. It is also the only part that matters.
Kanban forces a question most leaders avoid: How many things can I actually do well at once?
For me, the honest range is one to three.
When I have two active major tasks, I am in flow.
When I have five, I am just context-switching and creating anxiety.
Limiting WIP isn’t about being lazy. It’s about respect. Respect for the cognitive limits of the human brain. If you refuse to limit your WIP, you aren’t “hustling.” You are just deciding to do five things badly instead of two things well.
3. Intentional Flow
Movement from “To Do” to “In Progress” should feel deliberate. It’s a contract you make with yourself.
Before I drag a card over, I have to ask: What am I choosing NOT to do by starting this?
Kanban doesn’t just surface work. It surfaces tradeoffs. In a leadership role, that is your primary job. You can do anything, but you cannot do everything.
Kanban Beyond the Factory Floor
Most people associate Kanban with software devs or car parts. That’s a narrow view.
I use it for leadership responsibilities, creative writing, and even “life admin.” Why? Because all work is flow.
In a culture that is obsessed with “more,” Kanban quietly argues for “less, but better.”
It teaches patience.
It rewards completion over initiation.
It makes overcommitment visible instead of heroic.
Why This Matters in 2024
Work has become louder, faster, and more fragmented. We have AI generating tasks, Slack generating noise, and calendars generating conflicts.
Kanban doesn’t fight that with complexity. It counters it with clarity.
Make the work visible. Limit what you start. Finish what you begin.
I don’t use Kanban today because it makes me faster. I use it because it forces me to be honest about how I spend my attention. And that’s not a productivity win. It’s a life one.
If you’ve only used it as a project tracker, look again. Not as a system for output, but as a practice for focus.
It’s not about moving cards. It’s about respecting the limits of being human.
Resources
The Kanban Method: A Beginner’s Guide (Atlassian) – A solid, no-nonsense primer on the mechanics of the board.
The History of Kanban (Kanban Tool) – For the history buffs, a look at how Toyota turned “just-in-time” manufacturing into a global philosophy.
Introduction to Kanban (ICAgile) – A deeper dive into the core principles of flow and pull systems.