The objections, and what answers them

Written by a person. Last read by a person on 2026-09-07, 1 day ago. Its facts were checked by the eval suite on 2026-09-07.

You are about to argue against the strategy, or you want to know which objections it already answers.

Scenario-based sample. Halden Systems is invented, and so is every figure about it.

Two kinds of number appear below. Figures about Halden Systems and its staff come from data/survey.yaml and data/scenario.yaml, and are invented for a fictional company. Figures credited to DORA, Stack Overflow, McKinsey or PwC are real, were read on 2026-09-07, and are recorded in data/literature.yaml. They are never mixed without being labeled.

Bottom line. 3 objections arrive every time, all reasonable, and two of them are partly right. None of them changes the recommendation, and the answers are below.

Every strategy of this kind meets the same 3 objections, all of them reasonable, and two of them partly right. Each is answered below with the evidence rather than with reassurance.

"We do not need a study. We need to start."

This is the strongest objection and it deserves the strongest answer.

We are not proposing to wait. We are proposing to start on day one and hold the money until day sixty.

The pilot runs from day one. It already exists and costs nothing to begin. Eight other things start in the first week, and every one of them is listed below. Nothing is on hold except the spending commitment, which is the only decision that gets harder to reverse.

The external evidence

88 percent of organizations have adopted AI. 6 percent report real value. That is the action-first path, measured across the whole market by McKinsey in 2025. Two thirds have not begun to scale it. The difference between 88 and 6 is not who moved fastest.

Developer AI use went from 76 to 84 percent in one year. Distrust of its accuracy went from 31 to 46 percent. More adoption, worse outcome, same 49,000 people. Doing more of the same thing is not the missing ingredient.

The same investment returns 278 percent or 27 percent depending on documentation quality. That is DORA on version control, and the pattern repeats across every practice they studied. Acting before checking the precondition wastes the action rather than accelerating it.

The internal evidence, which is harder to argue with

Scenario figures from here to the end of this section.

We have already run this play three times.

Three migrations, each with a demonstration, a recording and a channel. 29 percent rate the training useful. Around $410,000 a year goes to regional training bought twice because waiting for a central answer cost more than paying locally.

The bias for action has already been exercised here. That is the invoice.

One more thing worth saying out loud

You get one credible relaunch. A second attempt at the same population meets more resistance than the first, because people remember. Choosing wrong in week one means defending it for two years.

"30 days for a survey is too long."

Correct, and the plan changed rather than being defended. There is real evidence on day fifteen, and the table below shows how it arrives that early.

The pulse is 6 questions open for 7 days, which is short enough that people answer it. The long instrument is a second pass that deepens the picture, and by the time it lands we have already been acting for a month.

"This is a training problem. Buy training."

Partly right, and the part that is wrong is the expensive half, because it buys more of the thing the organization already has too much of.

Completion is already at 78 percent. Understanding is at 31. We can buy more completion and it will change nothing, because completion was never the thing in short supply.

16 percent say a reward for finishing a course would motivate them. The population has worked this out already.

What starts in week one

Nine things start immediately, none of which waits for the survey to close or needs a budget line approved first.

1. The runbook pilot, at 1 site with a local expert and one without. That comparison is what the scaling case will need.
2. Stop reporting completion. While the dashboard says 78 percent, nobody believes there is a problem.
3. Cancel one competing initiative. Two thirds of staff report more changes than they can absorb. Removing one is the only credible way to say this matters.
4. Publish a checkable commitment on roles. A date, a scope, and notice. Not a reassurance.
5. Name local experts at the five stranded sites, with time in the role rather than a favor asked.
6. Open a wrongness log for cases where the assistant was confident and wrong. Turns private burns into shared knowledge.
7. Senior people ask basic questions in public, weekly, in writing.
8. Change the question managers ask from "did you finish it" to "what did you get stuck on".
9. Pull the existing data. Tickets, interruptions and regional spend are sitting there already.

Five of those nine, items 2, 3, 4, 7 and 8, are decisions rather than projects, which means they can be made in an afternoon by somebody who already has the authority to make them.

What we deliberately do not do fast

We do not take the regional training budgets. That $410,000 is the most obvious saving in the case and it is the one that would cost us the 5 site directors who decide whether this reaches their people.

They buy locally because waiting for a central answer costs them more. They stop when something arrives faster than their own purchasing does, and not before.

We do not sign a vendor inside 90 days. A response window is 40 days and reference calls run longer. A plan that ends in a signature tells anyone who has bought software that we have not.