Every organisation that has been through multiple major consulting engagements produces the same internal evolution. It is not always visible from the outside. It does not appear in any organisational chart. But it shapes who gets promoted, who gets listened to, and ultimately what the organisation becomes capable of doing on its own.
A new class of internal power emerges. We call them the translators.
They are not a conspiracy. They are a rational response to the environment. When an organisation repeatedly brings in major consulting firms, someone inside has to manage that relationship. Someone has to prepare the data rooms, brief the junior teams, manage the partner interactions, run the internal PMO that connects the consulting workstream to the operational reality. This is real work, and it requires real skill.
The skill it requires, however, is not the skill of understanding the business. It is the skill of understanding the consultants. How to speak their language. How to format information so they can absorb it quickly. How to run a steering committee meeting. How to present findings to a C-suite that has been primed to trust external validation. How to write status updates that satisfy the partner's oversight requirements without creating organisational friction.
These are learnable skills. They are also highly visible to leadership in a way that operational expertise is not. The person managing the consultancy engagement is in constant contact with the most senior people in the organisation. Their work product is visible at every leadership review. Their competence is measured against the standards the consulting firm itself has set, which are not the standards of operational excellence but the standards of executive-level communication and process management.
So they get promoted.
Over years, the people who rise in a consulting-addicted organisation are disproportionately the ones who have mastered the translator role. The internal strategy teams, often staffed with former consultants themselves, accumulate influence not because they understand the business better than anyone else but because they know how to manage the external relationship that the business has decided it cannot function without.
The people who actually build the product, run the customer relationships, understand the operational constraints they are not promoted at the same rate. Their expertise is not as visible. Their communication style does not match the expectations that have been set by repeated exposure to consulting-grade presentation standards. They are frequently excellent at their jobs. They are not excellent at the meta-game of organisational politics in a consulting-addicted culture.
The downstream effect is severe. The organisation begins to confuse the administration of the business with the actual craft of the business. It produces an extraordinary volume of tracking metrics, synergy reports, workstream status updates, and governance documentation. The quality of the core product, the service, the customer relationship, the operational process, degrades slowly and continuously because the people with the deepest understanding of these things have been systematically sidelined by a promotion culture that rewards a different kind of competence entirely.
What is left is an organisation that is administratively sophisticated and operationally fragile. It can produce a beautiful slide about its transformation progress. It cannot reliably execute the transformation the slide describes.
contraco's work often begins at this point not with strategy but with a reckoning about who actually knows what inside the organisation. The translators have genuine skills. But so do the operators, the engineers, the customer-facing teams whose pattern recognition has never been incorporated into the strategy that claims to represent them. Rebuilding that connection, making internal expertise legible to leadership again, is the precondition for any transformation that intends to last beyond the next consulting engagement.
A strategy that the people who must execute it did not help create is not a strategy. It is a document.
In your organisation, who has more internal influence the person who best understands your core product, or the person who best understands how to run a PMO?