An operating model is the connective tissue of an organization. It describes who does what, who decides, how work moves between teams, and how performance is reviewed. When it is clear, people stop negotiating the basics and start doing the work. When it is unclear, every task carries a hidden tax of coordination.
Why operating models drift
Operating models are rarely designed once and then left alone. They drift. A reorganization adds a layer. An acquisition introduces a parallel process. A new system changes a workflow without anyone updating the design. Over a few years, the organization accumulates contradictions that no single leader intended. Our work is to name those contradictions and resolve them deliberately.
Design principles we hold to
We design toward a small set of principles rather than a fixed template.
- Clarity over cleverness. A model people can explain from memory beats an elegant one they need a chart to follow.
- Fewer handoffs where possible, clean handoffs where necessary. Some handoffs are essential; each one should have a defined owner and a clear completion condition.
- Decision rights at the point of competence. Push decisions to the level with the context and capability to make them.
- Manager as the unit of change. If the design does not work for frontline managers, it does not work.
The design process
We start from the diagnosis and translate it into design choices. First we define the work: what the organization must be able to do reliably. Then we assign accountability for each stream of work. Then we map decisions and set escalation paths, so that disagreement has a resolution mechanism rather than becoming a bottleneck. Finally we describe the management routines that keep the model alive: how priorities are set, how performance is reviewed, and how the model itself is updated.
Deliverables
Design work produces artifacts that are meant to be used, not admired. A one-page model overview. Role clarity statements for key positions. A decision-rights map for the processes that matter most. A handoff inventory with owners and completion conditions. And a short guide for managers describing how the model shows up in their week.
Making design stick
Design that is not embedded fades within two quarters. We build embedding into the plan from the start: pilot teams that test the design, feedback loops that surface problems early, and a review cadence that keeps the model current. Our People stage, particularly manager enablement, is often where the design becomes daily practice.
Working with existing structures
We are pragmatic. Most clients cannot rewrite their organization from scratch, and they should not try. We design within the constraints you actually have: existing reporting lines, contractual obligations, union agreements, regulatory requirements, and the culture that already works. The goal is a model that fits your organization rather than one that fits a textbook.
Signs it is time to revisit the model
Recurring symptoms suggest the model needs attention: decisions that stall without a clear owner, teams that duplicate each other's work, new joiners who take months to learn how things really run, and managers who spend more time coordinating than leading. If several of these sound familiar, a design effort is likely worthwhile.
Reach out through our assessment request or ask us a direct question.