01
Which task needs fixing first
We focus research and prototypes on a real user goal rather than redesigning every screen at once.
Service 03 · Product design & UX
Make complex software easier to use.
Research, interaction design and visual systems for products people need to understand quickly and use every day.
- 01 · A sensible first step
- Walk through one important task with the people closest to it.
- 02 · Typical scope
- Product flows, prototypes, interface systems and design review.
- 03 · Works well with
- A product team ready to test assumptions and explain business rules.
When this is
the right fit.
Users struggle to complete a task, a product has grown inconsistent, or a new idea needs testing before development. The useful question is where people get stuck and what they need to do next.
We turn business rules and technical constraints into clear journeys. Designers cover the main path as well as permissions, validation, empty states and failure cases. Engineers join early enough to challenge assumptions, estimate the work and carry the design decisions into production.
How we can help
- 01User journeys and information architecture
- 02Wireframes and interactive prototypes
- 03Web and mobile interface design
- 04Reusable design systems and component rules
- 05Accessibility and usability reviews
Three steps
to a working start.
- Step 01
Map the task and context
Review the people using the product and the tasks they need to complete.
- Step 02
Test the difficult decisions
Prototype the important journeys and collect feedback on the decisions.
- Step 03
Support the production build
Document components and behaviour, then review the implementation together.
Tools chosen for the job.
Figma is used for collaborative design and prototypes. Component rules, accessibility considerations and implementation notes help carry the design into the application.
Tools & approaches
The details that keep
delivery grounded.
Clear answers here prevent avoidable rework later.
02
What every state should say
Permissions, validation, empty states and errors are designed with the main journey.
03
How design reaches production
Components, responsive behaviour and implementation notes are reviewed with engineers.
The work in practiceFrom the brief
From the brief
to the handover.
We map the journey, test the important decisions in a prototype and work through the details with engineers. Empty states, validation, permissions and error handling belong in the design alongside the main screens.
What you take away
- User journeys and information architecture
- An interactive prototype and reusable interface components
- Implementation notes covering states and behaviour
06
EducationA private network for alumni.
A private network for institutions, alumni and business partners.
- Mobile app
- Community platform
- Messaging
Let’s discuss the details
Discuss your product design.
Tell us about your current setup, the work ahead and any deadlines you need us to consider.