Research with the people who do the work
Interviews, observation and a review of the tools they use today, so design starts from real tasks.
Services / Start
Design the product
people will actually use.
User research, heuristic review, wireframes, interactive prototypes and a design system and handoff specifications your engineers can build from, led by designers who work beside our engineers.
- Best when
- People who did not choose the tool will have to use it every day.
- You bring
- Access to real users and a clear view of the business problem.
- You leave with
- Tested prototypes and a design system engineers can build from.
- Shape
- From a focused design sprint to continuing product design.
You might be here if
Does any of this
sound familiar?
- Your AI prototype works, but nobody outside the team that built it can use it.
- Staff avoid the internal tool and keep a spreadsheet instead.
- You are about to fund a build and want to see it, and test it, first.
- The product grew one request at a time and its screens no longer agree with each other.
Why design matters more now
With AI, the interface
carries the trust.
When a system can be wrong, the interface decides what happens next. Does the person see where an answer came from? Can they tell how sure the system is? Is it easy to correct a mistake, and does the correction go anywhere? Those details decide whether people check the output or quietly stop trusting it.
We design for the whole workflow: the research that shows what people really do, the flows that fit their day and the states that engineers often leave to chance, such as empty, uncertain, failed and in review.
What we do
From what people do to what gets built.
A usability review
An existing product checked against established usability principles, with findings ranked by how much they get in the way.
Wireframes and flows
End-to-end flows worked out before visual polish, so structural problems appear while they are cheap to fix.
Interactive prototypes
Clickable designs tested with real users before development begins.
Interfaces for AI
Patterns for showing sources, uncertainty, review, correction and escalation, so people can check what the system produced.
A design system for engineering
Components, states, content rules and handoff specifications, including the error and uncertainty states.
How it works
One clear step at a time.
Understand
Learn the users, the tasks and the constraints. Review what exists and what people do around it.
Explore
Sketch and wireframe the main flows, and compare alternatives with the people who will use them.
Prototype and test
Build interactive prototypes, test them with real users and revise what the sessions show.
Hand off and stay
Deliver the design model and stay with the engineering team so the build matches what was tested.
What changes
From where you are to where you want to be.
From: Screens designed one request at a time
To: A coherent design system and component set
From: Design opinions
To: Findings from watching people use the product
From: Designers and engineers working in sequence
To: One team building what was tested
From: AI answers shown as plain text
To: Answers with sources, uncertainty and a way to correct them
Before you start
What to expect.
Design reduces friction. It does not guarantee adoption.
Adoption also depends on training, incentives and whether the tool fits the way the work is organized.
Questions
Common questions.
Can you design without building?
Yes. You can take the prototypes and the design model to your own engineering team. The work usually lands best when design and engineering stay connected.
Do you design AI products specifically?
We design business software of all kinds. AI adds specific questions about trust, review and correction, and we bring patterns for those.
Who will work on our project?
We agree the design team and their roles before the work starts.
How do you test with users?
We run short sessions with the people who will use the product, using prototypes that behave realistically, and record what they do as well as what they say.
Can you redesign an existing product?
Yes. A heuristic review is often the first step. It shows which problems matter most before anyone commits to a redesign.
Design it, test it, then build it.
Tell us who will use the product and what it needs to do. We will suggest where design can help most.