User Research
Interviews, observation and analytics that show how people actually work, and where the product gets in their way.
01 / Approach
Design for the people who use it every day.
Complex software doesn't have to be hard to use. We start by understanding the people who use the product and the work they need to get done. Then we structure the information, design the interactions and test them with real users before anything is built. Because we are an engineering company, our designs are made to be built, not just presented.
02 / What we build
Six capabilities, one design practice.
Information Architecture
Navigation, content and workflows organized around user tasks rather than internal structure.
Interaction & Interface Design
Screens and interactions designed for clarity, from wireframes to high-fidelity interfaces.
Prototyping & Usability Testing
Interactive prototypes tested with real users, so problems are found before development starts.
Design Systems
Reusable components, patterns and guidelines that keep large products consistent and faster to build.
Complex & Data-Heavy Interfaces
Dashboards, enterprise tools and AI-driven products, where clarity matters most.
03 / Capability matrix
The working detail.
| Capability | Typical question | Methods | Tooling | Deliverable |
|---|---|---|---|---|
| User Research | Why aren't users adopting this feature? | Interviews, contextual inquiry, analytics review | Interview guides, product analytics | Research findings and priorities |
| Information Architecture | Why can't users find what they need? | Card sorting, tree testing, user flow mapping | Figma, FigJam | Site map and user flows |
| Interface Design | What should this screen look like? | Wireframing, visual design, accessibility review | Figma | High-fidelity designs |
| Prototyping & Testing | Will this design work before we build it? | Interactive prototypes, moderated usability tests | Figma prototypes | Tested prototype and test report |
| Design Systems | Why does every screen look slightly different? | Component libraries, design tokens, documentation | Figma, Storybook | Design system and component library |
| Complex Interfaces | How do we make this data understandable? | Data visualization, progressive disclosure, workflow design | Figma, charting libraries | Dashboard and tool designs |
04 / Method
From research to release.
-
01
Understand
Research the users, their tasks and the context they work in.
-
02
Define
Turn findings into clear problems, priorities and success measures.
-
03
Design
Structure the information and design the interface, from wireframes to final screens.
-
04
Test
Validate designs with real users and refine them before development.
-
05
Deliver
Hand over specifications and components, and work alongside developers during the build.
05 / Principles
How we design.
The principles behind every screen we design.
-
Tasks before screens
We design around what users need to get done, not around features.
-
Evidence over opinion
Design decisions are backed by research and testing, not preference.
-
Accessible by default
Contrast, keyboard use and screen readers are considered from the first wireframe.
-
Consistency through systems
Shared components keep the product coherent as it grows.
-
Built to be built
Designs account for real data, edge cases and technical constraints.
-
Measured after launch
We check whether the design improved the outcome it was meant to improve.
Are users struggling with your product?
Show us where people get stuck. We'll help you find out why, and fix it.
Start a project →