Most requests for help arrive fully formed. "We need a competency framework." "We need a leadership programme for our middle managers." "We need the job descriptions rewritten." The scope is defined, the deliverable is named, the budget is approved. All that remains is to find someone competent to build the thing.
This is the HR services model, and there is nothing dishonest about it. Someone needs a framework built; a firm builds it; it is delivered, invoiced and filed. Both sides behave honourably and the transaction closes cleanly.
The difficulty is what the request actually is. It is not a specification. It is a diagnosis.
By the time a brief reaches us, someone inside the organisation has already looked at a problem — attrition in the sales cadre, a promotion cycle nobody trusts, a leadership team that cannot agree in the room and will not disagree outside it — and decided what would fix it. The competency framework is not the problem. It is the prescription.
We are being asked to fill a prescription written by someone who never saw the X-ray.
The artefact is not the outcome
Sometimes the prescription is right. Often enough it isn't — not because the person who wrote it was careless, but because they were standing inside the thing they were trying to diagnose. That is not a failure of intelligence. It is a structural fact. The people closest to a problem have the most context and the least distance, and distance is what diagnosis requires.
So the framework gets built. It is thorough, well-evidenced, handsomely bound. It is launched at a townhall. And eighteen months later a new CHRO finds it on the shared drive and asks why nobody uses it.
Nothing went wrong in the execution. The artefact was exactly what was ordered. It simply wasn't the thing that would have changed anything, and the engagement was structured so that nobody was accountable for noticing.
Three things that actually change
The shift from services to transformation is not about doing more, or charging more, or using a grander vocabulary. Three specific things change, and they are uncomfortable.
- The brief becomes a hypothesis. We are allowed — required, in fact — to come back and say the framework isn't the issue. That the promotion cycle is distrusted because two of the five business heads have never once been overruled, and no rubric survives contact with that. This is a harder conversation than agreeing to build the framework.
- Accountability extends past handover. A services engagement ends at delivery. A transformation engagement ends when the behaviour has changed or demonstrably hasn't. That means being judged on something you do not fully control.
- The system is held whole. Structure, rewards, capability and leadership behaviour are one system. Redesign the operating model without touching how people are paid and the old model quietly reasserts itself through the incentive scheme. Most firms are organised to sell one lever at a time, because that is how procurement buys.
What the brief usually hides
A state-owned enterprise once asked us to rewrite the job descriptions for its middle and senior cadre. A clean, well-specified brief: roughly two hundred roles, a defined format, a deadline tied to the appraisal cycle. Any competent firm could have delivered it.
The interviews took three weeks and produced something the brief had not anticipated. The job descriptions were not merely out of date. They described an organisation that had reorganised twice since anyone last opened them — and, more importantly, several of the roles as actually performed had no owner at all. Two general managers had spent four years quietly absorbing work that belonged to a function which no longer formally existed. Their JDs were wrong because the org chart was a fiction, and rewriting the JD to match the fiction would have made the fiction permanent and signed.
We could have delivered exactly what was asked. It would have passed review. It would have been wrong in a way that took another three years to surface.
The brief described a documentation problem. The organisation had a structure problem that was producing documentation symptoms.
That distinction is the entire argument. A services engagement has no mechanism for making it — not because the consultants lack the insight, but because the contract does not permit the conversation. You were hired to write descriptions. Structure is out of scope, and out of scope is a commercial category, not an intellectual one.
Why most firms don't make the shift
Not because they can't. Because the services model is commercially superior in almost every respect.
It is scopeable, so it can be priced. It is deliverable, so it can be closed. It can be staffed with juniors under a partner's name, so it has margin. It ends at handover, so a failure that surfaces two years later is somebody else's. Every incentive in professional services points towards selling artefacts.
Transformation inverts all four. The scope moves as the diagnosis sharpens. The deliverable is a behaviour, not a binder. It cannot be staffed with people learning on the client's time, because the work is mostly judgement. And it holds you accountable long after the invoice cleared.
The services model isn't the lazy choice. It's the rational one. Which is exactly why so few firms leave it.
The test
There is a single question that separates the two models, and it takes about four seconds to ask.
What happens six months after you leave?
An HR vendor will describe a handover: documentation, a train-the-trainer session, a support window. All reasonable. All about the artefact.
A transformation partner will describe a return. A date already in the calendar. A measure agreed before the work started, and baselined before anyone was trained, so that the answer at six months is a fact rather than a feeling. And a willingness to report that number even when it is disappointing.
Three follow-ups make the answer harder to dress up:
- What will you measure, and what is it today? If a firm cannot state the baseline before starting, it has no way to demonstrate a shift afterwards — only to describe one.
- Who is on the room on day one, and are they the same people in month five? In the services model the seniority is concentrated in the pitch. Ask for names against phases, in writing.
- Tell me about an engagement where the six-month review was disappointing. Any firm that measures honestly has several. A firm with none has either never measured or never reported.
That last question is the most useful one in the procurement conversation, and almost nobody asks it. It is not a trap. A firm with a good answer — here is what we found, here is why, here is what we changed in our own method as a result — is telling you it has a feedback loop. A firm that has only triumphs is telling you it has a sales function.
You do not need to take anyone's positioning at face value. You only need to ask who is planning to still be accountable when the room has stopped applauding.
Meera Raghunathan · Organisation Development & Culture · Belvane Partners