Processes describe how work moves through the organisation to realise defined capabilities. They include sequencing, decision points, approvals, handoffs, exception handling and feedback loops.
If capabilities describe what must be achieved, processes describe how it is achieved in practice.
In a £5–100m SME, core processes often include:
Processes exist regardless of system configuration. Systems implement them. They do not define them.
When processes are designed intentionally around capability outcomes, work flows predictably. When processes evolve reactively around tool constraints or historical habit, complexity accumulates silently.
Processes are not:
A CRM workflow is not a process. It is a system-level implementation of part of a process.
A finance SOP document is not the full process. It describes a slice of it.
An automation flow is not a process. It accelerates one.
Confusing platform workflow with enterprise process leads to structural fragility. When the system changes, the organisation struggles to articulate how work should flow independently of it.
Consider a £60m distribution business experiencing margin compression. Leadership observes late shipments, frequent credit notes and increasing customer complaints.
A proposal emerges to implement a new warehouse management system.
Before committing, the organisation maps its end-to-end Order-to-Cash process. It becomes clear that order validation rules differ between sales teams. Credit approval thresholds are inconsistently applied. Inventory allocation decisions occur manually in email threads. Finance reconciliation is triggered only after dispatch discrepancies surface.
The issue is not warehouse software.
It is process fragmentation.
By redesigning the Order-to-Cash process deliberately — clarifying decision gates, ownership and exception handling — the organisation reduces shipment errors and invoice corrections without immediate system replacement.
The economic consequence of skipping process clarity would have been significant capital expenditure layered on unstable flow.
In scaling SMEs, process drift typically occurs when:
Symptoms often include:
These symptoms compound gradually. Each workaround appears reasonable. Over time, the process becomes opaque.
Unclear or unstable processes generate measurable cost:
Leadership impact is equally material. Executives lose confidence in forecast accuracy. Cross-functional tension increases. Technology teams are blamed for structural issues rooted in process design.
Process clarity restores predictability.
Predictability reduces cost volatility and improves investor confidence.
Processes sit directly beneath capabilities and influence every other pillar.
Capabilities define desired outcomes; processes operationalise them.
Data is created, consumed and transformed through processes. Poorly designed processes generate inconsistent data.
Applications implement process steps. When processes are unclear, systems inherit ambiguity.
Integrations connect process stages across domains. Fragmented processes create brittle integration logic.
Automation accelerates process execution. If process design is flawed, automation institutionalises inefficiency.
Controls embed assurance within process flow. When controls are bolted on rather than designed in, friction increases.
Processes are therefore the connective discipline between strategic intent and operational execution.
Processes are active throughout the lifecycle, but their emphasis shifts.
Sensemaking
Current-state process mapping exposes fragmentation, duplication and hidden labour. This is often the first point at which leadership sees structural reality.
Design
Target process design aligns to defined capabilities. System selection is evaluated based on ability to implement intended flow rather than enforce vendor defaults.
Execution
Delivery teams implement systems and integrations that support redesigned processes. Exception handling and decision points are formalised.
Institutionalisation
Process ownership becomes explicit. Metrics align to flow performance rather than silo activity.
Stewardship
Process reviews prevent drift as new products, regulations or acquisitions introduce change.
Skipping disciplined process design in early phases increases correction cost later.
For structural context across all domains, see:
Processes are most tightly coupled with:
Controls → /frameworks/seven-pillars/controls/
Redesigning processes without considering these domains introduces secondary instability.