UI Design & Prototyping
Turn user needs into clear interfaces, explore ideas through prototypes and test important decisions before development.
Support Capabilities
UI Design & Prototyping research that informs clearer decisions.
Research identifies the problems worth addressing. Interface design and prototyping help your team explore how to respond. We connect agreed findings to screen flows, content and interactions, then evaluate selected proposals with intended users where testing is included.
What we look at
Clarity of key screens and flows- Interaction affordances and feedback
- Visual hierarchy and content scanability
- Prototype fidelity matched to the question
How we study it
- Flow and interface design
- Low- to high-fidelity prototyping
- Prototype usability testing
- Iteration cycles with research feedback
When to research
When this support helps
Use this work when turning research findings into a proposed flow, evaluating a new feature or improving an existing interface. It can also help your team compare approaches before committing to detailed design or development.
A small team may need one focused flow. A larger organization may need several connected journeys, roles or platforms. We agree the screens, states and decisions in scope before work begins.
Research focus
Design around the task
We consider what users need to achieve, which information they need and how they move between steps. Scope can include navigation, forms, labels, feedback, error recovery and relevant empty or loading states.
We work with available brand guidance, design systems and technical constraints. Existing patterns are considered before proposing new ones. A visually consistent interface still needs to support understandable tasks and appropriate user control.
Our approach
Research grounded in evidence
We choose methods according to the decision your team needs to make, the people involved and the context of use.
Findings are linked to observations and participant accounts, with coverage and limits kept visible.
From context to opportunity
Our research process
Review the research. Identify supported needs and assumptions that require further investigation
Develop proposals. Create agreed flows and interface options with relevant states and content
Prototype priority tasks. Build suitable interactions for the questions being tested
Evaluate and refine. Where included, test with intended users and revise selected issues using the findings
Prepare the handover. Document the agreed design, behaviors, open questions and implementation considerations
The output
What your team receives
Depending on scope, deliverables can include task flows, wireframes, interface designs, an interactive prototype and annotated behavior notes. Where research is included, outputs can also include usability findings and a record of refinements.
The handover explains relevant states, content and interaction decisions, alongside dependencies and unresolved questions. File formats, access and delivery arrangements are agreed before work starts. A prototype alone is not a complete engineering specification.
Research focus
Choose the right prototype detail
Simple wireframes can explore structure and step order. More detailed visual or interactive prototypes can examine content, controls and selected behaviors. We choose the level of detail according to the question, not assume every idea needs a highly polished prototype.
A prototype may simulate data, integrations or outcomes. These limits are documented. It is not production software and does not demonstrate performance, reliability or security unless those capabilities are separately built and assessed.
Research focus
Testing and revisions with clear scope
Usability testing observes how intended participants interpret the prototype and complete agreed tasks. Findings distinguish observed difficulties, participant opinions and researcher interpretation. Stakeholder approval is not a substitute for user evidence.
We agree recruitment, test coverage, review milestones and revision rounds in the proposal. Additional flows or changes in direction may require a scope adjustment. We make untested states and remaining assumptions visible rather than label the whole design validated.
Research focus
Work alongside your team
We can use research from your team or another provider after reviewing its relevance and limits. Product and engineering input helps us understand feasibility while developing proposals.
This is a support capability within our research-led UX work. Production code, backend development, integrations, deployment and ongoing maintenance are not automatically included. Development Support or Design Systems work can be separately scoped where useful.
Research focus
Consider different users and platforms
We agree relevant devices, responsive layouts, languages and access needs. Longer content and alternative interaction methods may affect the design. Testing coverage is documented rather than assumed to include every device or user group.
Prototype research can identify accessibility barriers but does not certify the implemented experience. Technical accessibility and other specialist assessments need their own scope. Multi-market research and localization arrangements are agreed where relevant.
Research ethics
Appropriate participation and evidence
Research uses agreed consent, recording and reporting arrangements. Safe scenarios and non-production information should be used where practical. Identifiable recordings are not assumed to be available for public promotion.
Qualitative testing identifies issues but does not establish population success rates. A successful prototype task does not prove future adoption or conversion. We do not guarantee commercial outcomes or claim every implementation issue has been resolved.
Before we begin
Frequently asked questions
Yes. We can evaluate or refine a selected flow without redesigning the whole product. We agree which parts should remain and what needs investigation.
Not automatically. Testing, recruitment and revision rounds are specified in the agreed scope. Where testing is not included, we clearly identify unvalidated proposals.
The prototype communicates selected interactions but may omit technical requirements or edge cases. We agree handover documentation and discuss additional specifications with your development team.
Share the user tasks, existing research, design or brand guidance and delivery constraints. We will discuss scope, testing, deliverables, review rounds, timing and budget.
Experience Strategy
Translate research findings into priorities and an evidence-led direction.
Explore
Service Design
Translate evidence into service concepts, workflows and improvements.
Explore
Design Systems
Components, tokens, and the rules that keep them consistent as products and teams grow.
Explore
Development Support
Help teams carry agreed experience decisions into implementation.
Explore
Let us help shape the next step
Your interface has a UX problem.
Let’s find and fix it.
Next research service Design Systems Your interface has a UX problem. Let’s find and fix it. Contact Us Tell us which experience you want to explore.