ServiceNow: Where Design Goes to Die

(And why anyone who cares about adoption should care about aesthetics)

I hear it all the time: “Oh, we use ServiceNow, and I hate it.” As someone trained in graphic design – composition, hierarchy, whitespace, visual rhythm – that lands like a gut punch. I don’t hate ServiceNow. I hate that so many people hate using something that could make their workday calmer, clearer, kinder.

This essay isn’t a hit piece on the platform. It’s a critique of our industry habit: in ServiceNow delivery, functionality gets shipped; desirability gets skipped. Because developers are often the de facto designers, the dominant question becomes “does it work?” instead of “would anyone want to use this?” Both matter, but only one predicts adoption.

What my designer brain sees (that our delivery playbooks miss)

Design taught me that screens speak before we do. Visual hierarchy tells your eye where to go. Whitespace tells you what matters. Contrast says “click here,” not “good luck.” Good design is decision-making made visible. When that’s missing, users feel it; even if they can’t name it. They experience:

  • Cognitive friction: I can’t tell what this screen wants from me.
  • Visual noise: Everything is loud, so nothing is clear.
  • No path: I don’t know how to start, or when I’m done.
  • Zero hospitality: Nothing about this says “you belong here.”

They’re not asking for confetti cannons. They’re asking for legibility.

Apple, the iPod, and why people keep choosing “coherence”

The iPod didn’t win because it had the most checkboxes; it won because it felt inevitable; a simple wheel, a clear hierarchy, a single story: a thousand songs in your pocket. Same with iPhone versus the feature arms race: specs leapfrog every year, but people still gravitate to what looks and feels coherent. We can argue feature sheets all day; the market keeps rewarding clarity.

And, yes, the art-school bit matters. Ever notice how a photo sometimes just feels right? That’s often the rule of thirds whispering to your brain. You’re drawn to balance and tension without knowing why. That’s the point: appeal works underneath language. Enterprise software could use more of that quiet intelligence.

Why ServiceNow in particular earns the “I hate it” groan

  • Incentives: We measure throughput, not delight. If it saves and routes, it ships.
  • Ownership: UX often has no owner; devs carry the load by default.
  • Culture: Process checklists outrank human clarity; stakeholders win over users.
  • The myth: “Internal tools don’t need design.” (They need it more; users can’t opt out.)
  • The culture clash: Sometimes talking design with dev teams just…doesn’t compute. Under the Star Wars tees and the cargo shorts (the patron saint of functionality over aesthetics), there isn’t much oxygen for composition, tone, or emotional on-ramps. That’s not a dunk; it’s a diagnosis.

“But feelings? In enterprise software?” Yes, because adoption is emotional first

People return to what feels welcoming and predictable. Clarity beats training. Coherence builds trust. If that sounds squishy, remember: design decides whether functionality ever gets a fair trial. No one cares how many features your form has if the form feels like homework.

A helpful mantra here is the “delete” rule popularized around Elon Musk’s five-step process: remove anything you can; if you don’t end up adding at least 10% back, you didn’t delete enough. In other words: bias toward subtraction, then add back only what proves its worth.

A fairness clause (because nuance matters)

ServiceNow can support humane, even beautiful experiences. I’ve seen teams ship work that feels considered, calm, and clear. The problem isn’t capability, it’s our habit of treating UX as optional garnish rather than the plate everything sits on.

Also, the platform’s moving in the right direction. A senior ServiceNow dev told me recently that UI Builder is where the front-end is headed, which is good news. It puts layout, hierarchy, and composition within reach of the teams doing the work. We’ll always love writing scripts, but if we care about adoption we have to learn the design tools the platform already offers.

A simple reframe for dev-led teams

Before you ship on the strength of “it works,” pause and ask: Would someone choose this?

  1. Hierarchy: Can a new user find the primary action in three seconds?
  2. Economy: What can we remove without losing meaning? (Delete bravely; add back only what proves itself.)
  3. Tone: Does the screen feel like help – or homework?

If the answer to #3 is “homework,” this isn’t a nice-to-have redesign; it’s an adoption fix.

Why I care (and what I’m committing to)

Because beauty is hospitality. A well-composed screen is a welcome mat: Come in; we’ve thought about you. As a designer-turned-builder, I’m committed to asking on every ServiceNow project: Would anyone want to use this? If not, we’re not done.

One small closing challenge

Pick one workflow. Put it in front of five real users. Ask them one question:

“Did this feel like something you’d willingly use again?”

If the answer is yes, ship. If not, keep editing; especially by subtraction.

Pull-quotes

  • “In enterprise, we mistake compliance for consent.”
  • “Design isn’t lipstick, it’s legibility.”
  • “If dread is a login step, adoption is already lost.”

Bottom line: Does it work? ships software. Would anyone want to use this? builds products people return to.