The Professional Services Transformation Paradox #3 – Long-Term Investment vs. Short-Term Management

27. März 2026
Kategorien
Newsletter abonnieren

One of the most underestimated constraints in professional services transformation is not technology, capability, or even funding. It is time.

Real transformation takes longer than most firms are structurally able to tolerate. Core systems such as ERP platforms, data architectures, AI capabilities, or global workflow solutions are not incremental improvements. They are foundational changes. They reshape how a firm operates, how decisions are made, and how value is delivered to clients. These are multi-year journeys, typically spanning three to five years, often longer. They require continuity in leadership, consistency in funding, and a willingness to accept delayed returns.

This is where the structural tension begins.

Because professional services firms are not built to think in these time horizons.

Most partnerships operate on an annual economic cycle. Profit is distributed every year. Partners are evaluated on yearly performance. Utilization drives behavior. Leadership roles rotate, often every two to four years, sometimes even faster in key positions. The system is optimized for short-term performance, not long-term investment.

This creates a fundamental conflict that sits at the heart of many transformation failures.

Long-term transformation meets short-term economics.

At first, this conflict is not visible. Transformation programs typically start with strong momentum. There is a clear case for change, often triggered by competitive pressure, regulatory requirements, or the promise of efficiency gains. Budgets are approved. Leadership is aligned. The narrative is compelling.

But transformation is not a linear journey. After the initial phase, complexity increases. Costs become more visible. Benefits are still largely in the future. And this is usually the moment when the underlying economic model of the firm starts to reassert itself.

Around the 18 to 24 month mark, the tone changes.

Budget discussions become more critical. Questions shift from “How do we make this successful?” to “How much are we still willing to invest?”. Scope is revisited. Elements that were once considered essential are suddenly labeled as optional. The program is not stopped, but it is gradually reduced. Not in one decision, but in many small ones.

Individually, these decisions appear rational. Collectively, they change the outcome.

What started as a transformation becomes a compromise.

The impact is diluted, timelines extend, and the original ambition quietly disappears. From the outside, the program may still look active. Internally, it has already lost its ability to deliver the intended change.

At this point, the typical diagnosis is wrong.

The discussion often turns to technology choices, vendor performance, or execution quality. But in most cases, these are symptoms, not causes. The underlying issue is structural. The governance model does not protect long-term investment from short-term pressure.

There is no mechanism that forces the firm to stay the course when the economics become uncomfortable.

And that is the real problem.

Because as technology becomes central to how professional services firms operate, transformation is no longer an IT topic. It directly affects pricing, delivery models, risk management, and ultimately competitiveness. Decisions about continuing or scaling back transformation programs are therefore not operational decisions. They are strategic ones.

This makes transformation a board-level responsibility.

Not in the sense of reviewing status reports or approving budgets, but in actively shaping the conditions under which long-term investment can survive inside a short-term system. Without that, even well-designed programs with strong teams and capable technology will fail to deliver.

The uncomfortable question every firm needs to answer is simple.

Who is actually protecting long-term transformation when everyone else is incentivized to optimize short-term results?

As long as this question remains unanswered, the pattern will repeat itself. Programs will start with ambition, build early momentum, and then slowly erode under economic pressure. Not because the strategy was wrong, but because the system was never designed to sustain it.

Getting this right is not about better project management. It requires confronting the economic logic of the partnership model itself.

And that is where most firms hesitate.


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.

Das könnte Sie auch interessieren

When is your Project Backlog Item "Ready" for selection?

26. Juli 2017

As defined in the Simple Portfolio Management Framework, the Project Backlog is an ordered list of all projects that might be needed in the organization and is the single source of projects for any changes to be made in the organization. The Portfolio Owner is responsible for the Project Backlog, including its content, availability, and

Weiterlesen

The Project Portfolio Funnel

24. Juli 2017

When you look at the project portfolio funnel of the Simple Portfolio Management Framework (SPMF) it looks like the diagram below. Like I explained in previous articles, this is not greatly different from how PMI defines the project portfolio funnel. What is greatly different, is how you manage your funnel. SPMF is a framework within which

Weiterlesen

No More User Stories! There Are Jobs to Be Done

13. Juli 2017

Creating new and better products that thousands or millions of customers actually love is a top priority for almost every company. Agile frameworks and techniques have been hailed as a solution for exactly this problem. It started with eXtreme Programming (XP), where a conversation between the development team and the customer is the base for all requirements. And

Weiterlesen

The Reverse Triple Constraint of Troubled Projects

25. April 2017

Assuming you suspect or know that one of your projects is in trouble the first step is always an extensive project review. After such a review you hopefully have the necessary information for decision-making as well as the team’s support for the recovery of the project. It may be highly unlikely that the original requirements

Weiterlesen

8 Signs of troubled projects for project sponsors

19. April 2017

When you’re dealing with a troubled project, there are usually a number of red flags surrounding you. This article is written from the perspective of senior management (for instance the project sponsor, members of the Steering Committee, or the executive management). All of us have endured troubled projects that didn’t accomplish their intended business goals. Such watermelon projects,

Weiterlesen

Building Is the Easy Part…

6. März 2017

Agile Frameworks and books tell us how to build a product–that’s the easy part… What we are not told are equally important things like maintaining, operating, fixing and extending the built product. When your agile philosophies fail to cover these areas, it greatly reduces agile’s benefits. This is where DevOps comes into play. DevOps is the combination

Weiterlesen

Paying Technical Debt

15. Januar 2017

The metaphor of technical debt in code and design can be defined as follows: You start at an optimal level of code. In the next release, you are adding a new feature. This would take an effort E. This, of course, assuming that estimations are somewhere near reality. If the level of code was less

Weiterlesen

Outsourcing Technical Competence Is a Very Bad Idea

2. Dezember 2016

I have written about technical competence in the context of Software Engineering Practices. This article will shed some light on a different aspect of technical competency. Outsourcing it. A number of companies I have worked for have started a large project based on a technology they are not competent in, or even completely unfamiliar with.

Weiterlesen

Estimating with Wideband Delphi and Monte Carlo Simulation

18. Oktober 2015

During the LeSS training in Berlin last week with Craig Larman he mentioned the best estimating method he knows for any big software project. Wideband Delphi with Monte Carlo Simulation. I agree with him on this one hundred percent. This article will explain what Wideband Delphi and Monte Carlo Simulation is (Part 1 & 2),

Weiterlesen
Previous