The Transformation Assessment: An Executive Standard for Finding Why Strategy Is Not Becoming Operating Change

Projects and technology milestones may be progressing while customers and employees still face the same problems. Trace the funded decisions into daily work to find what has changed, what has not and which constraint is preventing better performance.

Use the Transformation Assessment to follow one strategic outcome from funding into everyday work. Examine the customer journey, workflow, data, technology, skills and decision rights needed to deliver it. Find where the agreed direction fails to produce a change in practice. Use the evidence to stabilise, validate, change, defer, retire, stop or proceed to a named next decision.

This is an Abrasim decision-support working methodology. It is not a statutory, financial, internal-audit, assurance, legal, privacy, security, employment or regulatory opinion. It does not certify transformation maturity or predict commercial results. Organisational baselines, capacity, costs, benefits, causal claims and future outcomes remain REQUIRES VALIDATION until authorised evidence establishes them.

Executive decision card: complete before assessing a programme

Assessment disposition enum STABILISE | VALIDATE | CHANGE | DEFER | RETIRE | STOP | PROCEED TO A NAMED DOWNSTREAM GATE

Use exactly one of those dispositions for each in-scope finding or option. Funding is not a competing disposition: record it separately as the resource commitment authorised for a selected next gate.

1. The Market Connection Context

The recognisable condition is not simply that a programme is late. It is that leadership cannot connect funded strategy to a changed experience, changed work or changed result:

• strategic objectives appear in programme language but not in the decisions, incentives or measures used by operating teams;
• customer or service journeys still cross the same avoidable handoffs while projects optimise systems or departments separately;
• delivery reports show scope, activity and milestones without a baseline or observable operating acceptance test;
• several initiatives depend on the same scarce people, data, integration or policy change, but each plan assumes that dependency is available;
• technology is being replaced while process, ownership, capability or decision rights remain unchanged;
• employees adopt workarounds because the new route adds burden, conflicts with local measures or does not cover real exceptions;
• leadership continues funding because stopping would expose sunk cost or disagreement, not because current evidence supports the next gate;
• expected benefits have no business owner, authoritative source, review cadence or change-and-stop threshold.

The primary value path is:

Strategy and funded decisions
→ coherent operating choices
→ changed workflows, behaviour and capability
→ different customer or service experience
→ measured operating and market outcome
→ evidence-led continue, change, stop or scale decision

The market connection is the purpose. Transformation, data, technology, process and capability are means. If an initiative cannot name the people or market outcome it is meant to improve or protect, the assessment should not rescue it by inventing a generic efficiency claim.

The eight connected assessment lenses

These lenses are not a maturity score and are not eight compulsory workstreams. Use them to test whether the selected outcome has a coherent route into daily operation.

For every material finding, use this causal chain:

Recognisable leadership or market condition
→ break between strategy and operating change
→ customer, employee or operating consequence
→ potential economic or service exposure
→ evidence needed to quantify and explain it
→ dated leadership decision

Potential effects may involve revenue, margin, cost, capacity, retention, risk, investment efficiency or service value. They remain REQUIRES VALIDATION until the organisation accepts the population, period, baseline, source, definition and causal logic.

The decision to make

Complete this statement before evidence collection:

By [decision date], [named decision owner] will assign [STABILISE, VALIDATE, CHANGE, DEFER, RETIRE, STOP, or PROCEED TO A NAMED DOWNSTREAM GATE] to [bounded transformation outcome and intervention set] because evidence shows that strategy is or is not becoming [named operating change], subject to [customer, employee, financial, capacity, legal, privacy, security, service and operating guardrails].

The date is a decision gate, not an implementation promise. If evidence is insufficient, leadership must record the exact validation required, owner and next date rather than approve a vague programme continuation.

When to use this method

Use the assessment when funded priorities span functions, journeys, workflows, data, technology and capability; when several programmes compete for the same dependencies; when delivered outputs have not produced accepted operating change; or when leadership needs evidence before committing to a larger transformation portfolio.

Do not use the full method when one bounded defect has a trusted cause, one owner and a cheaper direct repair; when an urgent safety, privacy, security, employment, legal or service issue requires immediate qualified containment; when leadership has already made an irreversible solution choice and will not consider contrary evidence; or when no authorised owner can act on the result.

The assessment is diagnostic. It must not produce a generic maturity score, an automatic technology roadmap, a supplier wish list or a fixed multi-year plan detached from current evidence and capacity. Official GOV.UK service guidance says discovery should understand and reframe the problem before building; this guide adopts that decision discipline while recognising that the source is public-service guidance, not a universal corporate mandate (GOV.UK Service Manual: discovery, VERIFIED official source at the source cut-off).

Scope, exclusions and dependencies

The minimum useful scope names:

• one strategic outcome and decision date;
• the affected market, customer, user, employee or service population;
• the selected business unit, geography, product, service, journey or workflow boundary;
• the funded initiatives, commitments and sunk-cost boundary relevant to the outcome;
• the operating-model, decision-right, data, technology, capability and governance dependencies;
• the evidence period, approved sources, access rules and baseline status;
• implementation, procurement, assurance and specialist conclusions explicitly excluded.

Material exclusions normally include implementation delivery, detailed solution architecture, software selection, formal procurement, workforce consultation, employment conclusions, statutory financial assurance, privacy or security certification, legal advice, guaranteed benefit quantification and enterprise-wide documentation unrelated to the decision.

Dependencies include an executive sponsor able to resolve cross-functional trade-offs, an operating owner who can accept changed work, authorised access to portfolio and source evidence, finance participation where economic definitions are material, affected people who can explain performed work, qualified control authorities, and protected capacity to make and operate a decision.

Expected results are decisions and artefacts: an accepted strategy-to-operating chain, evidence-bounded current-state diagnosis, material dependency view, diagnostic option set, baseline gaps, benefit ownership, next-gate requirements, executive disposition, handoff and dated review. Full investment cases, roadmaps, operating-model design and recovery methods remain downstream work. The assessment reduces visible uncertainty; it does not guarantee transformation results.

Assessment boundary and downstream handoff

The assessment locates the material break and records the next decision. It does not complete the specialist work that may follow:

The assessment may define the evidence and acceptance gate for these routes. It must not imply that their full diagnosis, investment case, roadmap, governance design, adoption work, technical decision, procurement or recovery method has already been completed.

2. The Leadership vs. Delegation Boundary

The work can be led internally or externally. The decisive conditions are cross-functional authority, controlled access, independent challenge and protected capacity, not possession of a branded methodology.

When an internal team can lead

A capable internal team can lead when the sponsor can resolve priorities and ownership across affected functions, source owners can provide controlled evidence, operating teams can be observed without retaliation or performance theatre, finance and benefit owners can reconcile baselines, and an independent challenger can test sunk-cost and solution bias. The team must have capacity to retain the evidence trail and follow the decision into operation.

When an independent senior partner is justified

Independent leadership is proportionate when the assessment challenges decisions made by current sponsors or suppliers, several budgets and functions are affected, reported progress conflicts with operating evidence, internal incentives protect sunk cost, or leadership needs one evidence model across customer, workflow, data, technology and capability boundaries.

The relevant paid Assess path is the Business Growth & Technology Opportunity Assessment when the question crosses the wider transformation portfolio and leadership needs an evidence-linked priority decision. Abrasim-led transformation, implementation, operating support or scale work must be separately scoped only after leadership accepts the assessment and funds the next gate.

When a narrower specialist or simpler intervention is sufficient

Use a process-improvement specialist for one stable workflow with an accepted outcome and no material cross-functional dependency. Use a technology, data, security, privacy, employment or finance specialist when the business decision is settled and the remaining question falls within that mandate. Use a contained proof when one risky assumption can be tested safely and reversibly. Retire an ownerless initiative rather than commissioning a broad assessment to preserve it.

Stop and escalation conditions

Stop or pause when evidence access is unauthorised, participation could create unmitigated employee or customer harm, a material incident requires qualified containment, the sponsor cannot protect an evidence-based decision, a finding is being used as assurance, or operating owners cannot accept the proposed change. Reduce the claim when source, period or population limits do not support it.

Escalate outcome and budget conflicts to the economic buyer; operating ownership and workflow disputes to the COO or named operating authority; data and technology source disputes to their accountable owners; access, privacy, security, employment, legal and regulatory questions to qualified authorities; unresolved benefit definitions to finance and the benefit owner; and scope or independence conflicts to the executive sponsor.

Questions for evaluating a provider

Ask:

1. How will you connect the strategic outcome to observable work and customer or service change before discussing technology?
2. Which evidence will distinguish project activity, delivered scope, adoption, operating performance and realised outcome?
3. How will you observe performed work, exceptions and local incentives rather than rely only on process documents and leadership interviews?
4. How will you expose sunk-cost bias, supplier interests, contested definitions, dissent and missing baselines?
5. Which transformation dimensions are material to this decision, and which will you deliberately exclude?
6. How will you distinguish a genuine technology constraint from a process, ownership, capability or decision-right constraint?
7. Which privacy, security, employment, finance, legal or assurance conclusions require our qualified owners rather than your sign-off?
8. What no-build, process, policy, capability, consolidation, retirement and stop alternatives will you compare?
9. What stable evidence, finding, option, decision, measure and gate IDs will remain with us?
10. How will operating ownership, capability transfer, access closure and benefit review work after the assessment?

Reject proposals that start with a platform replacement, universal maturity score, fixed roadmap or guaranteed benefit before the outcome, baseline, constraints and decision rights are understood.

3. The Step-by-Step Execution Standard

Use the Transformation Charter and Authority Register, Strategy-to-Operating Evidence Register, Transformation Finding, Option and Dependency Ledger, and Executive Decision, Benefit and Review Register. Store them in an approved location with a named custodian and version history.

Step 01: Charter the strategy-to-operating decision

Purpose and decision served Convert a broad transformation ambition into one dated leadership choice, one affected market connection and one observable operating-change question.

Accountable owner Executive sponsor, with the economic buyer accepting the funding and scope boundary.

Delegated lead and contributors Assessment lead; strategy owner; COO or operating authority; benefit owner; portfolio owner; finance, customer, data, technology, people and risk contributors.

Preconditions, inputs and access Approved strategy or funded decision; known programmes and commitments; an upcoming decision forum and date; authority to involve affected operating owners; approved working environment.

Actions

1. Write the decision using the assessment disposition enum: stabilise, validate, change, defer, retire, stop, or proceed to a named downstream gate for a bounded outcome and intervention set.
2. Name the customer, user, service recipient, employee, partner or market population affected and the outcome leadership intends to improve or protect.
3. Describe the observable workflow, behaviour, capability, decision right or service condition that must become different if the strategy works.
4. Record why confidence is contested, the potential consequence of delay or a wrong choice, and which claims still require a baseline.
5. Define business unit, geography, journey, workflow, portfolio, source period and system boundaries; list implementation and specialist conclusions excluded.
6. Set evidence-close and decision dates, proportionate burden, decision authority and stop conditions.

Evidence to retain Strategy and funding references, decision question, market boundary, operating-change statement, scope, exclusions, dates, baseline status and approved charter version.

Decision or scoring rule Proceed only when one authorised question, outcome, operating change, decision date and scope are explicit. Use change for an oversized or solution-led question, defer for unavailable authority and stop when no owner can act.

Output and template Charter rows in the Transformation Charter and Authority Register, with stable A4-AUD-* and A4-DEC-* IDs.

Acceptance gate PROCEED only if the sponsor and decision owner accept the outcome, operating-change test, scope, evidence threshold, dates and stop route; otherwise CHANGE, DEFER or STOP.

Leadership checkpoint The economic buyer confirms that the decision consequence justifies the evidence burden and that no preferred programme, supplier or platform is protected from challenge.

Human control point Only the authorised sponsor may accept or widen the charter; project activity and budget consumption cannot substitute for strategic authority.

Failure modes and safeguards Failure modes are enterprise-wide scope, generic “modernisation”, deliverables framed as outcomes and a predetermined solution. Safeguard with one decision card and a versioned scope-change record.

Change, stop or escalation condition Escalate competing outcomes or authorities to the economic buyer. Stop if the decision is already irreversible, performative or cannot change funding or operation.

Handoff to the next step Pass the accepted charter to Step 02 for decision rights, operating ownership, independent challenge and specialist authority.

Step 02: Assign decision rights and operating ownership

Purpose and decision served Make clear who can supply evidence, resolve cross-functional trade-offs, accept changed work and decide the next investment gate.

Accountable owner Executive sponsor.

Delegated lead and contributors Assessment lead; economic buyer; decision owner; benefit and finance owners; journey and workflow owners; portfolio, data, technology and capability owners; information and control authorities; independent challenger.

Preconditions, inputs and access Accepted charter; organisational mandates and forum terms; initiative ownership; applicable access, risk and people policies; supplier and sponsor interests.

Actions

1. Assign sponsor, economic buyer, decision owner, assessment lead, benefit owner, evidence coordinator, operating owner, information authority and working-pack custodian.
2. Map decision rights for scope, evidence access, baseline acceptance, initiative retirement, resource commitment, operating design, risk acceptance and scale.
3. Name business and technical owners for each initial measure, source, system and material dependency.
4. Identify who designed, funded, supplied or reported the current programmes and record conflicts, self-review risk and recusal controls.
5. Appoint an independent challenger able to inspect the evidence and retain dissent.
6. Define escalation routes and response dates for outcome, budget, operating, data, technology, people, control and evidence disputes.

Evidence to retain Named role acceptance, mandate and forum references, conflict declarations, recusal decisions, escalation routes, quorum and authority limits.

Decision or scoring rule A role is assigned only when the named person accepts it and has the authority and capacity stated. A sponsor title, steering-committee seat or supplier contract is not acceptance of operating ownership.

Output and template Authority and role rows in the Transformation Charter and Authority Register.

Acceptance gate PROCEED when every material outcome, source, dependency, control, operating change and final disposition has an accepted owner and credible challenge; otherwise CHANGE or DEFER.

Leadership checkpoint The sponsor resolves authority gaps and confirms that operating owners can challenge programme and supplier claims without penalty.

Human control point Finance, legal, privacy, security, employment, regulatory and risk authorities retain their mandates; the assessment team cannot approve its own access or assurance.

Failure modes and safeguards Failure modes are generic RACI labels, committee ownership, incompatible roles and a transformation office owning benefits it cannot operate. Safeguard with one accountable person per decision and explicit shared contributors.

Change, stop or escalation condition Pause affected work for missing authority or unmanaged conflict. Stop the assessment if leadership will not name who can accept, change or stop the programme.

Handoff to the next step Give the accepted authority map to Step 03 so evidence requests, observation and handling controls are authorised before fieldwork.

Step 03: Design the evidence and access plan

Purpose and decision served Establish a proportionate, controlled route to strategy, portfolio, customer, workflow, people, data and technology evidence before collecting it.

Accountable owner Information authority for access and handling; assessment lead for method; decision owner for proportionality.

Delegated lead and contributors Evidence coordinator; source owners; customer and service researchers; process analyst; finance partner; people, data, technology, privacy and security contributors; independent challenger.

Preconditions, inputs and access Accepted charter and role map; source inventory; approved environment; information classifications; retention and incident routes; known employee and customer participation conditions.

Actions

1. Translate the charter into evidence questions across outcome, journey, workflow, operating model, data, technology, capability, governance and benefit realisation.
2. For each question, state the minimum source, population, period, unit, method, comparison and owner required.
3. Record purpose or authority, information classification, approved users and location, extraction limits, retention, disposal and incident route before access.
4. Design interview, observation, work-sample and system-test methods that protect affected people and minimise unnecessary personal or sensitive information.
5. Predefine how facts, corroborated interpretations, single-source statements, assumptions, evidence gaps and constraints will be recorded and reconciled.
6. Give every source and evidence item a stable ID and controlled version or reference; keep one material evidence item per row.
7. Obtain named approvals; record denied or unavailable evidence as a limitation rather than substituting unsupported confidence.

Evidence to retain Evidence request, source owner, approved purpose and access, method, sample or population, consent or participation condition, retention date, incident route, denied-access record and version.

Decision or scoring rule An evidence route is approved only when decision use, authority, source, method, population, handling and limitations are explicit. Otherwise use change, defer, exclude or stop.

Output and template Access, source and evidence-plan rows in the Strategy-to-Operating Evidence Register.

Acceptance gate PROCEED only for authorised routes whose evidence can support the intended claim; all other claims remain REQUIRES VALIDATION or are excluded.

Leadership checkpoint The decision owner confirms that evidence burden is proportionate; information and people authorities confirm the access and participation route.

Human control point Qualified humans approve access, employment, privacy, security, legal and risk conditions. A programme office or automated discovery tool cannot grant that authority.

Failure modes and safeguards Failure modes are uncontrolled document dumps, copying employee or customer data into worksheets, collecting every available artefact and designing tests after seeing the result. Safeguard with pre-registered questions, least privilege and stable evidence rows.

Change, stop or escalation condition Stop for unsafe credentials, unapproved sensitive information or an incident. Escalate missing material evidence to the decision owner and reduce the conclusion rather than bypass controls.

Handoff to the next step Pass approved evidence routes and source IDs to Step 04 for portfolio, commitment and baseline reconciliation.

Step 04: Establish the funded portfolio and outcome baseline

Purpose and decision served Show what leadership has funded or committed, what each initiative is expected to change and whether a defensible starting point exists.

Accountable owner Economic buyer for investment; benefit owner for outcome definition.

Delegated lead and contributors Portfolio analyst; finance partner; programme and product owners; procurement or commercial owner; metric owners; operating owners; independent challenger.

Preconditions, inputs and access Approved evidence routes; current and prior business cases, budgets, contracts, roadmaps, benefits, risks, decisions, status reports and operating measures.

Actions

1. Inventory active, committed, paused and recently closed initiatives relevant to the chartered outcome, assigning stable initiative IDs.
2. Record sponsor, business owner, delivery owner, budget or capacity basis, supplier commitment, intended outcome, deliverables, dependencies, decision gates and current disposition.
3. Separate sunk cost from future resource decisions; record cancellation, renewal, exit and contractual constraints without treating them as reasons to continue.
4. Trace each promised benefit to an accepted definition, baseline, source, population, period, owner and review record.
5. Mark missing, reconstructed, incomparable or disputed baselines and record what evidence could establish or reject them.
6. Identify duplicate initiatives, conflicting outcomes, shared dependencies and capacity booked more than once.
7. Reconcile programme status with accepted delivery, adoption, operating and outcome evidence rather than one composite colour.

Evidence to retain Initiative, funding and contract references; intended outcomes; baseline sources and versions; benefit assumptions; owners; dependencies; status evidence; renewal or exit terms; dissent and gaps.

Decision or scoring rule An initiative is traceable to outcome only when its deliverables, required operating change, benefit owner, baseline status, dependencies and next gate are explicit. Otherwise classify it requires validation, candidate consolidation or candidate stop.

Output and template Portfolio and baseline evidence rows in the Strategy-to-Operating Evidence Register.

Acceptance gate Every in-scope commitment has a stable ID, future-decision boundary, outcome relationship, baseline status, owner and next gate; unknowns remain visible.

Leadership checkpoint The economic buyer confirms the portfolio perimeter and that sunk cost will not be scored as future value.

Human control point Finance or the authorised commercial owner validates financial definitions and commitments; programme self-reporting cannot certify realised benefit.

Failure modes and safeguards Failure modes are a project list without decisions, inherited benefit numbers, green status without acceptance evidence and hidden supplier dependencies. Safeguard with separate delivery, adoption, operating and outcome records.

Change, stop or escalation condition Escalate unrecorded commitments, duplicated funding or disputed benefit ownership. Stop using an unsupported baseline and create a baseline-establishment gate.

Handoff to the next step Give the bounded initiatives, outcomes and baseline gaps to Step 05 for direct journey and workflow observation.

Step 05: Observe priority journeys and performed work

Purpose and decision served Establish how the strategy meets customers, employees and operating reality, including exceptions that programme documents omit.

Accountable owner Customer or service owner for the journey; process owner for performed work.

Delegated lead and contributors Researcher or service designer; process analyst; frontline participants; accessibility specialist; operations, customer, product and data contributors; evidence coordinator.

Preconditions, inputs and access Approved participation and evidence plan; selected journeys and workflows; representative cases and periods; existing maps; authority to observe without creating service or employment harm.

Actions

1. Select journeys and workflows most directly connected to the chartered outcome and explain exclusions.
2. Observe representative real work and customer or service interactions across channels, roles and relevant edge cases; do not rely on workshops alone.
3. Map entry, desired next state, actors, handoffs, waits, decisions, information, systems, controls, workarounds and exceptions.
4. Record where the funded initiatives are expected to change the map and whether that change is observed, partial, resisted, bypassed or not yet testable.
5. Reconcile observation with service records, complaints, accessibility evidence, process measures and participant accounts.
6. Identify customer or employee burden shifted outside the measured workflow and record inclusion or accessibility limits.
7. Obtain participant and owner review while preserving dissent and protecting confidential information.

Evidence to retain Observation plan and notes, journey or workflow node IDs, case or sample boundaries, service and exception records, participant review, programme-change links, limitations and evidence status.

Decision or scoring rule A condition is observed only when retained evidence shows it in the defined context. Use corroborated interpretation, single-source statement, assumption or evidence gap where appropriate.

Output and template Observation and workflow rows in the Strategy-to-Operating Evidence Register.

Acceptance gate PROCEED TO DIAGNOSIS only when each material operating-change claim has observed or corroborated evidence, an affected population, owner and limitation.

Leadership checkpoint Operating and customer owners confirm that the selected work represents the decision context and that inconvenient exceptions have not been excluded.

Human control point Participants and qualified people, privacy, safety and accessibility authorities control participation and harm boundaries; observation is not covert surveillance.

Failure modes and safeguards Failure modes are idealised process maps, demonstrations instead of real work, convenient samples and blaming staff for system constraints. Safeguard with representative cases, exception evidence and separation of condition from cause.

Change, stop or escalation condition Change the sample when it cannot represent the scoped decision. Stop or escalate for unsafe observation, material harm, retaliation risk or lack of participation authority.

Handoff to the next step Pass observed handoffs, exceptions and operating-change status to Step 06 for operating-model, capability and decision-right analysis.

Step 06: Assess the operating model and capability conditions

Purpose and decision served Determine whether structure, roles, incentives, funding, workload, capability and management routines enable or preserve the observed operating condition.

Accountable owner COO or named operating authority.

Delegated lead and contributors Operating-model lead; process and product owners; finance, HR or people authority; portfolio and change leads; frontline managers; learning and support owners; independent challenger.

Preconditions, inputs and access Observed journeys and workflows; role mandates; performance measures; funding and capacity records; decision forums; capability and support evidence; applicable employment conditions.

Actions

1. Map accountability for the outcome, journey, workflow, product or service, data, technology, benefit and operational support.
2. Trace how priorities, budgets, performance measures and incentives influence the behaviour observed in Step 05.
3. Observe decision forums and escalation examples to test who decides, with what evidence, in what time and what happens when owners disagree.
4. Compare required roles, workload, skills, learning, support and management routines with current capacity and accepted responsibilities.
5. Record duplicated, missing or conflicting ownership, approval loops, hidden coordination work and reliance on individuals or suppliers.
6. Test whether adoption evidence shows changed behaviour and accepted operating competence rather than communication, attendance or access alone.
7. Refer employment, labour, organisation-design and workforce conclusions to authorised qualified owners.

Evidence to retain Role and decision maps, forum records, performance measures, workload and capacity evidence, capability requirements, learning and support records, adoption observations, owner review and limitations.

Decision or scoring rule A condition is a material operating-model constraint only when it has evidence, affects the named operating change and cannot be resolved within ordinary role authority. Use REQUIRES VALIDATION for unsupported capability or incentive claims.

Output and template Operating-model, decision-right and capability evidence rows in the Strategy-to-Operating Evidence Register.

Acceptance gate Every material ownership, authority, capacity or capability finding names the observed consequence, evidence, accountable owner and specialist boundary.

Leadership checkpoint The COO and people authority review trade-offs and confirm which constraints can be changed within current mandates.

Human control point Employment, performance, role and workforce decisions remain with authorised organisational authorities and affected governance processes.

Failure modes and safeguards Failure modes are generic “resistance” labels, training as the default response, organisation charts as operating evidence and change work added without removing existing load. Safeguard with performed-work evidence and capacity reconciliation.

Change, stop or escalation condition Withdraw a people claim that lacks evidence. Escalate unsafe workload, conflicted incentives or authority gaps; stop options that require unapproved role or employment change.

Handoff to the next step Pass the operating-model and capability conditions to Step 07 for data, technology, governance and dependency testing.

Step 07: Test data, technology and governance dependencies

Purpose and decision served Establish which information, systems, architecture, controls and supplier conditions genuinely constrain the named operating change.

Accountable owner CIO or named technology authority, jointly with business and information owners for decision relevance.

Delegated lead and contributors Data and architecture leads; application and integration owners; security and privacy authorities; service-management and procurement owners; business metric and process owners; assessment lead.

Preconditions, inputs and access Chartered outcome, observed work, operating-model evidence, approved technical access, architecture and change records, source and service ownership, control requirements.

Actions

1. Start from each material operating handoff and trace the data, application, integration, infrastructure, support, supplier and control conditions it depends on.
2. Record which condition is observed to prevent, delay, distort or increase the risk of the desired operating state.
3. Distinguish a genuine value constraint from inconvenience, age, aesthetic preference, duplicate functionality or an untested architecture assumption.
4. Test source quality, integration behaviour, manual adjustment, reliability, support, access, resilience and change-control evidence only to the depth required by the decision.
5. Map contractual, licensing, procurement, data-migration, interoperability, security, privacy, retention and vendor-exit dependencies.
6. Identify no-build, configuration, process, policy, data-quality, integration, containment and retirement alternatives before replacement.
7. Refer detailed security, privacy, architecture, legal, regulatory and procurement conclusions to their qualified authorities.

Evidence to retain Dependency and node IDs, source or system references, observed constraint, affected workflow, owner, test method, service and change evidence, contractual condition, control referral, alternatives and limits.

Decision or scoring rule A data or technology condition is a material transformation dependency only when evidence links it to the chartered operating change and consequence. Otherwise classify it inconvenience, assumption, local repair or requires specialist validation.

Output and template Dependency and technical-evidence rows in the Strategy-to-Operating Evidence Register.

Acceptance gate Every material dependency has evidence, consequence, owner, control boundary and at least one proportionate alternative; untested claims remain visible.

Leadership checkpoint Business and technology owners jointly confirm which constraints must precede value and which do not justify transformation scope.

Human control point Qualified authorities accept technical risk, security, privacy, architecture, procurement and supplier-exit conclusions; the transformation lead cannot self-certify them.

Failure modes and safeguards Failure modes are replacement by default, technical debt used as a universal business case, architecture detached from workflows and supplier claims accepted without operational evidence. Safeguard with consequence tracing and alternative classes.

Change, stop or escalation condition Escalate material control, resilience or contractual exposure immediately. Stop a replacement recommendation that cannot show why a smaller response is insufficient.

Handoff to the next step Give all customer, workflow, operating-model, data, technology and governance evidence to Step 08 for reconciliation and diagnosis.

Step 08: Reconcile evidence and diagnose the material break

Purpose and decision served Produce a shared, bounded explanation of why strategy is not becoming operating change without allowing the loudest function or supplier to define the problem.

Accountable owner Executive sponsor for cross-functional diagnosis; affected operating owner for each finding.

Delegated lead and contributors Assessment lead; evidence coordinator; independent challenger; customer, operating, finance, people, data, technology and control owners; programme representatives.

Preconditions, inputs and access Portfolio and baseline evidence; observations; operating-model, capability, data, technology and governance evidence; decision history; source-owner responses and open gaps.

Actions

1. Organise evidence by the strategy-to-operating chain and chartered decision, not by department or programme.
2. Reconcile differences in outcome, population, period, definition, status, source and causal interpretation.
3. Write each finding as condition, accepted expectation, evidence, affected operating change, customer or operating consequence, cause alternatives, uncertainty and required decision.
4. Test whether the apparent cause is outcome ambiguity, portfolio conflict, workflow design, ownership, incentive, capacity, capability, data, technology, governance, adoption or a combination.
5. Classify engagement evidence as observed fact, corroborated interpretation, single-source statement, assumption, evidence gap or constraint.
6. Apply public claim status VERIFIED, INFERRED, PROPOSED or REQUIRES VALIDATION and keep reasoning close to every material inference.
7. Review findings with affected owners and retain acceptance, qualification and dissent without forcing false consensus.

Evidence to retain Finding ID, evidence and dependency IDs, strategy-to-operating break, condition, expectation, consequences, causal alternatives, classifications, owner dispositions, dissent and validation need.

Decision or scoring rule A finding is decision-grade only when its condition is traceable, consequence is bounded, cause alternatives were tested, uncertainty is visible and a named owner can act. A maturity rating or anecdote alone is not a finding.

Output and template Finding rows in the Transformation Finding, Option and Dependency Ledger.

Acceptance gate Every material finding is accepted, qualified, sent for defined validation or withdrawn; dissent and evidence gaps remain linked.

Leadership checkpoint The sponsor decides whether contested but consequential findings require more evidence, provisional containment or removal from the decision set.

Human control point Affected owners validate internal source meaning; qualified authorities decide whether observations imply legal, privacy, security, employment, financial or regulatory consequences.

Failure modes and safeguards Failure modes are generic maturity language, technology as root cause by default, averaging disagreement and confusing correlation with causation. Safeguard with stable evidence IDs and alternative-explanation review.

Change, stop or escalation condition Downgrade or withdraw a finding when evidence does not support its consequence. Escalate urgent harm or control failures without waiting for the final decision pack.

Handoff to the next step Pass accepted and provisional findings to Step 09 for proportionate operating and investment alternatives.

Step 09: Develop transformation and non-transformation alternatives

Purpose and decision served Give leadership real choices rather than converting every finding into a large programme or technology project.

Accountable owner Decision owner, with the economic buyer owning material funding trade-offs.

Delegated lead and contributors Assessment lead; operating, finance, people, data and technology owners; architecture and risk specialists; procurement where needed; independent challenger.

Preconditions, inputs and access Decision-grade findings, accepted constraints, current commitments, available capacity, operating and control requirements, exit conditions and baseline status.

Actions

1. Create the applicable alternatives: leave unchanged with accepted exposure, stop or retire, simplify policy or process, clarify ownership, build capability, configure or integrate existing technology, repair data, replace technology, refer portfolio restructuring to The Transformation Portfolio and Investment Case: Funding the Smallest Coherent Set of Changes or run a bounded validation.
2. State each option's causal logic, affected customer and operating outcome, evidence strength, expected change, cost basis, capacity burden, dependencies and risk.
3. Separate immediate stabilisation, reversible proof, operating redesign and larger transformation scope.
4. Record no-action exposure without invented monetary value and distinguish avoidable risk from speculative opportunity.
5. Define reversibility, containment, exit, knowledge transfer and ongoing operating obligations.
6. Test accessibility, service continuity, people, privacy, security, data, financial and supplier guardrails.
7. Preserve rejected options, dissent and the evidence that would change the proposed disposition.

Evidence to retain Option ID, linked findings and evidence, option class, causal assumption, customer and operating mechanism, cost basis, capacity, dependencies, risk, guardrails, reversibility, dissent and evidence need.

Decision or scoring rule Use proceed, validate, change, defer or stop. Do not add ratings into an automatic winner. A critical control failure, absent owner or impossible dependency may override a promising value case.

Output and template Option rows in the Transformation Finding, Option and Dependency Ledger.

Acceptance gate Every recommended response traces to a finding, includes a no-action or stop comparison where applicable, states operating burden and has an owner, validation route and exit.

Leadership checkpoint The economic buyer reviews displaced work and future operating cost before any option enters a portfolio.

Human control point Only authorised leadership may accept residual risk, alter roles, displace budget or retire a material capability.

Failure modes and safeguards Failure modes are programme expansion, vendor-led options, false precision and treating local repair as insufficient because it is not called transformation. Safeguard with explicit option classes and evidence-linked rationale.

Change, stop or escalation condition Change an option when prerequisites or guardrails cannot pass. Stop options with no outcome owner, no operating capacity, no evidence route or no proportionate purpose.

Handoff to the next step Pass viable and rejected alternatives to Step 10 for coherence, dependency and priority decisions.

Step 10: Prioritise diagnostic dispositions and dependencies

Purpose and decision served Rank the evidence-supported next decisions and make dependencies visible without producing the full portfolio investment case or transformation roadmap owned by later guides.

Accountable owner Economic buyer and executive decision owner.

Delegated lead and contributors Portfolio lead; assessment lead; benefit and finance owners; operating, data, technology, people and control owners; independent challenger.

Preconditions, inputs and access Accepted findings and options; current portfolio; dependency map; capacity and funding evidence; control obligations; baseline and measurement readiness.

Actions

1. Group options by the outcome and operating change they may enable, separating local repairs from questions needing a downstream transformation method.
2. Map prerequisite, enabling, shared-resource, contractual, decision and evidence dependencies with named owners.
3. Assess customer or service relevance, business value, evidence strength, feasibility, risk, reversibility, time to learning, capacity and operating fit.
4. Identify duplicated initiatives, mutually exclusive options and commitments that should consolidate, wait or stop.
5. Classify the next decision as stabilise, validate, change, defer, retire, stop, or proceed to a named downstream gate; name the applicable The Transformation Scope Decision: Improve, Automate, Modernise or Transform–The Stalled Transformation Recovery and Value-Realisation Standard: Recover, Stop or Scale handoff when the final disposition is to proceed.
6. Make opportunity cost explicit: name the work, budget, leadership attention or capacity displaced by each priority.
7. Record the proposed stabilise, validate, change, defer, retire, stop, or proceed to a named downstream gate disposition with rationale, resource commitment and dissent.

Evidence to retain Portfolio record, option and finding IDs, dependencies, owner and capacity commitments, prioritisation rationale, opportunity cost, conflicts, dispositions, dissent and evidence gates.

Decision or scoring rule A recommendation set is decision-ready only when every proposed disposition traces to the bounded outcome, dependencies and capacity are visible, and the next evidence gate is testable. It is not a full investment case or roadmap. Scores inform discussion; narrative and control gates decide.

Output and template Disposition and dependency rows in the Transformation Finding, Option and Dependency Ledger.

Acceptance gate READY FOR NEXT GATE when the proposed dispositions are bounded by the evidence, every material dependency has an owner and excluded work has a recorded route.

Leadership checkpoint The economic buyer confirms funding and capacity trade-offs; the COO confirms that the organisation can absorb and operate the proposed change.

Human control point Leadership decides priority and opportunity cost. A weighted model cannot commit resources or accept control exposure.

Failure modes and safeguards Failure modes are hundreds of initiatives, dependencies hidden in footnotes, every item marked urgent and roadmaps ordered by supplier timeline. Safeguard with one outcome chain, finite capacity and dated decision gates.

Change, stop or escalation condition Return options for redesign if shared dependencies or capacity cannot be owned. Stop recommended items whose independent value cannot be tested or operated.

Handoff to the next step Give the evidence-linked dispositions and dependencies to Step 11 for next-gate requirements and handoff.

Step 11: Define the next evidence gate and handoff

Purpose and decision served Define only the bounded proof, control, handoff and acceptance requirements needed for leadership's next decision; route full portfolio, roadmap, governance, adoption, technology or recovery work to its canonical downstream guide.

Accountable owner Delivery owner for change execution; benefit owner for outcome and evidence logic.

Delegated lead and contributors Portfolio and implementation leads; operating owners; finance and metric owners; data, technology, people, change, privacy, security, accessibility and service specialists.

Preconditions, inputs and access Proposed dispositions; accepted findings; dependency and capacity evidence; baseline or baseline plan; control conditions and applicable downstream guide.

Actions

1. Define the smallest next scope that can establish a necessary control, test the key causal assumption or confirm whether deeper downstream work is justified.
2. Name target population, workflow, operating state, comparison method, evidence window, definitions and baseline status.
3. Specify deliverables, adoption conditions, operating acceptance tests, dependencies, owners and evidence-retention requirements.
4. Separate learning, delivery, operating adoption, customer or commercial outcome and guardrail measures.
5. Create the immediate dated evidence and decision gate with proceed, validate, change, defer and stop routes; do not manufacture a full programme roadmap.
6. Define the minimum rollback, containment, exit, service continuity, data handling, capability and support conditions that the receiving guide or delivery scope must resolve.
7. Name the applicable handoff within the guide sequence from the Transformation Scope Decision to the Stalled Transformation Recovery and Value-Realisation Standard. Confirm authority for the next assessment or separately scoped work.

Evidence to retain Approved scope, causal assumption, population, baseline evidence or gap, dated plan, resources, dependencies, acceptance tests, measures, guardrails, exit and approval references.

Decision or scoring rule The plan is ready for executive decision only when it can produce evidence fit for the decision or protect a mandatory condition within a bounded scope, with operating ownership and exit. Otherwise change, validate, defer or stop.

Output and template Proposed measure and gate rows in the Executive Decision, Benefit and Review Register.

Acceptance gate Business, operating, delivery, finance, information and applicable control owners accept scope, capacity, measures, safeguards, evidence and exit.

Leadership checkpoint The economic buyer confirms that the evidence sought justifies the next commitment and that a smaller intervention has not been ignored.

Human control point Benefit and control owners approve their definitions and limits; a delivery supplier cannot self-approve success criteria or waive a guardrail.

Failure modes and safeguards Failure modes are fixed multi-year plans, dates without dependencies, benefits without baseline and implementation completion treated as transformation success. Safeguard with separate records and evidence gates.

Change, stop or escalation condition Return to Step 09 when scope cannot be bounded. Stop if the plan cannot test its key assumption, required controls fail or no operating owner accepts handover.

Handoff to the next step Submit the next-gate requirements, decision-grade findings, options, dispositions and dissent to Step 12 for authorised decision.

Step 12: Make the executive decision and transfer ownership

Purpose and decision served Record one authorised stabilise, validate, change, defer, retire, stop, or proceed to a named downstream gate disposition for every in-scope item, then move accepted work and evidence into accountable operation.

Accountable owner Named executive decision owner in the authorised forum.

Delegated lead and contributors Assessment lead presents; economic buyer, COO, benefit, delivery and operating owners, finance and control authorities, and independent challenger contribute.

Preconditions, inputs and access Accepted charter; findings; alternatives; diagnostic dispositions; next-gate requirements; measurement contracts; resource and authority evidence; risks, gaps and dissent.

Actions

1. Present the market connection, operating-change chain, evidence statuses, material breaks, alternatives, dependencies, capacity and guardrails.
2. Ask affected owners and the independent challenger to state unresolved assumptions, conflicts, evidence gaps and dissent.
3. Record each in-scope finding or option as stabilise, validate, change, defer, retire, stop, or proceed to a named downstream gate; do not interpret silence or report receipt as approval.
4. Record rationale, rejected alternatives, resource commitment, accepted exposure and dated next evidence or decision gate.
5. Assign benefit, delivery, operating, workflow, source, metric, technology, capability and control ownership.
6. Transfer charter, evidence, definitions, findings, decisions, measures, runbooks, access obligations, retention actions, supplier conditions and incident routes.
7. Obtain handover acceptance and close, retain or reauthorise temporary and provider access.

Evidence to retain Authorised decisions, forum and mandate, rationale, dissent, commitments, owners, risk acceptance, approval reference, handover inventory, access review and next gate.

Decision or scoring rule Only the authorised forum issues a disposition. Proceed to a named downstream gate means leadership accepts the stated evidence limits, safeguards, resources and next gate; it is not a guarantee of outcome.

Output and template Decision and handover rows in the Executive Decision, Benefit and Review Register.

Acceptance gate ASSESSMENT CLOSED only when every in-scope item has a recorded disposition, owner and date, handover is accepted and outstanding evidence is assigned; otherwise the assessment remains open.

Leadership checkpoint The decision owner reads back the diagnostic dispositions, accepted uncertainty, commitments, stop authority and next gates.

Human control point Final funding, risk, role, customer, employee and operating accountability remains with named humans; no assessment score or provider makes the decision.

Failure modes and safeguards Failure modes are approving a report rather than choices, retaining every initiative, ownerless benefits and lingering supplier access. Safeguard with separate decision, measure, gate and handover rows.

Change, stop or escalation condition Escalate a decision outside authority or without mandatory controls. Stop work when the funded scope conflicts with the recorded disposition.

Handoff to the next step Pass accepted measures, controls, operating artefacts and dates to Step 13 for benefit and operating review.

Step 13: Review operating change and decide whether to change, stop or scale

Purpose and decision served Judge whether funded work has produced accepted operating change and whether observed outcomes support continuation, correction, closure or controlled extension.

Accountable owner Benefit owner and executive decision owner; operating owner for sustained work.

Delegated lead and contributors Metric and source owners; delivery and operating teams; finance partner; customer or service owner; people, data, technology and control owners; independent reviewer at material gates.

Preconditions, inputs and access Authorised decision, accepted handover, baseline or baseline plan, metric contracts, operating acceptance tests, guardrails, runbooks and dated review gate.

Actions

1. Record actual delivery, adoption, operating, outcome and guardrail evidence separately, preserving unit, population, period, definition version and data-quality status.
2. Test whether the named workflow, behaviour, capability, decision right or service condition changed and remains operable without exceptional project support.
3. Compare outcome evidence with the approved baseline or comparator while stating concurrent changes, market conditions, lag and attribution limits.
4. Review customer and employee consequences, workload, exceptions, service continuity, incidents, supplier reliance and control outcomes.
5. Investigate benefit shortfall, burden or guardrail breach and record containment and cause status.
6. Decide continue, change, hold, stop or scale; require fresh evidence and capacity review before extending purpose, population, geography or operating scope.
7. Update ownership, definitions, runbooks, access, retention, capability transfer and next gate; re-charter material changes.

Evidence to retain Actual measure results, source and definition versions, operating acceptance, customer and employee evidence, exceptions, costs where authorised, guardrails, causal interpretation, dissent, disposition and approval.

Decision or scoring rule Scale only when operating acceptance, outcome threshold, guardrails, capacity and ownership pass for the defined population and the new context is validated. Change or stop when harm, burden, control failure or unsupported causal logic exceeds the accepted boundary.

Output and template Measure, review and new gate rows in the Executive Decision, Benefit and Review Register.

Acceptance gate Every review ends with a named disposition, evidence status, owner, containment or next action and date; monitor alone is not a disposition.

Leadership checkpoint The economic buyer and COO accept the result, attribution limits, operating burden and opportunity cost before continuing or scaling.

Human control point Qualified authorities decide incidents and guardrails; affected customer and employee accountability and resource trade-offs remain human decisions.

Failure modes and safeguards Failure modes are success declared from delivery, temporary project behaviour counted as adoption, benefits claimed from correlation and scale before support capacity exists. Safeguard with separate measures and an operating acceptance gate.

Change, stop or escalation condition Re-charter material changes in purpose, population, workflow, identity use or operating model. Stop for failed guardrails, withdrawn authority, unmanageable burden or no evidence that the intervention supports its claimed mechanism.

Handoff to the next step There is no automatic next phase. Continue controlled operation, return to Step 01 for a changed decision, or close the intervention with retained evidence, access closure and accountable disposal.

4. The Evidence & Measurement Checklist

Copy the applicable tests into the working pack. A tick means the named evidence exists and its owner has accepted the test; it is not a maturity score or assurance opinion.

Preflight and authority

• One dated decision uses the assessment disposition enum for the bounded strategic outcome and records funding separately as resource commitment. Evidence: approved charter and decision ID. Owner: executive sponsor.
• The affected market, customer, user, employee or service population and required operating change are explicit. Evidence: accepted market-and-operating statement. Owner: decision owner.
• Scope names the business, journey, workflow, portfolio, period and dependency boundaries plus material exclusions. Evidence: versioned scope record. Owner: assessment lead.
• Sponsor, economic buyer, decision owner, operating owner, benefit owner, information authority and independent challenger accepted their roles. Evidence: role-acceptance record. Owner: executive sponsor.
• Evidence-close date, decision date, burden limit, forum authority, escalation routes and stop conditions are approved. Evidence: charter approval reference. Owner: executive sponsor.

Evidence access and quality

• Every material evidence item has a stable ID, decision use, source owner, version, period and approved location. Evidence: strategy-to-operating evidence register. Owner: evidence coordinator.
• Purpose, authority, information classification, authorised users, extraction limit, retention and incident route are recorded before access. Evidence: approved access record. Owner: information authority.
• Interview, observation, work-sample and system-test methods state population, sample, exclusions and limitations before execution. Evidence: approved evidence plan. Owner: assessment lead.
• One material evidence item is retained per evidence row and composite claims link their constituent IDs. Evidence: row-integrity review. Owner: working-pack custodian.
• Missing, denied, conflicting or inaccessible evidence remains visible and is not replaced by an unsupported maturity score. Evidence: evidence-gap and reconciliation rows. Owner: evidence coordinator.

Method execution

• The strategy-to-operating chain links outcome, funded choice, operating design, performed work, customer or service effect and review decision. Evidence: accepted transformation chain. Owner: decision owner.
• The current portfolio separates delivery, adoption, operating and outcome evidence and records sunk cost outside future-value logic. Evidence: portfolio and baseline register. Owner: economic buyer.
• Priority journeys and workflows were observed with exceptions rather than inferred only from documents or workshops. Evidence: observation records and participant review. Owner: operating owner.
• Operating-model, capability, data, technology and governance constraints trace to a named operating consequence. Evidence: dependency records. Owner: assessment lead.
• Findings test credible alternative causes and retain facts, interpretations, assumptions, gaps and dissent separately. Evidence: reviewed finding ledger. Owner: independent challenger.

Governance, privacy, security and risk

• Decision rights exist for outcome, scope, funding, operating design, evidence access, risk acceptance, handover and scale. Evidence: authority register. Owner: executive sponsor.
• Customer, employee, accessibility, privacy, security, service, financial and supplier guardrails have named qualified authorities. Evidence: control-owner map. Owner: decision owner.
• Participation and evidence handling avoid unnecessary personal or sensitive information and prohibit uncontrolled credentials. Evidence: access and participation review. Owner: information authority.
• Employment, legal, privacy, security, financial, regulatory and assurance conclusions are referred rather than implied. Evidence: specialist referral and disposition. Owner: proof owner.
• Conflicts, supplier interests, self-review risk, recusal, dissent and accepted residual exposure are explicit. Evidence: conflict and risk records. Owner: independent challenger.

Deliverables and acceptance

• The charter links one strategic outcome to a dated decision, market connection, operating change and evidence threshold. Evidence: accepted charter. Owner: executive sponsor.
• The evidence register connects funded commitments, baselines, observations, dependencies and limitations through stable IDs. Evidence: register acceptance review. Owner: evidence coordinator.
• Every material finding states condition, expectation, evidence, consequence, cause alternatives, uncertainty and required decision. Evidence: finding-owner disposition. Owner: assessment lead.
• The diagnostic option set includes applicable no-action, stop, simplify, process, policy, capability, data, technology and validation routes. Evidence: option comparison. Owner: decision owner.
• The next-gate handoff specifies acceptance, owners, dependencies, measures, guardrails, exit and the applicable downstream method. Evidence: handoff acceptance record. Owner: delivery owner.

Measurement

• Learning, delivery, operating adoption, customer or commercial outcome and guardrail measures are separate records. Evidence: benefit-and-review register. Owner: benefit owner.
• Every measure records definition, unit, population, exclusions, baseline status, source, owners, cadence and attribution limits. Evidence: metric contract. Owner: business metric owner.
• Actual results preserve baseline, definition version, population, period, source quality and comparator. Evidence: review measure rows. Owner: technical metric owner.
• Each threshold triggers a named continue, change, hold, stop or scale action rather than monitor alone. Evidence: accepted decision rule. Owner: decision owner.
• Scale requires operating acceptance, outcome evidence, guardrail passage and capacity for the new context. Evidence: authorised scale gate. Owner: economic buyer.

Decision and handover

• The authorised forum records a disposition for every in-scope initiative and option. Evidence: executive decision rows. Owner: decision owner.
• Decision rationale links evidence, findings, alternatives, dependencies, opportunity cost, dissent and accepted exposure. Evidence: approved decision record. Owner: decision owner.
• Every funded action, dependency, measure, control and next gate has one accountable owner and date. Evidence: decision, measure and gate rows. Owner: delivery owner.
• Charters, evidence, definitions, maps, decisions, runbooks, controls and supplier conditions transfer to operating owners. Evidence: handover inventory and acceptance. Owner: operating owner.
• Temporary and provider access is closed, retained or reauthorised with purpose and date after handover. Evidence: access review. Owner: information authority.

Review, change and stop controls

• Operating, adoption, benefit, source, definition, access and guardrail controls have an accepted review cadence. Evidence: governance schedule. Owner: benefit owner.
• Material changes in purpose, population, workflow, data, technology or operating model trigger impact review and version control. Evidence: change record. Owner: operating owner.
• Exceptions, incidents, workload burden and guardrail breaches trigger owned containment and qualified review. Evidence: exception and incident records. Owner: control owner.
• Every review records continue, change, hold, stop or scale with rationale, owner and next date. Evidence: authorised review decision. Owner: decision owner.
• A changed strategic outcome or operating boundary returns to a new charter instead of inheriting old approval. Evidence: closure record and new charter ID. Owner: executive sponsor.

Topic-specific measurement contract

The organisation must establish and approve its own baselines, thresholds and tolerances. None below is a benchmark or promised target.

Measure A: Decision-grade transformation evidence coverage

Measure B: Controlled change-gate acceptance

Measure C: Accepted operating-change adoption

Measure D: Named strategy-to-outcome transition rate

Measure E: Material transformation guardrail breach

Evidence classifications used in this guide

For engagement evidence, separately classify observed fact, corroborated interpretation, single-source statement, assumption, evidence gap and constraint. A public claim status controls what may be said; it does not replace source, method, population and limitation.

Sources and proof boundaries

• OECD: Digital transformation: VERIFIED current institutional source at the source cut-off. It describes digital transformation as the effect and use of digital technologies and data across activities and emphasises coordinated, evidence-based approaches. This guide adapts that context to a private organisational decision method; the OECD material does not validate Abrasim's model or any client outcome.
• GOV.UK Service Manual: How the discovery phase works: VERIFIED official guidance at the source cut-off. It supports problem framing, user context, constraints, alternatives and a decision before build. Its UK public-service context must be adapted and is not a universal corporate prescription.
• GOV.UK Service Manual: Measuring the benefits of your service: VERIFIED official guidance at the source cut-off. It supports baseline establishment, benefit mapping, assumption testing and continuing measurement. Organisational finance and benefit owners must approve definitions and causal use here.
• Protection of Personal Information Act 4 of 2013: VERIFIED official South African statutory source. Application to a particular evidence, employee, customer, identity or access plan requires the organisation's information officer or qualified legal and privacy review.
• Abrasim eight-lens assessment, strategy-to-operating chain and thirteen-step sequence: PROPOSED Abrasim working methodology. They are decision structures, not external evidence of maturity, prevalence, assurance or outcome.

The Leadership Audit Working Pack remains the shared governance layer. The Transformation Assessment: An Executive Standard for Finding Why Strategy Is Not Becoming Operating Change files add transformation-specific portfolio, journey, workflow, operating-model, capability, dependency, benefit and operating-acceptance fields. Retain stable audit, decision, evidence, finding, option, measure and gate IDs; keep one material evidence item per evidence row; and store decisions, measures and dated gates as separate rows.