A working dozen beats an encyclopedia
Most working consultants run on roughly a dozen structures: a profit or outcome driver tree for decomposition, segmentation for any market question, a cost and value chain walk, a prioritization two by two, a root cause five whys, a stakeholder map, a maturity ladder, a funnel for anything sequential, scenario branches for uncertainty, and the MECE habit underneath all of it, categories that do not overlap and do not leak.
Depth with twelve beats familiarity with eighty. The value is not knowing the framework; it is having used it enough times to know where it lies.
Match the tool to the question, then translate
The framework is chosen by the question, not the industry: why are margins falling wants a driver tree, which customers should we serve wants segmentation, what do we do first wants the two by two. Choosing by habit, the consultant who SWOTs everything, produces the shelf-ware the profession is mocked for.
Then translate into client language. Present the driver tree as where the money leaks, the maturity ladder as what good looks like in stages. Clients should experience clear thinking, not vocabulary. If the room is learning your terminology instead of their answer, the framework has become the product.
Know when to put it down
A framework earns its keep during structuring: it finds the gaps, organizes the interviews, disciplines the analysis. Somewhere in every good engagement the answer starts speaking for itself, and the framework becomes scaffolding to remove before delivery. The client gets the building, clean and answer-first, not the scaffolding with a bow on it.
The test: if the framework disappeared from the deliverable, would the recommendation stand on its own evidence? When yes, delete the template pages. When no, the framework is holding up thinking that has not finished.
Fifty structures, drafted into your engagement
The Consulting Desk’s template library carries fifty engagement structures with the thinking tools built in, and Velora applies them to your client’s facts: describe the situation and it drafts the driver tree, the segmentation or the prioritization view in your engagement record, in plain language, ready to translate for the room.
The deliverable libraries then present the answer, not the scaffolding. Structured thinking at drafting speed, from the Plus membership.
Frequently asked questions
Which frameworks should a consultant know?
A working dozen: driver trees, segmentation, value chain, two by two prioritization, root cause, stakeholder mapping, maturity ladders, funnels, scenarios, and the MECE habit underneath. Depth beats catalog size.
Should the client see the framework?
They should see its results in their own language. Frameworks structure your work; the deliverable presents the answer. Vocabulary lessons are a sign the analysis is not done.
Is MECE still relevant?
As a habit, absolutely: categories that neither overlap nor leak keep analysis honest. As a shibboleth to recite, it convinces no client of anything.