Consulting
10:02 AM. Wednesday. A consultant arrives with a deck of 47 slides and the answer to the question the brief asked. The brief was written by the previous COO, who left in February. The question in the brief is no longer the question the company is living. The consultant did good work. The work is now an artifact.
The consultant did not write the brief. That is the layer above.
A brief. A scope. A finite output. The team that ships it leaves.
A consultant takes a defined problem, applies analysis, returns a recommendation. The unit of work is the deliverable. The unit of time is the project. The relationship ends when the project does.
Consulting is excellent at supply chain rebuilds, system migrations, market entry analysis, organizational redesign within a brief, and operational diagnostics. It is structurally bad at frame questions, ownership questions, and "what should the brief itself be" questions.
[Note: a consultant who is good will tell you when the brief is wrong. A consultant who is great will refuse the engagement until the brief is right. Most consultants take the brief.]
The question is defined. The scope is finite. The output is a thing.
One. The work has a clear endpoint. A document. A deck. A new operating model. A system that goes live. If you cannot describe what gets handed over on the last day, the engagement is not consulting.
Two. The company has the operator to receive the work. A great consulting output dies if there is no one inside the company who picks it up and runs it. Consultants build the system. Operators run it.
Three. The decision underneath the brief has already been made. If you are still asking whether to expand into a new market, do not hire a consultant to "evaluate the expansion." Decide first. Then consult on how.
Ongoing operations. Identity work. Decisions that are still forming.
A consulting engagement to "improve marketing performance" without a marketing leader in the seat ships beautiful work that nobody owns. The deck becomes a graveyard.
A consulting engagement to "fix the team's communication" is a coaching problem dressed as a consulting brief.
A consulting engagement to "evaluate whether to sell the company" is private advisory dressed as a consulting brief. The advisor is paid to ask the founder a different kind of question.
Three engagements that look like consulting. None of them are.
Consulting against the six other layers in the pyramid.
Where the brief works, and where the brief is the problem.
- Layer 01Decision Architecture vs ConsultingWho writes the brief, vs who executes the brief.
- Layer 02Private Advisor vs ConsultantA seat in the conversation, or a project with a finish line.
- Layer 03Governance vs ConsultingApproving the company, or delivering a recommendation.
- Layer 04Consulting vs Fractional LeadershipA brief and a deck, or a seat and a quarter.
- Layer 06Consulting vs CoachingThe function gets analyzed, or the leader gets developed.
- Layer 07Consulting vs TrainingA finished deliverable, or a team that can do the work next time.
Where this sits.
Layer 05 of seven. Below the operator-in-seat layer. Above the operator-development layer.
Back to the Atlas root. See the outside-help market map.
The brief is the layer. Most consulting failures are brief failures, not consultant failures.