Financing Growth With Operating Debt

Growth is usually evaluated through what it creates: more revenue, more clients, new products, expanded markets, greater scale. What is harder to see is what the organization has to absorb in order to support it.

A new client may require special handling. A product may introduce another workflow. An acquisition may bring systems that cannot be integrated quickly. Each decision may be entirely rational when the commercial opportunity is worth capturing now.

The problem begins when those consequences stop being visible as part of the economics of growth. The business receives the benefit immediately while some of the cost is deferred into manual work, exceptions, headcount, fragmented systems and institutional knowledge.

That is operating debt.

Like financial debt, it is not inherently bad. It can be a deliberate way to move faster. The important question is whether leadership still understands what it is carrying, why it was incurred and what it will eventually cost.

Growth does not always require a new operating model

A company can grow significantly in volume without fundamentally changing the way it operates. If it is serving more clients or processing more transactions of essentially the same kind, the existing operating model may continue to work with additional capacity.

The problem is when growth is accompanied by increasing complexity. New products, client types, strategies, markets, acquisitions or servicing requirements change what the business is asking the operating model to support. The organization is no longer simply doing more of the same work. It is managing more kinds of work, more dependencies, more decisions and more exceptions.

Volume and complexity begin to compound each other. An operating model designed for an earlier version of the business may still appear functional, particularly if people keep compensating for its limitations. The cost starts to show up elsewhere: more manual intervention, additional coordination, duplicated work and greater dependence on people who know how to navigate the gaps.

A temporary workaround may still be the right decision. The problem is when those accommodations accumulate faster than the operating model evolves.

Watch the trajectory, not only the failure

One of the more useful lessons I learned operating at scale is that weakness often becomes visible before outright failure. The signal is usually a change in trajectory: exception volumes rise, processing times lengthen, manual intervention grows, and experienced employees spend more of their time compensating for work the operating model should handle without them.

I saw this in a proprietary trading environment. For years, latency worsened, crashes became more frequent, missing functionality pushed work downstream, and post-trade teams received data later and worked later. A broader improvement effort was already underway, but the fundamental capacity issue repeatedly lost priority to other work.

Then, during one of the extreme-volume periods at the beginning of COVID, the system collapsed under the load. Once failure made the issue urgent, the immediate capacity problem was fixed relatively quickly. What stayed with me was not the collapse itself. It was how long the trajectory had been visible before the underlying constraint became impossible to defer. Waiting for something to break is an expensive way to determine whether the architecture still fits the business.

When operating debt is still worth carrying

Organizations do not need to eliminate operating debt. Sometimes carrying it is the right choice. Speed may matter more than elegance. A valuable opportunity may justify temporary manual work or added complexity. Replacing a legacy system may cost more than continuing to support it.

Executive judgment lies in knowing when that debt is still serving the business and when it is beginning to constrain it. Keeping it visible means looking beyond whether the operation is meeting its obligations today. Are exceptions, processing time or manual intervention increasing faster than the business itself? Are downstream teams compensating for limitations that look acceptable elsewhere? Are temporary accommodations quietly becoming permanent architecture?

Leaders tend to evaluate growth through revenue, assets, customers or strategic opportunity. Those measures are necessary, but incomplete if they exclude what the organization must absorb in order to support that growth.

The economic case for growth should include the cost of complexity.

Most growing organizations will accumulate some form of operating debt. The goal is not to eliminate it. The goal is to keep it visible enough that leadership continues to make the tradeoff consciously.