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

Why Do Technology Projects Fail so Often and so Spectacularly? My Personal Top 10 Reasons

8. August 2018

It was to be a great digital leap for Germany’s biggest discount grocer. Instead, after seven years and €500 million, Lidl’s new inventory management system with SAP is dead on arrival. Now everybody is asking why. Big technology projects fail at an astonishing rate. Whether major technology implementations, postmerger integrations, or new growth strategies, these

Weiterlesen

10 Benefits of Project Portfolio Management Done Right

1. August 2018

Project Portfolio Management is a combined system of tools, methodologies, and processes to support your organization in reacting to change with the speed that is necessary for your organization to thrive. It helps you to do the right projects and to do projects right. Project Portfolio Management (PPM) does not involve making project-by-project choices based

Weiterlesen

How to Establish an Effective Steering Committee (And Not a Project Governance Board)

27. Juli 2018

Without exception, every large project I was involved with over the past 15 years had a Steering Committee (SC). Broadly speaking a SC is a group of high-level stakeholders who provide strategic direction for a project, provide governance, and supports the Project Manager. Ideally, SCs increase the chances for project success by closely aligning project

Weiterlesen

Many Decisions Are No Decisions (And This Makes Projects Difficult)

13. Juni 2018

Again and again, I am confronted with the situation during projects that I ask for a decision on something and as an answer I get «Oh, that has been already decided…». No, it is not. A decision has NOT been made until people know: > the name of the person accountable for carrying it out; > the

Weiterlesen

Understanding Your Problem Is Half the Solution (Actually the Most Important Half)

26. Mai 2018

Before we can solve a problem, we need to know exactly what the problem is, and we should put a good amount of thinking and resources into understanding it. And because today’s problems are so complex, we know they can’t be solved by being broken down into specific components. Russell Ackoff (1979) has one of

Weiterlesen

How to Review Your Team’s Software Development Practices

1. Mai 2018

An important part of the project reviews I do is a software development practices review. Notice I do not say «best practices». The term “best practices” is without meaning in many contexts. At best, it’s vague, subjective, and highly dependent on context. Wikipedia defines best practices as: “A best practice is a method or technique

Weiterlesen

Proactively Manage Your Project With RAID Lists (Risks, Assumptions, Issues and Decisions)

24. April 2018

RAID is an acronym for Risks, Assumptions, Issues, and Decisions. Some use the «D» for dependencies instead of decisions, and some use the «A» for actions instead of assumptions. I personally track dependencies on my assumption list (because that is what dependencies are) and I have no need for a separate action list since I

Weiterlesen

Start Your Project With a Walking Skeleton

14. April 2018

In order to reduce risk on large software development projects, you need to figure out all the big unknowns as early as possible. The best way to do this is to have a real end-to-end test with no stubs against a system that’s deployed in production. You could do this by building a so-called Walking

Weiterlesen

It's Never Too Early to Think About Performance

9. April 2018

Business users specify their needs primarily through functional requirements. The non-functional aspects of the systems, like performance, responsiveness, up-time, support needs, and so on, are left up to the development team. Testing of these non-functional requirements is left until very late in the development cycle, and is sometimes delegated completely to the operations team. This

Weiterlesen

Doing the Right Number of Projects

30. März 2018

I have written about project portfolio management extensively. In all my articles I relentlessly repeated the three goals of Project Portfolio Management. 1) Maximizing the value of your portfolio 2) Seeking the right balance of projects 3) Creating a strong link to your strategy After some thinking and new experiences, I have decided to add

Weiterlesen