About
A practice built around the reasoning, not the output.
OBOSU identifies practical problems, improves the processes behind them, and builds digital systems that make those processes simpler, more connected and, where appropriate, automated.
Most software problems presented as design problems turn out to be process problems. The interface is the last place it shows, and it is the place that decides whether everything after it works.
How the work runs
Five stages, in this order, every time.
Understand the problem
What is going wrong now, who it happens to, and what it costs them. Written down plainly enough that you can correct it if it is wrong.
Improve the process
Before anything is built, the process itself gets looked at. Software that automates a bad process makes it faster and harder to see.
Agree what success means
Measurable outcomes with a threshold attached, so there is a way to tell later whether the thing worked rather than whether it shipped.
Build one complete slice
One real thing, end to end, deployed and tested, before anything is built widely. It is the fastest way to find out that an assumption was wrong while it is still cheap.
Prove it, then extend
Automated tests, accessibility checks and performance budgets run on every change, each completed item points at the evidence for it.
Technology
Modern tools for real problems.
Chosen per project against the problem. Nothing appears here because it is new or in fashion.
- React 18, TypeScript, Vite, Tailwind CSS, TanStack Query
- Node.js, NestJS, Express, Prisma, PostgreSQL, Redis
- Docker, Terraform, Azure, GitHub Actions
- Playwright, Vitest, axe, Lighthouse budgets
Who builds it
Sandro Abomo
Product designer, architect and full-stack engineer. One person across design, architecture, engineering and delivery, with no account manager and no handover.
- OBOSU, trading in the United Kingdom
- Sandro Abomo, product design through to delivery
- A small number of projects at a time, deliberately
- Remotely, with on-site time where a project needs it