The Professional Services Transformation Paradox #2 – Internal vs. Client Execution

26. März 2026
Kategorien
Newsletter abonnieren

One of the most persistent, and least openly discussed, tensions in professional services firms lies in how they execute their own transformations. It is a tension that does not reveal itself in strategy decks or partner presentations, but in the day-to-day reality of large internal programs that quietly struggle to deliver.

At first glance, the logic seems compelling. Firms that advise clients on ERP implementations, AI transformations, and operating model redesigns should be uniquely equipped to execute similar initiatives internally. They have the frameworks, the methodologies, the talent, and the experience. If transformation is their business, then internal transformation should, in theory, be a natural extension of their core capability.

And yet, the opposite is often true.

When professional services firms turn their advisory capabilities inward, three structural issues tend to emerge with remarkable consistency.

The first is a fundamental gap in operational understanding. Advisory teams are trained to diagnose, structure, and deliver transformation in client environments. They understand frameworks, governance models, and implementation playbooks. But the internal reality of a professional services firm operates under a different set of rules. Audit, tax, and advisory practices each follow distinct economic logics. Partnership structures introduce layers of informal power that rarely appear on organizational charts. Incentives are fragmented, often short-term, and deeply tied to individual or local performance. What looks coherent from the outside becomes far more complex when viewed from within. As a result, internal transformation efforts often start with a model that does not fully reflect the system it is supposed to change.

The second issue is talent allocation, and it is more structural than most firms are willing to admit. Internal programs compete directly with client work for the same pool of high-performing individuals. In a system where revenue generation and utilization remain the dominant metrics, client engagements will always win. The best people are continuously pulled back into billable work, especially when markets tighten or performance pressure increases. What remains on internal programs is not necessarily a lack of capability, but a dilution of focus, continuity, and senior attention. Over time, internal transformation becomes, by design rather than intent, a second-tier priority.

The third issue is accountability. Internal transformation programs are often governed and steered by individuals who are not the long-term owners of the outcomes they shape. Senior sponsors rotate. Program leaders move on to new roles. External advisors complete their mandate and exit. Decisions are made in the context of the program, but the consequences unfold in the operational business long after the program has closed. This creates a structural disconnect between decision-making authority and lived accountability. The people defining the future state are not always the ones required to operate within it.

Taken together, these dynamics create a contradiction that sits at the heart of many failed or underperforming transformations in professional services firms. Organizations that are highly effective at delivering complex change for their clients struggle to replicate the same level of execution internally. Not because they lack expertise, but because their own operating model introduces friction at every critical point of the transformation lifecycle.

This is where the discussion needs to move beyond capability and into governance.

The key question is not whether a firm has the skills to deliver transformation. Most do. The question is how internal transformation is positioned and governed within the firm. Is it treated as a project, structured and executed like a client engagement, with clear scope, timelines, and deliverables? Or is it owned as a long-term operational responsibility, embedded within the business, with accountability that extends beyond program completion?

Many firms attempt to do both, and end up achieving neither.

Running internal transformation like a client engagement creates momentum, structure, and clarity in the short term. But it also introduces artificial endpoints and a bias toward deliverables over adoption. Treating it purely as an operational responsibility ensures continuity, but often lacks the focus, urgency, and resource allocation required to drive meaningful change.

The tension between these two models is not easily resolved. But ignoring it is costly.

And it starts by asking a deceptively simple question:

Who truly owns the outcome of internal transformation — the program, or the business?


This article is part of a series exploring the tensions at the heart of the Professional Services Transformation Paradox.

The paradox is simple. Firms that excel at transforming their clients often struggle to transform themselves. Deeply embedded incentives, partnership structures, and legacy operating models create internal resistance to the very change they advocate externally.

Each article in this series focuses on a specific contradiction. Structural, economic, or cultural. These tensions are not side effects. They sit at the core of how decisions are made, how transformation is executed, and why many programs underdeliver.


Most transformation failures do not start with strategy, technology, or vendors. They start with governance, incentives, and blind spots at board level.

If you are currently overseeing a critical transformation, I offer a focused board-level diagnostic to identify where your program is at risk before those risks become visible in financials and delivery.

If this is relevant, get in touch.

Tags

Das könnte Sie auch interessieren

How To Select a Good Project Manager for Your Large and Complex Transformation Project

14. Juni 2024

Most transformation programs do not fail in execution. They fail in selection. Long before the first milestone is missed, the trajectory is already set by one decision that is often treated as routine. The choice of the project manager. For a sponsor, this is not a staffing decision. It is a control decision. The project

Weiterlesen

How Your Rollout in Waves Can End in a Tsunami

14. November 2022

Multinational system implementations rarely fail because of technology. They fail because the rollout model collapses under its own operational reality. One of the most common triggers is a misunderstanding of what a rollout in waves actually implies. Most organizations believe they are reducing risk when they move away from a big bang deployment. In practice,

Weiterlesen

White Elephant Stampede: Case Studies in Policy and Project Management Failures

15. Oktober 2022

This month one of the book projects I have been part of has been published by Connor Court Publishing in Australia.  The book is titled «White Elephant Stampede: Case Studies in Policy and Project Management Failures«, and it examines the seemingly endless cavalcade of projects that fail to meet their objectives, cost more than expected and

Weiterlesen

Doing Something That’s Never Been Done

14. August 2022

Executives, project sponsors, project managers, and steering committee members can learn a lot from how some deep technology startups approach their projects. This isn’t true for all kinds of projects, but it is for every project that involves doing something that hasn’t been done before and has a high risk-reward profile. This isn’t another lean

Weiterlesen

Why Are Your Best People Not Working on This?

7. August 2022

Large organizations do not lose control of critical transformation programs because they lack capability. They lose control because they systematically keep their best people out of them. It happens again and again. The organization launches a multi-million ERP, CRM, HCM, or core banking program. The stakes are obvious. If it fails, it disrupts operations, damages

Weiterlesen

Don’t Forget SaaS Performance Testing!

7. Juli 2022

Most SaaS implementations do not fail because they lack functionality. They fail because they are too slow to use. That sounds trivial. It is not. Performance is one of the few factors that directly determines whether a system will be used at all. If users have to wait after every click, every search, every transaction,

Weiterlesen

Changing Technology Is Easy; Changing Behaviour Is Not.

2. September 2021

This is an article I have written for one of my clients. You can find the original article here.   Creating a modern workplace is key to digital transformation. If you’re embarking on such an initiative, remember that changing technology is easy, but changing behaviour is not. Begin with the end in mind, ask what you

Weiterlesen

The Biggest Challenge of Postmodern ERP – Cloud Integrations

2. Mai 2021

ERP never died. It changed form. When Gartner coined the term “enterprise resource planning” in 1990, it described a very specific idea. One integrated system to run the core of the business. Finance, HR, manufacturing, procurement, all connected through a single data model and a single process backbone. For a long time, this model dominated.

Weiterlesen

Create a Lighthouse to Drive Your Transformation

13. März 2021

I’m a firm believer in transformation through delivery. In my experience real change cannot be implemented without a vehicle that is used to drive it through the organisation and crash through existing barriers.  Transformation is far more than just deploying new technologies for the sake of it. A genuine competitive advantage can only be gained

Weiterlesen

Going Live Too Early Can Be Worse as Going Late

15. Februar 2021

Large transformation programs rarely collapse without warning. They collapse because the warning signs are ignored. In post-mortems, the pattern is almost always the same. The project team knows the system is not ready. The risks are visible. The defects are known. The dependencies are fragile. Nothing is hidden. And yet, the decision is made to

Weiterlesen