UI/UX Design for
Mid-Market Enterprises

Yes, and usually should. Most engagements extend an existing brand into a working interface system rather than replacing it — brand guidelines rarely specify focus states, error messages or empty screens, which is exactly the gap we fill. If something in the brand actively fails accessibility, such as a brand colour that can't meet contrast requirements, we'll flag it and propose an accessible variant rather than quietly ignoring it.

You need it in proportion to your uncertainty. If you're redesigning a well-understood internal tool, a handful of sessions with actual users may be enough. If you're entering a new market, skipping research means engineering builds your assumptions at full cost. Five to eight participants surfaces most serious usability problems — it's a smaller commitment than teams expect.

A design system: tokens for colour, type and spacing; components with every state documented, including hover, focus, disabled, loading, error and empty; and specified responsive behaviour. Plus working sessions with your engineers rather than a link to a file. The point is that they build from it rather than interpret it.

By testing it. Design arguments between stakeholders are usually unresolvable by discussion because both positions are plausible — putting the two options in front of eight users generally settles it in a week. Where testing isn't practical, we'll make a recommendation and write down the reasoning so the decision can be revisited on evidence rather than re-argued.

Designed in from the start, it adds very little — mostly discipline about contrast, focus and semantics. Retrofitted after launch it's expensive, because it often means reworking components you've already built everywhere. It's also a legal requirement in most markets our clients sell into, and increasingly a procurement condition, so the cheap moment to deal with it is now.