Decision 01
Test the environment before the candidate is committed.
System and connectivity checks expose what needs attention while there is still time to recover, reschedule, or choose another route.
OnVUE Remote Proctoring·Cross-device service · 0→1 → scale
A high-stakes check-in has to survive every handoff.
As Founding Product Designer, I led the 0→1 experience that became OnVUE and continued stewarding it as desktop, mobile web, native mobile, and human support became one synchronized service.
// RoleFounding Product Designer · multi-year stewardship
// AudienceCandidates · greeters · proctors
// TeamProduct · engineering · operations · accessibility
// Timeframe0→1 launch + years of platform evolution
// MaturityShipped, scaled global platform
// Signal300% growth · 2.3M exams annually
// Three product decisionsInterface first
Three decisions held the cross-device flow together.
Coordinate system tests, identity, room capture, queueing, and recovery across desktop and mobile under exam-day pressure.
Decision 02
Design the handoff as one product state.
QR, SMS, mobile web, and native capture share context.
Decision 03
Make recovery part of the primary journey.
Failed connectivity, incomplete capture, and accessibility needs lead to explicit choices instead of a dead end or a silent restart.
// UI evidenceAdditional product evidence
More of the cross-device check-in
Mobile identity and capture states that complete the desktop-to-phone journey.
Evidence and outcome
Stewardship turned a launch flow into a durable service.
The redesigned check-in contributed to approximately 25% fewer failures. The platform supported 300% growth and now serves 2.3 million exams annually.
// ReflectionLimits and next questions
Years of evolution make attribution important.
Tradeoff
Each new handoff adds failure risk.
Evidence boundary
The public case compresses years of platform evolution and cannot attribute every later feature to the founding design phase.
Next test
Keep reducing recovery time and measure where candidates still need a human to re-establish shared context.
// Protected deep caseDecisions · evidence · edge cases
See the evidence behind the decisions.
Includes the role breakdown, evidence, edge cases, outcomes, and lessons.