Executive readout: the capability gap

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

You have five minutes, or you want to see what survives compression.

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

Bottom line. $2.1M over three years, against a capability gap costing $6.1M a year. The decision asked for today is funding, this quarter.

Two kinds of number appear below. Figures about Halden Systems are invented, and come from data/scenario.yaml and data/survey.yaml. Figures credited to DORA, Stack Overflow, McKinsey or PwC are real, were read on 2026-09-07, and are recorded in data/literature.yaml.

Open the built deck, built from the specification in the presentation standard. It opens in a new place rather than on this page, and that is a decision rather than an oversight. This site promises that nothing third-party loads on it, and an embedded deck would make that promise false on the page carrying it. A link costs one click and costs the promise nothing.

9 slides for the COO, around day 65. The strategy document is the argument; this is the version that survives a thirty-minute meeting with a finance review after it. Everything that is not a decision is in the appendix, and the appendix is a separate file on purpose. A deck that contains the strategy document is a strategy document nobody read.

What follows is the script behind those slides: what is on each one, what the speaker adds, and what is deliberately absent.

Slide 1. The ask

We are asking for $2.1M over three years to close a capability gap that costs us $6.1M a year.

The decision today: fund it this quarter, or tell us to keep absorbing the cost.

Procurement is already in flight. No vendor contract is signed, and none will be inside these 90 days.

Speaker note: the amount and the decision go on the first slide because an executive who has to wait 6 slides to learn what is being asked spends those 6 slides guessing.

Slide 2. What is actually broken

78 percent can follow the steps. 31 percent can say what the steps do.

Four years ago we moved most non-engineering work into engineering systems. Every move was run as a tooling rollout. The tooling arrived and the capability did not.

Our dashboard reports the 78 and calls it success.

Slide 3. What it costs to leave alone

Every figure is already in a calendar, a budget or a queue. None of it needs a new measurement, and none of it is a projection.

Slide 4. Where the value is, in order of size

Revenue. Six solution-engineer days per enterprise customer, 240 customers a year. 95 partner implementations that need certified partner staff.

Cost. $5.7M in engineer time. $410,000 in duplicate spend.

Efficiency. 41 median days to a first merged change, and 58 at the sites with nobody to ask. The pilot runs at nine.

Speaker note: revenue opens the room because it is the largest number. Say the next line out loud, because somebody in the finance review will say it first if we do not.

Slide 5. The number we will not defend

Revenue attribution for an internal program is the weakest evidence we have.

We lead on it because it is the largest, and we rest the case on cost and efficiency because those are the ones a skeptic can check without our help.

Every learning function that has overclaimed revenue has been caught doing it. We would rather be the one that said so first.

Slide 6. Why more training will not fix it

Four findings, each ruling something out.

• One program for everyone measurably degrades the experts in it.
• Proximity to help predicts capability better than role does. Our own gap between sites with and without a local expert is 22 points, wider than the gap between job families.
• Recordings teach the steps and skip the thinking, which is exactly the population we have.
• Paying people to finish courses buys finished courses. We are at 78 percent completion already.

So the incentive is built on contribution, not completion.

Slide 7. AI is a chapter, not a second program

71 percent have used the assistant. 38 percent would sign their name to its output. 22 percent can tell which answers need checking.

That last figure is the skill, and it is the one nobody measured before rollout.

McKinsey: 88 percent of organizations have adopted AI, 6 percent capture real value, and the gap did not move between 2025 and 2026.

A strategy about a tool expires with the tool. This one absorbs the next arrival instead of being rewritten for it.

Slide 8. How you will know it worked

And how you will know it failed. Escalations do not fall within two quarters of a site going live. Failure also looks like completion rising while understanding does not, which means we bought more of the metric that is already full.

Slide 9. The decision

Fund $2.1M over three years, this quarter.

What the money buys. A platform, and 2.5 people. The platform is bought because we have no advantage in that market. The content is written here, because the content is the capability: a content lead holds the standard, and the team that owns each engineering system owns the pages about it. The 9 local experts run the program and do not write it.

What you get in 90 days: the funding decision made, procurement in flight, the pilot running, and a named owner on the promise that the assistant will not cost anybody their job.

What you do not get: a signed vendor contract. That is deliberate.

If it cannot be run by somebody who did not design it, we will tell you and stop it. The kill criteria are in the scaling proposal, and they are ours rather than yours to enforce.

Appendix

Kept separate so the deck stays 9 slides. Reach for these only if asked.

• A1. Survey instrument, sample and response rates, including the items inconvenient for the program. data/survey.yaml.
• A2. The 22-point site confidence gap, by site.
• A3. Three-year total cost of ownership, and the build-against-buy analysis.
• A4. The evaluation matrix, with weights fixed before any vendor was named.
• A5. The literature review, and the one claim we refuse to cite.
• A6. What we are deliberately not solving, and why each was cut.