Case Study · 01
Global Visitor Management System
A global enterprise visitor platform supporting multi-country policies, approval workflows, visitor registration, and workplace security operations.
Role
Product Manager
Timeline
2023 — 2025
Scope
Global visitor system, internal workplace tools, compliance workflows
Team
Engineering, Workplace Security, Legal & Compliance, Regional Operations
Background
Context
As the company expanded globally, visitor management became increasingly fragmented across regions, workplace policies, and compliance requirements. Local teams needed flexible configuration, while employees expected a simple and consistent visitor invitation experience.
Why it mattered
Problem
Fragmented regional policies — different countries and workplaces had different visitor requirements.
High operational configuration cost — policy changes required heavy manual configuration and repeated downstream support.
Inconsistent user experience — visitor invitation flows varied across regions, leading to confusion and lower efficiency.
What I owned
My Role
I owned the product strategy, requirement definition, cross-functional alignment, and rollout planning. I worked with engineering, workplace security, legal/compliance, and regional operation teams to translate complex policy requirements into configurable product capabilities.
How we built it
Solution Design
Unified Visitor Flow
Employee creates invitation → Visitor receives invite → Visitor submits required information → Approval triggered if needed → QR code issued → On-site check-in.
Policy Configuration Framework
Country / Region → Workplace → Visitor Type → Visit Purpose → Approval Rule → Duration Limit → Quota Rule → Minor Declaration / Disclaimer.
CN & Non-CN Experience Alignment
The system was redesigned to support a unified visitor experience while allowing region-specific compliance rules to be configured independently.
Admin-Side Policy Rollout
Back-office tools allow regional teams to manage workplace-level rules, configure approval logic, monitor quota usage, and maintain policy settings without changing the core visitor flow.
What changed
Before / After
Before
Region-specific flows were managed separately.
After
Unified H5 visitor experience.
Before
Policy changes required manual configuration.
After
Configurable policy and approval framework.
Before
Visitor purpose and approval logic were inconsistent.
After
Standardized visitor purpose and remarks fields.
Before
Non-CN experience lagged behind CN flow.
After
CN and non-CN flows aligned under one product structure.
Outcomes
Impact
95%
Reduction in downstream configuration effort
~2s
Single visitor creation time
70+
Country-specific compliance policies supported
4.85/5
Visitor satisfaction score
What I'd carry forward
Learnings
This project taught me that enterprise product design is not only about simplifying user flows, but also about absorbing policy complexity into a scalable system architecture. The key challenge was to keep the user-facing experience lightweight while making the backend flexible enough to support regional compliance differences.