Decision 01
Keep the candidate record visible before capture.
Administrators confirm the right person and test context before entering a biometric state that can be difficult to reverse.
Biometric Admissions·Native tablet · hardware-aware trust workflow
I had to make palm capture work across a person, a tablet, the biometric system, and an unreliable network.
I designed a tablet-based admissions direction for palm enrollment and matching, including capture guidance, success, failure, retry, QR/PIN handoff, device handling, and offline constraints.
// RoleProduct Designer · native interaction
// AudienceTest administrators · candidates
// TeamProduct · engineering · hardware vendor · field staff
// TimeframeTechnical direction + in-person usability
// MaturityPrototype and interaction-design evidence
// SignalPilot approved as next gate · not completed
// Three product decisionsInterface first
Three decisions shaped the palm-capture flow.
Guide repeatable biometric capture and recovery across hardware, identity, local server, cloud, and network constraints.
Decision 02
Turn positioning into visible progress.
Live guidance explains palm placement and capture quality so administrators can correct technique instead of guessing why the device has not advanced.
Decision 03
Design failure as a recoverable state.
The interface distinguishes capture failure, device or configuration problems, retry, and alternate handoff so the administrator knows what can be fixed at the station.
// UI evidenceAdditional product evidence
More of the palm-capture flow
A continuous capture sequence showing guidance, acquisition, validation, and recovery states.
Evidence and outcome
Field research changed the physical setup as well as the UI.
In-person testing showed that tablet placement, training, and capture technique affected success as much as screen wording. The work supports a technical design and prototype direction.
// ReflectionLimits and next questions
The pilot still had to prove the physical setup.
Tradeoff
More guidance can slow an experienced administrator.
Evidence boundary
The next pilot was approved, but a completed pilot and production performance are not claimed.
Next test
Validate the end-to-end flow with production-like hardware, offline handling, and repeat capture conditions.
// Protected deep caseDecisions · evidence · edge cases
See the evidence behind the decisions.
Includes the role breakdown, evidence, edge cases, outcomes, and lessons.