Case Studies
Cog & Flow in Practice
Real systems. Real friction. Practical change.
Every system has its own context, constraints and people. These examples show how Cog & Flow thinking has been applied to different operational challenges — from small repeated friction to wider workflow redesign.
The starting point may be technology, accessibility, growth, delegation or a recurring operational problem. The work begins by understanding what is really happening and what the system needs to support.
Cog & Flow Architecture™ in practice
Existing systems. Observed in practice. Redesigned around what the evidence reveals.
Architecture case studies show what happens when an existing system can be observed in use and the gap between intended and lived operation becomes visible.
The Hidden Cost of 1 Second
Eliminating friction in clinical notes selection.
What triggered the review
A designed implementation project needed a conduit between the project team and the clinical team — someone who understood both workflows and could recognise where they did not align.
What we found
A small system choice required staff to manually switch note types during every interaction. Individually it was trivial; at volume it repeatedly interrupted flow, attention and task rhythm.
What changed
The workflow requirement was translated back to the system team and the default setting was corrected.
What the evidence showed
around 1 second removed from each iteration;
approximately 300 iterations per person per week;
across a six-person team;
an estimated 3–4 working days of capacity recovered annually.
From Fragmented Motion to Designed Flow
A practical redesign of setup, replenishment and end-of-day reset flow.
What triggered the review
A need to put reasonable adjustments in place for a disabled colleague prompted a closer look at how the work was being carried out.
What we found
The existing process relied on fragmented movement, repeated journeys and reactive replenishment. Rather than design a workaround for one colleague, the system itself was redesigned for everyone completing the work.
What changed
Start-of-day setup was batched, rapid top-up buffers were introduced, and end-of-day equipment clearing was separated from consumables restocking.
What the evidence showed
setup time reduced from 60 to 30 minutes;
end-of-day work reduced from 60–90 minutes to 45 minutes or less;
motion waste removed at source;
a more sustainable workflow for colleagues, with improved support for customer service.
What the case studies demonstrate
The scale of the problem is not always the scale of the opportunity.
Small friction can have system-wide cost
A second is insignificant once. Repeated hundreds of times, across several people, it becomes capacity.
Accessibility can expose a wider design problem
Designing around one person's difficulty may create a workaround. Redesigning the system can improve the work for everyone.
Delegation requires decision logic, not just task lists
Work is not genuinely delegated if routine exceptions still depend on the founder making decisions that have never been made explicit.
Improvement starts with operating reality
The useful question is not only how the process is supposed to work, but how people actually experience and operate it.
A closer look
Different triggers. The same systems lens.
The reason for looking is not always the problem we find.
System reviews often begin with a visible need: a technology change, an accessibility requirement, growth, delegation or recurring operational friction.
Cog & Flow looks beyond the presenting issue to understand what the wider system is asking people to compensate for.
Friction
Where is work harder than it needs to be?
Where is friction hiding in your system?
You do not need to know the cause before getting in touch.
If work is repeatedly slower, harder or more dependent on individuals than it should be, tell me what you are seeing. We can explore whether Cog & Flow is the right way to understand it.
tell me what you need