One working week per sprint.
Four sprints, and something you can look at at the end of each one.
Every engagement runs the same nine steps. What changes is how deep each one goes, not whether it happens, the research still happens on a two-week job, it just takes an afternoon.
Shape of an engagement
How long it takes
Sprints 1 to 3, about three weeks from kickoff to a prototype tested with real users.
Sprint 4: the interface, the component system, and a handover engineering can build from.
Smaller pieces of work run shorter. A UX audit is a single sprint; fractional design runs continuously rather than in a fixed number of them.
Sprints 1 to 3, problem to validated prototype
Sprint 1
Align on the outcome
We agree on the goal, the users, the constraints, and how we'll know it worked.
You get A one-page brief: the goal, the users, the constraints, and the measure we will judge it by.
Understand the problem
Research, analytics and competitor teardowns to find the problem worth solving first.
You get Research notes, a read of your analytics, and a competitor teardown, ending in the one problem worth solving first.
Sprint 2
Map the experience
Journeys, flows and structure decided before anyone opens a UI file.
You get User journeys, task flows and the information architecture, agreed before any UI exists.
Explore the solution
Focused directions, weighed against user needs, engineering effort and speed to market.
You get Two or three directions, each weighed against user need, engineering effort and speed to market.
Sprint 3
Wireframe key flows
Low-fidelity screens surface the hard decisions while changes are still cheap.
You get Low-fidelity screens for the key flows, in Figma, with the hard decisions surfaced while they are still cheap to change.
Prototype and validate
Clickable prototypes tested with real users before engineering writes a line.
You get A clickable prototype, tested with real users, and a written read of what the testing changed.
Then the product moves from screens to a system.
Sprint 4, screens to a system
Sprint 4
Design the interface
High-fidelity, accessible UI with every real state covered: empty, loading, error, edge.
You get High-fidelity screens with every real state drawn: empty, loading, error, permission-denied and too-much-data.
Build the system
Reusable components and tokens, so the next feature ships faster than this one.
You get A component library with design tokens and usage notes, built so the next feature ships faster than this one.
Handoff and support
Dev-ready specs, plus me in the loop through build and design QA.
You get Dev-ready specs and assets, plus me in the loop through build and design QA.
Working together
Karachi (PKT, UTC+5), I overlap with European mornings and US mornings.
Usually replies within one business day.
