Home/What we do/Systems & operations
How work movesProcess & System Design
Disconnected processes and overlapping tools, made into a way of working that people can actually follow.
Overview
Operations rarely fail in one place. They fail at the joins: handoffs that lose context, systems that disagree on status, work that survives in spreadsheets because the official path is slower.
This work makes the current path visible, names the few constraints that create most of the strain, and redesigns the way of working so people can follow it without a second unofficial process.
Four stages before a path is treated as settled.
Each stage leaves an artefact you can challenge. Nothing is carried forward on confidence alone.
- 01
Understand
Study the work, the systems, the people, and the constraints as they are.
- 02
Define
Name the actual problem. Write the non-goals.
- 03
Explore
Hold more than one credible path long enough to compare them.
- 04
Structure
Turn the choice into architecture, owners, and sequence.
Inside systems & operations.
Work mapping
See how a request actually moves through the organisation.
Break-point finding
Locate delay, rework, and silent workarounds.
System landscape
Name what is connected, duplicated, or ignored.
Operating design
Redesign the path, not only the interface.
Role clarity
Make ownership visible where it has drifted.
Change load
Pace the change so operations can absorb it.
The terms of the work.
A working note.
The kind of thing this work produces — inspectable, arguable, and short enough to be read.
OFFICIAL Request → Team A → System 1 → Team B ACTUAL Request → Team A → spreadsheet → Team B → System 1 (later) LOSS Owner, exception reason, customer promise. DESIGN One status. One owner at the join. Spreadsheet retired after the join is live.
When this usually appears
- Handoffs that lose context
- Tools that do not talk to each other
- Work that lives in inboxes
- Operations that grew faster than design
Systems & operations, asked directly.
Frequently asked questions
Do you replace our systems?
Only if the situation requires it. Often the work is to make the existing landscape coherent.
Will staff have to change how they work?
If the current path is the problem, yes — but the new path has to be easier than the workaround.
Adjacent work.
Bring the situation as it is.
You do not need a polished brief to start. A conversation is usually enough to name the problem and decide whether there is work here at all.