Public health communicators needed a tool they could trust with accuracy and speed, so I helped build an AI platform trained only on verified health data instead of the open internet.
Previously, we built an AI content creation platform called VeriSci.AI (now called AKARI; see case study here) for our client, Science To People. With secured funding from our previous work, Science To People sought us out to scale their operations and create their first white label product, VeriComms, for the Public Health Communications Collaborative (PHCC).
“Messages that are simple, clear, and accurate can save lives.”
Public Health Communications Collaborative, About Us
The scope was more complex this time around, with a larger stakeholder team, more product ambiguity, and confidentiality constraints. As part of the UX design team, I shaped the vision of this product and was responsible for all design deliverables for handoff to the outsourced dev team for implementation. From cross-functional collaboration with 5 other teams of 20+ members, the client, and indirect stakeholders, we achieved an excellent SUS usability score of 75.7, client satisfaction rating of 95%, and 4 product changes to strengthen client market positioning.
Public health communicators face challenges in information overload, accuracy, approval bottlenecks, and tool fragmentation, making it difficult to deliver timely, trustworthy public communications.
To kickstart our project, we spoke with our indirect stakeholders at PHCC for better clarity and alignment between our team and their organization. From the interview, we learned that PHCC:
We also gathered the following insights after conducting a prioritization activity with them to understand the more pressing challenges and problems they had:
We also discussed with the client about their business goals for this white label product. Based on our conversations, we had to quickly adapt and pivot our focus based on some of the criteria and constraints they shared with us.
In essence, the client requested for us to:
From our previous work of creating VeriSci.AI, the client made substantial updates with the outsourced developer team to build AKARI. We looked closely at the heuristics of AKARI so we can build VeriComms based on its key features. Things we kept in mind for the audit included:
From our extensive audit of AKARI, we got the following takeaways to inform how VeriComms could look like:
Content customization features should be grouped based on their framework, workflows, and functions.
Empty states should be optimized to clearly guide users forward with direct actions that improve feature discovery.
Avoid cognitive overload by identifying areas with complex interactions that can overwhelm users and hinder task completion.
A more organized, neutral color palette would provide better structure, with accent colors highlighting key actions.
After understanding the business side, we first conducted 2 rounds of structured user interviews with 27+ public health professionals to hear their pain points and obstacles, particularly if and how AI tools can assist them with their work tasks and processes. Here's what they felt:
After the 2 rounds, we then conducted an additional round of user interviews with a prioritization activity to rank certain features and challenges for public health professionals. From this, the top priorities in the users' perspective were:
To ensure that we create a practical product for public health workers, we built and refined our customer lifecycle funnel based on user interview insights to envision how we can understand, attract, and personalize customer experiences. We then created a CX flow chart for current public health communicators to tailor touchpoints based on the customer stage they are in.
With these 2 deliverables, we determined that:
Trust and access to accurate information, respectful communication, and timely service delivery should be within the core experience.
Digital innovations, multilingual services, and partnerships are enhancements that can elevate the core experience.
We then trace customer end-to-end workflow to inform our target audience and highlight moments of friction and opportunity, ensuring that future decisions remain closely aligned with the realities of our users.
Synthesizing everything so far, I worked with our solutions architect to create technical architecture and business relationship diagrams that will guide the direction of future VeriComms implementation. These overall blueprints will help ensure that future development stays aligned with business requirements, user needs, and technical capabilities.
With our discovery insights and design direction defined, we built revamped certain features from AKARI to better suit the needs of public health communicators.
We adopted some conventions inspired by AI platforms like Claude AI, ChatGPT, and Perplexity for features that provide:
We then conducted 5 moderated, one-on-one concept testing sessions with our interactive prototype via Maze with members of PHCC to validate the value and efficacy of our designs. Key insights from concept testing included:
We also analyzed heatmaps and post-test surveys from Maze to give us quantitative data on workflow efficiency and user preferences. From these, our findings are as followed:
Afterwards, we made prototype iterations based on the concept testing feedback and left specific annotations, recommendations, and references for inspiration in our hand-off file for the client and the outsourced developer team.
Our work yielded high satisfaction ratings from both participants and the client, with great overall usability and relevant features. From a more holistic approach, we addressed frustrations for public health communicators and drove engagement with the product — to the point many participants verbalized excitement to see what the next steps are.
This enthusiasm reflected the business impact we had this project phase, which includes:
“I do like how … because of how versatile it is to navigate it and like it's pretty simple.”
- Participant 65 (User Test Participant 3)
This project phase had many more moving parts than our previous work, and there were moments where the direction shifted mid-way because new information from the client changed our project scope. Navigating that without losing momentum taught me that adaptability isn't just about staying calm, but also about keeping research and design decisions clear and aligned so that a pivot doesn't mean starting over.
Our work reflected and reinforced the importance of balancing user needs with business goals and constraints, thus earning us praise from both participants from various public health sectors, and the client team themselves.
To hear from the client herself about how our efforts were "extremely efficient, useful, and well-organized" and "have set them up for success" really makes me proud of the measurable impact we were able to produce in the short time we had.
In the next phase, I'd have more rounds of user testing, including one with the indirect stakeholders at PHCC, to continuously refine features for different public health sectors with a newer perspective.
Additionally, more discovery and user research will constantly update our knowledge about how public health communicators react to the current market of products out there. This will ensure that we stay informed of how we can build unique, optimized, and effective products for them.
With S2P's plans to scale out and build more tools and products, I'd collaborate with the stakeholder to explore some of the organization's CX itself. This could enhance awareness and engagement for all types of customers and provide valuable business insights, potentially securing a population of loyal and invested customers in the future.