Originally written Jan 2026

The card was clean. Really clean. Case name. Status. A thin border. Plenty of white space. It looked exactly like what every UX principle says a card should look like – focused, uncluttered, easy to scan.

We were in a UserZoom session. I was watching a fee earner navigate a prototype I'd spent weeks refining. She looked at the card for about two seconds, then opened the full case view.

"There's no clear indication that I'm in the Johnson case," she said. "It's not clear that the settlement offer is with the client for review. I've got no idea when it was sent, or when I should chase it, or if it's even my responsibility to chase."

She kept going. By the end of the session, her verdict was concise. "It's a shambles. I would not want to use this system at all." Production readiness: three out of ten.

The wrong question

The design wasn't bad – that was the problem. It was technically correct, following every rule I'd been taught. Reduced cognitive load. Progressive disclosure. White space for clarity. Fewer fields for focus.

In another domain, it might have worked. Legal professionals aren't making leisure decisions. They're managing risk across forty active matters under time pressure, where a missed deadline can mean a negligence claim. In that environment, minimalism doesn't reduce cognitive load – it removes context and creates anxiety.

The question I'd been asking was "What can we take out?" The question I should have been asking was "What does this person need to see to act without opening the full case?" Those are opposite instincts, and only one of them produces a useful card.

Density is not complexity.

That distinction took a UserZoom session and a shambles verdict to make real.

What the research said

The test data made the problem concrete. The first round of testing showed the same pattern across participants: users weren't struggling with the interface's complexity – they were struggling with missing context. Without a prominent case name at the top, they couldn't confirm they were in the right matter. Without visibility into deadlines, they couldn't tell if something was urgent. Without an assigned responsibility, they couldn't tell whether it was their job to act.

The feedback wasn't about preference. It was about confidence. Legal professionals need to be certain before they act, and a minimal card gives them nothing to be certain about.

Forty per cent of participants said the design was slower than the system it was meant to replace. Zero per cent said they would use it daily. Production readiness averaged three out of ten.

What we changed

After the test, we rebuilt with more.

Prominent case name and reference at the top of every view. Colour-coded priority borders so urgency was visible without reading. Assigned user, client communication status, and timing on each item. Tags made interactive for filtering rather than decorative.

The second round of testing ran six weeks later. Zero per cent said the new design was slower than the current system. Sixty per cent were now positive about using it daily. Production readiness moved from three out of ten to five out of seven.

The changes tracked directly to failures we'd watched in the first test. The fee earner who couldn't confirm her matter. The partner didn't know if an item was his responsibility. The paralegal opened every card individually because the summary told her nothing useful. Each addition was there because a specific person had needed it, and the design hadn't given it to them.

The design that looked cluttered to us looked workable to them. The design that looked clean to us looked like a shambles.

The principle was unlocked

The same finding kept reappearing.

The Case Overview header – the persistent top section showing matter reference, client name, work type, key dates, and financials – was deliberately dense. Nine elements, always visible. Every time we tested a version that hid some of them behind a toggle, users felt less in control.

The card zone structure packed case reference, category, trigger, context, and next action into every card in the dashboard. No progressive disclosure. Everything the fee earner needed to triage a card, present without clicking.

The accounts ledger defaulted to seven visible columns. The Tasks screen showed seven too. Each time we simplified by hiding, users pushed back.

The principal legal research taught – and kept teaching – is that information density and interface complexity are not the same things. A dense interface can be calm and structured if the information is well-organised and scannable. An empty interface can feel chaotic if the user has to leave it to find what they need. Legal professionals weren't asking for cluttered screens. They were asking for visible context. The difference matters.

A note on minimalism

Minimalism works when the cost of missing information is low. When I miss a product recommendation, I scroll. When a solicitor misses a deadline, they might not be in practice next year.

The design principles aren't wrong – they just weren't designed for this domain. White space and reduced cognitive load are valuable tools in contexts where users have time, flexibility, and low stakes. Legal professionals have none of those things at the moments that matter most.

The most useful reframe came from the research itself: legal professionals don't want to read their interface. They want to scan it, confirm the details they already know should be there, and act. Designing for that behaviour looks dense from the outside. From the inside, it feels like the system finally understands the job.