← All frameworks ~ framework 05 of 05 · diagnostics

When AI drops a plate, it's always one of four things.

When AI fails, most teams fix the wrong layer. They fix the output. The fix is always one layer deeper. Tuesday the email goes out wrong. Employee rewrites it. Tuesday-the-week-after, same email, same way, goes out wrong. Employee rewrites it again. The team gets quietly tired. The AI never gets better.

Right? Yeah. That's not an AI problem. That's a broken Feedback Loop. Which is one of four specific things it could be. Every failure I've ever seen an AI deployment throw maps to one of these four. Literally every one.

Diagnose the ingredient. Fix the recipe. Not the plate.

A single plated dish under the amber glow of a pendant heat lamp with a tasting spoon beside — the diagnostic moment before the recipe is revised.

the tasting spoon ~ before the recipe gets revised

~ the diagnostic layer

Four named failure modes.

Each one maps to a specific broken ingredient in the Professional Recipe. Diagnose the ingredient, not the output. Fix the recipe, not the plate.

The Generic Output Trap

Missing — Examples (#4)
Symptom

The output is clean but lifeless. Reads like stock copy. Doesn't sound like your business.

Cause

The station was never shown the house standard. It’s doing its best — from nothing.

Fix

Add three to five real work samples to the recipe. Watch the next plate sharpen in one sitting.

The Process Cage

Missing — Output Over Process (#5)
Symptom

You gave a sharp agent a paint-by-numbers kit, and it stopped using its judgment.

Cause

You over-specified the steps instead of the destination. The agent is following instructions, not cooking.

Fix

Describe what “plated well” looks like. Let the station figure out the path.

The Open Door Problem

Missing — Guardrails (#3)
Symptom

The station sent out a wrong price. Or made a promise you can’t keep. Or said something you’d never say.

Cause

You never told the station what it cannot do. Nothing stopped it.

Fix

Write the safety stops into the recipe. What’s off-menu? What needs the Chef’s eyes? Hard-code it.

The Silent Critic

Broken — Feedback Loop (#7)
Symptom

Your team is quietly rewriting bad output every day. They’ve given up on reporting it.

Cause

The Feedback Loop is broken. The recipe never gets updated — just the individual plates.

Fix

Build a thirty-second path from “miss” to recipe update. Fix it once, fix it everywhere.

~ four failure modes, four missing ingredients

The cultural shift.

Don't rewrite the output. Update the recipe. This is the hardest mindset change for a team that's been quietly fixing AI output all year. The thirty seconds you spend updating the prompt saves thirty minutes a week forever. Fix it once. Fix it everywhere.

The four failure modes, expanded.

The Generic Output Trap. The output is clean. It's readable. It's just lifeless. Doesn't sound like your business. Sounds like a well-written stranger. The station was never shown the house standard. The fix is Ingredient #4 — add three to five real samples to the recipe. It's the fastest quality jump you'll ever see.

The Process Cage. You hired a sharp agent and gave it a paint-by-numbers kit. Now it's following your instructions step by step and never using its judgment. Of course — you told it not to. The fix is Ingredient #5 — describe the destination, not the turns of the spoon. Let the station cook.

The Open Door Problem. The station sent out a wrong price. Or made a promise you can't keep. Or said something you would never say. Nothing stopped it because you never told it what it cannot do. The fix is Ingredient #3 — write the guardrails in. What's off-menu? What needs the Chef's eyes? Hard-code it.

The Silent Critic. Your team has quietly given up on the AI. They fix its output every day and never tell you. The Feedback Loop is broken. The recipe never gets better. The fix is Ingredient #7 — build a thirty-second path from "miss" to recipe update. Fix it once, fix it everywhere.

Don't diagnose randomly. Diagnose by ingredient.

How it connects.

Quality Control is the diagnostic layer for the Recipe. Every failure mode maps cleanly to a specific ingredient in the Professional Recipe. Quality Control doesn't exist on its own — it exists because the recipe has seven specific parts and any one of them can be the broken one. You don't diagnose randomly. You diagnose by ingredient.

This is also what you're doing when you're in the Dialing stance from the Four D's. Dialing means standing at the pass and refining. Quality Control is the diagnostic you run while you're dialing.

~ the monday move
This week, log one thing the AI got wrong. Don't rewrite the output. Diagnose which ingredient is broken. Update the recipe.