Proprietary Framework

The Operating Model Scale

Nine dimensions. Five stages of maturity. A structured way to see where your operating model sits today and what the next move looks like, built for SMEs scaling into the AI-native era.

The framework Run your assessment

Before You Begin

How to read this framework

The Operating Model Scale looks at your business through three lenses. Each one asks a different question about how the model holds up.

Architecture

How it's shaped

Strategy-to-structure fit. Decision rights. Capability model. The deliberate design choices that make the operating model hold together.

Flow

How value moves

Value streams. Ways of working. Technology and AI as the layer underneath. How work gets from intent to delivered outcome.

Adaptation

How it senses and reshapes

Performance signals. Ecosystem relationships. Change capacity. The ability to read the market and reconfigure before it hurts.

Cumulative capability. Each stage builds on the one before. A Calibrated operating model builds on Articulated and Architected foundations.

No grand finale. Most scaling businesses sit between Inherited and Architected. Composable is a direction of travel. The goal is the stage that fits where you are today.

Uneven progression is normal. You might be Calibrated on value streams and still Inherited on decision rights. Knowing the shape of your heat map matters more than knowing your highest score.

Built for the AI-native era. Composable operating models go beyond automation. They coordinate agents and humans across the whole model. This framework maps the path from today to that.

We use this framework to assess your current state, show you where the gaps matter most, and sequence the moves that get your operating model ready to perform and ready to evolve.

Tactical.ly

The Operating Model Scale

Operating Model Maturity Framework

The full Operating Model Scale: 9 dimensions, 5 stages of maturity. Read across a row to see how each dimension progresses from Inherited to Composable. Filter by lens to focus on Architecture, Flow, or Adaptation.

Inherited

Default

Articulated

Documented

Architected

Coherent

Calibrated

Performant

Composable

Adaptive

Strategy & Structure

Structure is a fossil of past decisions

Org chart reflects how the business grew. Reporting lines were drawn around individual hires. Structure lives in habit.

Owner: Founder / CEO

Strategy and structure both written down

The strategic plan exists in a deck. The org chart exists somewhere else. Both are documented, but the link is implicit.

Owner: CEO

Structure is designed to deliver the strategy

The operating model is mapped against strategy. Where they don't match, the structure has been redrawn deliberately.

Owner: CEO / COO

Strategy-structure fit is measured and adjusted

Performance gaps are diagnosed against the operating model, not just the P&L. Structure is reviewed when strategy shifts.

Owner: CEO / COO

Structure reshapes as strategy evolves

Strategic shifts translate into structural adjustments without major restructures. The model is built to be reshaped.

Owner: CEO / Board

Decision Rights

Decisions cluster around the founder

Most material decisions go to the same one or two people. Speed depends on their availability. Accountability is personal.

Owner: Founder

Decision rights have been named

A RACI or equivalent exists. Committees have terms of reference. In practice, escalation is still common.

Owner: COO / CEO

Governance is designed for speed and accountability

Decision rights match the work. Forums exist where needed, don't where they aren't. Escalation is the exception.

Owner: COO

Decision quality and speed are tracked

Decisions are reviewed against outcomes. Time to decide is measured on the ones that matter. Drag gets redesigned out.

Owner: COO / CEO

Governance flexes with context

Routine decisions devolve. High-stakes decisions converge. Governance reconfigures with the work, not against it.

Owner: CEO / Board

Capability & Talent

Roles are shaped around the people you have

When someone leaves, no one is sure exactly what they did. Capability lives in individuals, not the organisation.

Owner: Founder / People lead

Capability and roles are documented

A capability map exists. Job descriptions are current. Where critical capabilities sit is visible.

Owner: People lead / COO

Talent model is built around future capability needs

Capability mix is matched to the strategy. Build, buy, and borrow decisions are made deliberately.

Owner: COO / CHRO

Capability gaps are measured and resourced dynamically

Critical capabilities are tracked. Gaps trigger response. Workforce planning runs on a regular cadence.

Owner: COO / CHRO

Talent flows to where capability is needed

People move to work, not the other way around. Internal mobility is normal. Capability expands without permanent hires.

Owner: CHRO / CEO

Value Streams

Work moves through silos

Different functions own different stages. Handoffs are where things slow down. Customers experience the seams.

Owner: COO / Function leads

Value streams are mapped end to end

The journey from customer intent to delivered value has been documented. Bottlenecks have been named.

Owner: COO

Teams are organised around value streams

Cross-functional teams own outcomes end to end. Functional silos exist for capability, but value flows across them.

Owner: COO / Heads of function

Flow metrics drive continuous improvement

Lead time, cycle time, and flow efficiency are measured. Bottlenecks are identified before they cause damage.

Owner: COO / Stream leads

Streams reconfigure around customer intent

New customer needs trigger new stream configurations. Teams form, deliver, and reform. Flow follows the work.

Owner: COO / CPO

Ways of Working

Cadence depends on team and personality

Some teams meet weekly. Others don't. Rituals reflect history and preference. Information moves unevenly.

Owner: Team leads

Operating rhythm is documented

A defined cadence of meetings exists across the leadership team. People know where to bring things.

Owner: COO

Rituals are designed around what the model needs

Each meeting has a stated purpose, a clear output, and the right participants. Rituals serve the model.

Owner: COO

Meetings and rituals are reviewed for impact

Meetings are evaluated on outcomes, not attendance. Low-value rituals are removed. New ones are introduced as needed.

Owner: COO / Leadership team

Operating rhythm self-adjusts to demand

Cadence flexes with workload and priority. Standing meetings shift, pause, or scale. Rhythm serves the work in real time.

Owner: COO / Leadership team

Tech & AI Layer

Tools accumulated organically

Each function bought what it needed when it needed it. Tools don't talk to each other. AI is used by individuals if at all.

Owner: Office manager / Founder

Tech stack is mapped to processes

A current-state architecture exists. AI use cases have been identified and prioritised.

Owner: CTO / COO

Systems are integrated around value streams

Tooling supports flow rather than functions. Data moves across the stack without manual handoffs. AI is embedded, not bolted on.

Owner: CTO / COO

Workflows instrumented, AI in defined loops

Process performance is visible in real time. AI agents handle defined tasks with humans on the loop.

Owner: CTO / COO

Agents and humans coordinate across the operating layer

Workflows reconfigure based on intent. Humans set the loop, the system runs the rest.

Owner: CTO / CEO

Performance Signals

Lagging metrics only, mostly financial

Revenue and cash are watched. Other indicators show up after the fact, if at all. By the time it's measured, it's happened.

Owner: CEO / Founder

KPIs are defined for key areas

Each function has a small number of metrics that matter. Reporting cadence is established. Performance is describable.

Owner: COO

Leading and lagging signals across the model

Performance is measured across the operating model, not just the P&L. Leading indicators give early warning. Each measure is owned.

Owner: COO

Real-time signals trigger response

Operational dashboards are live. Anomalies are surfaced as they happen. Measurement is an input to running the model, not just reviewing it.

Owner: COO / CEO

Performance system surfaces what to change

Signals point toward operating model changes, not just operational fixes. The measurement layer is an engine of adaptation.

Owner: COO / Board

Ecosystem

Suppliers and partners arrived through relationships

The ecosystem is the result of who you knew. Contracts renew without review. Dependencies exist that nobody has mapped.

Owner: Founder / Procurement

Partnership and supplier strategy is documented

Suppliers and partners are mapped. The ones that matter are named. A view exists of where the ecosystem helps and constrains.

Owner: COO / CFO

Ecosystem is chosen to amplify capability

Build, buy, and partner decisions are made against the operating model. Partners extend capability you don't want to own.

Owner: CEO / COO

Partner performance and value contribution are measured

Partners are reviewed against contribution, not just contract terms. Underperforming relationships are renegotiated or replaced.

Owner: COO / CFO

Network expands and contracts with strategic need

The ecosystem is part of the operating model. Capacity flexes through partners as well as hiring. The model extends past the org chart.

Owner: CEO / Board

Change Capacity

Change is disruptive and resisted

Each change initiative consumes the organisation. People know the words and have learned to wait them out. Capacity is finite and burnt fast.

Owner: Founder / CEO

Change methodology is documented

A defined approach to change exists. Roles are named. Change still feels like an event rather than a way of working.

Owner: COO / Change lead

Change capability is built into the operating model

Standing teams know how to absorb new work. Communication, training, and feedback loops are designed in.

Owner: COO

Change capacity is tracked and protected

How much change the organisation can absorb is known and managed. Initiatives are sequenced against capacity. Burnout is a leading indicator.

Owner: COO / CHRO

Continuous reshape with minimal disruption

The organisation changes constantly without seizing up. Reorganisations are smaller and more frequent. Change is the operating mode.

Owner: CEO / Board

The Operating Model Scale

How to read this framework

See where your operating model sits today

Here's where you sit

Three moves for the most impact