
Complexity isn't a feature
Enterprise software often wears its difficulty as a badge of seriousness. The complexity belongs in the system — not in the interface people have to operate.
Notes from the work — on experience design, digital transformation, accessibility, and the technology in between.

Enterprise software often wears its difficulty as a badge of seriousness. The complexity belongs in the system — not in the interface people have to operate.

Most transformation programs don't fail at strategy or at build. They fail in the gap between launch and the way people actually work on a Tuesday.

Treated as an audit at the end, accessibility becomes expensive and grudging. Treated as a design constraint at the start, it mostly just makes the product better.
Most dashboards answer questions nobody asked. Designing for decisions rather than for data is the difference between a screen people check and a screen people close.
The useful question isn't whether to add AI. It's which parts of a process are genuinely tolerant of being wrong sometimes — and what happens when they are.
A design system rarely pays for itself while you're building it. It pays when the next thing gets built — which is exactly why so many are abandoned just before they start working.
Start a conversation with our senior team.
We reply within one business day.