The Architecture of Good Advice

The consulting industry produces a remarkable volume of analysis, frameworks, and recommendations. Much of it is competent work. Considerably less of it actually changes anything. The gap between technically sound analysis and advice that improves real decisions is worth understanding.

The most common failure isn't incompetence

It's irrelevance. Thorough analysis of questions that aren't quite the right ones. Recommendations that are correct in the abstract but disconnected from the client's actual constraints. Work that could have been produced for any organization in a similar industry, dressed up to look bespoke.

Good advice starts with problem definition, and problem definition is harder than it looks. The presenting issue is rarely the actual issue. The presenting question is often a proxy for a deeper decision that hasn't been named yet. Getting there requires enough context about the organization to see past the symptoms.

Independence isn't optional

The value of outside advice depends entirely on its independence. Not just as a matter of integrity (though that matters), but as a structural requirement. An advisor whose conclusions are shaped by the desire to extend the engagement, avoid a difficult conversation, or protect a relationship can't provide the kind of unvarnished assessment that justifies bringing them in.

This is why we don't do retainers. We don't want ongoing financial relationships that create incentives to find new work. An engagement should end when the question is answered.