AI
Enterprise UX · AI Agent Design · 2022–Present
OTTO
Company
ServiceNow
Role
Staff Product Designer
Timeline
2023 – 2025
Scope
Enterprise · Keynote Demo · Global
01

The Problem

Frontline operations managers at enterprise companies like FedEx run on 6–8 separate systems — HR for headcount, scheduling tools for coverage, compliance dashboards, email threads. When a surge event hits — Mother's Day, peak season, a last-minute volume spike — they manually cross-reference all of it, build their own analysis, and make high-stakes staffing decisions without a complete picture. The operational cost: understaffing, compliance gaps, and missed SLAs.

ServiceNow's bet was to build an AI-powered employee workspace that eliminates that gap entirely — not a chatbot bolted onto existing tools, but a new surface built around an AI agent that knows your context, runs multi-step analysis proactively, and turns insight into action. I was part of a large, cross-functional product team brought in to shape that vision from strategy through pixel — defining the interaction model for how this new kind of AI agent should behave.

THE PROBLEM
6 systems. 6 logins. Zero shared context.
◎ Frontline Manager
IT Ticketing
Access · Provisioning
Separate login
Workday HR
Headcount · Benefits
Separate login
Scheduling
Shifts · Coverage
Separate login
Email / Chat
Decisions · Approvals
No audit trail
Reporting
Excel · Dashboards
Stale data
Compliance
Certs · Audits
Separate login
Avg. 20 min lost before every decision
Data reconciled manually across systems
Zero shared context between tools
High-stakes calls made on stale data

The fragmented operations stack a FedEx distribution manager navigates daily — each system a separate login, a separate mental model, and zero shared context

02

Research & Discovery

We partnered closely with a dedicated UX research team who ran both quantitative and qualitative studies — diary studies with frontline managers, contextual inquiry sessions, and large-scale surveys across enterprise accounts. My role was to work directly alongside research: shaping the study questions, sitting in on sessions, and translating findings into design direction fast enough to keep pace with the product.

The pattern that emerged was consistent: the work itself wasn't the hard part. The 20 minutes before it — hunting for context across systems, reconciling stale data, rebuilding the picture from scratch — was where the day fell apart. Highest-stakes decisions (surge planning, staffing gaps, compliance deadlines) happened exactly when managers had the least time to dig.

"The job-to-be-done wasn't 'manage my team.' It was 'know what needs my attention right now, across every system, without having to ask.'"
RESEARCH METHODS
How we found the truth
Diary Studies
Frontline managers logged decisions, tools used, and friction points over two-week periods
Quantitative · 3 enterprise accounts
Contextual Inquiry
On-site shadowing sessions observing real shift handoffs and surge planning workflows
Qualitative · 12+ sessions
Large-Scale Survey
Cross-account survey quantifying time lost, tools used, and decision confidence scores
Quantitative · N=200+
My Role
Shaped study questions alongside the research team, sat in on sessions, and translated findings into design direction in the same sprint they were delivered.
03

Design Process

My contribution spanned strategy and execution. At the strategy level, I pushed for anchoring the entire surface around a single design question: what does a manager need to see at 7am before their shift starts? That framing shaped the Home dashboard as a proactive briefing surface — an Inbox of pending decisions, a contextual alert card surfacing the highest-priority business signal, and a Canvas for personal context they'd actually use daily.

At the execution level, I was deep in the pixels — prototyping the Otto agent's conversational thread, designing the step-transparency model (how the AI shows its 5-step reasoning in real time without overwhelming the user), and working through the visual language that separates "Otto thinking" from "Otto acting." Research validated our iterations through six rounds of usability testing; I partnered with the research team to turn findings into pixel-level decisions the same week they came in.

Left: Early information architecture explorations — mapping the "7am brief" and what proactive surface hierarchy earns manager trust on day one. Right: Otto's agentic step model — showing AI reasoning in-thread without overwhelming the user with process.

04

Key Design Decision

The hardest design problem on the team: Otto needed to go from answering questions to taking action — submitting HR requisitions, scheduling 35 interviews, blocking calendars — without losing user trust. The principle we landed on: AI can act, but never silently. Every autonomous action surfaces as a structured card with full justification, a confirmation step, and a clear undo. Users stay in control. Otto handles the execution.

I drove the visual framework for this — designing two distinct modes in a single thread: "Otto thinking" (analysis, reasoning, data retrieval shown as a collapsible step list) and "Otto acting" (a structured action card with context, data, and a single confirm button). Getting that distinction legible at a glance was the core design challenge, and it required close iteration with research to validate that users actually felt in control — not just looked at it and assumed they were.

KEY DESIGN DECISION
Otto Thinking vs. Otto Acting AI can act — but never silently
◐ Otto Thinking
Analysis, reasoning, data retrieval — shown as a collapsible step list. Users can scan or skip.
O Otto ✓ Thought for a moment · 5 steps
  • Checked seasonal worker status at Memphis Hub
  • Reviewed surge plan for Mother's Day
  • Pulled right-sort staffing coverage
  • Checked IT device and access provisioning
  • Reviewed Dock C capacity and trailer allocation
Demand is up 58% to 52.4K. Staffing is 37% short — 25 FTE. You have 3 days to close the gap or risk missing demand. I've identified the gap, drafted a hiring plan, and flagged high-risk days.
◆ Otto Acting
Structured action card — full justification, one confirm button, clear undo. User approves. Otto executes.
Staff Requisition — Seasonal Warehouse Associate High priority
Location
Memphis Hub (MEM)
Headcount
25
Start date
May 8, 2026
Cost
$28,400
AI justification: Demand projected 58% above baseline (52,400 vs. 33,000). Current staffing covers 63% of projected volume. Hiring 25 closes the gap and maintains 99.2% on-time delivery.
Confirm & Submit Edit Undo

The "Otto Acting" pattern — a requisition card auto-generated with full justification, priority, headcount, and a one-tap confirm. The user approves the decision. Otto executes it end-to-end.

05

Final Design

The workspace was demoed live at ServiceNow Knowledge — the company's flagship annual conference — as the platform's vision for AI-powered work. A FedEx distribution manager asks Otto one question: "How are we trending for Mother's Day?" From there, Otto runs a full surge analysis, surfaces a 37% staffing gap across the Memphis hub, auto-generates an HR requisition for 25 seasonal workers with full business justification, schedules 35 candidate interviews, and assembles a personalized Canvas — zero manual data entry, under 3 minutes.

What the audience saw wasn't a prototype. It was the gold standard for how AI-powered work should feel — the shipped interaction patterns our team built, validated through research, and pushed to production. Every card, every step list, every confirm action on that stage was a design system call we made together.

06

Outcomes

Knowledge
Featured in ServiceNow's flagship conference keynote demo
Platform
Agentic UX patterns adopted across the full ServiceNow product suite
0→1
First AI workspace built on ServiceNow — no prior design system to reference

The agentic interaction model our team designed — Otto's step-transparency, the "acting vs. thinking" visual distinction, the confirm-before-execute pattern — became the gold standard for how AI agents behave across the entire ServiceNow platform. What started as a visionary demo became the design language for an AI product suite used by hundreds of enterprise customers globally.