You are entering this mentoring scheme to transition into professional consultancy. To ensure our time is productive, we must align on what consulting actually is.

Many entrants to this field mistake consulting for "giving advice" or "sharing opinions." I reject that model. This paper outlines the methodology-first approach that will govern our sessions and your development.

My typical approaches centre on Evidence-Based Management and the Hypothesis-Driven Approach rooted in scientific inquiry.

1. Defining the Intervention

Before improving a client’s fortunes, the consultant must define the nature of the engagement. While the boundaries can blur, the intent differs:

• Coaching: Unlocking a manager’s existing potential; the answer lies within the client manager.
• Training: Transferring specific knowledge or skills to close a defined capability gap. The client manager then proceeds alone.
• Mentoring: A long-term relationship focused on the career and personal growth of the individual. Typically the mentor is expert and the mentee wishes to learn.
• Consulting: A time-bound intervention designed to solve a specific organisational problem through structured investigation and the provision of evidence for decision-making.

2. Consulting as Applied Research

Consulting is not a platform for pontification. It is a rigorous, research-based project. The consultant’s value does not come from their "gut feel," but from their method.

At its core, a consulting project is the development of a decision-making framework. The consultant is not there to make the decision; they are there to provide the evidentiary basis for it. This requires:

• Problem Decomposition: Breaking the client’s "mess" into a specific, addressable sub-problem.
• Methodological Rigour: Choosing a path (qualitative, quantitative, experimental, or comparative) that gathers data specifically to test assertions or hypotheses.
• Simulation & Modelling: Using data to project outcomes, allowing the client to "see" the results of a decision before they commit resources.

3. The Relationship is the Project

A common fallacy is that "client relationships" are built through charisma or social lunching. In professional practice, the relationship is a byproduct of the method. Trust is built when the client sees a robust process, agrees with the logic of the investigation, and observes the consultant delivering exactly what the method promised. If the method is sound, the relationship becomes secure.

4. Outcomes vs. Answers

In a consulting project, the Outcome is the delivery of a tested conclusion supported by evidence. The Answer is what the client chooses to do with that outcome.
A project can be a total success (the outcome is clear and evidenced) even if the outcome suggests that, for example, "The proposed strategy will likely fail."
Success is defined by:

• Agreement on the sub-problem.
• Commitment to the investigation method.
• Execution of the method to produce a verifiable outcome.

5. The Golden Rule: No Opinions

I have a "zero-opinion" policy. No consultant, regardless of experience, knows enough about a client’s specific, nuanced environment to offer an opinion without a project to back it up.

If you cannot point to a dataset, a benchmark, or a tested model developed during the project, you have no standing to speak. I believe in findings, not feelings.

6. Managing the Scope

In consulting, scope creep is a failure of methodology. By defining exactly how you will investigate the problem and what data will be gathered, you create a boundary. If the client wants to look elsewhere (other than what was agreed), they are asking for a new method and a new project. Consultants control the scope by being masters of the process.

7. Consulting skills and knowledge

The essential skills of a consultant centre on the method. The method must be appropriate for the client’s problem and sub-problem. Typically the consultant will select the method from a compendium of possibles and will discuss the method with the client. This discussion must achieve the client’s commitment to the method, the consulting project, and the outcome.
Typically, someone in the consulting team will be a subject matter expert, but a team may otherwise comprise mostly generalists. And typically someone in the team must be expert in methods.

8. In conclusion

A one-person consultant will need to have skills and knowledge in both subject and methods. They will also need to do the work and present the outcome.