Freestyle

Executive Monday Insights

Most organizations want to improve, but few are built for it.
They rely on central initiatives, large transformation programs, or bursts of executive attention to create progress. These approaches often generate initial energy, but the effect fades once the focus shifts. The underlying operating model remains unchanged – and with it, the organization’s ability to adapt.

The future COO takes a different path.
Rather than driving improvement through periodic intervention, they design an operating system where improvement happens naturally, led by teams and guided by real signals rather than top-down direction.

This is not a softer version of operations.
It is a more disciplined one – and far more sustainable.

Why Improvement Needs a New Operating Model

Modern organizations operate in environments marked by shifting customer needs, continuous technological change, and increasing complexity across products, partners, and processes. Traditional operating models were built for stability, not change. They rely on:

• Annual planning cycles
• Layered approvals
• Functional silos
• Centralized problem-solving

These structures create predictability, but they slow adaptation. When the environment demands rapid adjustment, organizations relying on top-down initiatives struggle to keep up.

A self-improving operating system solves this by embedding learning and adaptation into daily work – not as an initiative, but as a property of the system itself. Teams do not wait for permission to adjust; they adjust because they are designed to.

How Real Improvement Happens

In high-performing adaptive organizations, improvement doesn’t begin in meeting rooms or steering committees. It begins at the point of reality – where teams see friction, observe delays, feel customer signals, and experience the consequences of unclear decisions.

Teams:

• Identify problems based on real-time signals
• Engage directly with customers to understand needs and gaps
• Run small, low-risk experiments
• Scale the solutions that work

Leadership’s role shifts away from directing change and toward improving the system in which teams make decisions. The measure of success for leaders becomes how quickly and how well teams learn – not how many initiatives are launched.

Reducing Distance: Customers and Decisions

Two forms of distance determine how quickly organizations adapt:

Customer Distance

When teams are separated from customers by layers of intermediaries or filters, insight is delayed and distorted. Reducing this distance allows teams to understand intent, quality issues, and emerging needs directly.

An operating model built on proximity – where teams engage with customers themselves – responds faster and with better judgment.

Decision Distance

Most delays inside organizations come from decision friction: escalations, unclear authority, and a lack of shared reasoning.
Reducing decision distance means:

• clarifying who decides what,
• documenting decisions transparently,
• lowering the time between signal and action, and
• reducing how often decisions need to be reopened.

Over time, organizations that reduce these distances become faster and more accurate without adding pressure or workload.

The Conditions for Team Autonomy

Autonomy is not the absence of rules.
It is the presence of clear, disciplined boundaries.

Teams should act autonomously when:

1. They face a real problem, not an imagined one
2. They have the competence to decide well
3. Their decision does not undermine another team’s autonomy
4. The decision can be tested safely

This framework creates responsible autonomy – enabling speed while protecting the coherence of the broader organization.

When these conditions are met, decisions move closer to the work, quality increases, and outcomes improve. When they aren’t, autonomy simply pushes inconsistency downward.

Designing Work Before Selecting Tools

Organizations often reach for tools when what they need is clarity.
But tools amplify the underlying system, good or bad. They do not fix it.

Before introducing new systems, automation, or AI capabilities, COOs need to:

1. Remove unnecessary processes rather than automate them
2. Simplify decision-making pathways so teams know how to act
3. Ensure humans remain accountable for intent, constraints, and outcomes
4. Use tools to shorten time-to-value, not to hide complexity

When work is well-designed, tools accelerate progress.
When work is unclear, tools accelerate confusion.

Building a System That Gets Better Over Time

Sustainable improvement depends on alignment across five areas of the operating model:

Strategy

Clarity about global outcomes ensures that local optimization does not erode overall performance.

Culture

Improvement becomes the standard expectation, not a special event. Teams assume that change is normal, not disruptive.

Organization

Structures are designed to support continuous, effective decision-making rather than to reflect internal power or historical functions.

Processes

Workflows are kept as short and simple as possible, enabling visibility and reducing friction.

Execution

Teams are supported to reach good decisions quickly – and to adjust when evidence suggests they should.

When these elements reinforce each other, the organization becomes self-correcting.
Signals travel quickly.
Experiments are easy.
Learning is frequent.
And the operating model evolves continuously.

A New Role for the COO

The future COO does not scale improvement by adding more initiatives.
They scale it by removing the dependency on initiatives altogether.

Their work focuses on:

• reducing friction in the system,
• shortening the distance between signal and action,
• designing for autonomy with clarity,
• and enabling teams and value streams to improve without waiting for permission.

In doing so, the COO shifts the organization from a model of managed change to a model of constant evolution.

The goal is not simply higher efficiency or faster execution.
The goal is an organization that improves because it is designed to do so – an operating system that gets better every week, not every program cycle.

👉 If you want to explore what a self-improving operating system could look like in your organization, we’re ready to help.

To receive a new edition every week, we invite you to sign up to the Executive Monday Insights Newsletter

You can find other articled here.