Visitor Management — Harsha Andukuri
Work Visitor Management

Visitor Management Reimagination

Transforming a 2-minute paper-and-kiosk ordeal into a 10-second self-serve check-in — by replacing human-dependent processes with a modular, configurable platform built around the traits of a great host.

Visitor Management — hero
My Role
Design Manager
Team
7 Engineers · 1 PM · 1 Designer
Timeline
Jan – Jun 2024
Platform
ServiceNow Workplace
The Problem

Visitors were standing in
line to fill out a form.

Visitor check-in at ServiceNow offices relied on a receptionist handing over a tablet — visitors typed their name, host, and reason into an aging web-component form, waited for an email confirmation to be issued by a human, and received a printed badge. The whole process averaged 2 minutes, backed up during peak hours, and left visitors stranded if the front desk was unmanned.

The product had a kiosk, but it was largely unused. The underlying web-component architecture couldn't support self-service flows. There was no QR code check-in, no passcode pre-registration, no wayfinding, and no way for hosts to configure what their lobby experience looked like.

Before
Existing visitor kiosk product

The existing kiosk — aging web components, human-dependent flow

The Friction Points
  • Average 2-min check-in, human required at every step
  • No self-service — visitors stranded if front desk unmanned
  • No pre-registration, QR code, or passcode capability
  • Web-component architecture blocked meaningful iteration
  • ~5 facilities tickets per day for manual corrections
The Strategic Decision

Reimagine, don't patch.

The default path would have been to add a QR code feature to the existing product. I pushed back — the underlying architecture couldn't support self-service flows, and building on a broken foundation creates debt, not value. The redesign rested on three decisions.

Touch-first components
Rebuilt on a component architecture designed for iPad and touch — replacing aging web components that couldn't support self-service.
Configurable modular system
Each capability — check-in, wayfinding, NDAs, photo — is an independent module admins can enable, disable, and reorder per location.
Vision that becomes a roadmap
A North Star prototype secured stakeholder buy-in, and directly translated into a 1-year scrum team roadmap with clear module-by-module delivery.
Traits of a Good Host
I defined a simple lens that guided every decision: what does it mean to be a great host? A great host anticipates needs, reduces friction before it happens, and makes the guest feel expected. This became the "Traits of a Good Host" framework — the shared language between design, PM, and engineering.
Who We Designed For

Five distinct visitor types shaped every design decision — from first-time guests to recurring vendors. Timothy represented the core experience we optimised for.

Primary Persona
Timothy  ·  Visitor
"Help me navigate the new office without help."
Use Cases
  • Quick, frictionless entry to the workspace
  • Understand protocols before entering
  • Navigate to meeting rooms and amenities independently
Challenges
  • Unsure of the check-in process on arrival
  • Unaware of office layout or location
Also Considered
Business Collaborator
Allison
Vendor Delivery Person
Garry
Internal Employee
Rhylan
Family
Rhylan's Family
Shared Pain Points Across All Personas
Unsure of the check-in process before arriving
Not aware of spaces or layouts inside the workspace
Finding the right entry point or door to use
Not knowing who to contact or ask for help
How I Led This

From vision to validated roadmap.

I didn't just manage the designer — I drove the initiative. Here's how I structured the work and kept the team moving with clarity.

  • 01
    Created the vision design for cross-functional buy-in
    Built a high-fidelity prototype of the reimagined experience to make the case tangible. Presented to leadership and PM stakeholders to secure the mandate for a full redesign — not a feature addition.
  • 02
    Timebox + focused research
    Set a 3-week research window to prevent analysis paralysis. I personally led chair-side sessions in the Bangalore office — watching real visitors interact with the kiosk, observing lobby dynamics, and capturing the moments where the flow broke down.
    Chair-side research at Bangalore office
  • 03
    Empathy workshop with the team
    Ran a cross-functional workshop where the team mapped the visitor journey end-to-end — from the moment someone receives an invite to when they reach their host's desk. This created shared ownership of the problem, not just the solution.
    Visitor journey map — empathy workshop User journey and intervention mapping
  • 04
    Textual workflows before wireframes
    Before any screens, I required the designer to write out the flows in plain text — every step, decision point, and error state. This caught logic gaps early and gave engineering a clear spec to react to.
    Textual workflow documentation
  • 05
    PAC (Product Advisory Council) validation
    Used coffee chat polls with the PAC customer community to validate intent and priority before committing engineering cycles. This gave us external signal that reduced internal debate about what to build first.
  • 06
    Prototype usability testing — 9 participants, 2 scenarios
    Built an HTML prototype and ran structured usability tests with 9 internal participants across two check-in scenarios. The sessions revealed specific friction points and affirmed what was working — giving us a clear punch list before engineering started.
    HTML prototype — usability test session
  • 07
    What we learned — issues found & fixed
    4 key issues surfaced and resolved before build: no explicit "Next" button (users confused by Return key), on-screen keyboard obscuring host search dropdown, redundant "reason for visit" field, and no badge pickup guidance on confirmation screen.
    "That was amazingly quick, very efficient. Couldn't be easier, as long as you have the code." — Participant 3
    "I wish it was this easy everywhere!" — Participant 8
The Solution

A modular system
built for every lobby.

The redesigned Visitor Management product is a configurable, component-based kiosk platform. Instead of a one-size-fits-all form, workplace admins can configure which modules appear, in what order, and with what content — making the system adaptable to any office environment or visitor type.

The architecture was designed so that each module could be developed, shipped, and iterated on independently — allowing the team to deliver value incrementally rather than waiting for a big-bang release.

Impact in numbers
12×
Faster check-in
2 min → 10 sec
80%
Reduction in manual
facilities tickets
17%
Adoption increase in
first 60 days post-launch
166K
Visitors processed
through the new system
The Roadmap We Shaped

What began as a focused initiative became the foundation for a dedicated scrum team: 7 engineers, 1 PM, and 1 designer, with a 1-year roadmap we helped define. I worked with the PM to sequence modules by customer impact and engineering feasibility, ensuring the team could ship and learn quickly rather than over-commit to a big-bang release.

Q2 2024
  • New component architecture
  • QR code check-in
  • Passcode pre-registration
  • Host notifications
  • Badge printing
Q4 2024
  • Visitor Invitations flow
  • Wayfinding module
  • NDAs & document sign
  • Room availability widget
Q1 2025
  • Admin config panel
  • Branding
  • Host experience
Q2 2025
  • Receptionist experience
  • Banned visitors
  • AI native host experience
Reflections

What this taught me.

Vision is a leadership tool
A prototype can do what a slide deck can't — make the future feel real. Building the vision design wasn't a design deliverable. It was a change management move.
Architecture is a design decision
Pushing for a modular system wasn't just a technical choice — it was a product strategy that gave us the flexibility to iterate and ship value faster over 12+ months.
Research builds bridges, not just insight
Chair-side sessions and the empathy workshop weren't just about finding problems — they created shared ownership across the team. People build better when they've felt the friction themselves.