The Complaint Is Not the Constraint — Altvina Altvina Insights

Published July 14, 2026 · Altvina Insights · 5 min read

The Complaint Is Not the Constraint

Move two of the live diagnosis. There is a one-line test for whether your loudest complaint is real: imagine it suddenly fixed. If the firm would get worse, you were looking at a symptom.

Your loudest complaint is probably lying to you. Here is the 30-second test. Think of the problem your team complains about most, the one that comes up in every meeting and that everybody nods along to. Write it down. Now treat that sentence as a suspect, not a finding. The thing a whole team can name fluently, without anyone flinching, is usually the symptom they have all learned to describe in the same words. The actual constraint is the thing nobody quite says, because saying it would point somewhere uncomfortable.

That is move two. Yesterday we watched where the work physically stops, on the fifteen-person services firm we are diagnosing live this week. A reminder for anyone joining today: the firm is a composite. We built it from patterns we see across firms this size, and nothing it says is a real quote or a real number. We found the deliverable always stalls at one handoff, one review that has no fixed slot in anyone's week. Today we hold that next to what the team actually believes is wrong, and the two do not match.

Ask the room, then distrust the answer

Ask this firm what the problem is and you get a clean, unanimous answer. It is the sales process. They are sure of it. Leads come in unevenly, the pipeline is lumpy, some months are feast and some are famine, and the whole team can describe the sales problem in detail, because they have been describing it to each other for the better part of a year.

So we run the one test that settles it. If the problem is really sales, what happens when a good month arrives? Plenty of leads, a full pipeline, the thing they say they are missing. And the answer, once you actually ask, is that a good month makes everything worse. Delivery falls further behind. The deliverable that was already stuck gets more company in the queue. The same review with no fixed slot now has six things waiting on it instead of two.

That is not a sales problem. A firm with a sales problem gets healthier when sales improve. This firm gets sicker. More demand does not relieve the pressure; it exposes the bottleneck, the place the firm cannot move work through itself fast enough to keep up. The complaint failed the test the moment we imagined it fixed.

There was a clue in the room before we even ran the test, and it is worth learning to hear. Everyone agreed. There was no friction in the answer. No one lowered their voice. A real binding constraint usually has a little discomfort around it, a pause before someone names it, because it tends to implicate a decision someone made or a thing someone owns. The sales-process answer has none of that. It is the answer everyone can give without cost. That smoothness is the tell.

Why the loudest complaint wins the meeting

The complaint about sales wins the meeting for reasons that have nothing to do with whether it is correct. Sales is measurable, so it feels rigorous to talk about. It is external, so blaming it does not require anyone in the room to look at their own corner. And it is genuinely a little broken, the way most things are a little broken, so there is always real evidence to point at. All of that makes it a satisfying problem to discuss and a poor problem to fix, because fixing it would not stop the deliverable from being late.

The quieter candidate is the one we found yesterday, and notice nobody volunteered it. The review with no home in anyone's week is boring. It does not feel like strategy. It points, gently, at how the founder set up the workflow and never revisited it. None of that is fun to say out loud, so it stays unnamed, and the answer nobody gets blamed for keeps getting the airtime and the budget.

This is the trap worth naming for your own firm. You can spend a full quarter improving the thing everyone agrees on and feel productive the entire time, while the thing that is actually binding sits exactly where it was, because you never pointed at it. Check whether that describes your last quarter.

The test: imagine it fixed

Take the complaint you wrote down at the top and grant the wish. If it is sales, pull up your last genuinely good sales month and check what happened to on-time delivery. If your best month made delivery worse, the complaint failed the test with real data, not a thought experiment. If it is we-need-better-software, imagine the perfect tool live tomorrow. A review with no slot in anyone's week is still a review with no slot. If it is we-need-to-hire, imagine two good people starting Monday. Which queue does their output line up behind? If granting the wish makes the week worse, or nothing else in the firm moves, you were describing a symptom, and the constraint is somewhere quieter.

We are two moves in. We know where the work stops, and we know the team's favorite explanation just failed its own test. That leaves a strong suspect and, so far, zero proof. A small firm cannot afford to spend money chasing a confident guess that turns out to be wrong, which confident guesses often are.

So before this firm reorganizes or hires or buys anything, there is one more move, and it is the one we would not skip for anything. Tomorrow: the cheapest question you can ask that could prove your own guess wrong before you have spent a dollar acting on it.

This week's diagnosis, one move a day: JSX0 · the complaint is not the constraint · JSX1 · JSX2 · JSX3

Continue the series

This is part 2 of a 5-part series on Watch the Diagnosis. The full arc:

  • Monday: Why It Keeps Landing on Your Desk
  • Tuesday: The Complaint Is Not the Constraint (this post)
  • Wednesday: The Cheapest Question That Could Prove You Wrong (coming Wednesday)
  • Thursday: The One Thing That Moves Everything Else (coming Thursday)
  • Friday: The Recommendation, and the Honest Option to Do Nothing (coming Friday)

Content and Accuracy Disclaimer

This article was drafted with AI assistance and reviewed by the Altvina team. We rigorously fact-check all content to ensure reliability.

Should you notice any inaccuracies or outdated information, please contact us so we can correct it. Your feedback helps us maintain high standards of accuracy and transparency.