Drive Transformation and Change

1.0 Introduction

SPARA is more than a diagnostic – it’s a performance blueprint for change. Unlike traditional transformation approaches that start with new tools, org charts, or external methodologies, SPARA begins with what already exists: the hidden drivers of performance in every service organisation.

This chapter equips practitioners to use SPARA as a practical tool for initiating, governing, and sustaining transformation. It expands on how SPARA supports each phase of the change lifecycle, introduces artefacts to drive momentum, and provides guidance to avoid common failure patterns.

2.0 Why Levers Are Ideal for Transformation

SPARA is built around performance forces that are always active — even when they’re immature. This makes it an ideal model for transformation because:

  • It doesn’t disrupt unnecessarily: It builds from what already exists

  • It cuts across silos: Levers span technology, process, people, and governance

  • It is maturity-based: Change is about evolving, not replacing

  • It is context-aware: Levers can be prioritised and sequenced based on business need

Traditional frameworks ask, “What should we add?” SPARA asks, “What should we strengthen?”

3.0 SPARA in the Change Lifecycle

Each stage of the change lifecycle presents risks, blind spots, and opportunities. SPARA provides the structure to mitigate them and ensure alignment from beginning to end.

Vision & Case

Typical Pitfall: Business cases focus on vague value promises or cost cutting, not performance.

SPARA Fix:

  • Use lever maturity assessments to reveal gaps in outcomes (e.g., poor experience, high friction)

  • Anchor change around specific levers that map to strategic priorities

Tool to Use: SPARA Maturity Map, Strategic Outcome Traceability Matrix

Discovery

Typical Pitfall: Discovery is over-indexed on data, under-indexed on patterns of underperformance.

SPARA Fix:

  • Run workshops to self-assess lever maturity across business units or delivery chains

  • Visualise pain points across the four lever dimensions: internal, external, frameworks, governance

Tool to Use: Lever Heatmap, Ecosystem Friction Audit

Design

Typical Pitfall: Design gets stuck in operating model diagrams and roles, losing link to outcomes.

SPARA Fix:

  • Define the desired “Lever Mix”

  • Design a lever-aligned governance model to oversee performance post-launch

Tool to Use: Lever Mix Planner, Joint Lever Governance Map

Delivery

Typical Pitfall: Execution becomes a backlog of tasks detached from purpose.

SPARA Fix:

  • Structure backlog items and initiatives by lever

  • Monitor lever-specific maturity improvements as KPIs

Tool to Use: Lever-Driven Backlog Template, Value & Friction Forecast Canvas

Sustainment

Typical Pitfall: Momentum fades post-implementation. Old habits return.

SPARA Fix:

  • Use lever owners to maintain focus on outcomes

  • Embed lever maturity reviews into business-as-usual governance forums

Tool to Use: Lever Accountability Framework, Quarterly Maturity Reviews

SPARA brings structure to change. Not just a blueprint to start from, but a rhythm to govern by.

4.0 Lever-Based Change Planning Tools

Each tool is designed to anchor action in performance rather than just project activity.

  • SPARA Maturity Map: Visualises current vs target lever maturity

  • Strategic Outcome Traceability Matrix: Aligns change outcomes to specific lever goals

  • Lever-Driven Backlog Template: Structures the change roadmap around lever interventions

  • Value & Friction Forecast Canvas: Helps anticipate operational, cultural, or delivery challenges based on lever gaps

5.0 Portfolio Governance Using SPARA

Transformation is not a project – it’s a portfolio of outcomes. SPARA strengthens governance by:

  • Allowing PMOs and boards to review maturity improvement, not just delivery milestones

  • Prioritising investment based on lever gaps and business drivers

  • Creating lever owners who are accountable for sustained performance improvements

Portfolio governance becomes about performance enablement, not project traffic management.

 

6.0 Common Failure Patterns & How SPARA Prevents Them

“We have too many frameworks and no shared spine.”

Cause: Parallel adoption of ITIL, Agile, DevOps, and governance models with no integration. SPARA Fix: Levers act as a unifying layer across frameworks. Use the Framework Overlay dimension to create a common operational thread.

“The delivery is fast but unmeasured.”

Cause: Agile teams shipping features with no feedback loops, assurance, or outcome tracking. SPARA Fix: Embed Delivery & Assurance and Experience & Outcomes levers into planning and governance.

“Outcomes are unclear. Outputs are endless.”

Cause: Success is defined by what’s delivered, not what changes for the business. SPARA Fix: Anchor transformation goals to measurable lever maturity and value definitions.

“No one is owning performance.”

Cause: Responsibilities are defined by function, not value. SPARA Fix: Assign Lever Owners and use the Joint Governance Map to clarify strategic accountability.

7.0 SPARA 30-Day Quick Start Plan

Week 1: Socialise SPARA

  • Introduce the five levers in team workshops

  • Share the maturity model and how it applies to their work

Week 2: Baseline and Prioritise

  • Conduct a self-assessed Lever Maturity Map

  • Identify the 1–2 levers most impacting your current goals

Week 3: Target and Design

  • Run Lever Activation Mapping for the prioritised levers

  • Design quick-win interventions and assign lever leads

Week 4: Activate and Govern

  • Launch short-cycle improvements (e.g., governance changes, dashboards, flow redesign)

  • Schedule monthly Lever Reviews into governance forums

In 30 days, you won’t redesign your whole operating model — but you will start performing differently.

Username:
Password:
Remember Me