Insight
Technology won’t save a broken process.
But a sound one changes everything.
Whether it’s a Salesforce rollout, an AI initiative, or a broader transformation programme — the same failure patterns keep appearing. The root cause is almost always the same, and it has nothing to do with the tools.
Over the past decade, the speed of delivery has changed dramatically. Salesforce implementations that once took eighteen months now go live in a fraction of the time. AI capabilities can be stood up in weeks. Low-code platforms have removed barriers that previously required entire development teams.
This is genuinely valuable. It is also, for many organisations, a trap.
When you can move faster, the temptation is to move before you are ready. Teams skip the foundational work. The assumption is that modern tools will compensate for gaps in understanding. In practice, the opposite happens. Technology amplifies what is already there — including misalignment, inefficiencies, and structural complexity.
« Solutions get delivered quickly, then struggle to scale, adapt, or gain adoption. The technology works. The process underneath it doesn’t. »
The discipline that determines whether transformation programmes succeed or stall has not changed. It is not the latest AI capability, a Salesforce implementation, or any other platform investment. It is business process design — and most organisations are still treating it as an afterthought.
Process as a strategic lever, not a prerequisite
In most transformation programmes today, process work is treated as a gate to get through before delivery begins. Map it, sign it off, move on.
The organisations that consistently execute well take a fundamentally different view. They treat process design as a core enabler of delivery — not a precursor to it. When processes are clearly defined, grounded in reality, and aligned with how decisions are actually made, they act as a multiplier across everything else:
Delivery accelerates. Alignment improves. Systems are easier to design and maintain. Adoption increases.
When they are not, organisations compensate with additional layers of tooling, governance, and rework. The cost compounds.
Four dimensions that determine whether processes enable — or constrain
01 — Clarity
Establish a shared understanding
The first challenge is rarely the absence of a process — it is the absence of a shared version of one. Different stakeholders describe the same process in different ways. Key steps are assumed rather than defined. Ownership is unclear. Dependencies are only partially understood.
Formalising the process creates a baseline that enables teams to align not only on what should happen, but on how work flows across systems and roles. It is not about producing perfect documentation. It is about closing the gap between what people think happens and what actually does.
Map the process end-to-end — triggers, actions, decision points, systems, and outputs. Prioritise alignment over perfection.
02 — Reality
Validate against actual execution
Mapped processes typically reflect intent, not execution. In practice, work is shaped by constraints, workarounds, and informal adaptations that rarely appear in workshops or documentation.
This creates a gap between the designed process and operational reality — and it is in that gap where the most significant risks and inefficiencies live. Organisations that invest time in understanding how processes are actually executed consistently uncover insights that are otherwise invisible.
Observe real cases moving through the process. Compare expected steps with actual behaviour. Identify gaps and quantify their impact.
03 — Simplicity
Eliminate structural complexity
Complexity in processes accumulates gradually. Exceptions are bolted on, approvals multiply, and variations emerge across teams and regions. Over time, this produces processes that are difficult to explain, costly to run, and nearly impossible to automate cleanly.
Technology is often introduced to manage this complexity. More often than not, it reinforces it instead. Simplification is not about reducing capability — it is about restoring the clarity that makes capability possible.
Review each step critically. Is it necessary? Can it be streamlined? Does it contribute meaningfully to the process objective? If not, remove it.
04 — Decisions
Reconnect process to outcome
This is the most consistently overlooked dimension. Processes are frequently designed to capture information or move tasks forward. Far less attention is paid to how they support the decisions that actually drive business outcomes.
A process that does not serve a decision is structural theatre. A well-designed process reduces uncertainty, enabling individuals and teams to make consistent, informed decisions at the right moment — not after the fact.
For each step, identify the decision it supports. If that link is unclear, the step should be challenged.
What changes when the foundation is right
When all four dimensions are addressed together, the shift is measurable — and felt across the organisation, not just in the programme team.
Conversely, when one or more dimensions are missing, organisations encounter friction that no technology investment can fully resolve. The tools become more complex. The governance heavier. The rework more expensive.
Four questions to run against any critical process today
Before commissioning a full diagnostic, a straightforward self-assessment can reveal where the greatest opportunities — and risks — sit. Select one critical process and work through these:
The four-question test
- Is this process clearly mapped and genuinely understood by everyone involved — or does each team have a slightly different version?
- Has it been validated against how work is actually executed, not just how it was designed?
- Is it simple enough to explain in under two minutes — and easy enough that people follow it without workarounds?
- Does each step in the process clearly support a decision? If you removed it, would an outcome suffer?
Gaps in any of these areas are worth addressing before the next technology cycle begins — not after it.
Let’s look at what your processes are actually doing.
Whether you are navigating a live transformation or preparing for one, we can help you sense-check your process foundations, identify hidden complexity, and ensure your teams are aligned on what matters.
