Your Company’s Unappreciated Growth Engine

These questions may sound simple, but they’re not easy to answer. The achievement of a BOS is that it makes asking and answering these questions a routine organizational habit rather than an intermittent aspiration. It establishes a common language, a cadence of accountability, and a mechanism for cascading company-level goals down to individuals, so that every member of the team understands not just what they do but why it matters. Strategy becomes a shared, actionable blueprint.

Supported by data

The case for business operating systems has long rested on practitioner testimony and case evidence. What’s new is recent longitudinal research, which offers something more rigorous.

In a 2026 analysis, TrueSpace, which conducts industry research, examined about 300 small and medium-sized businesses over approximately five years using a standardized organizational capability instrument developed in collaboration with the analytics and advisory firm Gallup. The instrument scored the companies across five dimensions—alignment, discipline, endurance, predictability, and value creation—and the scores were synthesized into a composite investability index that had a scale of 300–850. Companies in the dataset were divided into those with a formal, structured operating system and those without.

One finding that stands out is methodological: The analysis confirmed that the instrument itself was sound and didn’t flatter the companies that already had structured operating systems in place. The study controlled for engagement depth through propensity matching, which involved pairing each structured-system company with a nonsystem counterpart at the same starting score and assessment history. On any given cross-sectional assessment, the two groups were statistically indistinguishable. The instrument measured where an organization was, not how it chose to get there. The playing field was level.

A second finding is where the performance gap between companies running a BOS or not becomes compelling: Companies operating with a structured system grew their organizational capability at nearly three times the monthly rate of those without one—a difference that widened, rather than narrowed, over successive assessment cycles. Among companies lacking a formal operating system, a growth inversion emerged: Early gains reversed themselves as assessment cycles continued, with mean scores turning negative by the second and third measurement periods. This is consistent with a broader mean-reversion pattern in the dataset.

Organizations without structural scaffolding might improve with intention and effort, but they will struggle to sustain those improvements over time. Companies with a formal operating system resisted this reversion. The mechanism appears to be structural—the meeting cadence, accountability cycles, and issue-resolution disciplines that a formal system provided converted initial gains into a durable trajectory rather than a single-cycle spike.

A third finding is the investability implication: Businesses with formal systems grew faster, more consistently, and with less volatility. On the composite index, companies with this type of system scored a mean of 602 (squarely in the “good” tier) versus 484 for companies without one, a gap of 118 points. The broader portfolio mean of 492 sat in the “at risk” band. Structured-system companies weren’t intrinsically better businesses; as the first finding established, they started in the same place. Their trajectory, sustained across multiple assessment cycles, is what determined organizational investability over time.

The research also illuminates where the growth comes from. The largest differentials appeared in alignment and endurance, the categories most directly addressed by the structured-meeting rhythms, goal cascading, and accountability mechanisms that characterize a well-implemented operating system.

The catch: It’s hard to do well

The evidence is persuasive. The implementation is hard.

Deploying a BOS is not a weekend project. Researchers and practitioners who have worked through these implementations estimate that embedding a new operating system into a company’s DNA typically takes 12–36 months, and often longer for full cultural internalization. It requires capital investment, executive attention, and a sustained commitment to utilizing and engaging with the new framework even as daily crises compete for that attention. It’s like replacing the engine of an airplane in midflight.

The transition is also genuinely disruptive. A formal operating system introduces new language, rhythms, and expectations around accountability and transparency. This can feel like a significant cultural shock. Some employees will welcome the clarity, while others won’t. Teams implementing these systems consistently report meaningful organizational churn as team members who are uncomfortable self-select out. This is not a failure of the system; it is the system working as designed. But it requires leadership resolve that some teams underestimate.

Two further limitations deserve emphasis. A BOS cannot rescue a fundamentally broken business model. If the underlying economics are poor, no amount of structural discipline will compensate. Similarly, a BOS cannot substitute for genuine leadership capability. The system provides scaffolding; it does not supply the judgment, interpersonal skills, and strategic acuity that effective leadership demands. Leaders who mistake the framework for a replacement for those qualities will be disappointed.

A high-return organizational investment

Given all of that, the reasonable question is whether the investment is worth it. The evidence says yes—and it says so in a way that should give pause to any leadership team that has been deferring this decision.

The TrueSpace data reveal something subtle but important: The disadvantage of operating without a formal system was not static. It compounded. Companies without a formal operating system did not simply grow more slowly; they regressed. Their early organizational gains eroded. The mean-reversion pattern was pervasive, and without the structural scaffolding that a formal operating system provided, initial improvements in organizational capability tended not to stick. Leadership teams that invest energy in organizational health without a system to sustain it are, in a sense, working against entropy.

The implication for privately held businesses is practical and urgent. For a leadership team trying to accelerate value creation, a BOS may be the highest-return organizational investment available. The organizations that implement these systems sustain growth in ways that their counterparts cannot, with the gap widening over time.

This is an insight that has historically been more intuitive than empirical, but the emerging research is making it quantifiable. A growth-rate difference of nearly 300 percent, a 118-point investability gap, a reversal of mean reversion—these are measurable outcomes associated with a specific class of organizational choice.

The concept of a BOS has been around a long time, but now there are data to demonstrate its effectiveness. Leadership teams that treat the decision to design and implement a formal BOS as optional, or as something to revisit once the business is “ready,” may be misunderstanding both the nature of the advantage and the cost of delay. The businesses that will look most transformed five years from now are likely already operating with an established system today.

Alex Hodgkin is adjunct assistant professor of entrepreneurship at Chicago Booth.