
Modernizing a high-security test center workflow from legacy desktop software to a tablet-based pilot.
Modernizing a high‑security test‑center workflow from desktop to tablet.
Business context: Test‑center admissions is a high‑stakes, security‑critical workflow where identity verification must be accurate, auditable, and fast-often across the desk from a Test Administrator.
What I led: I redesigned a legacy Java desktop “Admission Manager” into a tablet‑based pilot built for tethered operation and zero Wi‑Fi environments.

A legacy desktop tool created gaps, friction, and failure risk during ID verification.
The existing workflow relied on rigid desktop patterns under extreme security constraints (no Wi‑Fi, physical tethering, and strict procedural compliance). That created instructional gaps, increased cognitive load for administrators, and elevated failure risk at the point of biometric capture.
Lead IC driving UX, UI, and integration design across partners.

Offline, tethered, audited-no connectivity assumptions allowed.

Design for the offline edge, then validate the operational reality.
I approached this as a system redesign-mapping the workflow as a chain of verifiable steps, then simplifying interaction so administrators could stay confident under pressure. I iterated with stakeholders on edge cases (reconnect, partial completion, capture quality) and designed guidance that reduces error without slowing throughput.
Make the workflow resilient: graceful reconnect, orientation‑aware UI, and clear state.

Pilot‑ready admissions experience designed for secure offline capture.
The result was a pilot‑ready tablet workflow that modernized admissions while respecting test‑center realities. It set the direction for a broader modernization path and enabled a launch‑ready plan for early 2026.
See the Outcomes panel for the pilot timeline and metric targets tracked.
Modernization is risk mitigation: design for failure modes, not best‑case flows.
The senior work here was anticipating breakdowns-connectivity constraints, capture errors, and handoff ambiguity-and designing a workflow that stays trustworthy when conditions aren’t ideal.