There's an unspoken hierarchy in product design. Consumer-facing products sit at the top — the apps millions of people download, the interfaces that win awards, the work that fills portfolio case studies and gets shared on Dribbble. Internal tools sit somewhere near the bottom. Unglamorous. Inherited. Tolerated.
I'd like to make the case that this hierarchy is wrong — and that the designers willing to work against it are doing some of the most important, most complex, and most undervalued work in the field.
The bias is understandable
Consumer products are visible. They're measurable in downloads, ratings, and revenue. They're the thing a company shows the world. Internal tools, by contrast, are the thing a company shows only itself — and for a long time, the standard was simply "functional enough not to cause a revolt."
Design culture followed the money and the visibility. The best portfolios were full of consumer apps. The best jobs, we were told, were at companies whose products you'd actually use. Internal tools were what you worked on when you couldn't get the other job.
But something has shifted. The most sophisticated organizations have started to realize that the experience of the people inside the company is inseparable from the experience of the people outside it. If your associates are navigating twelve different systems to answer a single client question, that inefficiency doesn't stay internal — it shows up in every client interaction, every service delay, every moment where a banker has to say "let me look into that and get back to you."
The complexity is real
Here's what most people outside this work don't appreciate: internal tools are genuinely harder to design well than most consumer products.
Consumer products have the luxury of a relatively clean slate. You're designing for people whose primary job is not to use your product. Their attention is optional. Their tolerance for friction is low. That constraint is hard, but it's clarifying.
Internal tool users don't have that option. They're stuck with what you build. Which sounds like a design advantage — a captive audience — until you realize it means every flaw compounds. Every confusing flow gets repeated hundreds of times a day. Every piece of missing information creates a workaround that becomes a habit that becomes a dependency you didn't know existed.
The stakes are also different. A bad consumer app gets uninstalled. A bad internal tool gets blamed when a client doesn't get their answer, when a process breaks down, when an associate spends 40 minutes doing something that should take four.
Internal tool design is where design quality has the most direct, measurable impact on how a business actually operates. That's not a lesser challenge. It's a harder one.
The work is worth it
I've spent the better part of my career in this space, and I keep coming back to it for a reason.
When you get it right — when you design something that genuinely makes someone's working day better — the feedback is immediate and specific. Not a net promoter score. A person telling you that they used to dread opening this tool and now they don't. A team lead saying their associates are spending more time with clients because they're spending less time fighting systems.
That's the work. And it deserves better than the reputation it has.