The Professional Services Transformation Paradox #8 – Short-Term Revenue vs. Long-Term Capability

23. April 2026
Kategorien
Newsletter abonnieren

Professional services firms are built around revenue.

Revenue is visible, measurable, and immediate. It drives partner compensation, signals performance, and anchors decision-making across the firm. Every client won, every project sold, every hour billed translates directly into current-year outcomes.

Capability building works differently.

It requires investment upfront, often without immediate return, and pays off over years rather than quarters. New platforms, new offerings, new delivery models, and new capabilities take time to develop, time to scale, and time to translate into revenue. In the short term, they are a cost.

That difference creates a structural bias.

Firms are optimized to sell what they can deliver today, not to build what they will need tomorrow. When faced with the choice between immediate revenue and longer-term capability, the system naturally leans toward the option that improves current performance. Not because leaders do not understand the importance of investment, but because the economic model rewards what is realized now.

The effect is subtle, but persistent.

Investment decisions are framed as trade-offs against current-year performance. Capability building is delayed, scaled back, or re-scoped to fit within acceptable economic boundaries. Initiatives that require sustained commitment over multiple years struggle to maintain momentum, especially when leadership rotates and priorities shift.

Over time, this creates a gap.

The firm continues to grow, continues to sell, continues to deliver, but the underlying capability base evolves more slowly than the market. What looks like strong performance externally can mask a growing internal misalignment between what the firm is currently able to do and what it will need to do in the future.

This is where the tension becomes visible.

Markets move faster than capability development cycles. Technology evolves, client expectations change, and new competitors enter with different models. Firms that rely too heavily on existing capabilities can continue to generate revenue for a time, but they increasingly do so by stretching what they already have rather than building what they need next.

The partnership model reinforces this dynamic.

Compensation is tied to current-year results. Performance is evaluated annually. Leaders are measured on what they deliver within their tenure. In that context, long-term investments are always competing with short-term outcomes, and short-term outcomes are easier to justify.

This does not mean firms do not invest.

It means they tend to underinvest relative to what is required for structural change.

The result is a pattern that repeats across many firms. New capabilities are announced with ambition, but funded cautiously. Transformation programs are launched, but adjusted to protect current performance. Investments are made, but not always at the level or duration needed to fundamentally shift the trajectory of the business.

Externally, the firm appears active and evolving.

Internally, the pace of capability development remains constrained.

That is why the hardest part of building long-term advantage in professional services is not identifying what to build.

It is sustaining the commitment to build it.

Because unless the economic model allows firms to absorb short-term impact in exchange for long-term capability, they will continue to prioritize what is visible today over what is required tomorrow.

And over time, that gap becomes harder to close.


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.


I work with boards and executive teams on independent perspectives related to professional-services transformation, governance, operating models, platform economics, and the changing economics of professional-services firms.

If your leadership team is working through similar questions around ownership structures, governance alignment, investment pressure, or operating-model evolution, you may find my Future of Professional Services board sessions and Transformation Reality Review valuable. Feel free to reach out.

Henrico Dolfing

Tags

Das könnte Sie auch interessieren

The Project Recovery Process Explained

12. Februar 2018

Projects fail for a variety of reasons. Especially technology projects have a low success rate. Typically more than half of them are considered a failure. But it does not have to end that way. As soon as a project is identified as in trouble you can start thinking about project recovery. This sentence already states a very

Weiterlesen

What Exactly Is a Troubled Project?

11. Februar 2018

Most of my work as a project recovery consultant is with what you can call «troubled projects». But what does this actually mean? Many teams I have worked with seem to be stuck in the PMI view of things. The PMBOK® Guide defines the successful project as a project that meets its objective in terms

Weiterlesen

What is a Project Review?

5. Februar 2018

> You want to know where you are standing with that large, multi-year, strategic project? > You think one of your key projects is in trouble? > Or you know that one of your key projects is in trouble? Then a project review is what you are looking for. When we talk about a project review, there

Weiterlesen

When Is My Project a Success?

22. Januar 2018

Project success and project failure are NOT absolutes.  It may not be possible to be a little bit pregnant, but you can be a little bit successful.  Every project has multiple success criteria related to business results, product/service results, and project delivery results (cost, schedule, scope, and quality). Some criteria are absolute, meaning they must

Weiterlesen

The Only Test Plan You Will Ever Need

3. Januar 2018

Assuming an iteration between two and four weeks: 1) Programmers will write unit tests in the code to ensure product technically behaves. The team will perform QA activities to ensure these are valid tests. 2) In the iteration planning meeting and in the iteration itself, tests cases will be defined as acceptance criteria for each

Weiterlesen

No Validation? No Project!

27. Juli 2017

For large or high-risk projects (what is large depends on your organization) it should be mandatory to do business case validation before you dive head-on in executing the project. In my Project Portfolio Funnel you will see a phase that is called «Validation» after selection of a project has taken place. In this phase you typically have a

Weiterlesen

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