5 Mistakes Even Good Advisors Make

Most advisory fails aren't about competence. They're about pattern.

1. They walk in with the answer

They call it a framework. It's a conclusion dressed as a process. They prescribe before they diagnose.

The framework is usually real. It worked somewhere, more than once, and that is what makes it hard to put down. The tell is the sequence: the diagnosis arrives already shaped like the recommendation, and the evidence gathered afterwards fits it. Ask what they expected to find before they arrived. If that matches what they found, the diagnosis did no work.

2. They optimise for being liked

You sense the contradiction. You say nothing because the relationship feels fragile. That's not advisory. That's expensive companionship.

It is rarely cowardice. An advisor renewed by the person they advise has a live incentive to stay pleasant, and that incentive does not announce itself. It shows up as hedged language in the moments that matter most: the hire who is not working, the strategy nobody believes, the co-founder problem. The test is whether they have told you something you did not want to hear this quarter.

3. They fix the symptom, not the system

The team is misaligned. They run a workshop. Six weeks later, same drift. The belief underneath never got touched.

Workshops move what people say. They rarely move what people believe about who decides. If the meeting that produced the misalignment still runs the same way, with the same people holding the same unstated veto, the workshop bought six weeks of vocabulary. The question afterwards is not whether the session went well. It is which decision now gets made differently.

4. They confuse activity for impact

Decks, frameworks, workshops, OKRs. All motion, no movement. One question cuts through: what actually changed after you left?

Each of those artifacts is evidence of work. None is evidence of change. This survives because artifacts are easy to review and outcomes are not, so the review defaults to the pile. Set the question before the engagement starts rather than after: name the decision, the behaviour or the number that should look different by the end, and write it down. An advisor who resists that is telling you something.

5. They make themselves necessary

Good advisory work ends. If the client can't operate without you, you built dependency. Not capability.

Dependency is rarely designed. It accumulates: context that lives in one head, a relationship the advisor holds rather than the team, a decision that keeps routing back for a second opinion. The counter is dull and it works. Write things down where the team can find them, turn the advisor's judgement into a rule someone else can apply, and name the condition under which the engagement stops.

The best advisors leave rooms that no longer need them.