Marcus Andrey Study
Ler em português Library

Module 5 of 12 · 6 min read

Enterprise & Internal Applications

Why UX for internal and enterprise tools is different, and how to design, research and modernise for expert users.

Why it matters

Many UX leads work on employee-facing tools: back-office systems, operations platforms, internal portals. Leading UX for these tools is different from consumer UX. A common pitfall for new leads is to bring consumer habits (more whitespace, onboarding tours, "delight") to people who use the same screen 200 times a day. Another pitfall is accepting the argument that UX matters less because users "have no choice". Users with no choice build workarounds, make errors and need more training, and all of that costs the business money.

If you already know your organisation's internal tools well, that knowledge is an advantage. This module helps you put it into words that designers, product managers and IT leaders understand.


1. What makes internal/enterprise UX different

Dimension Consumer apps Internal enterprise apps
Choice Users can leave Users must use it (so they build workarounds instead)
Users Broad, novice Experts, repetitive daily use, deep domain knowledge
Goal Engagement, conversion Efficiency, accuracy, low training cost
Complexity Simplified Inherently complex data & workflows
Buyer vs user Same person Buyer/sponsor ≠ user
Lifespan Frequent redesign Long-lived, legacy, integrations
Context Personal device Multiple screens, warehouses or shop floors, shifts, interruptions, multiple languages
Success metric Retention, revenue Task time, errors, throughput, compliance, support load

2. Designing for expert users

  • Efficiency features: keyboard shortcuts, bulk actions, saved filters, defaults, inline editing.
  • Information density: experts prefer more data on screen. Don't "consumer-ise" it by adding whitespace.
  • Consistency across tools: operators switch between apps all day, so inconsistency costs time and causes errors. This is the core argument for shared standards and a design system (see Module 8: Design Systems & Standards Governance).
  • Progressive disclosure for rare, complex features.
  • Error prevention: constraints, validation, confirmation for destructive/bulk actions, undo.
  • Respect learned behaviour: big redesigns break muscle memory. Change incrementally and communicate it.
  • Data tables are the core UI: sorting, filtering, column config, export, row actions.

3. Research in internal contexts

Advantage
users are colleagues, so access is easier in principle.
Reality
their time is operational and costly; managers may block it; in some countries works councils (employee representatives) must be involved.
Method Use
Contextual inquiry / shadowing Watch operators in real work, which surfaces workarounds (sticky notes, Excel)
Task analysis Map complex workflows step by step
Usability testing with real data Fake data hides real problems
Support-ticket & training-material analysis Cheap signal of pain
Champions / power-user network A recurring panel of users per domain for quick feedback
Surveys (SUS/UMUX-Lite) Benchmark across apps

Lead-level idea: build an internal user research panel across domains and locations, with consent and manager buy-in. Because it is reusable, it reduces the recruiting cost of each study.


4. Legacy, platforms and IT reality

  • Many internal apps sit on legacy stacks or vendor platforms (SAP, Salesforce, ServiceNow, custom). Know which UX levers exist on each platform.
  • Design system across tech stacks: tokens and patterns travel; components may need several implementations.
  • Modernisation strategy: a strangler pattern in UX means a new shell/navigation, migrating screens over time.
  • Speak IT governance language: architecture boards, release trains (SAFe), change management, ITIL.

5. Employee experience as strategy

Internal tool UX is part of Employee Experience (EX). Good tools:

  • Reduce cognitive load and stress in operational roles.
  • Shorten onboarding, which matters when turnover in operations is high.
  • Reduce errors that have a real business cost (in a logistics business, for example: wrong customs data or misrouted shipments; in a bank: wrong payment details).
  • Support digital transformation goals. Read your organisation's public strategy material or annual report, and connect UX work to the goals you find there.

6. Accessibility & internationalisation

  • WCAG 2.2 AA as the baseline. Employees with disabilities use internal tools too, and regulation (for example in the EU) is getting stricter.
  • Multilingual UI: plan for text expansion (German text, for example, is often around 30% longer than English), date/number formats, and right-to-left languages if relevant.
  • Varied environments: warehouse lighting, gloves, scanners, tablets, older hardware.

Practice

Evidence to collect

Keep proof in your leadership log:

  • Cross-app inconsistency examples (screenshots, anonymised).
  • One insight from shadowing that changed a design decision.

Read / watch

Library → Enterprise UX: NN/g articles on complex applications and enterprise UX, Designing for the Digital Age (Goodwin), The User Experience Team of One (Buley) for the "only designer in a domain" context.


Talking about it

When you explain this topic to your manager, product managers or IT leaders, use their outcomes, not design vocabulary:

  • "Users have no choice, so why invest?" → "Because they have no choice, every problem turns into a workaround, an error or a support ticket. We pay for bad UX in time, rework and training instead of in churn."
  • Show, don't argue. Bring one shadowing story and one screenshot of a workaround (an Excel sheet, a sticky note). It is more convincing than any principle.
  • Name the constraints you respect. Saying "we'll change incrementally to protect muscle memory" and "we'll involve IT governance and the works council early" shows that you understand how the organisation works.
  • In a promotion or hiring conversation, describe one example where you improved an expert workflow and how you knew it worked (task time, errors, tickets).

Check yourself

Answer out loud, then open the section to compare.

  1. Why does UX matter when users "have no choice"? → answer
  2. Name two patterns that help expert users. → answer
  3. What's different about research with employees? → answer


Connections

← Module 4: People Leadership · UX Lead Course · Module 6: UX Strategy & Vision →

Related

Hubs: Frameworks index · Design your UX practice

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close