Note 1
From findings to flows
Findings are written as problems with evidence attached, then prioritised with you. We map the journeys that address the top problems, including what happens when things go wrong, before designing screens.
Discovery & UI/UX
How do we find out what people actually need?
Short answer
By asking well, watching carefully and testing cheaply. Discovery turns assumptions into evidence, and our UI/UX work turns that evidence into interfaces people understand.
Method finder
What are you trying to learn, and how much time do you have? We will show the research methods that suit.
Interviews
Five to eight conversations with a discussion guide. Reveals motivations, workarounds and language people use.
Diary study
Participants record experiences over days or weeks. Captures behaviour that interviews miss.
Existing data review
Support requests, analytics you already hold, sales notes. Often the fastest evidence available.
Contextual observation
Watching work happen where it really happens, with permission.
Prototype test
People attempt tasks with a clickable prototype while thinking aloud.
First-click test
Where would you click to do this? A quick check on navigation and labels.
Survey
Useful once you know what to ask. Poor at discovering things you did not expect.
Event analysis
Looking at how many people reach each step of a journey, using data collected lawfully.
Note 2
Interfaces that show their reasoning
Where products present data, we design so people can see where numbers come from, what time period they cover and what to do next. Charts are used only when they answer a real question better than a sentence would.
Note 3
What you receive
- Research plan and discussion guides
- Findings report with evidence and confidence levels
- Prioritised problem list
- Journey maps and wireframes
- Tested prototype and interface designs
- Component library with accessibility notes