Your Slowest AI Use Case Is Pricing All the Others

Speed and regulatory readiness are not a trade-off. Treating them as one is a sorting failure.

In March 2026, the financial industry was handed a seventeen-item answer to a question most firms had been asking backwards.

The MindForge consortium — two dozen banks, insurers and capital-markets firms convened under the Monetary Authority of Singapore — published its AI Risk Management: Executive Handbook, the operational companion to the MAS Consultation Paper on Guidelines on Artificial Intelligence Risk Management, issued on 13 November 2025 and closed to comment on 31 January 2026. The Handbook sets out seventeen Considerations spanning board accountability, third-party risk, data management, pre-deployment testing and ongoing monitoring. It is the most concrete articulation yet of what a regulator in this region expects an AI program to look like from the inside.

Buried in the consortium’s own description of its purpose is the line that matters more than the seventeen Considerations combined. The Handbook exists, in its authors’ framing, to enable AI use that is “rapid but responsible.” Three words, one conjunction, and the entire tension of the regulated-AI program folded inside it. Everyone underlines “responsible.” Almost nobody asks how the “rapid” survives contact with it.

That is the question this essay is about. Not what controls to add the Handbook lists those well enough. The question is why most firms experience every new control as a tax on speed, and what the firms that don’t have understood that the rest have missed.

The consensus is reading it as an addition problem

Steering committees are already turning the seventeen Considerations into a program backlog, and the backlog is already being described, with a straight face, as the reason the AI roadmap has slipped two quarters. Seventeen Considerations; build seventeen capabilities; check seventeen boxes; deploy.

That reading misses the load-bearing word in the entire document. It is not “governance.” It is “proportionate.” The organising principle of both the Guidelines and the Handbook is that controls scale to risk — that the depth of governance applied to an AI use case is a function of how much damage that use case can do, not a flat tariff levied on all of them equally. The consensus treats the Handbook as a longer checklist. Read correctly, it is the opposite: a licence to do less, deliberately, almost everywhere — so that you can do far more where it counts.

Here is the thesis, and it is meant to sting a little. Speed and regulatory readiness only trade off when you refuse to sort. A portfolio governed by a single gate pays the compliance cost of its most dangerous use case on every use case it ships — and then calls the bill “prudence.”

What follows:

- Why the AI inventory is a speed instrument, not a compliance chore — and why most firms build it last

- The risk-materiality classifier that turns one queue into three, and the four questions that drive it

- How “prior action” — readiness built before deployment, not during it — is the only thing that makes a gate fast

- Why two deployment lanes beat one, and what the fast lane is actually allowed to skip

- A seventy-two-hour diagnostic that will tell you, uncomfortably, which gate your last ten deployments were really waiting behind

The framework: sort, pre-load, release

The framework has three stages, and they are strictly ordered. You cannot pre-load readiness for a use case you have not classified, and you cannot run differentiated lanes if you have not pre-loaded the controls each lane depends on. Sort, then pre-load, then release.

There is a TRIZ move underneath it, and it is worth naming once. A contradiction that looks unwinnable the system must be both fast and rigorous usually dissolves the moment you stop demanding both *in general*. Separate the requirements by condition. Be rigorous where the stakes are high, fast where they are not, and let a classifier decide which is which. The rest of this is engineering.

Stage One — Sort (before anything ships)

You cannot move fast on anything until you know what is allowed to move fast. Sorting is not the bureaucratic prelude to the work. It is the work that makes everything downstream cheap.

1. The AI inventory as a speed instrument

The universal pattern. Every system that triages a hospital, an airport, a help desk — begins by knowing what is in the queue. You cannot prioritize a queue you cannot see. The inventory is not a record-keeping artefact; it is the precondition for ever treating two items differently.

The regulated-industries manifestation. The Executive Handbook’s sixth Consideration requires firms to ensure AI inventory capabilities that record and maintain core information on AI use cases. In financial services the inventory is invariably built last and resented most a compliance deliverable assembled the week before an examination. That sequencing is exactly inverted. The inventory is the first thing that lets you go fast, because it is the thing that lets you decide what *not* to govern heavily.

Your translation. The inventory is owned by whoever owns delivery velocity, not by whoever owns the audit response. Its primary consumer is the person deciding which use case ships next quarter, not the examiner arriving next year. If your AI inventory lives in the second line of defense and nowhere else, it has been built for the wrong reader.

*What to build by Friday.* A single register with one column most inventories lack: a materiality tier. Not a description. A verdict.

2. The risk-materiality classifier

The universal pattern. Triage works because it sorts on consequence, not on category. The emergency room does not prioritize by which limb is involved; it prioritizes by what happens if the patient waits. Good sorting asks one question: how bad is “wrong” here?

The regulated-industries manifestation. The Handbook’s fifth Consideration directs firms to enhance use-case-level risk management through risk-materiality assessments, proportionate controls, and pre- and post-deployment reviews. Public commentary on the MAS Guidelines has converged on four dimensions that drive that assessment: the significance of the impact on customer outcomes, the financial loss if the model fails, the reputational exposure, and the criticality to ongoing operations. A model that drafts internal meeting summaries and a model that shapes a claims decision are not the same animal, and the entire point of proportionality is to stop pretending they are.

Your translation. The classifier is a one-page rubric: four questions, a forced ranking high, medium, low and no ties permitted. The roles affected are the use-case sponsor, who proposes the tier, and a risk owner, who can challenge it. Critically, the classifier runs in hours, not weeks. A sorting function that is itself slow has reintroduced the problem it was built to solve.

What to build by Friday. The four-question rubric, applied retroactively to your ten most recent AI deployments. The distribution will surprise you, and the surprise is the finding.

Stage Two — Pre-load (before the queue forms)

This is TRIZ Inventive Principle #10, Prior Action, applied to governance: perform the required change in advance, so it need not be performed in the rush. A gate is slow when every passage through it is bespoke. A gate is fast when the controls it checks for were built, approved and shelved months earlier, waiting to be picked up.

3. The reusable control library

The universal pattern. No fast-moving operation re-engineers its safety equipment per journey. The fire door, the circuit breaker, the seatbelt — pre-built, pre-certified, installed on demand. Speed at the moment of action comes from rigour completed before it.

The regulated-industries manifestation. Most firms assemble guardrails per use case, which means every high-materiality deployment re-litigates prompt-injection defences, human-override design, logging standards and — for any agentic use case — the zero-trust controls at the agent boundary that a high-materiality classification should make non-negotiable. The Handbook expects use cases to be built with appropriate guardrails. It does not require that they be invented from scratch each time. A control library is how “appropriate” becomes “already on the shelf.”

*Your translation.* The platform or architecture function owns a versioned catalogue of pre-approved controls. The high-materiality lane assembles from the catalogue; it commissions bespoke controls only at the genuine frontier. This is the difference between a readiness function that scales and one that becomes the bottleneck everyone routes around.

What to build by Friday. A list — even a short one of the five controls your high-materiality use cases always need, with an owner for each and an honest note on which are built versus aspirational.

4. The graded pre-deployment gate

The universal pattern. A gate that asks every traveller the same hundred questions is not secure; it is theatre with a queue. Real screening varies its depth by risk, and is trusted precisely because it does.

The regulated-industries manifestation. The Handbook calls for thorough testing and review prior to deployment. “Thorough” is not the same as “uniform.” For a low-materiality use case, thorough may be a one-page attestation against the control library. For a high-materiality use case, thorough is a full adversarial review with documented sign-off. Same principle, calibrated depth. The firms that run one gate at maximum depth are not safer than the firms that grade it; they are merely slower, and they have taught their delivery teams that governance is the enemy of shipping.

Your translation. The gate is a branch, not a wall. The materiality tier set in Stage One selects the review depth. Low clears in days against pre-built controls; high gets the scrutiny it earns. The role that changes most here is the reviewer, who stops being a uniform bottleneck and becomes a risk-weighted allocator of their own scarce attention.

What to build by Friday. A one-page gate map: three tiers down the side, the required evidence for each across the top. One page. If it needs more than one, it is not yet a decision aid.

Stage Three — Release (and keep watching)

5. Differentiated deployment lanes

The universal pattern. Every mature logistics system runs more than one speed of delivery. Express and standard are not a failure to standardize; they are the standard. One lane for everything optimizes for the wrong case.

The regulated-industries manifestation. The Handbook asks firms to consider risk-informed deployment options. Read that phrase slowly: the regulator’s companion document is explicitly endorsing differentiated release. A low-materiality summarization tool and an agentic underwriting assistant should not share a deployment path, an approval chain, or a rollback posture. The firm that forces them to has not reduced risk on the dangerous one; it has only added drag to the harmless one.

Your translation. Two lanes, minimum: a fast lane for low-materiality use cases that clears on attestation against pre-built controls, and a gated lane for high-materiality use cases with full review and named accountability. A third, middle lane is optional and usually emerges on its own. The product owner takes the lane the classifier assigns and cannot self-upgrade to the fast lane without re-classification.

What to build by Friday. A written definition of what the fast lane is allowed to skip. This is the hardest and most clarifying artefact in the entire framework, because it forces you to state, on paper, the risks you have consciously decided are acceptable to move quickly on.

6. Proportionate monitoring

The universal pattern. Attention after launch should follow consequence, the same way attention before launch did. You do not watch the smoke detector in the store cupboard as closely as the one over the stove.

The regulated-industries manifestation. The Handbook requires ongoing monitoring of AI use cases to ensure they remain fit for purpose over time. Proportionality does not stop at deployment. High-materiality use cases earn real-time drift and performance monitoring; low-materiality ones earn periodic review. Monitoring everything equally produces the same failure as gating everything equally scarce attention spread thin enough to miss the case that mattered.

Your translation. Monitoring cadence is set by the materiality tier, recorded against the inventory entry, and owned by the use-case sponsor with second-line oversight on the high tier. The same four-question verdict that set the gate depth now sets the watch interval. One sort, used three times.

What to build by Friday. A monitoring-cadence column added to the inventory quarterly for low, continuous for high — so the watch plan is visible the day the use case ships, not reconstructed after an incident.

None of this is peculiar to finance. A pharmaceutical company validating a generative model for adverse-event triage, an energy operator placing AI in load-balancing, a hospital network deploying ambient clinical documentation, each faces the identical sorting problem under a different regulator, and each pays the same hidden tax if it refuses to sort.

A note on confidence

The seniority of the reader deserves the distinction. What is confirmed: the MAS Consultation Paper’s dates and scope, the existence and structure of the MindForge Executive Handbook and its seventeen Considerations, and the proportionality principle running through both; these are matters of public record, cited above and linked below. What is **strong inference** from observed pattern, not documented fact: that the default failure mode in regulated AI programs is the single uniform gate, and that it is the largest uncosted drag on delivery velocity in most portfolios. I have seen this repeatedly across jurisdictions; I have not seen it measured at industry scale, and I will not pretend the plural of steering-committee anecdote is data. What is design hypothesis, offered for testing rather than asserted: that two-to-three lanes is the right number, and that a four-dimension classifier is sufficient. Fewer lanes under-sort; more lanes re-introduce the overhead you were trying to escape. That one is worth arguing with.

The diagnostic

It takes an afternoon. Take your last ten AI deployments. For each, write down two dates: when it was ready to ship, and when it actually shipped. Then, for each, name the single governance step that consumed the gap. The pattern is reliable enough that I will predict it before you run it: most of your delay was low-materiality work waiting behind a review designed for a use case far more dangerous than it was. The summarization tool sat in the queue behind the underwriting model’s risk assessment, inherited its scrutiny, and waited. You did not govern the harmless thing. You taxed it at the dangerous thing’s rate.

What the Prompt kit does

Reading about proportionate governance is pleasant. Knowing which of your own use cases are over-governed, and which are dangerously under-governed, is the part that changes what you build next week. That is mechanical work; apply a rubric, sort a list, define a lane and mechanical work is exactly what a well-built prompt does fast and consistently. This week’s Prompt Kit is four sequenced prompts: the first builds your materiality classifier, the second runs your existing inventory through it, the third drafts the fast-lane skip-list, and the fourth produces the one-page gate map. It is the sorting machine in this essay, rendered as something you can run on Monday against your real portfolio rather than admire as a diagram.

Run this in seventy-two hours

Open your AI inventory — or, if you have none, list your AI use cases on one page, which is itself the finding. Tier each one high, medium or low against four questions: customer impact, financial loss on failure, reputational exposure, operational criticality. Now look at how each is governed today. If a use case you tiered “low” went through the same review as one you tiered “high,” you have found a tax you have been paying without booking it. If a use case you tiered “high” took the same fast path as a “low,” you have found something worse than a tax. The uncomfortable recognition most readers reach, somewhere around use case number six, is that their governance has been sorting on visibility who shouted loudest rather than on consequence. That is the gap. It has been hiding inside the word “thorough.”

If you are standing up a proportionate AI governance model — and want a structured outside read on your materiality classifier, your lane definitions, and the specific controls your fast lane is allowed to skip, mention it in your reply. I take one such conversation per month. Specific beats general: name the use case that is currently stuck, and we will start there.

Replies to this post reach me directly. I read all of them.

Regulated Intelligence — TRIZ × AI | Regulated Markets. Written by JL CREPPY.