Consulting Practice, Solution Design, and Client Communication
What to know cold
Consulting is about framing problems, scoping work, and communicating risk to decision-makers. Know how to elicit requirements (business drivers, constraints, stakeholders), define scope and assumptions, and document deliverables. Understand solution design: current state, target state, gap analysis, options with trade-offs, and a recommendation tied to risk appetite and budget. Communication skills matter: translating technical findings into business impact, tailoring language to the audience, and managing expectations. Know the ethics of independence, confidentiality, and avoiding conflicts of interest.
Traps that show up in questions
- Recommending the most secure option without regard to cost, usability, or business context.
- Presenting findings without business impact, leaving the client unable to prioritise.
- Expanding scope without a change request.
- Overpromising certainty; risk is probabilistic.
- Choosing an answer that serves the consultant's interest over the client's.
Rule of thumb
Frame every recommendation as: business objective → risk → options → trade-offs → recommendation → next steps. If an answer lacks a trade-off, it is usually wrong.
Worked example
A client asks for "the most secure" architecture. The consultant restates the objective (protect customer data while enabling remote work), presents three options with cost, usability, and risk implications, recommends the balanced option, and documents assumptions and residual risk for the client to accept. The client decides; the consultant advises.