CMC Competence Framework
The CMC Competence Framework is the reference model behind the Certified Management Consultant credential. It specifies what a competent consultant must know, do and be across an engagement, and the exam tests whether you can apply the framework to realistic situations rather than recite definitions. Questions typically present a scenario and ask what a competent consultant would do next, so you need the logic of the model, not just its labels.
How the framework is organised
It has three interacting layers. First, professional foundations: ethics, professional standards, independence, confidentiality, and commercial/legal literacy. Second, the consulting process itself, from entry and contracting through diagnosis, action planning, implementation and closure. Third, enabling competences: communication, stakeholder engagement, change leadership, project management and reflective learning. Exam items often sit at the seams between layers, for example an ethical tension that surfaces midway through implementation, or a change-resistance problem that is really a contracting problem.
The consulting process as the exam spine
- Entry and contracting: agree scope, deliverables, roles, decision rights, fees, confidentiality and success measures in writing. The contract is the primary risk-control instrument, not paperwork.
- Diagnosis: gather data from several organisational levels, separate symptoms from causes, test hypotheses, and present findings before proposing solutions.
- Action planning: co-design options with the client, test feasibility and risk, and agree who decides.
- Implementation: transfer capability, manage resistance, and monitor against a baseline.
- Closure: evaluate outcomes, capture lessons learned, and exit cleanly.
Ethics and professional conduct
Independence, confidentiality, honest competence boundaries, conflict-of-interest disclosure, and refusing work you cannot staff competently. Ethical duties outrank commercial pressure and client convenience.
Worked example
A client says: "Skip the diagnosis, just give us the answer by Friday." Accepting would breach the process and the professional standard of prescribing without evidence. The competent response is to clarify the presenting problem, propose a compressed but genuine diagnosis (targeted interviews plus a data review), state explicitly the risk of skipping it, and document any agreed scope change. That answer shows client focus and professional standards operating together rather than in conflict.
Traps that cost marks
- Treating contracting as a formality rather than the control that defines scope and liability.
- Confusing a methodology (Lean, Agile, a maturity model) with the competence framework itself.
- Solving the problem for the client instead of with the client, and failing to transfer capability.
- Leaving stakeholder and change considerations until implementation.
- Over-promising scope under time pressure instead of renegotiating it.