Services you can engage us for
We work before development starts or alongside your team on an existing product.
UX audits & user testing
We review journeys and observe users completing tasks to identify confusion and errors.
Deliverables : Usability diagnosis and prioritised recommendations.
Journeys, mock-ups & prototypes
We design screen flows, interactions and states, then test a prototype before development.
Deliverables : Mock-ups, interactive prototype and test-based decisions.
Design systems & implementation support
We define reusable components and their rules, then review their implementation with developers.
Deliverables : Component library, specifications and acceptance feedback.
An approach tailored to your engagement
We agree the steps needed for your scope. An audit or assessment can be commissioned separately, without committing to implementation.
01. Select a task to improve
Observe the current journey and define how improvement will be judged. Deliverable: prioritised problems and a test scenario.
02. Prototype and test
Ask participants to complete a task, record hesitation and errors, then revise. Deliverable: annotated prototype and decision notes.
03. Support implementation
Check states and interactions in the working product. Deliverable: component specifications and visual and functional review findings.
Illustrative example, not a client engagement
Approving a pricing exception
Illustrative example: a manager must accept or reject a discount. The prototype shows current and proposed price, margin impact and justification before the actions. Testing observes whether the manager understands the consequences and finds the required information without explanation from the designer.
Before you start
Can you work with our developers?
Yes. Technical constraints are discussed during design; deliverables describe the behaviours and states needed for implementation.
What if users are rarely available?
Support feedback and journey reviews can provide a starting point. Assumptions remain labelled until they can be tested with users.
Do we need a complete design system?
Not necessarily. A few documented components may suffice initially. Scope grows with repeated use, team needs and delivery cadence.
What happens after delivery?
Design continues through usage feedback. Support can include recurring error analysis, journey improvements and shared component maintenance. A design system becomes useful when a team can govern changes and keep it consistent with implementation.
What determines the budget?
Role diversity, business states, participant availability and product maturity drive effort. Screen count alone often hides interaction and exception complexity.
Discuss your project
Identify the journey to improve first.
Describe a difficult task, the users involved and observed mistakes or workarounds. We can start from an existing product or an idea for a journey.