logo
ServicesNow & ThenAbout
Book a Consultation
team
process

Kanban: strategy or excuse?

"We stopped doing Scrum and switched to Kanban. The meetings took too much time, and we just want to get things done."

If I got a euro for every time I heard this during an intake...

The "Scrum Escape" Trap

I understand the sentiment. As a former software developer, I know exactly how frustrating it is to be pulled out of your 'zone' for a poorly facilitated meeting. But be warned: Kanban is not 'Scrum Lite'. In fact, if your team struggled with the discipline of Scrum, you might find Kanban even harder to master.

Why?

Scrum provides a framework that forces you to inspect and adapt (Sprint Review, Sprint Retrospective). If you remove those constraints without replacing them, you’re often left with nothing but a digital board full of tickets. That’s not an Agile way of working; that is just a to-do list divvied up in multiple columns.

Applying Kanban well actually demands discipline. It’s not about the board; it’s about managing flow.

Without at least these three elements, you aren't doing Kanban; you are just "busy":

  1. Hard WIP Limits (Work In Progress)

    Does your team truly dare to say "no" to new work because the limit has been reached? Or do you squeeze "just one more" in? WIP limits aren't there to annoy you; they exist to kill context-switching and force focus.

  2. Active Steering on Flow Metrics (Data over Gut Feeling)

    Now that you have ditched Velocity, start looking at Cycle Time (how long a task takes), Throughput (how much is finished), and Work Item Age (how long a task has been rotting in a column).

  3. Service Level Expectation (SLE)

    Can you say with 85% certainty: "If we start this item today, it will be finished in X days"? If not, you are not predictable.

Being busy vs. being effective

When teams drop Scrum because of "too many meetings" but fail to implement WIP limits or metrics, they fall into a Visibility Trap.

It feels like you are more productive because you are in less meetings, but without reflection and data, empiricism dies. You lose the ability to see where work is piling up, and you lose the chance to improve the system. You might be faster, building the wrong thing, and not even know it.

A Quick Reality Check

Tomorrow morning, look at your board and ask: "Do I see work piling up in any column?" If the answer is yes, you're not flowing; you're accumulating work.

Ready to stop being busy and start being effective?

I help teams move beyond "to-do lists with columns" to gain real control over their predictability and effectiveness. Let’s look at your data instead of just your opinions.

Feel free to reach out if you’re ready to professionalize your Kanban practice.

MvA logo© 2026 Martijn van Asseldonk

Built with Next.js, Chakra-ui, TypeScript and lots of ☕️

Services

Training