Overview
Enterprise software is frequently designed around the data model and the org chart, then handed to the people who have to use it eight hours a day. The result is technically correct and operationally miserable.
We research first: what people are actually trying to accomplish, and where the current experience gets in the way. Then we prototype early and cheaply, test with real users, and leave behind a design system your teams can keep building against.
Signs you need this
Adoption of a system you paid for is far below what was assumed in the business case.
Users have built spreadsheets to work around the tool that was meant to replace spreadsheets.
Every team has designed its own screens and nothing looks like it came from one company.
Requirements are written as features rather than as outcomes for a person.
What we deliver
User and stakeholder research
Interviews, observation, and journey mapping that establish what people are really doing, including the workarounds.
Service design
The end-to-end experience across channels, handoffs, and back-office steps, not just the screens.
Product and interface design
Interaction and visual design, grounded in research and validated before it reaches a backlog.
Prototyping and testing
Low-fidelity prototypes tested early, so expensive assumptions fail cheaply.
Design systems
Components, patterns, and standards that let teams ship consistently without a designer in every sprint.
Accessibility
WCAG-aligned design and testing, treated as a requirement rather than a remediation project.
How this work runs.
Understand
Interviews, observation, and analysis of current behaviour, including the workarounds people have invented.
Define the problem
Journey maps and problem statements that the business and the delivery team both recognise.
Make it tangible
Low-fidelity concepts tested with real users before anything is engineered.
Resolve
Detailed interaction and visual design, with accessibility built in from the start.
Make it repeatable
Components and patterns documented so the next team does not start from a blank page.
What you are left with.
Documented and transferred, so your team owns it.
- Research findings and user journey maps
- Service blueprint across channels
- Tested prototypes
- Interaction and visual design specifications
- Design system and component library
- Accessibility standards and audit
- Usability test results and iterations
- Design handover documentation