Everyday Health Tracker
Design a calm daily tracker that helps someone notice patterns in symptoms, sleep, activity, and context without suggesting a diagnosis.
The brief
Understand the problem
Background
Health logging can become burdensome when every day requires a long questionnaire. It can also create unnecessary alarm when normal variation is framed as a warning rather than context for reflection or clinical discussion.
User context
Amina experiences recurring headaches and wants a simple record to discuss at her next primary care visit. She can log on her watch during the day and review detail on her phone each weekend.
Product problem
Amina needs a low-effort record that reveals useful associations while keeping uncertainty clear and making her private data easy to control.
Objective
Design quick logging, gentle reminders, pattern review, and a clinician-ready summary for a four-week tracking period.
What to design
Define the experience
Required experience
- Record a symptom and its immediate context
- Correct or add detail to a previous entry
- Review a weekly pattern with accessible explanations
- Choose exactly what to include in a shareable summary
Screens and states
- Quick daily check-in
- Entry detail and correction
- Weekly trend review
- Sharing scope and preview
Core user flow
Follow the critical path
- 01
Amina logs headache intensity and hydration from her watch
- 02
Later she adds sleep duration from her phone
- 03
At the weekend she sees headaches often followed short sleep but the interface avoids claiming causation
- 04
She exports four selected measures for her appointment
Product rules
Requirements and constraints
Requirements
- Keep the frequent check-in short and dismissible
- Distinguish recorded facts, user notes, and calculated patterns
- Represent trends through labels, shapes, and tables as well as color
- Provide granular export and deletion controls
- Route urgent symptoms to appropriate care guidance without diagnosing
Constraints
- Patterns cannot be described as medical conclusions
- Notifications must avoid revealing health details on a locked device
- Watch interactions should prioritize one-handed, brief input
Reality check
States worth considering
Ready-to-use content
Mock data
Use this content to test hierarchy and realistic data states. You can expand it when the concept needs more depth.
Weekly pattern
- Headache entries: 4
- Average sleep before headache: 5 hours 40 minutes
- Average sleep on other nights: 7 hours 5 minutes
- Hydration entries missing on 2 days
Finish line
What to deliver
- Four mobile screens plus one compact watch interaction
- Annotations for uncertainty, privacy, and urgent guidance
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.
Yeseva One & Merriweather
Clear interface writing gives people the confidence to understand what changed and decide what to do next.
Yeseva One & Merriweather
Clear interface writing gives people the confidence to understand what changed and decide what to do next.