Designed for
the person at
the desk.
Not for the person in the meeting. Not for the demo. For the analyst who will use this every day — and whose time matters.
"Good design is invisible.
Bad design is all you can see."
Design isn't
decoration.
It's clarity.
The best interface is the one that gets out of the way and lets the person do the work. Beautiful and functional are not in tension — they're the same thing done well.
We come to design from an unusual angle. Our background is in Six Sigma process improvement and operational software — which means we think about how a person actually uses a tool, not just how it looks in a mockup. That changes what we notice and what we fix.
Every interface decision has a cost. A confusing label costs the user three seconds of hesitation, multiplied by every interaction, multiplied by every user, multiplied by every day. That's not abstract — it's measurable, and it compounds.
We design with the goal of reducing cognitive load, improving adoption, and building something that reflects the quality of what's behind it. If the software is good, the interface should feel good. If it doesn't, people don't trust the software — even if the software is right.
The person who approves the design and the person who uses it daily are usually different people with different needs. We design for the person at the desk.
If you have to explain how an interface works, the interface needs work. Clever interactions that require a tutorial are not clever — they're incomplete.
Every inconsistency in an interface is a small tax on the user's attention. It adds up. We design systems, not screens — so every element behaves the same way every time.
If the interface feels polished and considered, users trust the data it shows. If it feels cobbled together, they second-guess everything. Design is not superficial — it's credibility.
A design that only works with the original designer is not finished. We document systems properly so your team or developer can maintain and extend them without us.
From brief to
build-ready.
We cover the full design process — from understanding the problem through to production-ready assets your developers can build from directly. No gap between design and reality.
UX Research & Strategy
Understanding the problem before designing the solution. User journeys, workflow mapping, and the kind of structured questioning that reveals what users actually need — which is often different from what they ask for.
Interface Design & Systems
Full UI design from wireframe to polished screen. Component-based design systems that scale consistently across an entire product — not a collection of one-off screens that drift apart over time.
Dashboard & Data Interface Design
This is where our Six Sigma background makes a real difference. We design dashboards that communicate correctly — not just clearly. The right chart type, the right level of detail, the right context for the decision being made.
Internal Tooling Design
Internal tools are the most used and least loved software in most organisations. They deserve the same design rigour as customer-facing products — often more, because the people who use them don't have the option to go elsewhere.
Product Design & Prototyping
Interactive prototypes that behave like the real product — for user testing, stakeholder review, or developer handover. Good enough that you can test assumptions before committing to a build.
Design for Custom Software
If you're commissioning custom software through us — UI/UX is included. We design and build. There's no gap between what we design and what gets built, because the same team does both.
Rigorous by default.
Not by request.
We apply the same structured thinking to design that we apply to process improvement. Every phase has a clear output. Nothing moves forward without it.
Understand the user, the workflow, and the problem. Not the brief as written — the actual problem the brief is trying to solve. These are usually different things.
Document what we're designing, for whom, and what success looks like. Agreed upfront. Prevents the redesign conversation six weeks in.
From wireframe to polished system. Iterative, visible, and reviewed before it's final. You'll see progress — not a surprise at the end.
Build-ready files, component documentation, and a handover thorough enough that any competent developer can implement without us in the room.
Design that understands
what it's designing for.
Most designers understand visual communication. Fewer understand the operational context their interfaces live inside. That context changes everything.
| Dimension | MODT approach | Typical agency approach |
|---|---|---|
| Starting point | →The actual workflow and process the interface lives inside | ·The brief as written, the brand guidelines, the mood board |
| Data interfaces | →Six Sigma background means we know what makes a dashboard correct, not just clear | ·Charts chosen for aesthetics, not statistical appropriateness |
| Handover | →Component documentation, design system, build-ready files | ·A Figma file and a meeting where the designer explains it |
| Integration with dev | →We often build what we design — zero translation gap | ·Design intent lost in the gap between designer and developer |
| User focus | →The person doing the work, every day, at speed | ·The stakeholder approval, the demo, the boardroom presentation |
| Ownership | →All files delivered — yours to modify, extend, or hand on | ·Assets retained in agency tools until you renew the relationship |
Design for people
who use tools,
not approve them.
If your team is losing time to confusing interfaces, or if your data is good but nobody trusts it because the dashboard looks like it was built in 2009 — this is for you.
Teams using tools that fight them every day.
Confusing navigation, inconsistent labels, workflows that require seven clicks for a task that should take one. The frustration is real, the productivity cost is measurable, and most organisations accept it as normal. It isn't. We fix it.
"If work was easy, it would be called happy fun time. The software shouldn't be the hard part."
Analysts whose dashboards don't get acted on.
The data is right. The analysis is right. But leadership looks at the dashboard and doesn't understand what it's telling them. That's a design problem — specifically, a data visualisation and information hierarchy problem. We design dashboards that lead to decisions.
"In Q we trust. But only if the dashboard makes the Q visible."
Teams building software that needs to work properly.
If you're building something — internally or for customers — the interface is part of the product. We can design it as a standalone engagement, or as part of a full software build where we design and develop end-to-end.
"Design is not what it looks like. Design is how it works."
Designers who need an execution partner.
If you have design direction but need someone to take it to a finished, build-ready state — or if you need a second perspective on a problem you're too close to — we work well as a collaborative partner, not just a vendor.
"No ego, just craft. Tell us what you're trying to do."
Got something
that needs
designing?
Tell us what you're trying to improve — a tool, a dashboard, a product, a process. We'll tell you honestly what we'd do and whether we're the right fit.
hello@makersofdifficultthings.comMODT · BUSHELL DESIGN · UK · TALK FIRST, BUY LATER.