Consultant For A Decision Problem.
A consultant can make the map sharper. A consultant cannot make the owner accept the mountain.
Definition
Consultant for a decision problem is the trap of buying analysis when the unresolved issue is ownership of the decision.
Consultants can be extremely useful. They clarify markets, functions, processes, economics, structure, and options. Good consulting can remove fog quickly.
But analysis cannot make a decision owner accept consequence. It can show the options. It can improve the model. It can make the deck dangerously elegant. The decision still belongs to whoever must live with what happens next.
Where it fits
This trap sits in the wrong-role cluster of Role Bias and links directly into Hub 7 Decision Architecture.
The consultant room sees the project. That can be exactly right. But when the project is only a shell around an unmade decision, the analysis becomes the company-approved way to postpone choosing.
When it works
Consulting works when the decision owner needs better information to decide. That is a clean use case. The question is known. The missing input is known. The consultant creates the input.
It works when a functional area is genuinely underdesigned. It works when the buyer needs market analysis, operational diagnosis, cost modeling, or implementation planning. It works when the decision owner has already accepted that a choice will be made after the work.
Respect the role. A good consultant can save months of internal wandering. The problem is not consulting. The problem is smuggling a decision problem into a consulting container.
When it does not work
Consulting does not work when the owner is using analysis to avoid accepting downside. If every answer creates another request for analysis, the project is not under-informed. It is under-decided.
It does not work when the team has not named who decides. The consultant can return options, but options without a decider become a very expensive menu.
It does not work when the true question is control, succession, authority, ownership, or trust. Those are not solved by a prettier matrix. The matrix can be excellent. It can also be furniture.
Common misuse
The first misuse is the "one more analysis" loop. The company asks for another model because the model is easier to approve than the consequence. The model improves. The decision hides.
The second misuse is outsourcing courage to a deck. No deck has ever walked into the room and accepted accountability. It just sits there, formatted nicely, waiting for an adult.
The third misuse is hiring a consultant to create consensus among people who disagree on decision rights. That is not a consulting gap. It is an authority gap wearing a project plan.
Related roles
Consultant Before Decision Clarity is the deeper Hub 7 page.
Advisor vs Consulting helps when the buyer is comparing buying paths.
Neutral Triage Before Role Choice helps before the next consulting scope is written.
Decision test
- Is the question already known, or is the team asking analysis to discover it?
- Will the decision owner commit to deciding after the work?
- Have previous analyses created clarity without movement?
- Is the consulting scope actually a proxy fight about authority?
- Would naming the decision make half the analysis unnecessary?
Next route
Read Consultant Before Decision Clarity for the decision-architecture version. Read AI In The Wrong Costume if the same mistake is happening through prompts instead of consultants.