"We need to deliver faster." The board says the sentence in a quarterly meeting and everyone nods. Then the commercial director starts thinking about shorter quotation times, the operations director about less lead time in production, and the IT director about faster releases. All three are right and all three mean something different. That is not a lack of intelligence in the boardroom, it is a lack of layer. An ambition like "delivering faster" needs a vision (why speed matters now), a vision state (what the organization looks like once it has succeeded), a target (a concrete reference point) and a target state (the way of working that goes with it). Without those four layers, the board is talking in images, not in work.
At some of the companies that say "deliver faster," something concrete has already happened: drafting a quotation, routing a support ticket, summarizing a customer question before it reaches an employee — that work is now partly done by AI, with a human who approves or rejects it and does so with reason. At other companies, with comparable products and comparable customers, that is not yet happening. The difference rarely lies in the technology itself. It lies in whether the work was first broken down into tasks that are transferable, partly transferable with oversight, or inseparably human work. Companies that have never made that distinction keep repeating "deliver faster" as a wish without any capacity being freed up to deploy elsewhere.
Speed as an ambition rarely affects only one department. A readiness check looks at, among other things: whether processes are standardized enough to break down into tasks, whether data is available at the right place at the right moment, whether decision rights are clear when a task is partly automated, whether managers are trained to assess AI outcomes instead of performing the work themselves, whether governance is set up for oversight rather than execution, whether the technical infrastructure fits, whether change capacity is present to let new ways of working land, and whether measurement points exist to actually track speed. On each dimension the organization may be far along or barely have started. That difference is exactly where the delay comes from that the board feels but cannot name.
Delivering faster does not call for more people working harder. It calls for roles that may not currently exist or have not been named as such: someone who owns lead time per process, not per department; a role that assesses AI outcomes for quality before they reach customers; and decision rights assigned to whoever may reject the exception, not just to whoever may approve the standard. Without that translation back into roles, "deliver faster" remains a graph on a dashboard that no one feels responsible for. This concerns the organization of work, not the organization of personnel: whether and how job roles change as a result is a question with its own legal requirements and falls outside what a readiness check answers.
An ambition only becomes a target once there are confidence gates: moments at which you can determine whether the conditions are in place to proceed, not afterward whether it succeeded. For "delivering faster" that means, for example: has the process been mapped and broken down into tasks; is data available at the moment the task is performed; has an oversight role been set up that is not the same person as the one performing the work; is there a measurement point that tracks lead time at task level rather than department level; and is there a judgment on which part of the work is actually transferable. Comparable gates apply to other ambitions — with making international expansion measurable it is equally a matter of whether the organization has the conditions in place before the target is stated, not after.
Not a percentage of speed gain that no one remembers how it was measured. Rather, concrete signals: lead times that can be traced per task instead of estimated per quarter; a manager who can explain which part of the work is now done with oversight instead of entirely by hand; and freed-up hours that are visibly deployed on work that used to be left undone. That last point is the difference between an ambition that exists on paper and an ambition that has actually freed up capacity. The same logic applies to a merger or acquisition: there too, "integrate faster" only becomes a target once it is clear how you make the integration of an acquisition measurable on comparable eight dimensions.
Underneath "delivering faster" lies the same question every time: which work in this company can genuinely be taken over by AI, which part requires oversight, and which part remains human work. That question is answered task by task with the work scan from FTE TO AI. For those who first want to understand why the same words already cause confusion in the boardroom, there is the explanation of why people mean different things by the same words, and for those wondering what a target operating model concretely means, that is explained in plain words for a target operating model.
The free readiness check consists of eight short questions, one per dimension, and gives a picture of where the organization is furthest along and where it still lags behind. That picture is the starting point, not the final verdict. The full ambition check, with the four layers and the five confidence gates worked out for your own ambition, is under construction.
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.