An organization changes as quickly as the slowest of the four layers between vision and execution allows: vision, vision state, target and target state. It is not ambition that determines the pace, but how quickly that ambition can be translated into what people do differently tomorrow.
Most boards do not underestimate this because they are naive, but because they judge change on a single layer: the announcement. That can be ready within a week. The rest of the process — from intention to workable pattern — structurally takes longer, and that difference can be made measurable instead of merely felt.
A board of an organization with 50 to 300 employees often decides on a change of course within a quarter. The vision is on paper, the management team is convinced, the newsletter has been sent. That feels like change, but it is the top layer: the vision. The vision state — how that vision translates into a concrete picture of the organization in two years' time — is often still completely absent at that point. Without that intermediate step, the announcement remains an intention, and intentions do not change anything about a planning process, a customer conversation or a production line.
The pace of real change is determined by how quickly the target state becomes concrete: which working methods, roles and decisions look different once the new course is set. This is the layer where most delay arises, not because people are stalling, but because no one has recorded exactly what is changing. An organization that states "we are becoming more customer-oriented" has a vision. An organization that knows this means the service team may now make price agreements themselves within a certain bandwidth has a target state. The first can be decided in an afternoon. The second requires a check on what that means for authority, systems and evaluation — and that is exactly where a double check across eight dimensions shows its value: not to slow down the ambition, but to show on which dimension the translation is still missing.
Boards that only inform the entire organization after the target state has already been fixed lose time elsewhere: at the point of acceptance. An ambition round in which the organization thinks along before the target state is recorded costs more time at the start, but saves the time that would otherwise go into resistance, reinterpretation and separate conversations afterward. That is also where how do you involve the workfloor in a strategy without endless discussion becomes relevant: organizing involvement without the process itself becoming the delay you were trying to prevent.
A mid-sized manufacturing company that wanted to take on a new market position noticed this directly: the management team was convinced within a few weeks, but three months later the operational layer still did not understand which decisions they were now allowed to make themselves. Those three months were not resistance — it was a gap between vision and target state that no one had noticed because there was no fixed check in place for it.
An organization that pushes through a change too quickly without going through the five confidence gates usually does not get stuck at the start but at the third or fourth step: the moment it becomes clear that the capabilities are not there, or that the systems do not support the new way of working. Every gate that is skipped comes back later as remedial work, and remedial work is always slower than the original step would have been. What is often missing at that point is visible in which capabilities does my organization need for this ambition: not the question of whether the ambition is good, but whether the organization has the skills and capacity to execute it at the planned pace.
The speed of a change cannot only be judged afterward. There are signals along the way that show whether a change is taking hold or getting stuck, described in what are early signals that a change is taking hold, and those signals are often visible sooner than a board expects — sometimes within just a few weeks of the first step into the target state.
The question "how fast can we change" is actually the question "which layer have we not yet made concrete". A test of six questions about the four layers, is your vision steerable, shows in a few minutes where the delay is likely to occur before the process itself causes that delay.
The next step, after the test, is the translation into capabilities: which roles and tasks the target state requires, alongside what capacity and skills are already present today. That difference in hours — between what the new course requires and what the organization can currently deliver — is worked out in the work scan on ftetoai.com.
Vertel wat u wilt bereiken, dan kijken we samen wat daarvoor moet staan.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.