Health and wellness apps get built around what the clinical team thinks patients need, then the drop-off numbers show something different. We run research that tells you which is true before you rebuild the wrong thing twice.
The Problem
Clinical validation gets treated as a substitute for usability research
A feature can be clinically sound and still fail because patients cannot navigate to it, do not trust it, or abandon onboarding before it does anything useful. Clinical teams are good at proving a mechanism works; they are not trained to test whether a stressed, distracted, or symptomatic user can actually complete the flow. That gap shows up as onboarding drop-off and support tickets, not as a clinical failure, which is why it gets missed until adoption numbers are already bad.
HIPAA and device-safety rules cut off the research methods consumer teams default to
Session recordings, unmoderated remote testing tools, and third-party analytics pixels that consumer product teams reach for by habit can touch PHI or create a compliance exposure the moment a real patient uses them. Teams either skip research to avoid the risk, or run it through a generic agency that does not know which methods are safe, and ends up redoing consent and data-handling work from scratch. Both outcomes cost more than doing it right the first time.
Patients, providers, and caregivers are three different users inside the same product
A dashboard built for a busy clinician's 90-second workflow will overwhelm a patient managing a chronic condition, and a caregiver checking in on a parent needs neither view. Generic UX research treats this as one persona and optimizes for engagement metrics that do not map to any of the three groups' real constraints, which is how a product ends up used by none of them the way it was designed to be used.
How We Help
We start with HIPAA-compliant research that separates what patients, providers, and caregivers each actually need from what the product currently assumes they need. That means structured interviews and task-based testing under a data-handling protocol that does not touch PHI improperly – not a generic discovery sprint borrowed from a consumer product playbook. The output is a set of usability gaps tied to specific screens and flows, not a persona deck.
From there, we build the rest of the research plan around what your regulatory posture actually allows: which testing formats are safe for your device classification, what can be recorded, and what needs de-identification before it leaves the clinical environment. Most teams either over-restrict out of caution or under-restrict out of unfamiliarity with the rules. We map the boundary once so every later test cycle moves fast instead of re-litigating compliance each time.
Usability testing is built around real clinical context, not a lab task list: a patient self-managing a condition on their own phone, a provider moving through the flow between patients, a caregiver coordinating remotely. We test each context separately because the failure modes differ, and a fix for the provider workflow can make the patient workflow worse if nobody is watching for it. Execution means sitting with your clinical, accessibility, and engineering teams on the same cadence, not a handoff at the end.
Design changes get checked against clinical workflow before they ship, and against accessibility needs – screen readers, motor-impairment navigation, low-literacy content – before they get called done, because a design that tests well with able-bodied staff and fails for the patient population it serves has not solved the problem.
What we deliver
- HIPAA-compliant research protocol – patient, provider, and caregiver research run under a data-handling standard that will not create a compliance exposure
- Regulatory-safe testing methodology – a defined map of which research methods your device classification and privacy posture actually allow
- Context-specific usability testing – separate test passes for patient self-management, provider workflow, and caregiver coordination, because one persona cannot cover all three
- Accessibility validation – testing against screen readers, motor-impairment navigation, and low-literacy content, not just standard usability heuristics
- Embedded design-clinical coordination – ongoing sessions with your clinical and engineering teams so design changes get validated before they ship, not after
A dashboard built for a clinician's 90-second workflow and a screen built for a patient managing a chronic condition are not the same design problem wearing different skins. Most health products fail because they solve one and ship it to both.
Our Methodology
The engagement runs as a 90-day research and design cycle. Weeks 1-2: HIPAA-compliant research across patient, provider, and caregiver groups to establish what each one actually needs, separately. Weeks 3-6: usability testing built around each group's real context, plus the accessibility validation most health products skip until a compliance review forces it. Weeks 7-12: design changes get implemented and checked against clinical workflow and patient outcomes, not just a usability heuristic checklist. The difference from a typical product design engagement is what gets measured at the end: whether patients complete the flows that matter clinically, not whether they clicked through a prototype. A screen that tests well in a usability lab and gets abandoned by real patients within a week has not been validated, it has just been demoed.
How We Work
First 30 days: research across patient, provider, and caregiver groups, run under the data-handling protocol we establish with your compliance team before any session happens. Weeks 5-8: context-specific usability testing and accessibility validation, with findings reviewed against your clinical requirements as they come in, not batched into a final report. Weeks 9-12: design changes ship, and the ones tied to clinical workflow get checked against real usage, not just a follow-up interview. You provide product access, clinical stakeholders, and a route to real patients or providers for testing; we run the sessions, the analysis, and the coordination with your engineering team. Monthly reporting covers what we found, what changed, and what we are still watching – not a usability score with no context behind it. Most engagements run 6-12 months because product development and clinical validation both move on cycles longer than a single design sprint, and a health product that works needs both to land.
- Clinical usability improvement
- Accessibility compliance
- Patient onboarding completion
- Provider workflow efficiency
If your health & wellness company needs product design & research leadership, we should talk.
Expand your marketing team output with our experts
Let us take a custom approach to your growth goals by assembling and leading the best-in-class marketing team to support your next stage.
Frequently asked questions
How much does product design research cost for a health or wellness company?
Most engagements run $20K-42K monthly depending on how many user groups need separate research tracks and how deep the accessibility testing goes. A full-time health UX researcher with HIPAA experience costs more than that on salary alone, before you add the compliance and clinical-liaison work that role would also need to cover. The range moves with device classification too – a Class II device needs more testing rigor than a wellness app with no clinical claims.
How long before we see results from health product design research?
Concrete usability findings, tied to specific screens and flows, typically land within 30-60 days. Design changes and accessibility fixes usually ship within 60-90 days. The clinical-outcome signal – whether patients are actually completing the flows that matter – takes another 60-90 days after that to show up cleanly, since it depends on real usage volume, not a testing session.
How does your research team work with our clinical and accessibility staff?
We sit with your clinical team to understand workflow constraints directly, rather than relying on a spec document that already lost detail in translation. Accessibility requirements get built into the testing plan from week one, not bolted on before a compliance review. Every finding gets reviewed with clinical stakeholders before it turns into a design change, so nothing ships that looks right on a screen and wrong in a patient's hands.
What makes Winston Francois different from a traditional UX research agency?
A generic agency runs the same research playbook it runs for e-commerce clients and treats HIPAA as a checkbox instead of a constraint that should shape the methodology itself. We build the testing plan around what your regulatory posture actually allows, and we test patients, providers, and caregivers as separate groups instead of one blended persona. The result is design decisions grounded in your actual clinical and compliance reality, not a template.
How do you measure ROI from a health product design research engagement?
We track onboarding completion, task success rate within each user group, and accessibility compliance against the standards your product needs to meet. For products with a clinical claim, we also watch whether patients are completing the specific flows tied to that claim, since that is the number that actually matters. None of this is engagement-metric theater – it is tied to whether the product does what it was built to do.
What type of health or wellness company should invest in specialized product design research?
Companies with a patient-facing app, a provider-facing tool, or both, where a real usability failure would show up as clinical risk or non-adoption, not just a bad review. Digital therapeutics, telehealth platforms, and medical device companies with a software component benefit most, since the regulatory stakes are highest there. The first step is a usability assessment to find out where the current product is actually losing patients or providers, before committing to a full research cycle.
