The Operating Model and Workflow Root-Cause Audit: Finding the Constraint Beneath the Programme

If the same programme problem keeps returning, investigate how the work is organised. A growing queue may involve a system fault, unclear approval rights, competing targets, exception work or missing skills. Find the supported cause before funding another intervention.

1. The Market Connection Context

The recognisable leadership condition is familiar: the programme reports activity, but customers, users or frontline teams still encounter the same delay, rework, failure demand or unresolved exception. Each function can explain its own performance, yet nobody can trace an outcome from the market-facing event through the workflow, handoffs, decisions, incentives and enabling systems.

The value path is:

Customer or stakeholder need
→ end-to-end work
→ handoffs and decisions
→ usable service or outcome
→ retained operating evidence
→ leadership action on the governing constraint

A repeated symptom can expose revenue, margin, cost, capacity, retention, risk, investment efficiency or service value, but the amount is REQUIRES VALIDATION until an accepted population, period, unit, baseline and causal boundary exist. The audit therefore separates an observed symptom from a mechanism and a root-cause claim. A root-cause claim is decision-fit only when changing the claimed condition is both within authority and reasonably expected to alter the symptom without transferring unacceptable harm elsewhere.

The important decision is: by [decision date], the COO or named decision owner will VALIDATE, CHANGE, CONTAIN, DEFER, STOP, or HAND OFF each material constraint, with an owner, evidence boundary, safeguard and next gate. This is a diagnosis decision, not approval of a programme, platform, supplier or quantified benefit.

Use the method where symptoms recur across functions; local fixes move rather than remove work; formal process differs from performed work; measures encourage contradictory behaviour; decisions wait between roles; or technology is blamed before workflow and authority are observed. Do not use it as an incident response, an employment investigation, a regulated assurance opinion, or a substitute for qualified safety, legal, privacy, security, financial or labour review.

Scope one market-facing outcome, a defined population and period, the workflow that produces it, material variants and exceptions, decision rights, handoffs, controls, incentives, capability, data and technology dependencies. Exclude transformation classification under The Transformation Scope Decision: Improve, Automate, Modernise or Transform, portfolio economics under The Transformation Portfolio and Investment Case: Funding the Smallest Coherent Set of Changes, roadmap design under The Fundable Transformation Roadmap: Outcomes, Dependencies, Capacity and Decision Gates, full governance redesign under The Transformation Governance and Decision-Rights Standard: Sponsorship, Ownership and Escalation and stalled-programme recovery under The Stalled Transformation Recovery and Value-Realisation Standard: Recover, Stop or Scale. The expected outputs are a charter, evidence register, performed-work map, constraint ledger, tested causal claims, executive disposition and operating review, not a guaranteed saving or implementation promise.

Official GOV.UK guidance says end-to-end mapping should cover online and offline touchpoints, backend processes and the people involved, while user research should distinguish evidence from internal opinion (Map and understand a user's whole problem, VERIFIED; Learning about users and their needs, VERIFIED). Its experience-mapping guidance also recommends representing several users and cross-team dependencies rather than treating one account as the whole service (Creating an experience map, VERIFIED). The ILO describes work organisation and job design as part of how skills become productive work (Better Use of Skills in the Workplace, VERIFIED). These sources support observation and governance principles; the diagnostic sequence below is an Abrasim working method, PROPOSED, and must be validated in the organisation.

2. The Leadership vs. Delegation Boundary

The reader recognises that root-cause work requires cross-functional observation, workflow evidence and authority to challenge how the organisation is structured and measured.

A capable internal team can lead when it can observe work across organisational boundaries, protect participants, challenge sponsor assumptions, obtain source records and place findings before a decision owner. An independent senior partner is proportionate when budgets, suppliers or executive incentives are implicated; functions dispute the performed workflow; or the internal team cannot challenge the programme premise. A workflow specialist may be sufficient for one bounded, accepted process; a qualified control specialist is required for conclusions inside a regulated mandate.

Stop or pause for unsafe observation, unauthorised personal or confidential data, retaliation risk, an unmanaged conflict of interest, missing operating ownership or a sponsor who requires a predetermined cause. Escalate market consequences to the economic buyer, workflow authority to the COO, technology facts to the CIO, people implications to the CHRO and regulated conclusions to qualified authorities. Evaluate a provider by asking how it will distinguish symptoms from mechanisms, preserve dissent, test alternative explanations, prevent surveillance, recommend no-build or stop, and transfer the evidence model to operating owners.

3. The Step-by-Step Execution Standard

Step 01: Charter one recurring symptom and decision

Purpose and decision served Bound the audit around one consequential symptom and the decision it must inform.

Accountable owner COO or named operating executive.

Delegated lead and contributors Audit lead with customer, operations, finance, data, technology, risk and people representatives.

Preconditions, inputs and access Named outcome, affected population, decision date, known incidents, programme papers and authority to challenge the stated cause.

Actions

1. Write the symptom as an observable condition, not a diagnosis.
2. Define population, period, value-path boundary, exclusions and decision dispositions.
3. Record safeguards, dependencies, conflicts and stop routes.

Evidence to retain Signed charter, symptom statement, scope map and assumption log.

Decision or scoring rule Proceed only when one owner accepts a falsifiable symptom and a usable decision.

Output and template Audit charter and authority register.

Acceptance gate PROCEED if outcome, boundary, authority and decision date are explicit; otherwise CHANGE or STOP.

Leadership checkpoint Sponsor confirms that no preferred cause or solution is protected.

Human control point The decision owner approves scope and participant protections.

Failure modes and safeguards Solution-shaped framing is countered by neutral wording and documented alternatives.

Change, stop or escalation condition Stop if evidence access or participant safety cannot be authorised.

Handoff to the next step The charter sets the authority map and evidence boundary.

Step 02: Establish authority, participation and evidence controls

Purpose and decision served Make access, decision rights and protected participation explicit before observation.

Accountable owner Transformation Sponsor.

Delegated lead and contributors Audit lead, data owner, CHRO, privacy, security, legal and employee representatives where applicable.

Preconditions, inputs and access Accepted charter, source inventory and organisational policies.

Actions

1. Map who owns decisions, work, systems, records and controls.
2. Define collection minimisation, retention, access and challenge routes.
3. Disclose sponsor, supplier and analyst conflicts.

Evidence to retain Authority register, participation protocol, access approvals and conflict record.

Decision or scoring rule No evidence is collected without a lawful owner, purpose and permitted use.

Output and template Completed authority rows in the audit charter register.

Acceptance gate AUTHORISED or PAUSE; silence is not consent.

Leadership checkpoint Sponsor resolves missing cross-functional authority.

Human control point Qualified owners approve sensitive collection and participation safeguards.

Failure modes and safeguards Covert monitoring and retaliation are prevented through disclosure, minimisation and protected escalation.

Change, stop or escalation condition Escalate any request to bypass an authority or control.

Handoff to the next step Approved access defines the observation and sampling plan.

Step 03: Design a evidence relevant to the decision plan

Purpose and decision served Collect enough varied evidence to test causes without turning the audit into open-ended discovery.

Accountable owner COO.

Delegated lead and contributors Audit lead, analyst, research lead and source owners.

Preconditions, inputs and access Authority register, known variants, operating calendar and source catalogue.

Actions

1. Define cases across normal work, exceptions, channels, teams and periods.
2. Pair records with observation and affected-person accounts.
3. State evidence thresholds, gaps, independence and expiry.

Evidence to retain Sampling rationale, source plan, definitions and limitations.

Decision or scoring rule A plan is fit when it can reveal variation and contradict the sponsor hypothesis.

Output and template Performed-work evidence register.

Acceptance gate COLLECT only after coverage and safeguards are accepted.

Leadership checkpoint Decision owner accepts what the evidence can and cannot establish.

Human control point Source and research owners approve the plan.

Failure modes and safeguards Convenience samples are labelled and expanded where material.

Change, stop or escalation condition Change the plan when a material population or exception is absent.

Handoff to the next step The sampling plan controls end-to-end observation.

Step 04: Observe the performed workflow end to end

Purpose and decision served Establish how value actually moves rather than relying on the approved procedure.

Accountable owner Process Owner.

Delegated lead and contributors Audit lead, frontline participants, customer research and system/data observers.

Preconditions, inputs and access Approved plan, cases, observation protocol and secure evidence location.

Actions

1. Trace selected cases from trigger to customer or stakeholder outcome.
2. Record work, wait, rework, queues, exceptions, systems, controls and informal workarounds.
3. Separate timestamped fact from participant explanation and analyst interpretation.

Evidence to retain Case traces, event records, observations, redacted artefacts and provenance.

Decision or scoring rule No map element is treated as fact without a traceable observation or source.

Output and template Evidence rows and a performed-work map.

Acceptance gate COMPLETE when normal and material exception paths reach an outcome or explicit dead end.

Leadership checkpoint Operating owner reviews differences between prescribed and performed work.

Human control point Participants can correct factual representation without suppressing dissent.

Failure modes and safeguards Workshop memory is not substituted for observation; personal data is minimised.

Change, stop or escalation condition Pause if observation changes unsafe behaviour or exposes uncontrolled risk.

Handoff to the next step The performed map supports handoff and decision analysis.

Step 05: Examine handoffs, queues and exception demand

Purpose and decision served Locate where responsibility, information or work stops flowing.

Accountable owner COO.

Delegated lead and contributors Process owners, frontline representatives, analyst and customer/service lead.

Preconditions, inputs and access Performed-work map and case evidence.

Actions

1. Record sender, receiver, entry condition, acceptance rule and rejection path for each handoff.
2. Distinguish productive work from wait, rework, correction and avoidable contact.
3. Test whether local targets transfer burden downstream or to customers.

Evidence to retain Handoff ledger, queue definitions, exception cases and burden transfer notes.

Decision or scoring rule A handoff is suspect when required information, authority or acceptance is repeatedly unavailable.

Output and template Completed workflow and handoff rows in the evidence register.

Acceptance gate ADVANCE when material breaks have evidence and owners; otherwise VALIDATE.

Leadership checkpoint Cross-functional owners accept or dispute each break on record.

Human control point An affected-person representative tests whether burden has been hidden.

Failure modes and safeguards Average flow does not erase severe variants; one loud case does not define prevalence.

Change, stop or escalation condition Escalate material customer, safety or control harm immediately for containment.

Handoff to the next step Observed breaks are tested against decision rights and incentives.

Step 06: Test decision rights, ownership and escalation

Purpose and decision served Determine whether work waits because authority is absent, duplicated, ambiguous or unused.

Accountable owner Transformation Sponsor.

Delegated lead and contributors Audit lead, governance owner, process owners and control authorities.

Preconditions, inputs and access Decision records, policies, meeting logs and handoff evidence.

Actions

1. Identify material decisions, recommenders, approvers, vetoes and escalation routes.
2. Compare formal authority with observed authority and elapsed waiting states.
3. Test whether evidence thresholds and consequences for inaction are explicit.

Evidence to retain Decision-right map, sampled decisions, exceptions and unresolved conflicts.

Decision or scoring rule Classify a decision constraint only when the authority defect plausibly governs the observed break.

Output and template Constraint and causal-test ledger.

Acceptance gate Each material decision point is CLEAR, CONTESTED, MISSING or UNUSED with evidence.

Leadership checkpoint Sponsor addresses authority conflicts that the team cannot resolve.

Human control point Named authority owners confirm formal boundaries; observers retain contrary evidence.

Failure modes and safeguards An organisation chart is not treated as proof of performed authority.

Change, stop or escalation condition Escalate unlawful delegation or unmanaged control override.

Handoff to the next step Authority findings join incentive and capability tests.

Step 07: Test incentives, measures and resource conditions

Purpose and decision served Find whether rational local behaviour preserves the end-to-end failure.

Accountable owner COO with CFO and CHRO.

Delegated lead and contributors Audit lead, finance, people, performance and operating owners.

Preconditions, inputs and access Team measures, goals, workload, capacity rules and reward/control descriptions.

Actions

1. Trace each material measure to behaviours and downstream consequences.
2. Compare workload and capability with assigned responsibility.
3. Record conflicting targets, unfunded controls and exception burdens.

Evidence to retain Measure definitions, workload evidence, role expectations and corroborated accounts.

Decision or scoring rule Do not call an incentive causal because it is unpopular; require a mechanism and observable pattern.

Output and template Constraint ledger rows for incentive, capability and resource claims.

Acceptance gate Every public claim is classified VERIFIED, INFERRED, PROPOSED or REQUIRES VALIDATION. Evidence relationships and test results such as supported or contradicted remain separate fields and must not replace the public-claim taxonomy.

Leadership checkpoint COO, CFO and CHRO review cross-functional burden and control implications.

Human control point People and finance owners approve interpretation inside their mandates.

Failure modes and safeguards The audit examines system conditions and avoids attributing structural failure to individual character.

Change, stop or escalation condition Stop any use of findings for unapproved individual performance action.

Handoff to the next step Operating conditions are reconciled with data and technology dependencies.

Step 08: Test capability, data and technology dependencies

Purpose and decision served Determine whether enabling conditions constrain work or merely coincide with the symptom.

Accountable owner CIO with Process Owner.

Delegated lead and contributors Architecture, data, service management, operations and capability leads.

Preconditions, inputs and access Performed-work evidence, incident records, data definitions, access model and support evidence.

Actions

1. Trace system, information, access and skill dependencies at each material break.
2. Test alternative non-technology explanations and workaround effects.
3. Separate containment needs from structural change claims.

Evidence to retain Dependency map, source records, incident links, data limitations and competing explanations.

Decision or scoring rule Technology is causal only where the dependency mechanism and counterevidence are explicit.

Output and template Updated constraint and causal-test ledger.

Acceptance gate DIAGNOSE only when each material dependency has proof status and limitation.

Leadership checkpoint CIO and COO agree what is fact, inference and unresolved question.

Human control point Technical owners confirm system facts; business owners retain outcome authority.

Failure modes and safeguards Vendor narratives and incident correlation are not accepted as causal proof.

Change, stop or escalation condition Escalate a material security, resilience or data-control exposure to qualified owners.

Handoff to the next step All candidate constraints move into causal reconciliation.

Step 09: Reconcile causal claims and competing explanations

Purpose and decision served Select the smallest set of constraints that best explains the observed pattern without overstating certainty.

Accountable owner COO.

Delegated lead and contributors Audit lead, analyst, independent challenger and source owners.

Preconditions, inputs and access Constraint ledger, performed-work map, contradictions and evidence gaps.

Actions

1. Write each causal claim as condition, mechanism, consequence and boundary.
2. Seek disconfirming cases and alternative explanations.
3. Classify evidence, uncertainty, transfer risk and validation action.

Evidence to retain Causal-test results, dissent, rejected explanations and open gaps.

Decision or scoring rule A governing constraint must explain material variation and be changeable without merely relocating harm.

Output and template Reconciled causal ledger.

Acceptance gate Claims are VERIFIED, INFERRED, PROPOSED or REQUIRES VALIDATION; none become fact by consensus.

Leadership checkpoint Decision owner reviews uncertainty and dissent before options are formed.

Human control point Independent challenger can require validation or preserve disagreement.

Failure modes and safeguards Five-whys simplicity, confirmation bias and single-cause storytelling are countered by competing hypotheses.

Change, stop or escalation condition Return to evidence collection when a decision-critical claim lacks an observable test.

Handoff to the next step Accepted claims define bounded response options.

Step 10: Compare containment, change, validation and stop options

Purpose and decision served Prevent diagnosis from becoming an automatic programme recommendation.

Accountable owner COO.

Delegated lead and contributors Audit lead, operating owners, finance, risk, technology and affected-person representatives.

Preconditions, inputs and access Reconciled constraints, guardrails, dependencies and resource boundary.

Actions

1. Develop contain, validate, change, defer, stop and handoff alternatives.
2. Test each against mechanism, customer consequence, transfer risk, reversibility and operating ownership.
3. State evidence and authority required for the next gate.

Evidence to retain Option comparison, rejected routes, safeguards and dissent.

Decision or scoring rule Prefer the smallest coherent action that addresses the governing mechanism within guardrails.

Output and template Option rows in the causal-test ledger.

Acceptance gate At least one non-build and one stop or defer route receive genuine consideration.

Leadership checkpoint Sponsor confirms options are not constrained to the current programme.

Human control point Qualified authorities review specialist risks; the executive retains the business decision.

Failure modes and safeguards Sunk-cost protection is disclosed and supplier-authored assumptions are labelled.

Change, stop or escalation condition Stop option design when the diagnosis is insufficient for a material commitment.

Handoff to the next step Decision-ready options go to executive disposition.

Step 11: Make and record the executive disposition

Purpose and decision served Turn diagnosis into an authorised, bounded next action.

Accountable owner COO or named economic buyer.

Delegated lead and contributors Audit lead presents; accountable owners, CFO, CIO, CHRO and control authorities advise.

Preconditions, inputs and access Decision paper, evidence index, options, dissent and authority confirmation.

Actions

1. Review the causal chain, limitations, alternatives and transfer risks.
2. Assign VALIDATE, CHANGE, CONTAIN, DEFER, STOP, or HAND OFF.
3. Name owner, resource boundary, acceptance gate, review trigger and expiry.

Evidence to retain Decision record, rationale, conditions, dissent and approvals.

Decision or scoring rule No disposition proceeds without an owner, evidence boundary and stop condition.

Output and template Executive constraint decision and review register.

Acceptance gate ACCEPTED, RETURNED FOR VALIDATION, or STOPPED by the named authority.

Leadership checkpoint Economic buyer accepts consequences and resource commitment separately.

Human control point Only the authorised executive records the final business disposition.

Failure modes and safeguards Conditional findings are not rewritten as certainty in the decision paper.

Change, stop or escalation condition Return when authority, evidence or operating ownership is missing.

Handoff to the next step Accepted conditions move to operating handover and measurement.

Step 12: Transfer ownership and establish review controls

Purpose and decision served Keep the diagnosis testable after the audit team exits.

Accountable owner Process Owner.

Delegated lead and contributors Audit lead, measure owners, data owners and change or containment leads.

Preconditions, inputs and access Authorised disposition, accepted artefacts and resourced owners.

Actions

1. Transfer definitions, evidence, controls, measures and open validation actions.
2. Confirm baseline plans, review cadence and evidence expiry.
3. Schedule human decisions to continue, change, re-diagnose, hand off or stop.

Evidence to retain Handover acceptance, measure contracts, review record and change log.

Decision or scoring rule Handover completes only when operating owners can reproduce the causal claim and evidence trail.

Output and template Completed executive decision and review register.

Acceptance gate OPERATING OWNERSHIP ACCEPTED or RETURN.

Leadership checkpoint COO confirms ownership and the next decision gate.

Human control point Operating owner signs acceptance and may reject an unsafe or unfunded handover.

Failure modes and safeguards A slide handoff is insufficient; source access, definitions and decision rights must transfer.

Change, stop or escalation condition Re-charter if the symptom, population, mechanism or authority materially changes.

Handoff to the next step The operating owner runs the review cycle; recovery questions route to The Stalled Transformation Recovery and Value-Realisation Standard: Recover, Stop or Scale only if a programme is demonstrably stalled.

4. The Evidence & Measurement Checklist

Preflight and authority

• The symptom is observable and does not embed a preferred cause. Evidence: accepted audit charter. Owner: COO.
• The market-facing outcome and affected population are explicit. Evidence: value-path boundary. Owner: Customer Director.
• The decision date and allowed dispositions are recorded. Evidence: decision row. Owner: Transformation Sponsor.
• Cross-functional evidence and challenge authority are approved. Evidence: authority register. Owner: COO.
• Conflicts and protected interests are disclosed. Evidence: conflict record. Owner: Transformation Sponsor.

Evidence access and quality

• Every source has a lawful owner, purpose and permitted use. Evidence: access approval. Owner: Data Owner.
• Normal work and material exceptions are represented. Evidence: sampling plan. Owner: Audit Lead.
• Observed facts are separated from accounts and interpretations. Evidence: evidence register. Owner: Audit Lead.
• Population, period, unit and limitations accompany quantitative evidence. Evidence: source metadata. Owner: Analytics Lead.
• Contradictions and missing evidence remain visible. Evidence: gap and dissent log. Owner: Independent Challenger.

Method execution

• The performed workflow reaches an outcome or explicit dead end. Evidence: performed-work map. Owner: Process Owner.
• Material handoffs show sender, receiver and acceptance rule. Evidence: handoff ledger. Owner: Operations Director.
• Decision points show formal and observed authority. Evidence: decision-right map. Owner: Transformation Sponsor.
• Incentive, capability, data and technology claims have mechanisms. Evidence: constraint ledger. Owner: Audit Lead.
• Competing explanations received disconfirming tests. Evidence: causal-test record. Owner: Independent Challenger.

Governance, privacy, security and risk

• Participant protections and challenge routes are active. Evidence: participation protocol. Owner: CHRO.
• Personal and confidential data are minimised. Evidence: collection specification. Owner: Privacy Authority.
• Security and resilience exposures route to qualified owners. Evidence: escalation record. Owner: CIO.
• Findings are not repurposed for unauthorised individual action. Evidence: use restriction. Owner: CHRO.
• Material customer, safety or control harm has a containment owner. Evidence: containment decision. Owner: Risk Executive.

Deliverables and acceptance

• The charter, map, evidence register and causal ledger reconcile. Evidence: artefact cross-reference. Owner: Audit Lead.
• Every root-cause claim states condition, mechanism and boundary. Evidence: causal claim row. Owner: Audit Lead.
• Every material constraint has a proof status and limitation. Evidence: constraint ledger. Owner: Independent Challenger.
• At least one non-build route is decision-ready. Evidence: option comparison. Owner: COO.
• Rejected options retain rationale and evidence. Evidence: option disposition log. Owner: Transformation Sponsor.

Measurement

• Each measure has a stable definition and denominator. Evidence: measurement contract. Owner: Analytics Lead.
• Baseline gaps have owners and collection plans. Evidence: baseline plan. Owner: Measure Owner.
• Leading and outcome measures remain separate. Evidence: measure register. Owner: COO.
• Transfer-of-harm guardrails accompany improvement measures. Evidence: guardrail row. Owner: Risk Executive.
• Attribution limitations and time lags are explicit. Evidence: attribution note. Owner: CFO.

Decision and handover

• The executive disposition names one authorised owner. Evidence: decision record. Owner: COO.
• Resource commitment is recorded separately from diagnosis. Evidence: resource decision. Owner: CFO.
• Dissent and conditional evidence reach the decision forum. Evidence: decision pack. Owner: Transformation Sponsor.
• Operating owners accept source access and definitions. Evidence: handover acceptance. Owner: Process Owner.
• The next evidence or implementation gate is named. Evidence: handoff row. Owner: COO.

Review, change and stop controls

• Evidence expiry and review triggers are recorded. Evidence: review register. Owner: Audit Lead.
• New contradictory evidence can reopen the diagnosis. Evidence: change-control rule. Owner: Process Owner.
• A materially changed symptom requires a new charter. Evidence: re-charter decision. Owner: COO.
• Unowned, unsafe or unfunded action is stopped. Evidence: stop record. Owner: Transformation Sponsor.
• Recovery work routes to The Stalled Transformation Recovery and Value-Realisation Standard: Recover, Stop or Scale only after a stalled programme is evidenced. Evidence: boundary decision. Owner: COO.

Topic-specific measurement contracts

Measure A: Causal evidence coverage

Measure B: Material handoff acceptance

Measure C: Decision waiting burden

Measure D: Recurrence of the chartered symptom

Measure E: Unintended burden transfer

Evidence classifications used in this guide

• VERIFIED: a source or observation supports the stated fact within its recorded boundary.
• INFERRED: a reasoned interpretation remains distinguishable from the supporting facts.
• PROPOSED: an Abrasim method, option or future operating condition awaiting organisational acceptance.
• REQUIRES VALIDATION: a material claim, baseline or causal link is not yet decision-fit.

Source notes

1. Map and understand a user's whole problem: UK official guidance used for end-to-end service and backend observation; it does not prove a local cause; recheck at publication.
2. Learning about users and their needs: official guidance used to distinguish user evidence from internal opinion; it does not replace local research; recheck at publication.
3. Creating an experience map: official guidance used for multiple users and dependencies; it does not establish local prevalence; recheck at publication.
4. Better Use of Skills in the Workplace: ILO publication used for bounded work-organisation principles; it is not local employment advice; recheck edition at publication.