The Thing You're Asked to Fix Isn't Always the Constraint

I've been handed a lot of stated problems over the years. "Fix our CRM." "Get us more leads." "The campaign isn't converting." "We need better reporting." Every one of those is a real request, and every one of those, more often than not, turned out to be pointing at the wrong thing.

Not because the person asking was wrong to notice a problem. They were right that something wasn't working. They were usually wrong about which thing. The stated problem is where the pain shows up. It's rarely where the pain starts.

This isn't a theory I arrived at in a workshop. It's a pattern that kept repeating, independently, across five genuinely different businesses over roughly a decade.

At Sojern, running travel ad-tech campaigns across airlines and hotel brands, a campaign that looked underperforming turned out to have a tracking gap underneath it. The numbers weren't wrong because the campaign was bad. They were wrong because they couldn't be trusted yet. Optimising the campaign on top of that gap would have optimised the wrong thing, confidently.

At one agency I worked with early in my career, the standard request was a quote for a dedicated team. The standard mistake, on both sides, was pricing that before understanding the client's actual cost structure, their skills gaps, their existing workflow, their reporting. A proper scoping conversation, asked in the right order, usually found a different, smaller, more specific problem than "we need a team."

Running my own agency, Alexander Twelve, the same instinct showed up connected to a different part of the chain. It wasn't enough to structure a campaign well. The cost-per-lead only meant something once it was tied to what happened after the click, not just before it.

At Nordic Markets, the request was to scale email outreach against a two-million-contact database that wasn't converting. The obvious move was to send more, or send better copy. The actual constraint was the list itself, an open rate sitting at 4.8% against a 15-25% benchmark. No amount of better copy fixes a list that's already been burned.

The stated problem is where the pain shows up. It's rarely where the pain starts.

And in my current work, the habit hasn't gone away, it's just gotten more current. One thing I still run every engagement through: defining what actually counts as a qualified result, before measuring anything against it. Change the definition of "success" and you often find the campaign, the CRM, or the team was never the problem at all.

Five different businesses. Five different industries. The same underlying move, applied to a different object each time, tracking infrastructure, client scoping, funnel architecture, list quality, measurement definition. That's not a coincidence, and it's not one clever trick repeated. It's a consistent instinct to ask "what's actually broken here?" before reaching for the obvious fix, applied to whatever domain happens to be in front of me.

This is Halo's First Law, and it's worth being direct about why it's a law rather than a preference: diagnosis before prescription isn't a nicer way of doing consulting. It's the only way I've found that reliably avoids fixing the symptom instead of the cause, because I've watched the alternative fail, in five different rooms, in five different industries.

What this means in practice, if you're the one holding the stated problem right now:

• Write down the problem exactly as you'd currently describe it to someone you're about to hire to fix it. That sentence is your starting hypothesis, not your brief.
• Ask what would have to be true for that stated problem to actually be the constraint, and check whether the evidence in front of you supports it, or just doesn't contradict it. Those aren't the same thing.
• Look one step upstream and one step downstream of the stated problem before spending against it. The tracking behind the campaign, the list behind the email, the definition behind the metric.
• Be honest about whether "we think the issue is X" and "the evidence says the issue is X" are actually the same claim in your business right now. They frequently aren't.

None of this means the stated problem is always wrong. Sometimes the CRM really is the CRM. But five for five isn't a coincidence, and it's the reason Halo's Commercial Audit is built to find the constraint first, and price the fix second, on the Commercial Audit page. The full career context behind this pattern is on About.

What people ask about this pattern.