The capabilities you need do not follow from the ambition itself but from the target state that underlies it: the concrete situation over a fixed period, worked out in what the organization must then be able to do. Without that translation step, "capabilities" remains a word on a slide instead of a list you can steer by.
An ambition such as "market leader in the mid-market segment" or "fully data-driven working" says nothing about what needs to change internally. That is also precisely the difference between a goal and an ambition: a goal is measurable and time-bound, an ambition is a direction. You link capabilities to the goal, not to the direction. A manufacturing company with 120 employees that "wants to grow internationally" gains nothing from that sentence. Only once the target state describes that sales will take place in two new countries within three years, at what volume and through which channel, does it become visible whether there is a need for export expertise, multilingual customer service, or a different kind of supply chain planning.
The vision describes the long-term direction, the vision state the picture of that over a longer horizon, the target the measurable goal, and the target state how the organization stands on a fixed date. Capabilities belong to the target state, because that is the layer where tasks, roles and work processes become concrete. A healthcare institution with 200 employees that has as its target "20% less administrative time per care provider" sees in the target state which way of working is needed for that: different input at the source, a different kind of coordination role, perhaps a different meeting structure. Those three things are the capabilities. Without the intermediate step of the target state, the goal and the means blend together, and projects arise that touch the KPI without changing the underlying way of working.
To see whether your own direction is already sharp enough for this translation to be possible, there is the free test "is your vision steerable": six questions about the four layers that show within a few minutes where the picture is still too vague to derive capabilities from.
A target state that only holds up on paper produces the wrong capability list. That is why the target state is tested along eight dimensions — including customer, process, people, technology and money — and simultaneously along five confidence gates that measure how certain the organization is that this is achievable within the set time. A trading company with 80 employees that had written a target state around "fully automated order processing" turned out to score low on the confidence gates on the people dimension: there was no clarity on who would keep handling the exceptions. Without that check, the capability list had been written on an assumption that did not hold. With the check, it became clear that not only a system capability was needed, but also a smaller, ongoing role for handling exceptions.
Capabilities that are named only by management often miss the picture of what is or is not already possible on the work floor. The ambition round involves the entire organization, which does not mean that everyone is spoken to individually: it concerns a structured way of gathering input without this turning into a series of meetings, as described in how you involve the work floor in a strategy without endless meetings. At a logistics company with 150 employees, that round revealed that the planned capability "new planning software" would deliver little as long as the existing scheduling logic on the floor worked differently than was assumed in the office. That information does not come from a management meeting, but from the people who do the work daily.
Naming a capability on paper is no guarantee that it will actually materialize. Whether a change in working method is truly taking hold can be seen from early signals, as described in what early signals are that a change is taking hold — think of spontaneously using new terms or employees proposing improvements themselves without being asked. How quickly a capability can be built up depends on how accustomed the organization already is to change, on the complexity of the role, and on the available capacity to learn alongside ongoing work.
The capability list itself is the starting point, not the end point: the next question is how much of the named work is already being done today, by whom, and in how many hours. That translation back — the roles and tasks the target state requires, alongside the staffing already in place — is precisely what the work scan on ftetoai.com is meant for, and it shows the difference in hours between what exists and what the ambition requires.
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.