The Integrated Model: Why the Diagnosis and the Build Should Be the Same Person

The typical split, and where it breaks

The consultant interviews your team, reviews your numbers, and delivers a deck: here are your three biggest gaps, here is what to do about them. Then they leave. Implementation is now your problem, or an agency's problem — an agency that never sat in your leadership meeting, never heard the context behind why the last three attempts at this fix failed, and is working from a document instead of from the room.

Nothing in that handoff is malicious. It's just structurally lossy. The person who understands why a recommendation makes sense is not the person building it, and the person building it is not accountable for whether it actually solves the original problem — only for whether they built what was in the brief.

What changes when one person does both

When the same person diagnoses the gap and builds the fix, there is no brief to misread. The context from the diagnostic — the failed prior attempts, the political reality of who resists what, the actual reason the scorecard has been abandoned twice already — carries directly into the build, because it's the same person's memory, not a handoff document.

It also means accountability doesn't have a seam. If the fix doesn't work, there's no ambiguity about whether the diagnosis was wrong or the execution was wrong — one person owns both, which means one person has to actually make it work.

The tradeoff, stated plainly

A single person doing both diagnosis and build can serve fewer clients at once than a firm that separates the two functions across specialists. That's a real constraint, not a marketing footnote — and it's the reason this model favors a small number of deep engagements over a large roster of surface-level ones. If you want breadth across every function at once, a larger firm's division of labor may serve you better. If you want one person who actually remembers the last conversation, this is the tradeoff you're making on purpose.

How to tell if you already have a translation-loss problem

• A consultant's recommendation from six months ago is still sitting in a deck, unbuilt
• Your team can describe what the new process is supposed to be but nobody can explain why it was designed that way
• The agency you hired built exactly what was scoped, and it solved a different problem than the one you actually had
• You've become the translator between your strategic advisor and whoever executes — and you didn't sign up to be middleware

Related reading