And how translation sessions can change that

Why your strategy doesn't land in the organization

I regularly visit organizations where the management has done good strategy work. Clear choices on paper. A logical story. Beautiful language.

And yet: weeks later it feels like nothing has changed.

Not because people are "against". Not because they don't understand. But because strategy often does not fail on content. She fails on landing.

The tipping point

That moment is always the tipping point for me. Because that's where you see the biggest misconception that managers make: they think that deciding and communicating automatically leads to execution. As if a strategy is a kind of software update that you install centrally and then run automatically for everyone.

But organizations don't work that way. People don't work like that.

What really happens after the announcement? Teams go back to their reality. Customers, deadlines, incidents, targets. And if the strategy there does not clash very concretely with the old behavior, usually nothing changes.

Four conditions for a strategy to land

In conversations, I always hear the same questions: "What does this mean for us?" and "What should we do differently on Monday?" Among those questions are four conditions that almost always make the difference.

 

Brightness. Can people retell the strategy without everyone making their own version of it? If words like "customer-oriented" or "focus" remain elastic, you get strategy as an interpretation game.

 

Relevance. Do people feel that this is about their world, not about a slogan? A strategy that doesn't link to real frictions in customer value or collaboration feels like extra work on top of the real thing.

Feasibility. Do teams believe this is realistic with the time and resources they have? If not, you will get cynicism from exactly the people you need.

 

Support. Can people support it, even if they don't think it's perfect? The best question I learned for that: "What do you need to be able to support this?"

This is not a communication problem

You don't solve any of those four with another presentation. These are not communication problems. These are translation problems. And that's exactly where the lever lies.

Strategy cascade

The strategy cascade: translation sessions at every level

What we do in practice, in addition to the classic communication or roadshow, is organize a strategy cascade. A series of translation sessions in which each level in the organization translates the strategy into its own reality.

The principle is simple. You let the direction seep through at every level: first the departments or business units, then the teams and in the case of the real toppers also the translation to an individual level.

In every translation session, teams ask themselves the same key questions: What does this mean for us? What can we contribute? What behavior do we stop, what behavior do we start and which decisions do we make faster from now on?

What that yields

Translating the strategy locally ensures anchoring at three levels. Leaders can manage more precisely, with shared language and expectations. Teams develop a sharper picture of their role in the bigger picture. And employees gain insight into how they want to develop themselves towards the future, linked to where the organization is heading.

You make teams not only recipients of the strategy, but co-owners of its meaning. You don't ask them "do you understand?", but "how are you going to notice it with us?" And that is exactly the tipping point where strategy stops being a story from above and becomes a working system in daily work.

Do you want to know what the strategy cascade looks like in practice?

We help management teams to make clear choices together and to make those choices land at every level. Schedule a short intake and together we will map out your context.

Pieter Daelman CEO and co-founder, Bedenk

Interested? Contact us!

Is your innovative muscle stimulated? Then don't hesitate to contact us!

contact