What comes to mind when you hear the word"strategy"?
Ask an employee, and they'll probably tell you it's something distant and abstract, cooked up in a boardroom somewhere. Something to complain about, but not something they can actually influence.
Sit at the table with founders and business creators instead, and the picture changes completely. For this group, the day-to-day isn't a 9-to-5, ticket-by-ticket routine. It's calls, emails, rapid-fire observations, and high-stakes negotiations, back to back. They're not looking for a comfortable salary. They're looking for impact and results they can actually point to.
Facilitating strategy for this level of leadership takes a genuinely different approach than facilitating it for an operational or coordinating layer. Yet across the consulting world, plenty of coaches are still running strategy sessions like a magic show: dazzle the room, produce a vision, take a bow.
The real question is what happens after the show ends.
As a ProKanban trainer, I try to stay agnostic. My job isn't to sell a rigid framework, it's to help organisations build habits that support flow. I use Kanban as more than a tool. I use it as a strategy, a philosophy that guides decision-making without being overly prescriptive about the "how".
Kanban is usually associated with service and manufacturing work, but it's flexible enough to work at every level of an organisation, from a single innovation project through to corporate-wide alignment.
So how does the Kanban strategy actually support an organisation's wider business strategy? I'm not trying to swap one piece of consulting sorcery for another. The goal is a strategic plan built on three pillars
The first phase of most corporate strategy work is a familiar ritual: defining the organisation's Values, Vision, and Mission.
The problem is that this exercise usually turns into a game of buzzwords with very little intention behind it. Values like"Entrepreneurship" go up on the wall, which is a trait you'd already expect from senior leadership in a for-profit business. Putting it on a poster doesn't change how the system actually functions.
If Kanban is going to support real strategic thinking, the focus needs to shift to system-wide health. A useful lens for this is W.Edwards Deming's 14 Points for Management. These aren't just a checklist. They force an organisation to answer two questions:
● Where do you hope to be in five years' time?
● How will you get there? By what method?
Answering these questions systemically is the firstreal step towards change. Once a leader sponsors that kind of strategy, action becomes the only logical next step.
The power in these 14 points is that they're deeply connected, and frequently in tension with each other. They force leaders to stop looking at their departments as silos and start thinking systemically. A facilitator can use this tension productively during an executive offsite("How can we meaningfully pursue point 14 if we're actively failing at point 8?"), but boardroom alignment is only the beginning.
If I had to put Kanban simply, I'd say this: you rollup your sleeves and participate in the success of the whole system, not just your own piece of it.
The real breakthrough happens when this thinking cascades down from leadership into every layer of the business. Deming's 14thpoint, “Involve everyone in the transformation”, is a reminder that a systemicmindset can't be a luxury reserved for the executive suite. Strategy onlysucceeds once people stop defending their own silo and start participating inthe wider effort.
When front-line staff and mid-management both understand how their daily decisions affect the rest of the business, the organisation becomes genuinely resilient. The output of your strategy discussions shouldn't just be a list of goals. It should be a clear plan for how this whole-system mindset gets nurtured and lived across every rank, everyday. Once that mindset is in place, the next milestone is turning it in to measurable action.
A strategy that only exists on paper is useless if the organisation can't actually execute it. This is where Kanban's operational thinking meets high-level strategy directly.
The Kanban Guide boils this down to three core practices, aimed at three core goals:
Core Practices
Flow Goals
1. Define and visualise the workflow
1. Efficiency
2. Actively manage work in the workflow
2. Effectiveness
3. Continuously improve the workflow
3. Predictability
Applied to corporate strategy, these practices push a leadership team to check how their daily reality actually maps to their grandvision.
● Define and visualise the workflow. Is our current workflow supporting our strategic direction, or actively workingagainst it? If the strategy is to innovate rapidly, but the operationalworkflow requires six layers of bureaucratic approval, the workflow is defeating the strategy.
● Actively manage the work. Are we actually managing our strategic initiatives, or treating strategy as a quarterly status update? Leaders need to collectively manage the flow of strategic initiatives, and keep them from being choked by excessive Work in Progress at the executive level.
● Continuously improve the workflow. Are we capturing what we learn from our strategic successes and failures, and feeding it back into how we operate as a business?
Viewed through efficiency, effectiveness, and predictability, strategy stops being an abstract concept discussed once a year at an offsite resort. It becomes a tangible process. But building an actionable workflow is only half the job. The system also needs to sustain itself, and adapt as conditions change. That's where the third pillar comes in, and it's the subject of Part 2.