How to Create a Repeatable Consulting Methodology
For consultants and advisory teams: learn how to make your reasoning, evidence and decision points reusable while adapting each diagnosis to the client’s context.
On this page
A repeatable consulting methodology makes the reasoning, evidence and decision points reusable—not every client’s diagnosis identical. Start with a client decision, choose an analytical framework that fits it, identify the evidence needed and make clear where professional judgement matters. Another practitioner should be able to follow how the recommendation was reached, what could change it and who is responsible for the advice.
Start with the decision#
Write down what the client needs to decide before choosing a framework. “Assess the market” is too broad to guide the work. A more useful question might be: “Should we commit resources to test this market over the next six months, and what evidence would justify that commitment?”
Then clarify:
- Who owns the decision? Who can approve the next step, and who will be affected?
- What constrains the options? Consider time, budget, capacity and risk.
- What is uncertain? Identify the fact or assumption most likely to change the recommendation.
The decision determines what the analysis needs to establish. If the main uncertainty is whether buyers will pay, investigate buying behaviour and willingness to pay. If it is whether the business can serve the market, examine delivery capacity. Starting with a favourite framework instead can produce a tidy analysis that leaves the client’s real question unanswered.
Connect the decision to evidence and judgement#
Choose a framework or analytical lens because it helps answer the decision—not because it is familiar. State what it can help assess and what it cannot establish on its own.
For each important question, record the evidence that would help answer it, where that evidence might come from and what its limits are. Keep client-provided information, external evidence and practitioner assumptions distinct. Note conflicting observations rather than smoothing them into a single story; they may point to differences between customer groups or show that the question needs narrowing.
Then explain the judgement: what the evidence supports, where interpretation is needed and what new information would change the recommendation. A compact working record can keep those links visible:
| Record | What to include |
|---|---|
| Decision and constraints | What the client must decide, who owns it and what limits the options |
| Framework and rationale | The analytical lens and why it fits |
| Evidence and gaps | Questions, sources, conflicting information and limitations |
| Assumptions and judgement | What is not established, how the evidence is interpreted and why |
| Recommendation and next action | What to do, the reasoning and what would prompt reconsideration |
For the market-entry example, an entry might read:
Decision: Should the business commit resources to test a new market?
Assumption to test: Target buyers have a problem the proposed offer addresses.
Evidence needed: How potential buyers handle the problem now, what it costs them and who approves a purchase.
Limit: A small set of conversations can surface questions and patterns; it cannot establish that the whole market will buy.
Next action: Review the evidence before deciding whether a bounded test is justified.
This is a proposed way to document consulting work, not a validated standard or proof of commercial results. Its purpose is to make the path from question to recommendation inspectable: a reviewer can see what was investigated, what remains uncertain and where the consultant interpreted the evidence.
Standardise the reasoning, not the diagnosis#
Make consistent the parts another practitioner needs to understand: the decision being addressed, the evidence considered, the distinction between facts and assumptions, and the reasoning behind the recommendation.
Leave room for context-sensitive judgement. Clients and evidence differ; a consultant may need to reconcile conflicting information, adapt a framework or recommend more investigation rather than give a confident answer. Record why that judgement was made instead of hiding it inside a template.
The test is not whether everyone used the same framework. It is whether a reviewer can understand why it was selected, what evidence informed the diagnosis and how the practitioner reached the recommendation. Different conclusions may be reasonable when the evidence or context differs; the record should make those differences clear.
Try the method on comparable work#
Before using the method more widely, ask another practitioner to apply it to a comparable piece of work using the information available for that exercise. Compare the reasoning, not just the final recommendations:
- Were the important questions and sources identified? What was missing?
- Could each practitioner explain how they moved from evidence to diagnosis?
- Did differences come from the client context, interpretation or unclear instructions?
- Which parts needed clarification, correction or extra client input?
Agreement does not prove the method is sound: practitioners may share an incorrect assumption. Disagreement does not automatically mean it has failed: the evidence or context may justify different conclusions. The useful question is whether the method makes the reasons for a decision visible—or merely produces similar-looking documents.
Revise the instructions or evidence requirements where they are unclear. If the difference reflects genuinely different circumstances, specify what should prompt adaptation. If practitioners cannot tell which evidence matters or who owns a consequential decision, clarify that before wider use.
