Why Most Multi-Site Operators Adopted a Break-Fix Operating Model

Over the past several months, I’ve spent a great deal of time speaking with school districts, self-storage operators, dealerships, hotels, and other multi-site organizations. While these industries have very different missions, I’ve been struck by how similar their operational challenges really are.

The conversations inevitably gravitate toward the same themes. Large portfolios. Hundreds or thousands of assets. Numerous service providers…often for the same asset types. Outdated spreadsheets. Fragmented information. And perhaps most importantly, limited visibility into asset lifecycle readiness and operational risk.

Yet despite these challenges, very few leaders question the importance of understanding their assets. They want to know what they own, where those assets are located, how they are performing, and where operational or capital risk may be emerging. They want confidence that critical assets will continue to perform as expected and visibility into where future investments may be required.

Nobody disputes the value of that information.

What is less obvious is why so few organizations have been able to obtain it consistently.

The common explanation is that asset management simply hasn’t been a priority. I don’t believe that’s true. Most operators care deeply about their facilities, equipment, service providers, and capital investments. In fact, in most cases these assets are directly responsible for delivering customer experience and revenue.  So, the problem is not a lack of awareness or commitment.

The problem is that for most multi-site organizations, the economics, complexity, and provider ecosystem made anything other than a break-fix operating model incredibly difficult to sustain.

Historically, building a meaningful asset management program required significant investments of time, people, and money; resources that were already in short supply. Organizations often found themselves engaging consultants to perform facility assessments, conducting extensive asset inventories, implementing software platforms, building spreadsheets, and then attempting to maintain all of that information as their portfolios evolved.

Even when these efforts were successful, the result was often a point-in-time snapshot rather than a living operational capability.

The challenge, of course, is that facilities do not stand still.

Assets are replaced. Equipment is relocated. Facilities are renovated. New locations are added. Service providers change. Operating conditions evolve. The information begins aging almost immediately, and keeping it current often becomes as difficult as collecting it in the first place.

As portfolios grow, the problem compounds. A single facility can often be managed through local knowledge and direct observation. Once an organization expands to dozens, fifty, one hundred, or even several hundred locations, the operating environment changes dramatically.

Multi-site operations are inherently complex. They involve thousands of assets, numerous service providers, multiple disciplines, and countless operational decisions occurring across a distributed portfolio. Much of this coordination has historically been managed through spreadsheets, reports, emails, phone calls, work orders, and institutional knowledge.

As portfolios expanded, organizations needed practical ways to coordinate maintenance activities, control costs, and create accountability for who was performing work. This led to the emergence of work order and ticketing systems, which became the operational backbone for many facilities organizations. These systems helped organizations manage service delivery, dispatch technicians, track labor, manage vendors, and monitor maintenance spending across increasingly complex portfolios.

The challenge, however, is that work order systems were designed to control work, not govern readiness. They provided visibility into what work was requested, assigned, completed, and paid for, but they offered limited insight into overall asset condition, lifecycle risk, operational readiness, or future capital exposure. As a result, organizations became increasingly effective at managing maintenance activity while continuing to struggle with the broader challenge of understanding and governing the health of their portfolios.

As portfolios continued to expand, the complexity compounded. More sites created more assets, more vendors, more operating variations, and more opportunities for information to become fragmented. Every additional location increased the challenge of maintaining consistency, accountability, and visibility across the portfolio.

Questions that should be simple became surprisingly difficult to answer.

• What assets do we actually own?

• Which assets represent our greatest operational risk?

• Which assets represent capital risk?

• Which sites require immediate attention?

• Where are we carrying avoidable capital exposure?

• Which service providers are improving performance and which are not?

Most organizations can answer these questions eventually. The problem is the amount of effort required to get there.

Over time, this challenge evolved from an information problem into an operating model problem.

Most organizations never set out to adopt a break-fix strategy. In fact, nearly every leader I speak with would prefer a more proactive and governed approach to managing assets, maintenance, and capital planning. The challenge is that as portfolios grow, the complexity of achieving that outcome grows even faster.

Over time, a powerful form of organizational inertia begins to emerge. Standardization becomes harder. Local workarounds become common. Information drifts into different systems and different formats. Decision-making becomes increasingly decentralized. Every site, provider, and technician develops slightly different ways of operating.

As this happens, attention naturally shifts toward the events that are easiest to see and react to.

Failures → Complaints → Emergencies → Service calls.

These events become the primary signals driving operational attention, not because they are the most important indicators of readiness, but because they are the most visible.

The industry evolved around those events. Service providers were engaged when something broke. Assessments were performed periodically. Capital planning exercises occurred infrequently. Data was refreshed inconsistently. Operational attention became centered on responding to issues rather than continuously governing readiness across the portfolio.

The result was not a failure of leadership or execution. It was a rational response to an operating environment where complexity continued to grow while visibility, standardization, and accountability struggled to keep pace.

In many ways, break-fix became the default operating model not because it was preferred, but because it was the only model the ecosystem could reliably support.

Looking back, it is difficult to blame operators for embracing this model. The cost was high, the effort was significant, the data became stale almost immediately, and the ecosystem itself rewarded reaction more than readiness.

For decades, the industry attempted to solve these challenges with better assessments, larger software platforms, and increasingly sophisticated reporting tools. Many of those innovations created value, but they did little to address the underlying challenge. Continuous asset intelligence remained difficult to obtain and even harder to maintain.

The more I study this problem, the less I believe break-fix is a maintenance strategy.

I believe it is the natural outcome of an operating model that lacks the visibility, accountability, and coordination required to continuously govern readiness across a portfolio.

Perhaps that is why the more interesting question is not why so few organizations embraced asset management.

The more interesting question is whether the industry ever made continuous asset intelligence practical in the first place.

Because until organizations can continuously understand asset condition, operational readiness, and lifecycle risk across their portfolios, they will continue to manage exceptions instead of performance.

And that is ultimately what break-fix has always been: not a preferred operating model, but a rational response to an operating model that lacked the information necessary to do anything else.

— David Trice, CEO Oversiit

If your organization manages multiple facilities and still relies on spreadsheets, assessments, and fragmented information to understand operational risk, we’d welcome the opportunity to share how we’re thinking about the future of operational readiness at Oversiit. Contact us for more information.