digital-health-ux-planning
UX Planner
Plan user experience flows for digital health products without assuming a specific client technology.
When to Use
Use this skill when you need to:
- design end-to-end journeys for patients, participants, clinicians, or coordinators
- plan onboarding and consent-adjacent flows
- structure recurring health tracking or task completion workflows
- think through engagement, motivation, and accessibility
Working Style
Begin with the people, decisions, and moments that matter. Do not start with screens.
Clarify:
- primary users
- core jobs to be done
- highest-friction moments
- what users need to understand, decide, or complete
- what success looks like for both the user and the program
Planning Framework
1. User Segments
Identify:
- primary users
- secondary users
- staff or caregiver roles
- user constraints such as health literacy, accessibility needs, fatigue, or limited time
2. Core Journeys
Map the main flows in plain language, for example:
- discover and enroll
- learn what the product is for
- provide consent or required acknowledgements
- complete the first meaningful task
- return for ongoing use
- review progress or history
- get help or recover from confusion
3. Onboarding
Plan what users need at the beginning:
- orientation and trust-building
- account setup if applicable
- permissions or access requests only when needed
- profile or baseline setup
- first action that creates value quickly
Challenge any onboarding flow that asks for too much too soon.
4. Day-to-Day Workflow
Describe the recurring experience:
- what prompts the user to return
- what they see first
- what they are expected to do
- how completion and progress are communicated
- what happens when they skip, fall behind, or lose context
5. Engagement Strategy
Consider:
- reminders
- summaries
- milestone feedback
- streaks or encouragement, if appropriate
- how to avoid manipulation, shame, or alert fatigue
6. Accessibility and Inclusion
Review:
- readability and plain language
- color contrast and visual hierarchy
- support for assistive technologies
- cognitive load
- language, cultural, and trust considerations
Deliverable Format
Produce a concise UX planning brief with:
- primary user segments
- top user journeys
- onboarding strategy
- recurring workflow design
- engagement principles
- accessibility and inclusion notes
- unresolved risks or UX questions
Save the brief as docs/planning/ux-brief.md in the project repository.
Guardrails
- Do not assume mobile tabs, specific screens, or platform conventions unless implementation context requires it.
- Prefer user goals and decision points over UI inventories.
- Keep trust, burden, and accessibility central.
- Call out where clinical safety or compliance requirements change the UX.
Checklist
- User segments identified
- Core journeys mapped
- Onboarding scoped to the minimum necessary steps
- Day-to-day workflow defined
- Engagement strategy reviewed for burden and ethics
- Accessibility and inclusion considerations captured
- Major UX risks and open questions documented
More from stanfordspezi/spezivibe
fhir-data-model-design
Design a FHIR R4 data model for a healthcare application by mapping clinical concepts to resources, terminology, and implementation-ready relationships.
69digital-health-compliance-planning
Plan healthcare privacy, research, and regulatory compliance for a digital health product, including HIPAA, IRB, FDA, GDPR, governance, and operational controls.
55keep-a-changelog-generator
Generate changelog entries from git history using Keep a Changelog structure and user-facing release language.
54biodesign-needs-finding
Guide a user through Stanford Biodesign's needs-finding process to define, scope, and refine a rigorous health-app need statement without jumping prematurely to solutions.
53spezi-platform-selection
Ask about an app's requirements, explain the tradeoff between the React Native Template App and the Spezi Template Application for Apple Platforms, clone the right repository, and hand off to the cloned project's local skills and instructions.
53release-notes-generator
Create release notes that summarize features, fixes, and migration guidance for software releases.
53