AI PRODUCT DESIGN · FORTUNE 50 TELECOM

The AI Was Smart. The UX Was Wrong.

Role: Lead Designer

Team: 9 designers (3 on AI POS)

Scope: Retail Point-of-Sale System

The AI Was Smart. The UX Was Wrong.

Challenges

2%

Adoption rate on AI features

200+

AI UI components built

0

Representatives using it voluntarily

Two percent. That's how many retail employees were actually using the AI-powered features in a Fortune 50 company's point-of-sale system. Not because the AI didn't work — the AI was technically excellent. The problem was that nobody wanted to use it. Representatives hated the tool. When adoption stayed near zero, leadership made it mandatory. Representatives responded by opening the tool to satisfy the requirement, then immediately closing it. My job was to fix that — not by building better AI, but by designing an experience that respected how these people actually worked.

From Push to Pull

THE CORE SHIFT

The old model pushed AI at representatives. Recommendations appeared unsolicited. The system auto-added items to customer carts. The representative was a passenger. We flipped this entirely — the new model let representatives pull AI assistance when they needed it.

We used progressive disclosure throughout. The first layer was a contextual suggestion the rep could tap to explore, ignore, or modify. If they wanted more detail, they could go deeper. If they didn't, the suggestion stayed out of the way — reducing cognitive overload during fast-paced customer interactions.

From Push to Pull

BEFORE

System builds the cart for the rep. AI auto-adds items. Representative has no control over the flow.

AFTER

System says: let's build this together. Rep chooses which AI tools to use, and when.

Simplified AI Outputs

WHAT CHANGED

Complex bill analysis and product matching turned into clear, actionable guidance. Outputs defined by customer inputs. Contextual agentic prompts based on each unique customer.

DESIGN PRINCIPLE

“AI assists, employee decides.” Every pattern reinforced human control. Override by deleting, clearing, changing inputs. Supervisor escalation built into the flow.

Progressive disclosure

Slide 1

The AI UX Framework

WHAT I BUILT

I didn't just redesign one product. I built a framework — principles, design patterns, and approximately 200 UI components — specifically for AI interactions in retail. The core principle: AI assists, employee decides.

Every pattern reinforced human control. Recommendation cards could be dismissed. Suggestions could be overridden. The AI never took an action the representative didn't explicitly approve. All standardized and reusable across any AI feature in the POS system — so when new AI capabilities were added, the team had a playbook.

The Tiger Team: Testing in the Real World

HOW WE VALIDATED

We didn't trust lab testing. I coordinated a Signal Capturing Tiger Team — designers collaborating directly on front-end React components, deploying micro-flows to production and observing how they performed in actual stores.

Bill optimization was our proving ground. It's one of the top reasons customers visit stores — high stakes, high visibility. We deployed it first, observed it, iterated, and used its success to earn permission for the next feature. Each micro-win built the case for the next expansion.

The Tiger Team: Testing in the Real World

Outcomes

Voluntary Adoption

Reps went from closing the tool to actively using it during customer conversations

200+ Components

AI UX framework standardized across the entire retail system

Sentiment Shift

"I feel like the Verizon team is finally understanding how we work"

PM Method Shift

Micro-experiment approach adopted across product for scoping new features

I feel like the Verizon team is finally understanding us and the way we work.

Retail Representative

AI adoption fails at the UX layer, not the ML layer. Give users control. Let them pull, not push.

More Case Studies