Engineering Journal
We Don't Design for \
A dashboard built for the most technical person in the room fails everyone else. At Mpaukwu, every interface starts by asking who actually uses it every day - a nurse, a receptionist, a security guard, a first-time customer - and designs around their confidence level, interruptions, and mistakes, not an idealized power user.
The question we ask before "what should this look like?"
One of the first questions we ask after understanding a business isn't "what should the dashboard look like?"
It's something much simpler: "who is actually going to use this every day?"
A business owner, an accountant, a receptionist, a warehouse officer, a nurse, a security guard, and a first-time customer all experience the same software differently. If we build for only the most technical person in the room, we've already failed everyone else.
Every business has different levels of digital confidence
Walk into almost any organization and you'll find people with very different relationships with technology.
Some people instinctively explore every menu. Others worry that clicking the wrong button might break something. Neither group is wrong - they're simply approaching software from different experiences. Good software respects both.
This is why MediSeen HMS has a deliberately different interface for a receptionist doing patient registration than for a lab technician logging a result - same system, different confidence levels, different jobs to do. On MyEstate, a security guard verifying a visitor code needs one tap and a clear approve/deny decision, not a dashboard.
We map the human journey before the screen
Before designing an interface, we identify:
- Who is using this feature?
- What are they trying to accomplish?
- What information do they already know?
- What decisions do they need to make?
- What mistakes are most likely?
- What happens if they become interrupted halfway through?
The interface is built around those answers - not the other way around.
Every screen has one primary job
One of the easiest ways to overwhelm people is to make every page do everything. We prefer a different principle: one screen, one purpose.
If someone is registering a patient, they should feel like they're registering a patient - not navigating a control panel. If someone is checking a job status on SortAm, the next step should always feel obvious. Clarity reduces training.
Error messages should teach, not blame
One of the quickest ways to frustrate people is with messages like Error 500 or Invalid Request. Those messages may describe what happened. They don't help anyone recover.
Instead, we ask: what does this person need to know to move forward?
Instead of Authentication Failed, we prefer:
Your session has expired after a period of inactivity. Please sign in again to continue. Your unsaved work has been preserved.
The problem is explained. The next step is clear. Anxiety is reduced.
We design for mistakes
People double-click buttons. People lose internet connections. People answer phone calls halfway through a task. People close browser tabs. People accidentally upload the wrong document. People misunderstand instructions.
That's normal. Rather than expecting perfect behaviour, we build systems that anticipate these moments and guide people back to where they need to be - because good software isn't software that never encounters errors. It's software that helps people recover gracefully. On StoreBase, that's a big part of why offline-first sync matters: a shop assistant on a weak connection shouldn't lose a sale because the app assumed a perfect network.
Confidence is part of the interface
Every action should answer three questions: what just happened, what should I do next, and can I safely continue?
If people are left wondering whether a payment went through, whether a file uploaded, or whether their work was saved, the interface has failed - regardless of how attractive it looks.
We design for the busy day, not the perfect demo
Software demonstrations happen in quiet meeting rooms. Real work happens during interruptions. Phones ring. Customers ask questions. Someone needs help. Power flickers. The internet slows down. A staff member is serving three people at once.
That's the environment we design for. Not because it's ideal - because it's real.
Great interfaces build confidence
When people feel confident, they work faster. They make fewer mistakes. They need less training. They trust the system. And when customers trust the system, they trust the business behind it.
That's why we believe interface design isn't decoration. It's communication. Every button, every message, every confirmation, and every warning is part of a conversation between the business and the people it serves.
The takeaway
At Mpaukwu, we don't measure a successful interface by how modern it looks. We measure it by something much simpler: can a first-time user complete their task without feeling lost?
Great software doesn't impress people by being complicated. It earns their trust by making complicated work feel simple.
Mpaukwu Trading builds founder-led SaaS products, automation systems, and production-ready platforms for African businesses, including MediSeen HMS, SortAm, and MyEstate. Read more from the Engineering Journal or start a project.