Digital Transformation
Transformation measured in shipped outcomes.
Advisory and delivery for organisations rebuilding how they operate — sequenced so value lands each quarter instead of at the end of a three-year programme.
25+
Programmes led
12 wks
To first outcome
31%
Avg. cycle-time cut
90%
Adoption at 6 months
Why programmes become theatre
Three failure modes that look like progress
A transformation programme can run for two years, hit every milestone, and change nothing measurable. These are the usual reasons.
Nothing is proven until the end
A three-year plan defers all evidence to year three. By the time the first outcome is testable, the market, the sponsor and the strategy have all moved.
- Milestones measure activity, not outcome
- No stop condition written down
- Sunk cost makes cancelling unthinkable
Consultants own the delivery
A programme staffed entirely by outsiders ends when they leave. The slide deck transfers; the capability does not.
- No named internal owner per workstream
- Decisions recorded in the supplier's systems
- Capability never transfers, so the next change needs the same spend
No baseline, so no verdict
Without measuring the current state first, 'it feels faster' is the only available conclusion — and it is the one everybody reports.
- Cycle time never measured before the change
- Benefits restated as forecasts, not results
- Failed initiatives quietly re-scoped instead of reported
Capabilities
Where transformation programmes get their value
Rarely from the strategy deck. Almost always from a handful of processes that were never designed, only accumulated.
Operating model design
How teams, decisions, and systems fit together — redesigned around the outcomes you are accountable for rather than the org chart you inherited.
- Value-stream mapping
- Decision-rights model
- Team topology design
Process automation
The queues, approvals, and re-keying that consume the working day. Automated where it is safe, simplified where automation would only make it faster to do the wrong thing.
- Process mining
- Workflow orchestration
- Exception handling design
Legacy modernisation
Incremental replacement of systems too critical to switch off, using strangler patterns that ship continuously rather than a single high-risk cutover.
- Strangler-fig migration
- Parallel-run validation
- Incremental cutover
Change & enablement
The half of transformation that determines whether the other half is used. Run in parallel with delivery, not bolted on before go-live.
- Stakeholder mapping
- Super-user network
- Adoption measurement
Delivery capability
Building your organisation's ability to keep shipping after we leave — engineering practice, product ownership, and the governance that supports both.
- Product operating model
- Engineering practice uplift
- Governance redesign
Benefits realisation
Baselined metrics, instrumented systems, and a quarterly review that reports what actually changed — including the initiatives that did not work.
- Baseline measurement
- Instrumented outcomes
- Quarterly benefit review
Programme anatomy
Four workstreams that have to move together
Run any one of these alone and it stalls. Process without technology is a memo; technology without change management is shelfware.
Operating model
Value-stream map
How work actually flows today, drawn from observation rather than the process manual.
Decision rights
Who decides what, at which threshold, without a committee.
Team topology
Teams organised around the outcome they own, not the systems they inherited.
Funding model
Money follows delivered benefit rather than annual plan adherence.
Process and automation
Process mining
Event logs from live systems showing the real path, including the rework loops.
Simplify before automating
Steps removed first, so automation does not just speed up the wrong thing.
Orchestration
Durable workflow engines handling approvals, retries and long-running state.
Exception design
The unhappy path designed deliberately, since it is where the cost actually sits.
Technology
Strangler-fig migration
Legacy replaced incrementally behind a stable interface, never in one cutover.
Parallel run
Old and new executed side by side with variance reported until it is boring.
Integration layer
Events and APIs that outlive whichever system is currently behind them.
Delivery practice
Trunk-based development and preview environments so change is cheap to reverse.
Change and evidence
Baseline measurement
Cycle time, error rate and cost per transaction captured before anything changes.
Super-user network
Practitioners trained early who carry the change into their own teams.
Instrumented outcomes
Benefit tracking built into the new process rather than reported by hand.
Quarterly review
Raw data to the sponsor, including the initiatives that missed.
Every workstream has a named owner from your organisation from week one. Our headcount is planned to taper across the programme, and that taper is in the contract rather than in a good intention.
Our approach
How we keep a programme from becoming theatre
Sequencing
Quarterly value, not a three-year promise
Long programmes fail because nothing is proven until the end. We sequence work so a measurable outcome lands every quarter, which also means the programme can be stopped at any point without having wasted the investment.
- A defined, measurable outcome for each quarter agreed in advance
- The riskiest assumption tested in the first eight weeks
- Funding reviewed against delivered benefit, not against plan adherence
- Explicit stop conditions written down before work starts
Ownership
Your people lead it, we supply the engine
Programmes run entirely by consultants end when the consultants leave. Every workstream has a named owner from your organisation, and our role is explicitly to make ourselves unnecessary.
- Named internal owner accountable for each workstream from week one
- Paired delivery so capability transfers as the work is done
- Our headcount planned to taper across the programme
- All artefacts, decisions, and code in your systems, not ours
Evidence
Measured against the baseline you started from
We insist on measuring the current state before changing anything, because it is the only way to say honestly whether the programme worked. That occasionally produces uncomfortable findings, which is the point.
- Cycle time, error rate, and cost per transaction baselined up front
- Instrumentation built into the new process, not bolted on later
- Quarterly benefits review presented to the sponsor with the raw data
- Initiatives that miss their target are reported, not quietly re-scoped
Sequencing
What a quarter of the programme commits you to
Each quarter has one measurable outcome and an explicit stop condition. You can end the programme at any gate having already banked the previous quarter's benefit.
| Quarter | Outcome committed | Evidence produced | Your commitment | Stop condition |
|---|---|---|---|---|
| Diagnostic4 weeks | Ranked list of where the operation loses time and money | Process mining output and baselined metrics | Access to systems and eight to ten interviews | Findings do not justify a programme |
| Quarter 1 | One end-to-end process rebuilt and live | Before-and-after measurement against the baseline | One named process owner, part-time squad | Target improvement not met and not explainable |
| Quarter 2 | Second and third processes on the proven pattern | Repeatability demonstrated without our lead | Internal squad leads delivery, we pair | Pattern does not transfer beyond the first team |
| Quarter 3+ | Scale across the remaining value streams | Benefit curve reported to the sponsor quarterly | Your delivery capability, our advisory only | Benefit plateaus below the business case |
| Exit | Governance and practice fully transferred | Capability assessment against agreed criteria | Ownership of all artefacts and decisions | By design — the programme ends here |
Diagnostic
4 weeks- Outcome committed
- Ranked list of where the operation loses time and money
- Evidence produced
- Process mining output and baselined metrics
- Your commitment
- Access to systems and eight to ten interviews
- Stop condition
- Findings do not justify a programme
Quarter 1
- Outcome committed
- One end-to-end process rebuilt and live
- Evidence produced
- Before-and-after measurement against the baseline
- Your commitment
- One named process owner, part-time squad
- Stop condition
- Target improvement not met and not explainable
Quarter 2
- Outcome committed
- Second and third processes on the proven pattern
- Evidence produced
- Repeatability demonstrated without our lead
- Your commitment
- Internal squad leads delivery, we pair
- Stop condition
- Pattern does not transfer beyond the first team
Quarter 3+
- Outcome committed
- Scale across the remaining value streams
- Evidence produced
- Benefit curve reported to the sponsor quarterly
- Your commitment
- Your delivery capability, our advisory only
- Stop condition
- Benefit plateaus below the business case
Exit
- Outcome committed
- Governance and practice fully transferred
- Evidence produced
- Capability assessment against agreed criteria
- Your commitment
- Ownership of all artefacts and decisions
- Stop condition
- By design — the programme ends here
Delivery
The shape of a transformation engagement
Short, evidence-led phases with a genuine decision point between each.
- 01
Weeks 1–4
Diagnostic
Process mining, systems inventory, and interviews across the operation. Output is a ranked list of what is costing you the most, with evidence.
- 02
Weeks 5–8
Target design
Operating model, technology direction, and a sequenced roadmap with a costed business case for the first two quarters only.
- 03
Quarter 1
Prove it once
One end-to-end process rebuilt and in production, with before-and-after measurement. This is the decision point for the rest of the programme.
- 04
Quarters 2+
Scale the pattern
Subsequent processes follow the proven pattern, with your teams increasingly leading and our involvement reducing each quarter.
- 05
Exit
Capability handover
Governance, delivery practice, and ownership fully transferred. We stay available, but the programme no longer depends on us.
What you get
Artefacts that stay with your organisation
Held in your systems, written for your teams, and usable by whoever picks the programme up next.
Diagnostic
- Value-stream maps drawn from observed work
- Process-mining output with rework loops quantified
- Baseline metrics: cycle time, error rate, cost per transaction
- Ranked opportunity list with evidence per item
Design
- Target operating model and decision-rights matrix
- Sequenced roadmap costed for two quarters only
- Technology direction with build-versus-buy reasoning
- Explicit stop conditions agreed with the sponsor
Delivery
- Rebuilt process live, with instrumentation in place
- Super-user network trained and operating
- Quarterly benefits review pack with raw data
- Capability handover assessed against agreed criteria
Toolchain
What we bring to the work
Method and tooling that stays with your organisation after the engagement closes.
Discovery
Process mining, value-stream mapping, and event storming run as workshops with the people who do the work.
Automation
Camunda, Temporal, Power Automate, and custom orchestration, chosen by the complexity of the process rather than by preference.
Delivery
The same engineering practice as our software work — trunk-based development, preview environments, and automated release trains.
Measurement
Product analytics and operational instrumentation wired into the new process so benefit tracking is automatic.
Engagement models
How the programme is bought
Never as one multi-year commitment. Each stage is priced and approved on the evidence the previous one produced.
Diagnostic
Fixed fee
Four weeks, quoted up front
Evidence about where your operation loses time and money, useful whether or not you continue.
- Process mining and value-stream mapping
- Baseline measurement across the target streams
- Ranked opportunities with cost attached
- No obligation to proceed
Prove it once
Quarterly
One quarter, one outcome
A single end-to-end process rebuilt and measured. This is the real decision point for the programme.
- One process live in production
- Before-and-after measurement published
- Pattern documented for reuse
- Stop or scale decided on the numbers
Scale and transfer
Programme
Quarterly gates, tapering headcount
The proven pattern applied across the operation while delivery capability moves to your teams.
- Quarterly outcomes with funding reviewed against benefit
- Our headcount reducing on a contracted taper
- Governance and practice uplift in parallel
- Defined exit with a capability assessment
Questions
Fair questions about a word that has been overused
'Digital transformation' has been sold badly for a decade. These are the objections we think are correct.
Credibility
How is this different from every transformation deck we have been sold?
Three structural differences: we measure the baseline before changing anything, we commit to a measurable outcome each quarter rather than at the end, and we write the stop conditions down before starting. The last one is the real test — if a supplier cannot tell you what result would make them recommend cancelling, the programme has no way to fail and therefore no way to succeed.
What if the diagnostic says we do not need a programme?
Then we say so and you keep the findings. It happens, most often where the real constraint is a single system or a single team rather than the operating model. A four-week diagnostic that saves a two-year programme is the best value we can offer, even though it is the smallest invoice.
Do you report initiatives that fail?
Yes, in the quarterly review, with the raw data. Quietly re-scoping a missed target is how programmes lose sponsor trust, and it removes the only mechanism you have for learning which changes actually work in your organisation.
Running it
How much of our people's time does this take?
Meaningful amounts, deliberately. Each workstream needs a named internal owner with real authority, and the first quarter needs a part-time squad from the affected team. A programme your people can ignore is a programme that will not change how they work.
Can you work alongside our existing suppliers?
Routinely. We are usually one of several parties, and the operating-model work often involves clarifying who is accountable for what across them. We do not require exclusivity and we do not need to own the systems integration to be useful.
What happens to the roadmap when priorities change?
It changes, which is why we only cost two quarters at a time. A three-year roadmap survives contact with the business for about one quarter, and pretending otherwise just means the plan and the work diverge silently.
Start with a diagnostic, not a roadmap.
Four weeks of evidence about where your operation actually loses time and money — useful whether or not you engage us to fix it.