Operating Model Diagnostic

Scope note
This is a general Ninth Atlas decision guide. It is not client-specific advice, statutory audit, regulated assurance or a substitute for appropriately qualified legal, tax, accounting, investment or technical professionals.

Direct answer

The Operating Model Diagnostic is a practical working document for converting an organisational issue into visible evidence, choices, ownership and follow-through. Its usefulness depends on disciplined completion and review.

Why this matters

For CEOs, COOs, CHROs, transformation teams, functional leaders and business heads, leadership and organisation matter when they improve decisions, coordination, capability and execution. Operating Model Diagnostic helps the organisation align structures, roles, processes, information and management routines so work moves effectively across organisational boundaries.

Strong organisational work connects business strategy with roles, decisions, behaviour, systems and leadership signals. It should make the organisation easier to understand and operate without pretending that human systems behave like machinery.

When to use it

Use this topic when decisions stall, roles overlap, leadership teams send mixed signals, capability gaps block strategy, growth creates coordination problems, succession risk is high or transformation is not being adopted. The depth of work should match the sensitivity, consequence and reversibility of the organisational decision.

Questions the work should answer

What organisational outcome does operating model diagnostic need to improve?
Which role, decision, behaviour or system is shaping the current pattern?
What evidence shows the problem is structural rather than anecdotal?
Which incentives, routines or leadership signals reinforce the behaviour?
What capability or transition risk could block improvement?
Who owns the change, the outcome and the review trigger?

Suggested fields in the tool

Organisational outcome: capture enough detail to make the diagnosis and follow-through traceable.
Observed pattern: capture enough detail to make the diagnosis and follow-through traceable.
Evidence and source: capture enough detail to make the diagnosis and follow-through traceable.
Role or decision affected: capture enough detail to make the diagnosis and follow-through traceable.
Reinforcing system: capture enough detail to make the diagnosis and follow-through traceable.
Intervention option: capture enough detail to make the diagnosis and follow-through traceable.
Transition risk: capture enough detail to make the diagnosis and follow-through traceable.
Action owner: capture enough detail to make the diagnosis and follow-through traceable.
Review date: capture enough detail to make the diagnosis and follow-through traceable.
Outcome evidence: capture enough detail to make the diagnosis and follow-through traceable.

How it works

1. Define the organisational outcome

State the business, people or execution outcome that operating model diagnostic must improve.

2. Map the current system

Connect the issue to relevant elements of cross-functional work, handoffs, role interfaces. Document roles, decisions, interfaces, routines and signals.

3. Gather multiple perspectives

Use leadership, employee, process and outcome evidence. Separate recurring patterns from isolated incidents.

4. Identify reinforcing conditions

Test whether structure, incentives, capability, information, leadership behaviour or governance sustains the problem.

5. Design proportionate interventions

Compare role redesign, decision changes, leadership action, capability building, routine changes and structural options.

6. Assign ownership and review

Produce a operating model diagnostic, cross-functional interface map, role and process design, with owners, timing, transition risks and review triggers.

Evidence required

Attributable evidence relevant to operating model diagnostic, including source, period and organisational context.
Evidence covering cross-functional work, handoffs.
Evidence on role interfaces, management routines.
Observed decision and operating behaviour, not only policy or stated intent.
Multiple perspectives where hierarchy or functional position may shape interpretation.
Business and execution outcomes linked to the organisational pattern.
Transition, confidentiality, fairness and legal considerations.

Illustrative example

A leadership team can use the Operating Model Diagnostic during an organisation review. Each issue is linked to evidence, consequence, owner, intervention and review date. The completed tool becomes a decision record rather than an offsite artefact.

What a decision-ready output looks like

A useful output should state the organisational issue, evidence, reinforcing conditions, chosen intervention, owner, transition risk and review trigger. Typical outputs for this cluster include a operating model diagnostic, cross-functional interface map, role and process design, management cadence, operating model roadmap.

It should distinguish individual performance questions from system-design questions, and immediate transition actions from longer-term capability building. This prevents structural problems from being personalised and personnel issues from being disguised as organisation design.

Common mistakes

Treating operating model diagnostic as a communication exercise rather than an organisational choice.
Diagnosing individuals when the system repeatedly creates the same behaviour.
Redesigning structure without changing decisions, incentives or routines.
Using employee sentiment as the only evidence.
Creating new roles without removing old work or ambiguity.
Assuming seniority automatically creates accountability.
Announcing change before transition risks and ownership are clear.
Failing to define what behavioural or business evidence would show improvement.

Limitations and professional boundaries

Operating-model design should be reviewed alongside employment, legal, regulatory, technology and governance requirements.

Organisational evidence can be shaped by hierarchy, fear, recent events, selection bias and unclear confidentiality. Where decisions involve employment rights, collective consultation, discrimination, health, privacy, fiduciary duty or regulated governance, qualified specialists should review those elements.

Practical checklist

Is the organisational outcome explicit?
Are recurring patterns separated from anecdotes?
Are roles, decisions and interfaces visible?
Have leadership behaviour and system signals both been examined?
Are multiple stakeholder perspectives represented?
Is the intervention proportionate to the cause?
Are transition risks and confidentiality considered?
Are owner, timing and review evidence defined?
Are legal and professional boundaries clear?

Frequently asked questions

Can organisation design guarantee better performance?

No. It can improve clarity, alignment and execution conditions, but outcomes still depend on leadership behaviour, capability, market conditions and implementation.

Does every organisational issue require restructuring?

No. Many issues can be improved through clearer roles, decision rights, routines, incentives or management capability.

How should sensitive evidence be handled?

Use proportionate confidentiality, anonymisation and access controls. Distinguish diagnostic evidence from personnel judgement.

When the decision is live

Use this guide to frame the issue, identify the evidence required and decide whether the question can be resolved internally or needs independent challenge. Ninth Atlas engagements are scoped around the decision at stake rather than a fixed consulting menu.