← All work
Case study · U.S. telecom company · Nov 2024 – Jan 2025

Staff and customers were both avoiding the kiosk. The fix wasn’t the screen.

A mandatory ID kiosk was meant to speed up store visits. Instead, staff skipped it at peak hours and customers walked straight past it. I showed the team it was a trust problem, not a usability one, and the redesign we piloted halved peak queue wait.

My roleUX Research Consultant, embedded with Retail Operations & Store Experience
TimelineNov 2024 – Jan 2025
Scope20 pilot stores, U.S. retail network
MethodsInterviews, store observation, staff shadowing, service blueprint
Customers waiting at a telecom store check-in area with an ID verification kiosk
−50%
Peak queue wait, from about 2 minutes to 1
~100%
Customers checking in on their own, up from 3–4 a day
20
Pilot stores running the redesigned flow
S

SituationA kiosk everyone was quietly working around

A national telecom provider had rolled out a kiosk at the entrance of its stores. Customers had to verify their identity on it before speaking to anyone. New privacy regulation was pushing for stricter ID checks, and the internal hypothesis was simple: if customers identify themselves first, agents have less work and service gets faster.

That isn’t what was happening on the shop floor:

“Sometimes I just stand there for 15 minutes before someone even knows I’m here.”Customer, in-store interview
T

TaskFind out why, and fix the right thing

I was brought in to improve the kiosk experience. Before planning any study, I rewrote the brief. Low adoption on its own told us nothing about the cause, and a usability study would only ever find usability problems.

The brief I was given

How do we improve kiosk usability?

The question I proposed

How might we design identification that balances operational efficiency, privacy trust and real retail behaviour?

That shifted the work from tweaking an interface to redesigning a workflow, and it widened who I needed to hear from: customers, store agents, store managers, retail operations and compliance.

A

ActionResearch the system, not the screen

01Mapped the whole identification journey

To see how policy, staffing and customer behaviour interacted, I mapped the service end to end, from walking in to leaving, across what customers do, what agents do, and the policy and systems behind them.

Service blueprint: five stages from store entry to service completion, with pain points, KPI impact and opportunities.
Service blueprint: five stages from store entry to service completion, with pain points, KPI impact and opportunities.

02Talked to people and watched the floor

11Moderated interviews with urban store visitors of mixed ages and backgrounds
Peak + quietIn-store observation at busy and quiet hours
ShadowingFollowed agents to see their workarounds first-hand
StakeholdersInterviews with retail ops, compliance and store managers

Interview sessions used think-aloud on short kiosk tasks, so I could hear hesitation as it happened rather than a tidied-up version afterwards.

Session structure: pre-test survey review, think-aloud, task scenarios, post-test interview.
Session structure: pre-test survey review, think-aloud, task scenarios, post-test interview.
See the full research plan (11 steps)
From understanding the problem to presenting insights: planning, execution and delivery.
From understanding the problem to presenting insights: planning, execution and delivery.

03Found three teams measuring three different things

The stakeholder interviews explained the store behaviour. Each team was succeeding on its own metric, and nobody owned the customer’s experience in between. High kiosk adoption was being celebrated even when customers felt forced into it.

Retail operations wanted throughput, compliance wanted verification accuracy, product wanted kiosk adoption.
Retail operations wanted throughput, compliance wanted verification accuracy, product wanted kiosk adoption.
Retail operations → throughput

Pressure for speed meant agents skipped the kiosk whenever the queue grew.

Compliance → verification accuracy

One rule for every store, regardless of traffic or what the customer came in for.

Product → kiosk adoption

A number that went up even when people used the kiosk reluctantly.

04Heard why customers resisted, and when they didn’t

It felt like a waste of time

People didn’t see why they had to check in before talking to someone, especially in a quiet store.

“If the store is empty, why should I enter my details? It’s faster to just talk to someone.”
Privacy was misunderstood

Customers weren’t sure why their data was needed, how it would be used, or whether a public device was safe.

“I thought entering my phone number might mean getting marketing calls later.”
They trusted people more than machines

Showing ID to a person felt safer. The kiosk removed the human at exactly the moment people wanted reassurance.

“If I have to show ID, I’d rather show it to a person.”
But at busy times, it made sense

When queues were long, people valued the speed and not losing their place, and many wanted to be notified instead of waiting.

“If it’s busy, this makes sense. I know I won’t lose my place in the queue.”
See the affinity map these came from
Affinity map of barriers and positive perceptions, built from interview quotes.
Affinity map of barriers and positive perceptions, built from interview quotes.

Customers also judged the kiosk against systems they already knew and trusted: token screens, a number on their phone, paper slips at government offices. None of those asked for personal details up front.

Token numbers on a screen
Token numbers on a screen
A queue number on your phone
A queue number on your phone
A paper token slip
A paper token slip
Waiting until you’re called
Waiting until you’re called
The core insight

Identification isn’t a task. It’s a trust transaction. When a visit feels urgent or complex, people want a human. When it feels routine and predictable, digital works. The system failed because it assumed one context for everyone.

05Turned findings into a new way of working

Each problem became a specific recommendation, traced back to what people actually said.

From problem to participant quote to recommendation.
From problem to participant quote to recommendation.
Four recommendations: a dual-path workflow, clear privacy messaging, a peak-hour switch for managers, and assisted onboarding.
Four recommendations: a dual-path workflow, clear privacy messaging, a peak-hour switch for managers, and assisted onboarding.

The biggest change was replacing one mandatory route with two. At peak hours the fast kiosk path is the default; when the store is quiet, customers choose between the kiosk and an agent, after a short explanation of why ID is needed.

Before: a forced kiosk-first flow. After: an adaptive dual-path flow with a peak-hour switch, a privacy step and a human option.
Before: a forced kiosk-first flow. After: an adaptive dual-path flow with a peak-hour switch, a privacy step and a human option.

Before: demand first, explain never

“Check in”, with no reason given
“Check in”, with no reason given
ID requested straight away
ID requested straight away

After: choice, reassurance, then a token

A choice: quick check-in or an agent
A choice: quick check-in or an agent
Privacy first, with an anonymous token option
Privacy first, with an anonymous token option
Why is ID needed? Answered plainly
Why is ID needed? Answered plainly
A token number, not a name called out
A token number, not a name called out
Checked in, with an estimated wait
Checked in, with an estimated wait
Check in on your phone and wait elsewhere
Check in on your phone and wait elsewhere

Store teams got the other half of the system: a live view of who was waiting and how busy the store was, so managers could switch the kiosk into peak mode when traffic rose.

Agent tablet: live store status and waiting customers.
Agent tablet: live store status and waiting customers.
Manager dashboard: real-time traffic and estimated wait.
Manager dashboard: real-time traffic and estimated wait.
R

ResultFaster stores, and a different definition of success

−50%Peak queue wait, from about 2 minutes to 1
~100%Customers completing check-in on their own, up from 3–4 reluctant customers a day
20Pilot stores running the adaptive flow
A quick self check-in when the visit is routine.
A quick self check-in when the visit is routine.
Agents introducing the kiosk to first-time visitors.
Agents introducing the kiosk to first-time visitors.
Help close by, so nobody gets stuck.
Help close by, so nobody gets stuck.
✦

ReflectionWhat I’d carry forward

Low adoption is a signal, not a verdict. Agents and customers weren’t being difficult. They were making sensible choices inside a system that didn’t fit their day. In operational products, the experience can’t be separated from the policy and workflow around it.

What I’d do differently: include lower-literacy users and non-English speakers from week one. Accessibility gaps surfaced late in this project, and I now plan for them from the start.

Field researchService blueprintingStakeholder alignmentReframing the briefDefining success metricsPrivacy and trustService design

Client data is anonymised. To respect the telecom provider’s branding and intellectual property, all kiosk screens and store photos are re-imagined, depersonalised illustrations created with AI. The research, process and outcomes are real.