The Forgotten User: Designing Internal Dashboards That Boost Employee Productivity
Here's an irony that exists in almost every company:
We spend millions optimizing customer-facing products:
- A/B testing button colors
- Reducing page load by 100ms
- Perfecting onboarding flows
- Obsessing over conversion rates
But our internal tools?
- Look like spreadsheets from 1998
- Require 47 clicks to complete a basic task
- Crash regularly with cryptic error messages
- Force employees to maintain personal workarounds in Excel
The result:
Your customer support team spends 6 hours per day fighting with your ticketing system instead of helping customers.
Your operations team copies data between three different dashboards because none of them talk to each other.
Your sales team maintains a shadow CRM in Google Sheets because the official one is "too slow."
And this costs real money.
If 100 employees waste 2 hours per day on inefficient internal tools, that's 200 hours × 5 days × 52 weeks = 52,000 hours per year.
At an average salary of $70,000, that's $1.8M in wasted productivity annually.
Here's my thesis:
Applying the same rigorous UX principles to internal dashboards can drive significant cost savings, reduce error rates, and boost team morale.
And the ROI is better than almost any customer-facing optimization.
In this post, I'll share the framework I use to design high-performing internal tools, walk through a detailed before/after case study, and show you how to calculate the business impact.
The Business Case: Why Internal UX Matters
Let's start with why companies neglect internal tools.
The Common Objections
Objection 1: "Internal users are captive — they have to use it anyway"
The reality:
- Frustrated employees build shadow systems (Excel, Notion, Airtable)
- This creates data silos and compliance risks
- Shadow systems cost more to maintain than fixing the official tool
Objection 2: "We can't afford to invest in internal tools"
The reality:
- Poor internal tools cost 10-30% of employee productivity
- That's millions in wasted salary
- One-time investment in UX pays for itself in months
Objection 3: "Internal users are technical — they don't need good UX"
The reality:
- Technical users need better UX because they use the tool 8 hours per day
- Cumulative friction adds up to hours of wasted time
- High-frequency users benefit most from optimization
The Hidden Costs of Bad Internal UX
Direct costs:
- Time waste: Tasks take 2-5x longer than necessary
- Error costs: Mistakes due to confusing UI require rework
- Training costs: New employees take weeks to learn badly designed tools
- Support burden: IT spends time troubleshooting UI issues
Indirect costs:
- Turnover: Employees leave jobs with bad tools (22% cite tools as a reason - Gallup)
- Morale: Frustration with tools impacts overall satisfaction
- Opportunity cost: Time spent fighting tools isn't spent on strategic work
Real example:
A customer support team of 50 agents using a clunky ticketing system:
- Average ticket resolution time: 8 minutes
- 3 minutes wasted navigating the UI (searching, clicking, loading)
- 37.5% of their time is wasted on UI friction
Cost calculation:
- 50 agents × $50,000 salary = $2.5M total
- 37.5% waste = $937,500 per year in lost productivity
A $200K redesign project pays for itself in 2.5 months.
The ROI of Internal UX Investment
Common improvements from internal tool redesigns:
| Metric | Typical Improvement | Business Impact |
|---|
| Task completion time | -30% to -50% | More work done per employee |
| Error rate | -40% to -70% | Less rework, fewer mistakes |
| Training time | -50% to -80% | Faster onboarding |
| Employee satisfaction | +25% to +40% | Lower turnover |
| Support tickets | -30% to -60% | Lower IT burden |
ROI example:
Investment:
- 1 designer (3 months) = $60K
- 2 engineers (4 months) = $160K
- Total: $220K
Return (first year):
- Time savings: 100 employees × 2 hours/day saved × $35/hour × 250 days = $1.75M
- Error reduction: 40% fewer errors × $50K rework cost = $20K
- Reduced turnover: 2 fewer quits × $40K recruiting cost = $80K
- Total: $1.85M
Payback period: 1.4 months
This is why internal UX is low-hanging fruit.
Phase 1: Researching the "Power User"
Internal tools are different from consumer products. Your users are:
- Experts who use the tool 8 hours per day
- Time-pressured and task-focused
- Intolerant of friction because it compounds over thousands of uses
This requires a different research approach.
Why Standard User Research Fails
Traditional interviews don't work because:
-
Experts can't articulate their workflow
- They've internalized their process
- They work on autopilot
- They don't remember what's hard anymore
-
Self-reporting is unreliable
- Users say: "It's fine, I'm used to it"
- Reality: They waste 2 hours per day on workarounds
-
Lab tests don't capture real context
- The tool behaves differently under load
- Real tasks are more complex than test scenarios
- Time pressure changes behavior
The Better Approach: Contextual Inquiry
Contextual inquiry means observing users in their actual work environment while they perform real tasks.
The process:
Step 1: Shadow users for 4-8 hours
- Sit next to them while they work
- Watch how they actually use the tool
- Don't interrupt (take notes silently)
Step 2: Ask questions during natural breaks
- "Why did you click that?"
- "What were you looking for?"
- "What's the fastest way to do X?"
- "What workarounds do you use?"
Step 3: Identify patterns across users
- Which tasks are most frequent?
- Where do users slow down?
- Where do they make errors?
- What workarounds are common?
What to Look For
High-frequency, time-critical tasks:
These are your optimization targets. If a task happens 50 times per day and takes 2 minutes, optimizing it to 1 minute saves 4 hours per user per week.
Example patterns:
Pattern 1: The "Search → Filter → Export" loop
- User searches for customer
- Applies 5 filters to narrow results
- Exports to Excel to do analysis
- Repeats 20 times per day
Optimization: Save filter presets, add in-app analytics
Pattern 2: The "Copy → Switch → Paste" dance
- User opens ticket in system A
- Copies customer ID
- Switches to system B
- Pastes and searches
- Repeats 40 times per day
Optimization: Integrate systems, add deep linking
Pattern 3: The "Undo everything" mistake
- User bulk updates 100 records
- Realizes they selected wrong filter
- No undo button
- Spends 30 minutes manually reverting changes
Optimization: Add bulk undo, add confirmation for high-risk actions
Real Example: Call Center Dashboard Research
Context: Customer support team (80 agents) using a ticketing dashboard
Research findings:
High-frequency tasks (per agent per day):
- Search for customer by phone number: 60 times
- Update ticket status: 45 times
- Add internal note: 38 times
- Escalate to specialist: 12 times
- Check knowledge base article: 25 times
Time wasters:
- Search requires 3 clicks and 2 page loads: 45 seconds per search
- Status update requires clicking through 3 dropdowns: 20 seconds per update
- Knowledge base opens in new window, requires re-search: 90 seconds per lookup
Total waste per agent per day:
- 60 searches × 45 sec = 45 min
- 45 status updates × 20 sec = 15 min
- 25 KB lookups × 90 sec = 37.5 min
- Total: 97.5 minutes per agent per day
Cost:
- 80 agents × 97.5 min × 250 days = 325,000 minutes = 5,417 hours per year
- At $30/hour = $162,500 in wasted time annually
This became our ROI target for the redesign.
Internal tools have different requirements than consumer products. Here's the framework.
Consumer products: Lots of whitespace, minimal UI, one task at a time
Internal tools: Dense information, multiple data points visible, context at a glance
Why?
Power users need to scan, compare, and decide quickly. Whitespace forces scrolling and pagination, which slows them down.
Bad (too much whitespace):
┌────────────────────────────────────┐
│ │
│ Ticket #12345 │
│ │
│ Status: Open │
│ │
│ Customer: John Doe │
│ │
│ [View Details] │
│ │
└────────────────────────────────────┘
(User needs to click "View Details" to see anything useful)
Good (information dense):
┌────────────────────────────────────────────────┐
│ #12345 | Open | P1 | John Doe | 2h ago │
│ "Payment not processing for premium account" │
│ Assigned: Sarah T. | SLA: 4h remaining │
│ Last action: Customer replied 45min ago │
│ [View] [Assign] [Escalate] [Add Note] │
└────────────────────────────────────────────────┘
(All key info visible at a glance)
The rule:
Show 80% of the information users need without requiring clicks. Reserve clicks for actions, not for viewing basic data.
Principle 2: Keyboard Shortcuts Are Mandatory
Consumer products: Mouse/touch optimized
Internal tools: Keyboard-first
Why?
Power users keep their hands on the keyboard. Reaching for the mouse 100 times per day is slow and causes fatigue.
Essential shortcuts:
| Action | Shortcut | Why |
|---|
| Search | / or Cmd+K | Most common action |
| Create new item | N or Cmd+N | High frequency |
| Save | Cmd+S | Muscle memory |
| Submit/Send | Cmd+Enter | Faster than clicking |
| Close modal | Esc | Fastest way to cancel |
| Navigate list | ↑ ↓ | Faster than mouse |
| Quick actions | 1-9 | Common bulk actions |
Advanced shortcuts:
G then H = Go to HomeG then I = Go to Inbox? = Show all shortcuts
Real impact:
In the call center dashboard redesign:
- Keyboard shortcuts reduced average task time by 18 seconds per ticket
- 45 tickets per agent per day = 13.5 minutes saved per agent per day
- 80 agents = 18 hours saved per day
Principle 3: Auto-Save and Auto-Suggest Are Non-Negotiable
Consumer products: Manual save, manual input
Internal tools: Auto-save everything, suggest everything
Why?
Power users work fast. They shouldn't have to remember to save, and they shouldn't type entire IDs/names when autocomplete can help.
Auto-save rules:
✅ Save drafts automatically every 30 seconds
- Users never lose work
- No "Are you sure?" dialogs needed
✅ Save on field blur, not on form submit
- Each field saves independently
- Users can work in any order
✅ Show "Saving..." and "Saved" indicators
- Provides confidence
- No anxiety about lost work
Auto-suggest rules:
✅ Suggest after 2 characters typed
- Reduces typing by 60-80%
- Speeds up data entry
✅ Show keyboard shortcut to select suggestion
↓ to select first suggestionEnter to accept- No mouse required
✅ Learn from user's history
- Most common selections appear first
- Personalized to each user
Example: Customer search
Bad:
Search customer:
[ ]
(User types full name "John Smith", clicks Search, waits for results)
Good:
Search customer: (Press / to focus)
[Jo ]
↓ John Smith - #12345
↓ John Doe - #67890
↓ Joan Davis - #11111
(After typing 2 characters, suggestions appear.
Press ↓ then Enter to select)
Principle 4: Error Prevention > Error Messages
Consumer products: Forgiving, hand-holding
Internal tools: Strict validation, prevent mistakes before they happen
Why?
High-speed work leads to mistakes. Fixing mistakes is expensive. Prevention is cheaper than recovery.
Prevention strategies:
Strategy 1: Inline validation
Don't wait until form submit to show errors. Validate each field as the user types.
Example:
Phone number: [555-1234-567]
❌ Must be exactly 10 digits
Strategy 2: Smart defaults
Pre-fill fields with the most likely value based on context.
Example:
Ticket priority:
[●] Medium (85% of your tickets are Medium priority)
[ ] Low
[ ] High
[ ] Critical
Strategy 3: Confirmation for destructive actions
Only for actions that can't be undone (delete, bulk update, send email to 10,000 customers).
Example:
You're about to delete 347 customer records.
This cannot be undone.
Type "DELETE" to confirm:
[ ]
[Cancel] [Delete Records]
Strategy 4: Undo for everything else
Don't ask for confirmation. Just allow undo.
Example:
✓ 52 tickets updated to "Closed"
[Undo] (Available for 30 seconds)
Principle 5: Reduce Clicks, Increase Actions Per Screen
Consumer products: One action per screen, linear flows
Internal tools: Multiple actions accessible, non-linear workflows
Why?
Power users don't follow linear paths. They need to jump between tasks quickly. Every click to navigate is wasted time.
Optimization strategies:
Strategy 1: Bulk actions
Allow users to select multiple items and perform actions on all at once.
Bad:
Select ticket → Click "Assign" → Select agent → Repeat for each ticket
Good:
[x] Select 15 tickets → Bulk actions ▼ → Assign to Sarah T.
(15 tickets assigned in 3 clicks)
Strategy 2: Quick actions on hover
Don't force users to open detail pages to perform common actions.
Example:
Ticket list:
#12345 | Open | John Doe [Assign] [Close] [Escalate]
(Actions visible on hover, no page load required)
Strategy 3: Inline editing
Let users edit directly in the list view, not in a modal or detail page.
Example:
Customer: John Doe
Status: [Active ▼] (Click to change inline)
Email: john@example.com (Click to edit inline)
Real impact:
In the call center dashboard:
- Reduced clicks per ticket from 12 → 4 (67% reduction)
- Saved 8 clicks × 10 seconds per click = 80 seconds per ticket
- 45 tickets per day × 80 agents = 1 hour saved per day per agent
Case Study: Before & After Redesign
Let me show you a real project where these principles drove measurable impact.
The Context
Company: Enterprise SaaS company with 200-person customer support team
Tool: Internal ticketing dashboard
Problem: Average ticket resolution time was 8 minutes, but 3 minutes were wasted on UI friction
Goal: Reduce resolution time by 30%
Before: The Old Dashboard
What it looked like:
┌────────────────────────────────────────────────────────┐
│ Customer Support Dashboard │
│ │
│ Search: [ ] [Go] │
│ │
│ Tickets: │
│ │
│ ┌────────────────────────────────────┐ │
│ │ Ticket #12345 │ │
│ │ Status: Open │ │
│ │ Customer: John Doe │ │
│ │ [View Details] │ │
│ └────────────────────────────────────┘ │
│ │
│ ┌────────────────────────────────────┐ │
│ │ Ticket #12346 │ │
│ │ Status: Pending │ │
│ │ Customer: Jane Smith │ │
│ │ [View Details] │ │
│ └────────────────────────────────────┘ │
│ │
│ [< Previous] Page 1 of 47 [Next >] │
└────────────────────────────────────────────────────────┘
Key problems:
-
Inefficient search:
- Required 3 clicks: Click field → Type → Click "Go"
- Loaded entire page (2-3 second delay)
- No keyboard shortcut
-
Low information density:
- Only 2 tickets visible per screen
- Had to click "View Details" for any information
- Pagination required for >2 tickets
-
No filter/sort options:
- Users had to scroll through all 47 pages
- No way to see only high-priority tickets
- No way to see only their assigned tickets
-
Hidden actions:
- Had to open ticket → Find actions menu → Select action
- 5-7 clicks per action
-
No keyboard shortcuts:
- Everything required mouse
- Slow for power users
After: The Redesigned Dashboard
What it looked like:
┌─────────────────────────────────────────────────────────────────────────┐
│ Customer Support Dashboard Press / to search │
│ │
│ ┌──────────────────┐ ┌────────────────────────────────────────────┐ │
│ │ Filters │ │ Tickets (234) Sort: [SLA ▼] │ │
│ │ │ │ │ │
│ │ [x] Assigned to │ │ #12345 | P1 | John Doe | 2h ago 4h SLA │ │
│ │ me (28) │ │ "Payment not processing for premium" │ │
│ │ [ ] Unassigned │ │ Last: Customer replied 45min ago │ │
│ │ [ ] Team Queue │ │ [Assign] [Close] [Escalate] [Note] More▼ │ │
│ │ │ │ │ │
│ │ Priority: │ │ #12346 | P2 | Jane Smith | 4h ago 1d SLA │ │
│ │ [x] Critical │ │ "Cannot access dashboard after login" │ │
│ │ [x] High │ │ Last: You replied 2h ago │ │
│ │ [x] Medium │ │ [Assign] [Close] [Escalate] [Note] More▼ │ │
│ │ [ ] Low │ │ │ │
│ │ │ │ #12347 | P1 | Bob Johnson | 10m ago 6h SLA│ │
│ │ Status: │ │ "Server error during checkout" │ │
│ │ [x] Open │ │ Last: Customer sent screenshot 5min ago │ │
│ │ [x] In Progress │ │ [Assign] [Close] [Escalate] [Note] More▼ │ │
│ │ [ ] Pending │ │ │ │
│ │ [ ] Closed │ │ (15 more tickets visible with scroll) │ │
│ │ │ │ │ │
│ │ [Save as preset] │ │ [← Previous 50] Page 1 of 5 [Next 50 →] │ │
│ └──────────────────┘ └────────────────────────────────────────────┘ │
│ │
│ Quick Actions: [1] Assign to me [2] Close [3] Escalate [?] Shortcuts│
└─────────────────────────────────────────────────────────────────────────┘
Key improvements:
1. Persistent filter panel (left rail)
- All filters always visible
- One-click filtering
- Can save filter presets
- Shows count per filter
Impact:
- Finding tickets went from 47 page loads → 1 click
- Saved 2 minutes per search
2. Dense information display
- 18 tickets visible (vs. 2 before)
- All key info at a glance (priority, customer, SLA, last action)
- No "View Details" needed for 80% of cases
Impact:
- Reduced need to open tickets by 60%
- Saved 30 seconds per ticket
3. Inline quick actions
- Actions visible on each row
- No page load required
- Keyboard shortcuts (1, 2, 3 for most common)
Impact:
- Reduced clicks from 7 → 1
- Saved 40 seconds per action
4. Keyboard-first design
/ to focus search↓ ↑ to navigate tickets1-9 for quick actionsG+I for inbox, G+M for my tickets
Impact:
- 40% of users adopted keyboard shortcuts
- Saved 20% time on average
5. Smart search with auto-suggest
- Search starts on keystroke 2
- Shows customer name, email, ticket #
Enter to select first result
Impact:
- Reduced search time from 45 seconds → 8 seconds
The Results: Measurable Impact
After 3 months of rollout:
| Metric | Before | After | Change |
|---|
| Avg. ticket resolution time | 8:20 min | 5:35 min | -33% ✅ |
| Tickets per agent per day | 45 | 62 | +38% ✅ |
| Time spent navigating UI | 3:10 min | 0:45 min | -76% ✅ |
| Error rate (wrong actions) | 4.2% | 1.1% | -74% ✅ |
| Training time for new agents | 12 days | 4 days | -67% ✅ |
| Agent satisfaction (1-10) | 4.2 | 7.8 | +86% ✅ |
Business impact:
Time savings:
- 200 agents × 2.75 min saved per ticket × 50 tickets/day = 458 hours saved per day
- 458 hours/day × 250 days = 114,500 hours per year
- At $30/hour = $3.4M in productivity gains
Capacity increase:
- 38% more tickets handled = 76 additional agents' worth of capacity
- Avoided hiring cost: 76 × $70K = $5.3M
Error reduction:
- 74% fewer errors × $120/error rework cost × 4.2% error rate × 45 tickets × 200 agents × 250 days = $470K in error costs avoided
Total annual value: $9.17M
Investment:
- 1 designer (4 months) = $80K
- 3 engineers (6 months) = $360K
- Total: $440K
ROI: 2,085% or payback in 0.58 months (17 days)
But the biggest impact?
Agent satisfaction went from 4.2 to 7.8. Turnover decreased by 31%.
Agents went from dreading the tool to praising it in reviews. That's priceless.
Ready to redesign your internal tools? Here's the playbook.
Phase 1: Audit and Prioritize (Week 1)
Step 1: List all internal tools
Make a spreadsheet:
| Tool | Users | Frequency | Pain Level (1-10) | Business Impact |
|---|
| CRM | 50 | Daily | 8 | High - Sales blocked |
| Ticketing | 200 | Daily | 9 | Critical - CS productivity |
| Inventory | 30 | Weekly | 6 | Medium - Occasional delays |
Step 2: Calculate time waste per tool
For the top 3 tools:
- Users × Hours per day × Estimated waste % × Days per year × Hourly cost
Step 3: Prioritize by ROI potential
High users + High frequency + High pain = High priority
Phase 2: Research (Weeks 2-3)
Step 1: Contextual inquiry
Shadow 5-10 power users for 4-8 hours each:
- What tasks do they do most often?
- Where do they slow down?
- What workarounds do they use?
Step 2: Identify high-frequency tasks
Track:
- Task frequency (times per day)
- Task duration (seconds/minutes)
- Error rate (% of time they make mistakes)
Step 3: Calculate optimization opportunity
For each task:
- Current time × Frequency × Users × Days = Total annual time
- If you reduce time by 50%, what's the savings?
Phase 3: Design (Weeks 4-6)
Step 1: Apply the 5 principles
For each high-frequency task:
- ✅ Can you increase information density?
- ✅ Can you add keyboard shortcuts?
- ✅ Can you add auto-save/auto-suggest?
- ✅ Can you prevent errors inline?
- ✅ Can you reduce clicks?
Step 2: Create before/after wireframes
Show:
- Old design (annotated with problems)
- New design (annotated with improvements)
- Side-by-side comparison
Step 3: Prototype high-risk changes
For any changes that affect core workflows, build a prototype and test with 3-5 users.
Phase 4: Build and Launch (Weeks 7-12)
Step 1: Build in phases
Don't rebuild everything at once:
- Phase 1: High-frequency tasks (search, filter, quick actions)
- Phase 2: Inline editing, keyboard shortcuts
- Phase 3: Advanced features, integrations
Step 2: Pilot with power users
Before full rollout:
- Launch to 20% of users (power users)
- Collect feedback
- Fix critical issues
- Then roll out to 100%
Step 3: Measure impact
Track:
- Task completion time
- Clicks per task
- Error rate
- User satisfaction
Compare to baseline metrics from research phase.
Phase 5: Iterate (Ongoing)
Step 1: Monitor usage patterns
- Which features are most used?
- Which are ignored?
- Are there new bottlenecks?
Step 2: Quarterly review
- What new tasks have become high-frequency?
- What can we optimize further?
- Are there new integrations needed?
Step 3: Continuous improvement
Treat internal tools like you treat external products:
- Regular A/B tests
- User feedback collection
- Performance monitoring
Common Mistakes to Avoid
Mistake 1: Designing Without Research
❌ Bad:
"I'll just make it look modern and clean"
✅ Good:
"I'll observe users and optimize the 5 highest-frequency tasks"
Why? Without research, you'll optimize the wrong things.
Mistake 2: Copying Consumer Product Patterns
❌ Bad:
"Let's add lots of whitespace and animations like the Apple website"
✅ Good:
"Let's prioritize density and speed over aesthetics"
Why? Consumer patterns optimize for conversion. Internal patterns optimize for productivity.
Mistake 3: Forgetting Keyboard Shortcuts
❌ Bad:
"We'll add shortcuts later if users request them"
✅ Good:
"Keyboard shortcuts are part of the MVP"
Why? Power users will never request them — they'll just keep being slow with the mouse.
Mistake 4: Asking Users What They Want
❌ Bad:
"What features do you want in the new design?"
✅ Good:
"Show me how you currently do X task"
Why? Users are experts at their job, not at UX. Observe behavior, don't ask for solutions.
Mistake 5: Launching Without Pilot
❌ Bad:
"We'll launch to all 500 users on Monday"
✅ Good:
"We'll pilot with 50 power users for 2 weeks, fix issues, then roll out"
Why? Internal tool outages are catastrophic. Pilot reduces risk.
Conclusion: The Low-Hanging Fruit You're Ignoring
Here's what we've learned:
Bad internal tools cost millions:
- 10-30% of employee productivity is wasted
- Errors, rework, and turnover compound the cost
- For a 200-person team, this can be $3-5M annually
Internal UX investments have better ROI than external:
- Payback period: 1-3 months (vs. 6-12 months for external)
- Impact: Measurable, quantifiable productivity gains
- Risk: Low (internal users are forgiving during pilots)
The framework that works:
- Research with contextual inquiry (observe, don't interview)
- Apply 5 design principles (density, keyboard, auto-save, prevention, reduce clicks)
- Measure before and after (time, errors, satisfaction)
- Calculate business impact (hours saved × hourly cost)
The opportunity:
Most companies are sitting on millions of dollars in internal tool optimization opportunities — and they're ignoring them because internal users are "captive."
But here's the truth: Internal UX is the highest-ROI design work you can do.
It pays for itself in weeks, not years.
It improves employee satisfaction more than any perk.
It's the forgotten user — but it shouldn't be.
Key Takeaways
- Internal tools cost $1-5M+ in lost productivity per year for mid-sized companies
- Use contextual inquiry, not interviews — observe power users in their actual work environment
- 5 design principles for internal tools:
- Information density over whitespace
- Keyboard shortcuts are mandatory
- Auto-save and auto-suggest are non-negotiable
- Error prevention > error messages
- Reduce clicks, increase actions per screen
- Real case study results: 33% faster resolution, 38% more tickets handled, 76% less UI friction, $9.17M annual value
- ROI payback period: 1-3 months — faster than any external optimization
- Common mistakes: Designing without research, copying consumer patterns, forgetting keyboard shortcuts
- Internal UX is low-hanging fruit — high impact, low risk, fast payback
Your next step:
- Pick your most painful internal tool
- Shadow 5 users for 4 hours each
- Identify the 5 highest-frequency tasks
- Calculate time waste (hours × cost)
- Apply the 5 principles to optimize those tasks
- Measure impact
- Enjoy your promotion when you save the company millions
Because internal UX isn't just good design — it's good business.
