The Intentional Approach to Organisational Change (and Why Reactive Never Works)

Key takeaways

• Organisational change works when it's deliberate and sequenced, not a pile of one-off initiatives bolted on whenever something breaks.
• The reactive pattern (a workshop here, a new tool there) burns budget and goodwill because nothing connects to anything else.
• No single program fixes culture or performance. The fix is usually a combination of things, done in the right order, with foundations first.
• Every workplace is different, so the diagnosis matters more than the framework. Read the room before you reach for a solution.
• Happier, more accountable teams aren't a side effect of doing more. They come from doing the right things, on purpose, as one joined-up plan.

A potential client said something to me recently that made me stop mid-sentence.

"I get a lot of people trying to sell me their wares. What makes your program any different?"

Fair question. Harder to answer than it sounds, because I'm not selling a single program. And honestly, if I were, I'd be part of the problem she was describing.

Why the reactive approach quietly fails

Here's the pattern I see over and over. Something goes wrong. Engagement scores dip, a good manager quits, two teams stop talking to each other. So the organisation reaches for the nearest fix.

A resilience workshop. A new performance tool. A values poster in the kitchen. Each one sounds reasonable on its own. None of them are connected, and none of them address why the thing broke in the first place.

I worked with a business a while back that had run four separate "culture" initiatives in two years. Four. Each one launched with good intentions and a launch email, and each one faded within a quarter. Staff had stopped believing anything would stick, which meant the fifth idea, no matter how good, was already dead on arrival.

That's the real cost of reactive change. It isn't just wasted money. It's the credibility you spend every time you start something and let it drift. People remember. The next time you say "we're going to do things differently," they nod politely and wait for it to pass.

What an intentional approach to organisational change actually looks like

The real goal is moving an organisation away from reactive, one-off initiatives and towards a structured, deliberate plan for improving culture at every level.

That sounds tidy on paper. In practice it starts with a diagnosis, not a solution. Before I recommend anything, I want to understand where the actual pressure points are, and in what order they need attention.

I've spent 20 years watching how people behave at work. I see the same patterns come up again and again, but they show up in different combinations, at different times, and the symptoms don't always look the same. Low engagement in one business is a management problem. In another, it's a broken bonus structure. Same symptom, different cause.

So the fix might be leadership development, technical skills training, clearer roles and accountability, better performance measures, stronger systems, improved communication, or a structural change. Often it's a combination, done in a deliberate sequence.

This week alone I drafted an enterprise-wide capability plan for a board, proposed a restructure with accountability built into the design, and redesigned a set of performance measures so they'd actually be useful and tie back to strategy. Three different clients, three different problems, and not one of them needed a leadership workshop as the first move.

Order matters more than effort

If I had to name the single most common mistake, it's this: organisations try to do everything at once, or they do the visible thing before the foundational thing.

You can't build accountability on top of roles nobody understands. You can't run a leadership program for managers who've never been given a clear remit. You can't measure performance sensibly when the measures aren't tied to what the business is actually trying to achieve. Foundations first, every time.

Think about it like renovating a house. You don't hang the artwork before you've fixed the wiring. It might look finished for a photo, but you've built something that fails the moment you flick a switch.

Here's the sequence I tend to work through with a client:

• Understand the business and its strategy. What are we actually trying to achieve, and what's genuinely in the way?
• Get the foundations right. Roles, accountability, and the basic systems people work inside every day.
• Fix the measures. If you're rewarding the wrong things, nothing else you do will hold.
• Build capability. Leadership and skills development, once there's a clear structure for it to land in.
• Keep adjusting. Some of it is an experiment that needs tweaking as you go. That's normal, not a failure.

None of that is glamorous. It's just the difference between change that sticks and change that becomes the fifth dead initiative.

But doesn't everyone sell a framework now?

They do, and I understand the temptation. Every consultant these days seems to have their own branded framework, mostly because a marketing guru told them they needed one to look credible.

The trouble is that frameworks rarely leave room for simplicity, or for a solution that fits the one organisation sitting in front of you. A framework is a shortcut for the consultant, not the client. It lets you skip the reading-the-room part and jump straight to the deliverable.

And while AI takes some of the load off my week, it still can't replace years of reading the room. It can't pick up the nuance of each organisation the way real practice across cultures and generations can. It's a brilliant assistant. It's a poor substitute for having sat in enough rooms to know when the thing being said isn't the thing that's actually wrong.

That's the whole idea behind our consulting work. I'd rather understand your business properly and recommend the right tool at the right time than sell you a program and hope it fits. There are no shortcut suggestions once you genuinely understand a team.

What you get when the plan is joined up

I work with clients to figure out where their resources are best spent. That means long-term relationships, because you can't diagnose a culture in a single visit, and you can't sequence a plan you don't understand.

The outcomes are pretty consistent. Higher engagement. More collaborative teams. People who are, quite simply, happier at work. And happy people perform better. Every time.

The organisations that get the best results aren't the ones doing the most. They're doing the right things, in the right order, as part of one plan that actually holds together. It's less activity and more intention, which feels counterintuitive right up until you see it work.

That's also the thinking behind Whyser Work, our platform for the employee side of the equation. The experience your people have every day is the real measure of whether the plan is landing, not the number of initiatives you've launched.

Frequently asked questions

Isn't a single leadership program a good starting point?

Rarely, and not as a first move. A leadership program lands well when there's already a clear structure, defined roles, and accountability for it to reinforce. Drop it into a business with muddy foundations and it becomes another well-meaning initiative that fades. Diagnose first, then decide whether leadership development is genuinely the right next step.

How is intentional change different from just having a strategy?

A strategy tells you where you're going. Intentional change is the sequenced plan for getting there, foundations first, the right tool at the right time. Plenty of businesses have a strategy and still change reactively, reaching for quick fixes whenever something breaks. The difference is discipline about order, not the existence of a document.

How long does this actually take?

Longer than a workshop, shorter than you fear. It depends on where the foundations sit and how much reactive debt has built up. I work in long-term relationships because sequencing matters and trust takes time. But you'll usually feel the difference early, once people see that this plan connects and the last four didn't.

So maybe the better question isn't "what's your program." Maybe it's this: if you stopped reaching for the next quick fix, what would you actually need to build first?