UI and UX design
Research, interface design and design systems — tested with the people who will use the system every day.
The challenge
Institutional software is usually designed for the person who commissioned it rather than the clerk who will use it forty times a day. The difference only becomes visible during training, when it is expensive to fix.
The other failure is a set of well-made screens with no rules behind them: the eleventh screen gets drawn from scratch, and the interface stops agreeing with itself.
How we approach it
Watch the work being done
Observation of the current task before anything is sketched.
Design the hardest path first
The exception case, not the tidy demonstration flow.
Build a system, not screens
Tokens and components, so the next screen is assembly.
Test with the real users
Including those for whom this is their first such system.
The same four phases, whatever we are building.
- 012–3 weeks
Discovery
We map your current process, users and constraints, then define scope in writing.
- 022–4 weeks
Design
Interface and data design, reviewed with the people who will use the system daily.
- 036 weeks+
Build
Delivery in two-week increments, each one testable, with progress visible throughout.
- 04Ongoing
Launch & support
Deployment, training and documentation, then optional support at a level you choose.
What you get
- What we observed, with the counts and the quotes behind it.
- The task paths, including the exceptions staff actually hit.
- Screens in the states they reach — empty, loading, error.
- Tokens, components and usage rules, documented.
- Contrast, focus order and keyboard paths specified in design.
- Specifications an engineer who was not in the room can build from.
What changes
Designed for the user
The person doing the work, not the person buying.
Consistent by construction
A system means the next screen already matches.
Cheaper to roll out
A clear interface needs fewer hours of training.
Accessible from the start
Specified in design, not audited after a complaint.
Often looked at together.
Web development
Accessible, fast web applications with a performance budget agreed up front.
Mobile development
Native and cross-platform apps built for shared, low-end devices and patchy signal.
Government digital systems
Registries, e-services, MIS platforms and reporting for ministries, agencies and regional bureaus.
About this work specifically.
General questions about scope, ownership and timelines are answered on the resources page.
Usually yes, and it is short. A few hours watching the task performed surfaces the workarounds nobody mentions in a requirements meeting — and those workarounds are generally the real requirements.
Yes. The research, the interface and the documented design system are a legitimate standalone deliverable. We hand them to your own engineers or to another vendor without conditions attached.
Tell us what you need built.
We reply within two working days with honest scope and next steps — including when we are not the right fit.