An operating model is the connective tissue between strategy and execution — the integrated system that determines how an organization’s capabilities, processes, decisions, roles, culture, and workforce combine to get work done. It is not an org chart. Org charts show reporting relationships; an operating model answers the harder question: how does strategic intent become the daily reality for thousands of people across the organization?
This distinction carries consequences. Most organizations, when performance lags, redraw the org chart. When accountability is unclear, they add a management layer. When collaboration breaks down, they restructure teams. But the architecture of boxes and reporting lines does not, on its own, determine whether a strategic decision reaches the front line, whether the right people are making the right calls, or whether the organization can actually deliver on what it has promised. Structure is one input. The operating model is the full system.
An Operating Model Is a Translation System, Not a Structure
Lotis Blue defines the operating model across seven interconnected elements:
- Differentiating Capabilities
- Processes & Technology
- Roles & Accountabilities
- Decisions & Governance
- Organizational Structure
- Behavioral Norms & Culture
- Workforce Strategy
These are not independent levers to be adjusted separately. They form a system in which each element shapes the others. A governance structure built for one decision-making authority must align with the roles that carry it. Behavioral norms must reinforce the capabilities the organization needs to win. Workforce strategy must reflect what the model actually requires of the people executing it.
The implication is that partial operating model work — redesigning structure while leaving governance, norms, and capabilities unchanged — typically produces partial results. The elements that were not redesigned impose their existing logic on the ones that were, and the desired change gets absorbed by the system rather than embedded in it.
Why Execution Breaks Below the Executive Layer
Most operating model failures are not failures of strategy design. The strategy is often sound. The failure is in translation, or the gap between what leadership decides and what actually happens several organizational layers below.
This is a structural problem, not a personnel problem. When operating model design focuses on executive-level alignment — which is the correct starting point — it naturally produces clarity at the top. The CEO and the senior leadership team understand the model, agree on priorities, and share a view of how decisions should be made. But that clarity tends to live in the conversations and documents the executive team engaged with. Several layers down, operations managers and front-line supervisors are still working from the structures, habits, and informal norms they have always used. They have not received clear guidance on which decisions they can make, what behaviors are expected, or how their daily work connects to the strategy the leadership team just ratified.
This happens not because leaders intend to design a model that stops at the top, but because the work of deep translation is routinely underestimated. Achieving alignment at the executive level is visible and verifiable — the leadership team is in the room, and agreement can be confirmed. Translating that alignment into middle-management and front-line behavior requires a different kind of effort: explicit accountability structures designed for operational contexts, governance norms adapted to the decisions that actually occur below the senior team, and feedback loops that surface whether the intended behaviors are taking hold. Most operating model efforts invest heavily in the former and insufficiently in the latter.
The gap compounds as you move further from the executive team. The people who fulfill the order, serve the customer, manage the distribution center, or deliver the service are executing inside a model that was never fully designed for their context. They perform against a strategy they cannot see, inside an accountability structure clarified at levels above them but never translated into the specific terms of their work. The operating model, as a result, never fully materializes below the organizational surface.
How the Seven Elements Shape Work Beyond the Top of the House
The seven elements are only as effective as the depth at which they are applied. Their design at the corporate level is necessary. Their translation into the organizational layers where execution actually happens is what makes them functional.
Differentiating Capabilities must exist in the work itself — in how operational teams coordinate a fulfillment cycle, respond to a customer escalation, or deliver continuity of service. Defining differentiating capabilities at the corporate level without translating them into what they require of front-line performance leaves the capability as aspiration rather than practice.
Processes & Technology must reach the workflows that front-line employees use every day. A process redesign that stops at the department-head level leaves the people who execute the process working the old way.
Roles & Accountabilities are the element most often designed well at the top and most poorly deployed below it. Translating executive role clarity into the third and fourth layers of management — where most operational decisions are made — is where most organizations fall short. Who owns a customer complaint that crosses three departments? Who decides when to escalate a production issue? These questions need answers at the operational level, and the operating model is the mechanism for providing them.
Decisions & Governance face the same constraint. Decision rights defined for the executive team must cascade into the governance norms that operational leaders use daily. A governance framework that only guides the senior leadership team has not solved the organization’s decision-making problem.
Organizational Structure— spans, layers, and formal reporting relationships — are where the connection between executive intent and operational reality is most visible. Alignment across the top leadership levels is the foundation; building the middle-management and front-line structure that supports the new model is where structure becomes execution.
Behavioral Norms & Culture depend entirely on depth. Culture is not what the leadership team articulates. Culture is what behavior is rewarded, tolerated, and modeled at every level. A leadership team that names collaboration as a value without embedding collaborative expectations into the accountability of managers two and three levels below has produced a statement, not a culture.
Workforce Strategy must account for the full workforce. An operating model designed to drive execution cannot ignore the capabilities, composition, and incentives of the people who actually do the work.
What Alignment Looks Like When It Reaches the Whole Organization
When an operating model extends across the full organization — designed at the top and meaningfully translated into every relevant layer — the evidence is behavioral, not structural.
Decisions get made at the right level. Operational managers do not escalate every judgment call upward because they know what they are authorized to decide. Accountability is functional — people know what they own and have the clarity and resources to own it.
Behavioral norms reinforce strategy without constant management intervention. When the design of work, incentives, and leadership behavior is consistent at every layer, teams do not need to be reminded of the model’s intent. They operate within it because it defines the environment they work in.
In Lotis Blue’s work with a national wholesale food distributor — a $15B organization with 15 distribution centers serving more than 30,000 stores — the engagement began with strategic alignment at the executive level, focused on cost discipline and G&A margin improvement. Sustaining those results required embedding the model into the operational structure: decision rights and accountability at the distribution-center level, talent management tools extending beyond the corporate team, and a PMO that tracked execution across the full organization. The immediate result was a 3.5% profit increase in the fiscal year. The following year brought double-digit revenue growth and more than 50% profit improvement. The financial performance followed from an operating model that reached the organization’s operational core, not just its leadership suite.
Operating Model Design Is a Leadership Responsibility, Not a Design Exercise
The operating model does not operate itself. A well-designed set of elements, aligned at the executive level and documented clearly, will not survive contact with an organization that has never been equipped to work within it.
Leaders own the model’s translation into behavior — making decisions in the way the governance framework intends, modeling the behavioral norms the culture element requires, and holding middle managers accountable for translating the design into the work of their teams. The operating model is a living system, not a ratified document. It requires ongoing reinforcement and deliberate calibration to stay aligned across the full depth of the organization.
Strategy is set at the top. Execution lives everywhere else.
