VAX Translate
Overview
VAX Translate is a user-friendly application that aims to address needs and pain points faced by the Seattle and King County Public Health workers during vaccine translation processes.
Challenge
Health officials lack the proper tools to efficiently translate and input public vaccination records into their system, leading to low health assistance turnover time and public restrictions.
My Approach
Empathize
I began by developing a User Persona and User Journey to empathize with the target user and the problem space.
User Persona
User Journey
Define
After taking on a user persona, we were able to prepare for a preliminary interview with members from the Seattle and King County Public Health to confirm our projected pain paints
We found that user pain points lied in:
Accuracy of health document translations
Efficiency of task completions
Ideate
From a competitive analysis, we were able to ideate requirements needed for VAX Translate
Competitive Analysis
The Spanish Group | Sure Translation | VAX Translate | ||
|---|---|---|---|---|
Availability | Free | $0.10 per word | $18 per page | Free |
Turnaround | Under 30 seconds | 1 day | +1 Days | Under 30 seconds |
Features |
|
|
|
|
General Requirements for VAX Translate:
Accurate health document translations
Efficient inputting and translation methods
Auto-population of fields from translated documents into their integrated system
I then developed a quick Feature Map to build a quick Mental Model of the site.
Feature Map
This was followed by quick mid-level wireframes to share with the team for option analyses and to ensure feature concordance.
Batch uploads
Translation
Overlayed translation option which includes a "VAX Score" that would predict the accuracy of specific translations.
Prototype
I created an interactive flow to present an overview of how VAX Translate would operate. While not common practice, developing a Mid-Fi Wireframe as a point of reference enables the design and development teams to work in parallel. This approach maximizes team-task efficiency by:
Identifying usability or technical constraints early, allowing for quicker iterations and adjustments during the process.
Allowing developers to start building foundational components without waiting for a final design hand-off.
Providing a shared visual reference for team alignment on layout, functionality, and user flows, while reducing misunderstandings.
Testing & Iteration
After testing internally, the prototype took a turn to focus on a quick MVP design I developed that focused on the Phase 1 main features, which highlights the critical path and basic functions that need to be implemented. This is also the currently deployed version.
What's Next?
We are currently in the middle of an iteration phase. After this, a stakeholder meeting will ensue. Checkback for updates!
