When designing interfaces, we’re often taught to make things visible, accessible, and easy to discover.

But what happens when visibility becomes the problem?

In one of my recent projects — a game testing hub — I faced a different kind of challenge.
Not how to help users navigate the system… but how to stop navigation from getting in their way.

👉 Full case study

The reality of working with data

This wasn’t a typical product.

Users weren’t browsing content or exploring features.
They were working with large datasets — mostly tables — reviewing test results, comparing executions, and validating outcomes.

Their workflow looked like this:

• scanning rows of data
• switching between reports
• tracking inconsistencies
• making decisions under time pressure

This kind of work requires focus.

And focus breaks easily.

The moment everything clicked

At some point, it became clear:

The biggest UX problem wasn’t complexity.
It was interruption.

Every time the interface:

• shifted layout
• revealed too much UI
• required extra interaction

…users lost context.

And in a data-heavy environment, losing context is expensive.

Rethinking navigation

That’s when I stopped thinking about navigation as a menu.

And started treating it as a system layer.

Not something that helps users explore —
but something that supports their workflow.

Designing for “not being in the way”

This changed everything.

Instead of asking:

How do we expose more features?

The question became:

How do we remove friction without removing control?

What that meant in practice

Navigation had to be:

• present, but not dominant
• accessible, but not distracting
• stable, but not rigid

We designed it to:

• take up minimal space
• avoid unnecessary visual noise
• never interrupt the main workspace

What navigation is NOT

Another important decision:

Navigation should not do everything.

It doesn’t:

• onboard users
• explain the system
• communicate updates

Those responsibilities belong elsewhere.

👉 This keeps navigation predictable and lightweight.

The result

Navigation became something users barely noticed.

And that was the point.

Because when users focus on data instead of interface:

• they move faster
• they make better decisions
• they stay in flow

Final thought

The best navigation isn’t the one users explore.
It’s the one that lets them keep working without thinking about it.

👉 Full case study