Business Orchestration & Operating Model Transformation
How I approached fragmented workflows as an operating model problem, connecting process, accountability, governance and technology around the way work needed to move.
I Did Not See This as an Automation Problem
Work depended on people moving between systems, translating requests, coordinating handoffs and determining what needed to happen next. Individual activities could be completed, but the end to end journey remained fragmented.
It would have been possible to approach this as a technology problem and automate individual steps. My concern was that this could preserve the underlying fragmentation while simply making parts of it faster.
It was, “How should this work operate before we decide where technology belongs?”
Four Things Changed How I Framed the Problem
The Handoffs Were Symptoms
Manual coordination was visible, but removing individual handoffs would not necessarily solve the underlying problem. I needed to understand why those handoffs existed and what responsibility, decision or system boundary each one represented.
User Intent and System Activity Were Different Things
What a person wanted to achieve was often much simpler than the sequence of activities required across systems. Separating the intended outcome from the current execution path created room to rethink the process rather than reproduce it.
Accountability Could Not Disappear Into Automation
Some activities were suitable for automated execution. Others involved approval, exceptions, material risk or judgement. I treated that distinction as an operating model decision rather than simply a technical capability question.
Governance Needed to Move With the Work
If controls, evidence and approvals remained separate from the workflow, the redesigned process would still depend on parallel governance activity. I therefore considered control points as part of the operating process itself.
The Decisions That Shaped My Approach
My approach drew on programme governance, process design, technology delivery and quality assurance. I was looking for a model that could work operationally, remain controlled and still be implemented through technology.
Start With the Outcome
I centred the design on what the user was trying to achieve rather than treating the existing systems and process steps as fixed constraints.
Redesign Before Automating
I separated necessary work from activity that existed because of historical processes, system boundaries or manual coordination. Automation would support the redesigned journey rather than reproduce the old one.
Make Ownership Explicit
I considered who owned initiation, execution, approval, exceptions and outcomes so that greater automation did not create less accountability.
Define Decision Rights
I distinguished activities that could progress within predefined authority from decisions requiring explicit review or approval.
Build Controls Into the Journey
Permissions, evidence, approval and traceability were considered within the execution path so governance did not become a separate administrative layer around the process.
Design for Exceptions, Not Only the Happy Path
A workable operating model needed to account for uncertainty, failed actions, unusual requests and situations requiring human intervention rather than assuming every transaction would progress normally.
Four Parts of My Background Came Together
The operating model was shaped by more than process design. Different parts of my delivery background influenced what I looked for and the questions I asked.
Programme Governance
Who owns the decision, what authority applies, what needs escalation and how does accountability remain visible?
Process & Operations
How does work actually move, where does friction occur and which activities genuinely contribute to the outcome?
Technology Delivery
Where can systems remove friction, coordinate execution and support the redesigned process without dictating it?
Quality & Assurance
What could fail, how would we know, what evidence should exist and where does human validation remain necessary?
Maintaining a Line of Sight From Intent to Evidence
I wanted the operating model to preserve the relationship between what someone intended to happen, who was accountable and what actually occurred.
Intent
What outcome is required?
Workflow
What needs to happen?
Ownership
Who is accountable?
Decision
What authority or judgement applies?
Execution
What should technology or people do?
Evidence
Can we show what happened and why?
Four Questions I Kept Returning To
Does This Activity Need to Exist?
Challenge whether each step contributes to the outcome or simply reflects the way the process historically operated.
Who Remains Accountable?
Ensure ownership remains explicit even when technology performs more of the underlying execution.
Where Is Human Judgement Necessary?
Preserve review and approval where risk, exceptions or consequential decisions require accountable judgement.
Can We Evidence What Happened?
Maintain traceability between request, decision, execution and outcome so greater automation does not reduce assurance.
I start by understanding how the work should operate, who should own it, where decisions belong and what controls are required. Technology can then remove friction from a model that has already been deliberately designed.
What My Contribution Helped Establish
Transformation Risk
Capability Established
What This Case Study Demonstrates
Operating Model Thinking
Looking beyond individual processes to understand how people, decisions, controls and technology work together.
Process Transformation
Challenging existing workflows and redesigning work around the required business outcome.
Governance & Decision Rights
Defining ownership, authority, approvals and accountability within the operating process.
Technology Translation
Connecting business intent to technology enabled execution without allowing technology to dictate the operating model.
Quality & Assurance
Considering exceptions, evidence, traceability and validation as part of the design rather than after implementation.
Transformation Judgement
Balancing efficiency, automation, control and human accountability rather than optimising any one dimension in isolation.
Explore More of My Transformation Work
Return to my portfolio to view selected work across AI transformation, enterprise technology, programme governance and operating model transformation.
Back to Portfolio →