Your board probably does agree on the vision and disagree on what that vision means for the organization tomorrow. That difference is exactly where the discussion breaks down, and it can be resolved by layering the vision instead of squeezing it into one sentence.
In a board meeting, everyone nods along with the mission. Growth, customer focus, becoming market leader: no one is against that. The problem sits one layer deeper. The commercial director reads "customer focus" as more customization and shorter delivery times. The operations director reads the same word as stable processes and fewer exceptions. Both agree on the vision and completely disagree on the consequences. At a company of roughly 150 employees, you see this reflected in two departments that both act "according to the strategy" and yet make opposite decisions. That is not a communication problem to be solved with an extra meeting. It is a structural problem: there is no layer between the vision and the daily choices.
It helps to develop the vision in four steps: the vision itself, the vision state (what the organization looks like in three to five years if the vision becomes reality), the target (the concrete goals that follow from it) and the target state (what the organization specifically looks like once those goals have been achieved). As long as a board only talks at the level of the vision, everyone keeps being right, because abstract language allows for every interpretation. Once the vision state and the target state become explicit, the commercial director must translate his interpretation of "customer focus" into a concrete picture of what the organization looks like then, and that picture can be placed alongside that of the operations director. It often turns out that our vision is too vague, how do I make it concrete is not so much a wording problem, but a lack of an intermediate layer where that concreteness needs to land.
A board that sets a target state in isolation risks building a consistent vision that no one in the organization recognizes. An ambition round in which several layers of the company take part exposes a different kind of difference: not just where the board members differ among themselves, but where the board as a whole diverges from what the organization itself considers possible or desirable. At a company of 50 to 300 employees, that knowledge often sits with team leaders and senior specialists who run into practical reality every day. Their input in the ambition round prevents the board from setting a target state that is consistent on paper but immediately creates friction in execution.
A board that has finally reached agreement does not want to reopen that discussion. Yet agreement is no guarantee that the target state is also correct. A check on eight dimensions verifies whether the four layers are mutually consistent: does the target align with the vision state, does the target state align with the target, and so on throughout the organization. Five confidence gates check something else, namely whether each step is sufficiently substantiated to serve as a basis for the next one. That distinction is exactly where many board discussions get stuck: is this goal logically derived from the vision, or is it an assumption that no one has tested out loud? The same double check is also what how do you make a vision measurable is about: measurability is not created by attaching a KPI to an ambition, but by making the layers in between explicit.
Sometimes the board does agree, but the departments' goals work against each other as soon as they are executed. Sales wants speed, finance wants certainty, operations wants stability, and all three can be right within their own objective. That is a different issue than a lack of agreement at board level, and it calls for a different approach, which is worked out in what to do when department goals work against each other. Anyone unsure whether the problem lies within the board or between the departments can clarify this with the free test "is your vision steerable": six questions about the four layers that show in a few minutes where the layer is missing that is locking up the conversation.
It starts with making the four layers visible instead of continuing to hold the discussion at the level of the vision. After that, the capability back-translation is the next step: the roles and tasks that the target state actually requires, placed alongside the roles and tasks that already exist today. Once that difference becomes concrete, the difference in hours also appears, and that is exactly where the workload scan on ftetoai.com takes over.
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.