Complex Workflow Design · Five weeks
Complex workflows,designed to be built
You know the problem. We take one core workflow from a flow map to a clickable prototype and a handover your engineers can build from, using your brand and design system.
- The scope
- One workflow, one role8–12 screens with every state
- The timing
- Five weeksTwo review rounds built in
- The handover
- Prototype + notesAnd a live session with your engineers
When it helps
When a workflow needsa clear design
- A feature that started simple has grown into something users struggle with.
- Designs only show the happy path, so engineers guess the empty, error, loading and permission states.
- Stakeholders go round in circles because there’s nothing concrete to react to.
- Engineering is ready to build but waiting on design.
Typical workflows: onboarding, applications and approvals, setup and configuration, dashboards, and team roles and permissions.
What you’ll have at the end
One agreed flow,designed in full
What happens, in what order and why, with Figma screens for the whole journey, including the states people forget.
- 01
A workflow map
Steps, decisions, roles and priorities, agreed with your team before any screens are designed.
- 02
Figma designs
8–12 screens for one core workflow and one user role, including loading, empty, error and permission states.
- 03
A clickable prototype
The chosen approach, ready to put in front of users or stakeholders.
- 04
Reusable components
New components, or extensions to your design system, that the journey needs.
- 05
An engineering handover
Implementation notes and a live handover session, so your engineers can build without guessing.
How it works
Five weeks, withtwo review rounds
One person on your side gathers and combines feedback at each review, so decisions land quickly.
- Week 1
Map
We align on the task, users and constraints, map the flow and explore structural options. Review round one.
- Weeks 2–3
Design
We turn the chosen direction into full screens and states, using your brand and design system. Review round two.
- Weeks 4–5
Prototype and handover
A clickable prototype, implementation notes and a handover session with your engineers.
Is it the right fit?
Designed for onecore workflow
We build designs up from core patterns into each journey, so stakeholders can follow the reasoning and there are fewer questions at the end.
Good fit if
You understand the problem and the users and need it designed. You have a brand, and ideally a design system, to work within. One person on your side can gather and combine feedback.
Not a fit if
You’re not sure what’s wrong yet; start with a UX Audit. You need production code, a full rebrand or several unrelated workflows at once.
User testing
The prototype is ready for testing with users. Recruiting participants and running sessions can be added to the scope; ask us when we first talk.
Experience behind the work
Experience with complex,regulated workflows
Led by Marian Cozma, who started as a front-end engineer, so the designs account for how they will be built.
Financial services / Complex workflows
Prioritising supervisory alerts for a global investment bank
Personal and team views, grouped actions and clearer review paths, tested with users before delivery.
Read the case studyEnterprise technology / Systems & delivery
Specifying an event platform for a global technology company
Configurable authoring and consent-aware guest management, specified state by state for engineering.
Read the case studyGetting started
Tell us aboutthe workflow
Tell us what the workflow needs to do, who uses it and when engineering wants to start building.
Discuss your workflowScope, deliverables and start date agreed in writing before we begin.
What we need from you
- A product contact who can make decisions.
- Existing research and design files.
- Engineering constraints and your brand guidelines or design system.
- One person who gathers and combines feedback.
What if we don’t have a design system?
We’ll design the components the workflow needs in a way your team can grow into a system later, and document them as part of the handover.
How many revisions are included?
Two structured review rounds: one after the flow map and one after the first full design. Feedback is gathered by one person on your side, so each round moves the work forward.
Do you write production code?
Not as part of this service. We specify behaviour in enough detail for your engineers to build it, and we can review the build against the design if you’d like.
More than one workflow or user role?
We’ll scope it as a separate or extended engagement, so each workflow gets proper attention.