Confidence at every entry

White-label visitor and contractor kiosk — intelligent check-in, on-site safety training, and seamless entry for 1024×768 touchscreen kiosks

ecoPortal — visitor management platform

Client

ecoPortal

My Role

  • UX Strategy
  • Product Design
  • Interaction Design
  • Visual Design
  • User Research

Timeline

2025

Platform

1024×768 touchscreen kiosk

Context

A visitor arrives for a meeting, stands at a kiosk — and freezes. Where to tap? A contractor late for a job is forced through a long registration — again. The receptionist doesn't know who's arrived until someone walks up to the desk.

This was the daily reality at sites using visitor and contractor management kiosks. The interface assumed digital confidence. Every visit was treated like a first visit. And behind the screen, no one was sure if the host had been notified.

The challenge: design a check-in experience that feels fast, safe, and certain — on a fixed kiosk, for users who may be anxious, rushed, or unfamiliar with touchscreens.

Core tension
How do you design a check-in experience that works in under 2 minutes — for users who may be anxious, rushed, or unfamiliar with touchscreens?
Discovery & Research

To ground the design in real-world patterns, I benchmarked three kiosk categories — airport self check-in, hospital triage kiosks, and coworking reception kiosks. Each revealed a different set of strengths and risks for the kiosk context.

Airports
Linear flow, one action per screen. Clear success messages, extensive use of icons and color status. Risk: inexperienced users stuck on poorly explained fields.
Hospitals
Identity and contact validation with required fields. Simple text, step-by-step instructions. Risk: anxious patients may abandon if too many steps.
Coworkings
Visitor selects host/company, host is notified. Welcoming messages, immediate feedback. Risk: duplicate names or missing host lists cause frustration.
Comparative benchmarking overview — airport, hospital, coworking kiosk patterns
Comparative benchmarking — patterns extracted from airport self check-in, hospital triage, and coworking reception kiosks.
Personas

Quick personas centered on kiosk use — pragmatic representations to guide UX decisions, not full marketing profiles.

Visitor
Arrives for meeting, interview, event
Goals
Quick check-in, notify host
Frictions
Unsure if host was notified, fear of email error
Digital Skills
Low–Medium
New Contractor
First time at location
Goals
Register + complete training to gain entry
Frictions
Too many fields, time pressure, long training
Digital Skills
Low
Returning Contractor
Already registered + trained
Goals
Quick check-in, skip repeated steps
Frictions
Forced to repeat sign-up or training
Digital Skills
Medium
Receptionist / Host
Awaits visitors or contractors
Goals
Be notified at the right time
Frictions
Visitor lost, no arrival confirmation
Digital Skills
High
Pain Point Mapping

Every step in the kiosk journey carried potential friction — from initial hesitation at the home screen to uncertainty after submitting data. Each pain became a design implication.

Flow StepPotential Pain / FrictionsUser ImpactDesign Implication
Start (home screen) Unsure whether to choose Visitor or Contractor Anxiety, errors Large and clear options
Visitor Form Unclear mandatory fields (host optional, email required) Errors, rework Clearly differentiate required vs optional
New Contractor Form Too many fields (company, reason, host) Drop-off, frustration Highlight essentials, group optional
Existing Contractor Detection Email mismatch / typo not recognised Flow repetition Inline validation
Training Long, technical text, hard to understand Skipping reading, abandonment Break into simple checkboxes
Final Confirmation No visible host notification Insecurity, queues Strong success message + visual icon
Fixed 1024×768 Too much content for small screen Scrolling, poor readability One action per screen, large typography, generous spacing
Research synthesis — pain points, personas, and design implications
Research synthesis — connecting user pains to design implications across the full kiosk journey.
Jobs To Be Done

To keep the design anchored in real user needs, I framed the core interactions as JTBDs — capturing the situation, motivation, and desired outcome for each kiosk scenario.

When I...
arrive at the building as a visitor
I want to...
sign up easily so my host knows I am here
When I...
am a new contractor on-site
I want to...
register and complete training on the spot so I can start working without delay
When I...
have already completed training
I want to...
avoid repeating it so I save time and frustration
Hypotheses

With the pain points mapped, I turned each friction into a testable hypothesis — connecting design decisions to expected outcomes.

Pain / FrictionHypothesis of SolutionExpected Impact
Visitor unsure where to click Clear start screen with 2 large buttons: Visitor or Contractor Fewer errors at start
Confusing optional fields Distinguish required from optional fields Less frustration, faster completion
Returning contractor not recognized Use email as main ID, with inline validation Avoid unnecessary repetition
Training too long / dense Convert items into clear mandatory checkboxes Faster completion, higher clarity
No final confirmation Success screen with strong message + icon + "Host notified" Increased confidence, less anxiety
Small screen (1024×768) One action per screen, large type Better readability, less scrolling
Heuristic Checklist

I adapted Nielsen's heuristics for the kiosk context. Three principles drove the design decisions more than any others.

Visibility of system status
Show progress clearly: check-in → sign-up → training → done. Confirm visibly when the host is notified.
Lack of confirmation increases user anxiety.
Error Prevention
Inline validation (email required, mobile optional). "I Acknowledge" button enabled only after all checkboxes are marked.
Silent errors lead to incomplete data and wasted time.
Recognition vs. Recall
Users shouldn't recall field formats — use input masks and clear labels. Training as self-explanatory checkboxes, not long text.
Memory load causes frustration and abandonment.
User Flows

The kiosk experience branches into distinct flows, each optimized for a specific entry scenario. Below is the complete flow architecture.

ecoPortal — complete user flow architecture
Complete user flow architecture — visitor check-in, contractor registration, returning detection, training gate, and offline fallback.
Key Decisions

Three structural decisions shaped the kiosk experience — each one a deliberate trade-off between safety, speed, and simplicity.

DecisionRejectedChosenWhy
Flow structure Single flow for all users Branching flows by user type Visitors and contractors have fundamentally different needs — one size fits none
Returning users Require full registration each visit Email-based recognition with inline validation Returning contractors save time and avoid frustration
Training format Long text with a single checkbox Modular checkboxes with clear acknowledgments Breaking training into verifiable items increases comprehension and compliance
The Solution

The final design is a streamlined, intuitive kiosk flow that redefines the check-in experience by combining speed, compliance, and clarity in a single touchscreen interface.

Visitors complete check-in in under a minute — select their role, enter contact details, and receive immediate confirmation that their host has been notified. Contractors follow a dedicated path that detects returning users, validates training status, and enforces safety compliance without unnecessary repetition.

The interface adapts to the kiosk's physical constraints: one action per screen, large typography readable from 1 meter away, and generous touch targets for users of all digital skill levels.

Final screens — the complete check-in experience, from home screen through confirmation.
Key Deliverables
Kiosk interaction system — one action per screen, large touch targets, 1m readability
User flow architecture — branching paths for visitors, new contractors, returning contractors
Pain-to-hypothesis framework — every friction mapped to a testable design response
Offline fallback mode — resilient check-in without network connectivity
On-site safety training — modular compliance checkboxes with acknowledgment validation
Kiosk-specific prototyping — 1024×768 constraints, 1m readability, dark-mode interface
Impact
<2
Minutes per check-in interaction
1
Unified flow replacing fragmented manual processes
Friction for returning contractors
Reflection

I'd test with actual kiosk hardware earlier. Screen glare, touch responsiveness, and reading distance changed a lot of assumptions that looked fine in Figma.

The biggest lesson was designing for anxiety. Visitors and contractors at a reception kiosk are often uncertain, rushed, or unfamiliar with touchscreens. Clear progress indicators, immediate confirmation, and forgiving input validation aren't nice-to-haves — they're the core of the experience.