The Myth of “Keep It Simple”: Why Enterprise UX Needs Density

ENTERPRISE PRODUCT DESIGN

Larry Tesler figured this out in the 1980s. Most product designers are still ignoring it.

Early in my design career at a fast-moving consulting startup, I had one rule for every screen: make it clean.

I added 48px padding, hid extra fields behind sleek accordions, and split long forms into neat, multi-step modals. On Dribbble, it looked gorgeous.

Then I watched actual operators use the software.

They weren’t impressed by the whitespace. They were frustrated. They were clicking three times just to check a single status code. They had to memorize values from Step 1 while typing into Step 3.

My “clean” design hadn’t removed the complexity. It had simply dumped it directly into the user’s working memory.

That failure led me to one of the most foundational principles in product design: Tesler’s Law.

What is Tesler’s Law?

Formulated by computer scientist Larry Tesler at Xerox PARC, the Law of Conservation of Complexity states:

Every system has an inherent amount of complexity that cannot be removed. It can only be handled either by the system (software) or by the user.

In consumer apps like Uber or Spotify, the software absorbs nearly all the complexity. You tap one button; algorithms match drivers, calculate pricing, and handle tokens in the background:

Consumer Apps:
[ Software absorbs 90% ] ──► [ User does 10% ]

Enterprise and safety-critical tools (like clinical EHRs or financial ledgers) don’t work that way. A doctor prescribing medication or an accountant reconciling claims must retain situational awareness. You cannot automate high-stakes judgment into a single magic button:

Enterprise & Mission-Critical Systems:
[ Human Operator Exercises Judgment ] ◄── Shared Responsibility ──► [ System Manages Complexity Rules ]

“Simplicity isn’t the absence of information. It’s the absence of confusion.”

When UX designers try to force consumer-grade minimalism onto enterprise workflows, we create false simplicity.

The 3 Hidden Costs of “False Simplicity”

Hiding complexity doesn’t eliminate it. When you arbitrarily strip fields from an interface, you trigger three failure modes:

• The Memory Tax: The user must juggle critical parameters in their head across separate screens.
• Click Fatigue: What used to take a glance and a single keystroke now takes four clicks and context switching.
• Silent Errors: Vital warning signs tucked behind a “Show More” toggle get missed entirely.

How to Absorb Complexity Without Ruining the UI

If we can’t remove inherent complexity, what should we do with it? The system must shoulder the mechanical grunt work so the human can focus purely on the decision.

Three practical ways to do that:

1. Contextual Defaults Over Blank Forms

Don’t make an operator re-enter standard baseline data every session. Pre-populate sensible defaults based on user role, past patterns, or current record state — while keeping every value immediately visible and editable.

2. Visual Hierarchy Over Arbitrary Deletion

You don’t need to delete 20 columns from a data table to make it readable. You need better typographic contrast:

• High-contrast bold text for the primary identifier (e.g., Patient ID or Order Number).
• Muted neutral grays for secondary metadata.
• Strict color tokens (amber, red) reserved exclusively for abnormal thresholds, never decorative badges.

3. Proactive Constraints Over Reactive Errors

The worst place to handle complexity is an error banner that pops up after form submission.

• Use inline input masks to enforce formats automatically.
• Disable conflicting choices dynamically so impossible combinations cannot be selected.
• Prevent the error before it happens instead of forcing the user to debug it later.

The Takeaway

Great enterprise design isn’t about how much empty whitespace you leave on the canvas.

Stop treating density like a visual flaw you need to hide. Embrace the irreducible complexity of your domain, let your system do the heavy lifting, and give your users the transparent, dense data they need to do their jobs safely.

The Myth of “Keep It Simple”: Why Enterprise UX Needs Density was originally published in Bootcamp on Medium, where people are continuing the conversation by highlighting and responding to this story.