“Intuitive” is UX’s Most Dangerous Word in Enterprise Design

Designing for “intuitive” feels like the right goal. Until you work on systems where mistakes have consequences. A reflection on why intuition breaks down in enterprise and healthcare UX.

Photo by Ryoji Iwata on Unsplash

“Intuitive.”

For years, this was the word I chased hardest in my UX career.

If an experience felt intuitive, it was considered a win.

No further justification required.

No deeper questions asked.

That belief didn’t come out of nowhere. It was reinforced everywhere: by mentors, by design leaders, and most convincingly, by users themselves. When users said, “This feels intuitive,” it sounded like validation. Like proof that the design had done its job.

What no one warned us about was the cost of relying on that word.

I started questioning this belief when I moved from designing consumer-facing apps to enterprise platforms.

Healthcare was the breaking point.

The harder I pushed for “intuitive,” the more problems surfaced.

Misinterpretations, missed edge cases, and workflows that looked simple but collapsed under real-world complexity. What felt obvious to me often turned out to be risky, incomplete, or outright misleading for the people using the system.

That’s when I realized: in complex domains, intuitive isn’t just insufficient. It can be dangerous.

When “intuitive” starts removing safeguards — and accountability

Photo by Sasun Bughdaryan on Unsplash

In the early days, I was designing workflows for nurses who constantly switched between patient care and complex claim audit reviews.

I joined call after call, watching them work — the tools they relied on, the screens they moved between, the moments they paused.

My first reaction was blunt: this looked poorly designed. Inefficient. Almost careless.

Because nothing moved forward without verification. Every action was cross-checked against documentation before a nurse felt confident submitting an audit.

I treated that as friction.

So I simplified the workflow. Removed steps that felt redundant. Consolidated screens. Reduced visual noise. Anything that slowed progress became a candidate for removal.

I walked into the next round of calls confident. The design was cleaner. Faster. More intuitive.

Instead, the questions started.

“Where did this information go?”

“How do I verify this now?”

“What happens if this assumption is wrong?”

The workflow moved faster — but the confidence was gone.

And that’s when the real issue surfaced.

When something goes wrong, teams don’t look for intuition. They look for answers.

Why was this action taken?

What did the user see?

What signals did the system provide — or fail to provide?

“This felt intuitive” isn’t a defensible answer.

In enterprise systems — especially healthcare — users work within SOPs and legal constraints. Safeguards exist because the cost of getting it wrong is high.

In workflows like audits or investigations, intuition disappears. What remains is what the system showed, allowed, and failed to prevent.

Design choices must be explainable — not just usable.

When “intuitive” is only “intuitive to the designer”

It’s hard to step into the shoes of an enterprise user — and pretending otherwise is where many design decisions start to go wrong.

Surface-level empathy can’t replace direct exposure to how people actually work. Without deep user research or sustained conversations, what we call “intuition” is often just a projection of our own assumptions.

The problem gets worse under pressure. In service-based environments like the one I work in, velocity is rewarded. Designers are expected to move fast, ship confidently, and unblock teams. Research gets trimmed. Stakeholder discussions get shortened — or skipped entirely.

What fills that gap is “intuition.”

More often than not, it belongs to the designer — not the user. It’s shaped by patterns we’ve seen, built, or reviewed repeatedly.

Designer intuition tends to model a clean, happy path. In the process, cues that users rely on to reason safely — especially in edge cases — get removed.

What feels obvious to the designer may be neither obvious nor safe for the user. The interface gets simpler, but the cognitive burden quietly shifts to the person least equipped to absorb it.

What to design for instead of “intuitive”

When “intuitive” breaks down in complex systems, the answer isn’t to make users work harder. It’s to design systems that are easy to understand under pressure.

In enterprise and healthcare settings, users don’t need interfaces that feel obvious at first glance. They need interfaces that make it clear why something is happening, what they are acting on, and what the consequences are.

This means choosing clarity over speed.

Choosing explainability over visual neatness.

Designing workflows that can be explained later — not just completed quickly.

Good enterprise design doesn’t remove complexity. It organizes it. It keeps the cues users rely on to double-check their work, understand system decisions, and pause when something feels off.

Instead of asking, “Will this feel intuitive?” more useful questions are:

• Can the user explain why this action was taken?
• Does the system show enough context to support the decision?
• If something goes wrong, can this interaction be reviewed and defended?

In these environments, success isn’t about reducing thinking. It’s about helping users think clearly, safely, and with confidence.

Hi, I’m Swati Soni, a product design leader working on complex B2B healthcare platforms.

My work focuses on how design decisions play out in real-world systems, where scale, risk, and operational constraints matter as much as usability. I write about design leadership, enterprise UX, and the trade-offs teams navigate when building beyond consumer products.

You can find more of my work and case studies on my **website, or follow my thinking on [LinkedIn](http://www.linkedin.com/in/swatisoni1) and [Instagram](https://www.instagram.com/swatisoni.ux/)**.