A good mechanic doesn’t hear “there’s a noise.” He hears low-frequency rumble under load between 35 and 50 mph. He’s spent twenty years listening to engines, and the noises have stopped being noises. They’re a vocabulary.
After enough lunches across a burger-joint napkin table with operators trying to draw how their business actually runs, the same thing happens. You stop hearing words. You start hearing tells. The drawing breaks the same seven ways every time, and once you can hear that, you can’t unhear it.
Here’s the thing. This is the diagnostic that sits underneath every “why isn’t the AI working” conversation I’ve had this year. The AI agent is the most literal-minded employee you’ve ever hired. It gets stuck in exactly the places these tells point to. So the seven tells aren’t just a way to read your team. They’re a way to read why your last automation stalled, and what the next one is going to fumble.
The frame the tells sit inside is Quality Control, our list of Failure Modes. Each tell maps to one of the four anti-patterns we use to diagnose a station that isn’t producing. The Generic Output Trap, the Process Cage, the Open Door Problem, the Silent Critic. Different sounds. Same root. The work was never specified well enough for someone outside the head it lives in to do it.
Here are the seven I listen for. Each one is a sound, what the sound means, and what to do about it.
1. “Well, normally, but sometimes…”
The sound: They lay out the clean version, and then there’s a but. “Normally we send the quote within 24 hours, but sometimes, if it’s a repeat customer, or if Dana’s the one handling it, we…”
What it means: The exception isn’t an exception. It’s the operating reality. The clean version is the story they tell themselves. The “but sometimes” is what the business actually runs on. There’s a branch in the process with no written rule, and everyone’s been navigating it by feel.
The fix: Chase every “but sometimes” to ground. Write the rule for the exception, not just the happy path. If you can’t write the rule, you’ve found a decision that’s still living in one person’s judgment. Which is fine for a human, and fatal for an agent.
2. They explain the same step three times
The sound: You ask about one step, and they circle it. Explain it, then re-explain it differently, then reach for an analogy. They’re not confused. They’re generating the explanation on the spot, because it’s never existed outside their head.
What it means: That “step” isn’t a step. It’s a judgment call wearing a step’s clothing. “Qualify the lead” sounds like one action. It’s actually fifteen micro-decisions they make in two seconds and have never decomposed.
The fix: Don’t accept the verb. Crack it open. “When you say qualify, what are you actually checking? In what order? What kills the deal? What’s a yellow flag versus a red one?” The step that takes three explanations is the step that takes forty hours of specification later. Pay it now.
3. “It depends on who’s working that day”
The sound: You ask how something gets handled, and the answer routes through a name. “If it’s Mike, he’ll just know to… if it’s the new guy, he’ll usually…”
What it means: The process doesn’t live in the process. It lives in a person. You don’t have a system. You have Mike. The day Mike is on vacation, or the day you try to hand this to an agent, the process doesn’t exist.
The fix: This is your highest-value extraction target. Whatever Mike “just knows” is the exact knowledge that’s missing from every doc, every new-hire packet, and every prompt. Get it out of Mike. He’s not the problem. He’s the only person who can tell you the rule. Until it’s out of his head, you don’t own this process. He does.
4. The box they draw and then talk past
The sound: They draw a box on the napkin, “and then it goes to review,” and immediately keep moving. They never say who does the review, what review means, or what happens if review fails. The box is a placeholder they’re hoping you won’t ask about.
What it means: That’s a stage everyone assumes and nobody owns. It works today only because some specific person quietly absorbs it. It’s the most common place a process silently breaks when you scale it or automate it, because the absorbing person isn’t in the loop anymore.
The fix: Point at the box. “Who does this? What does done look like? What happens when it’s wrong?” If the table goes quiet, you’ve found an orphan stage. Give it an owner and a definition before you give it to anything, human or machine.
5. “You just kind of know”
The sound: The most honest tell, and the most dangerous. “You just kind of know when a customer’s about to walk.” “You can just tell which jobs are going to be a headache.”
What it means: Tribal knowledge. Real, valuable, and completely invisible to anyone who doesn’t already have it. It’s the pattern-matching that took them twelve years to build. It’s also a folklore-shaped hole in every system you try to build around them.
The fix: “You just kind of know” is never the end of the answer. It’s the start of the interview. What do you know? What are the actual signals? When you “just tell” a job’s going to be a headache, what did you see? They can almost always name it once you refuse to let them stop at “you just know.” That naming is the specification.
6. They only ever draw the happy path
The sound: The whole napkin is one clean line from start to finish. Lead comes in, gets qualified, gets quoted, closes, gets serviced, everyone’s happy. No branches. No failures. No “and if that doesn’t work.”
What it means: This process has never met a hard day on paper. The happy path is the easy 80%. The business actually lives or dies in the 20%. The angry customer, the missing part, the deal that stalls, the wrong address. A process with no failure branches isn’t specified. It’s just optimistic.
The fix: Ask the unhappy questions. “What happens when the customer says no? When the part’s backordered? When it’s the wrong tech at the wrong house?” The failure branches are where the real money and the real liability live. They’re also exactly the branches an AI agent will fumble, because nobody drew them.
7. “We handle that” / “They take care of it”
The sound: A pronoun with no owner. “Oh, we handle that on the back end.” “They take care of the follow-up.” Said smoothly, in passing, like it’s settled.
What it means: We and they are where accountability goes to disappear. A responsibility assigned to “we” is assigned to no one, which means it’s actually assigned to you, the owner, picking it up by reflex without realizing you’re the only thing holding it together.
The fix: Replace every we and they with a name. “When you say we handle that, who, specifically, is we?” If the honest answer is “…me,” you just found another process that doesn’t scale because it runs on the owner’s reflexes. Those are the first ones to specify and hand off.
What you’re actually listening for
Notice what none of these tells measure. Whether the person is smart, experienced, or good at their job. They usually are. The tells aren’t about competence. They’re about whether the work has ever been defined well enough for someone outside the person’s head to do it.
That distinction is the whole game right now. Every “the AI isn’t working” conversation, every “I can’t find good people,” every “nobody can run this when I’m out,” they all trace back to the same root. The work was never specified. It lived in someone, ran on instinct, and worked beautifully right up until you tried to give it to a new hire, an agent, or a partner.
Right. That’s the trap. The tells are how you catch it before you’ve spent six months and a software budget discovering it the expensive way. Pull out the napkin. Ask the hard question. Then just listen for the seven sounds.
Once you can hear them, you can’t stop. Which is exactly the point.
Original framework. Distilled from client work.
Framework callback: Quality Control, our four Failure Modes. The diagnostic that sits underneath every “why isn’t the AI working” conversation.
~ source material · Original framework. Distilled from client work.
