Operational design
Operational flow: Rebuilding trust in a flow that wasn't meeting user needs
The flow had already failed multiple times. Users were sceptical, and previous fixes had not stuck.
Context
Written at a high level due to NDA restrictions. Late on a Friday evening, the senior head of product asked me to take over an operational flow that had become a persistent source of frustration. A third-party team had designed the original version, but the design had not been validated as it evolved and several internal attempts to fix it had failed. The users I inherited were frustrated, sceptical, and felt they had been repeatedly told that compromises were unavoidable.
Challenge
The flow had already failed multiple times. Users had been involved in earlier attempts but still felt unheard. The challenge was not just fixing the design. It was rebuilding enough trust that users would engage honestly and tell us what was actually wrong.
Approach
I spent time with users to understand the real sequence of actions, the workarounds, and where the system slowed them down. In parallel, I worked with engineering to understand what was technically possible, challenging frequently when told something could not be done, and often finding it could. To break looping conversations, I brought users directly into working sessions and set a clear principle: nothing moved forward unless users confirmed it genuinely helped. They had been consulted before. What they had not experienced was someone making their perspective consistently visible and impossible to dismiss.
Below are three examples of structural problems in the flow that were identified and reshaped:
Outcome
The revised flow reduced unnecessary steps, clarified terminology, and aligned more closely with real operational needs. Trust improved as users saw their feedback acted on. One client service lead described the work as leaps and bounds ahead of the existing flow, noting it provided much clearer guidance for both internal and external users.
Reflection
Trust came from designing with users, not for them. Not every idea worked, but they could see their input shaping the outcome in real time.
Selected working artefacts from the project. Blurred intentionally to protect business context, shown to demonstrate the depth and shape of the work, not as polished deliverables.