“Don’t make me think” is the golden rule every UX designer carries around. In consumer apps it mostly holds. In enterprise systems it is not always true, and holding onto it too tightly is how good designers build bad systems.

The enterprise users I have worked with do not want an interface they never have to think about. They want every piece of data they need for a decision visible at once, so they can make better calls and better strategy. Thinking is their job. The system’s job is to feed it.

The two worlds

A while back a colleague and I compared notes and noticed something. We both work under the same title, UX designer, and our daily work has almost nothing in common. The problems that matter, the constraints, the way a solution gets judged: all different.

Design Thinking 101 and the word user-centric are hardwired into us by now. Then real work starts and the textbook keeps not fitting. The trap is not that the frameworks are wrong. The trap is applying one playbook to every product without asking what kind of product it is and who is being served.

The consumer world and the enterprise world do not share gravity. Walk into one using the physics of the other and you create a genuinely bad experience, for the company and for the people who work in it.

What consumer UX trained me to value

My early work was loyalty programs and food apps. Products people open because they feel like it. The user’s relationship with the interface is voluntary, so the real problem is attention. How do you keep a stranger in the app? How do you make the flow so intuitive that nobody ever stops to think?

I got good at happy paths and at removing friction. I chased wow moments. My vocabulary orbited delight, retention, conversion. The instinct that settled in was simple: if something is complicated, that is a design failure. Shorten the path. Remove the decision. Make it effortless.

For a long time I thought that was what good design meant: visually clean, immediately satisfying, nothing to explain.

What enterprise demanded instead

Then I moved into enterprise work and the old playbook stopped answering. Nobody cared about visual fluff or micro delights. And my simplify reflex was the first thing that broke.

Enterprise users are not voluntary. They are professional operators running a system under work pressure and constraints, eight hours a day, whether they like the software or not. They cannot uninstall it and leave.

Three things hold up an enterprise system, and none of them is minimalism.

Density is a utility. Data density is what lets an operator see the critical facts at once, without paging through screens, and make the call that matters.

Workflows are role-driven. There is no single linear journey. Screens behave differently by role, permission, and approval level, and the design has to compute that governance, not decorate it.

Legacy is a constraint, not a choice. You rarely start from zero. There is a decades-old core database behind everything, and the craft is bending a humane experience around data structures that will not move.

The cost of error is also a different animal. In a consumer app, a wrong tap buys the wrong color jacket. In an enterprise system, one wrong variable can cost the company a fine in the millions. Every button and toggle can ripple all the way down into the data structure. Zoomed out, a flow looks easy. Zoomed in, it is full of oh no moments that follow you into your sleep.

From interface thinker to systems thinker

Here is the mix-up I see most often: designers hear systems thinking and picture a design system with lots of components. Not the same thing. You can build an excellent component library and still be an interface thinker.

To change a system, find the leverage points: the places where a small shift in one thing produces a large change in everything.Donella Meadows · Thinking in Systems, paraphrased

Most of us, me included, spend most of our time on low-leverage problems. A clearer button. A shorter confirmation flow. A nicer empty state. Important, but they do not change how the whole system behaves.

The real shift for me was mental: stop treating every new problem as a fresh fire, start looking for the leverage point. Problems never stop arriving. Where you push back is the design decision.

What this did to my identity

Consumer work has a fast feedback loop. You ship, people see it, people say nice things. You screenshot it into a portfolio and a case study. That visibility is real dopamine.

Enterprise work lives behind NDAs and confidential systems. You cannot screenshot a permission matrix you spent a month getting right. There is no social currency in a governance flow. Some days the invisibility fed my imposter syndrome badly.

But sitting inside that invisibility, I finally understood something. The screen was never the output. The decisions the screen serves, the people it connects, the workflows it protects: that is the output. The work is not less visible because it is worse. It is less visible because it sits deeper under the iceberg’s surface.

Since that clicked, I open Figma with a different intention. In an era where AI agents can generate working prototypes, this matters even more. Figma stopped being a canvas where I assemble components. It became the common medium where I stand between business requirements and engineering limits and negotiate. AI can write the code. Someone still has to be the bridge that understands both sides well enough to get a shippable feature out of a legacy workflow.

Going through this shift from the SEA region makes it sharper. Most enterprise design literature comes out of Slack, Meta, and Salesforce, and their context is not mine. Designing enterprise systems from Myanmar for Singapore clients means different organizational culture, different stakeholder dynamics, different assumptions. I have to ask more questions and verify more things. That questioning, it turns out, is where a designer’s resilience actually comes from.

Moving forward

Leveling up is not doing your current work slightly better. It is being able to switch modes when the product demands it.

The point is not to decide whether you are a consumer designer or an enterprise designer. Most of us will cross both worlds. The point is to notice, at any given moment, which discipline you are actually using, and whether your instincts are calibrated for the problem in front of you.

Next time you are moving components around in Figma, ask which problem you are solving. Making the eye happy, or making the system hold.