Clarity Before Diagnosis

Clarity Before Diagnosis

Clarity Before Diagnosis

Clarity Before Diagnosis

Clarity Before Diagnosis

Foresee is a time based understanding system that helps users make sense of recurring symptoms and decide when to take action.

Role:

UX / Product Design

Timeline:

8 weeks

Focus:

Long term tracking

Scope:

Mobile & Watch

Role:

UX / Product Design

Timeline:

8 weeks

Focus:

Long term tracking

Scope:

Mobile & Watch

Role:

UX / Product Design

Timeline:

8 weeks

Focus:

Long term tracking

Scope:

Mobile & Watch

The Problem

Many people live in a “gray zone”. They have recurring symptoms like fatigue or dizziness over time, but lack a clear diagnosis. While these signals are noticeable, they are hard to interpret, making it difficult to tell if they matter. This uncertainty makes people keep checking and delay action.

Many people live in a “gray zone”. They have recurring symptoms like fatigue or dizziness over time, but lack a clear diagnosis. While these signals are noticeable, they are hard to interpret, making it difficult to tell if they matter. This uncertainty makes people keep checking and delay action.

Many people live in a “gray zone”. They have recurring symptoms like fatigue or dizziness over time, but lack a clear diagnosis. While these signals are noticeable, they are hard to interpret, making it difficult to tell if they matter. This uncertainty makes people keep checking and delay action.

Many people live in a “gray zone”. They have recurring symptoms like fatigue or dizziness over time, but lack a clear diagnosis. While these signals are noticeable, they are hard to interpret, making it difficult to tell if they matter. This uncertainty makes people keep checking and delay action.

Positioning

Most health tools track data or manage serious sickness but they do not help people decide if small symptoms matter. Foresee fills this gap by helping users turn scattered signals into actionable understanding over time.

Research

Online Questionnaire

To validate whether this “gray zone” is a real and widespread problem, I conducted a survey with 46 participants.

88.9%

88.9%

88.9%

experienced recurring symptoms without a diagnosis

experienced recurring signals without a diagnosis

have recurring symptoms without a diagnosis

(User Survey, 2026, n=46)

(User Survey, 2026, n=46)

(User Survey, 2026, n=46)

60%

60%

60%

don't know whether their symptoms are serious

don't know if their symptoms are serious

(User Survey, 2026, n=46)

(User Survey, 2026, n=46)

(User Survey, 2026, n=46)

User Interview

I interviewed users to see how uncertainty shapes decisions, focusing on how unclear symptoms lead to delayed action.

“I feel something is off, but I don’t know if it’s serious enough to do anything.”

Participants: 6 people from the survey pool
Format: Semi structured 1:1 interviews (30 mins)
Goal: Understand how they make decisions, what they forget, and how they decide to seek care

Across interviews, a consistent pattern emerged:

When symptoms cannot be connected into patterns over time, users tend to ignore them until they become disruptive, delaying action.

Across interviews, a consistent pattern emerged:

People are not ignoring their health — they lack confidence in interpreting their symptoms.

Competitive Analysis

I analyzed the market to understand how existing tools fail to support users in interpreting symptoms over time.

Data tracking apps

Provide a lot of data but do not explain what changes mean, so users cannot interpret their symptoms.

Collect lots of health data and show trends, but don’t explain meaning when something feels off.

Symptom logging apps

Require frequent manual input but give fragmented, delayed insights, making it hard to see value in continuous logging.

Symptom checker apps

Offer one time answers but do not support ongoing symptoms, making it hard to see patterns over time.

As a result, users must invest effort to interpret fragmented data themselves, often without clear results, which reduces motivation to continue tracking.

Key Insights from Research

Uncertainty blocks action

Users experience symptoms but can’t interpret their meaning or severity. So they hesitate and delay action.

Effort must lead to value

Logging requires continuous effort, but without clear feedback, users quickly lose motivation and stop logging.

Signals fail without patterns

Small recurring symptoms are ignored as unrelated, and without patterns, they are treated as noise.

Uncertainty blocks action

Users experience symptoms but can’t interpret their meaning or severity. So they hesitate and delay action.

Signals fail without patterns

Small recurring symptoms are ignored as unrelated, and without patterns, they are treated as noise.

Effort must lead to value

Logging is too much work without a payoff. Users stop when the effort does not lead to insight or a clear path..

Uncertainty blocks action

Anxiety stems from a lack of knowledge. Users can‘t interpret symptoms or connect them into patterns.

Signals fail without patterns

Small recurring symptoms are ignored as unrelated, and without patterns, they are treated as noise.

Effort must lead to value

Logging is too much work without a payoff. Users stop when the effort does not lead to insight.

How might we help people understand their symptoms over time so they can decide when to take action?

Design Principles

Simple and Intuitive

Reduce interaction cost. Show only the most relevant information to prevent user fatigue.

Data Supported Decisions

Validate insights with biometric signals. Link history to trends for trust and informed choices.

Action Driven

Prioritize the "What to do next". Turn raw data into clear, actionable health guidance.

Passive and Consistent Signals

Use automated background tracking from wearables to reduce the friction of manual data entry.

Simple and Intuitive

Reduce interaction cost. Show only the most relevant information to prevent user fatigue.

Action Driven

Prioritize the "What to do next". Turn raw data into clear, actionable health guidance.

Data Supported Decisions

Validate insights with biometric signals. Link history to trends for trust and informed choices.

Passive and Consistent Signals

Use automated background tracking from wearables to reduce the friction of manual data entry.

Simple and Intuitive

Reduce interaction cost. Show only the most relevant information to prevent user fatigue.

Data Supported Decisions

Validate insights with biometric signals. Link history to trends for trust and informed choices.

Action Driven

Prioritize the "What to do next". Turn raw data into clear, actionable health guidance.

Passive and Consistent Signals

Use automated background tracking from wearables to reduce the friction of manual data entry.

Design Solution Flow

Foresee helps users understand patterns that emerge over time, guiding them from sensing symptoms to making informed decisions.

Integrated Data Capture
Path A: Quick Check In

To address the high effort of continuous logging, the system introduces quick check ins triggered only by significant body signal changes, so that users can log symptoms with minimal effort.

Path B: AI Chat Logging

To address uncertainty when symptoms feel complex, the system allows users to log through AI chat, so that they can capture detailed context and receive more meaningful input.

Pattern Discovery

To address the difficulty in interpreting recurring symptoms, the system reveal patterns that emerge over time, so that users can understand when and why symptoms occur.

AI Generated Health Summary

To address the gap between tracking and action, the system generates structured health summaries, so that users can better communicate their condition and decide next steps.

Process

I mapped Personas to identify Drop off Risks and built Design Interventions to solve them. This System Diagram shows how passive data generates health insights.

  • Personas

  • Core Scenarios

  • Long-term Journey (3–6 Months)

  • Drop off Risks

    • Quiet period disengagement (First week → early weeks): users drop off when symptoms aren’t noticeable and the app feels inactive or unnecessary.

    • Delayed value fatigue (First month): users stop engaging when early check ins don’t yet lead to visible insights or outcomes.

    • Uncertainty avoidance (One to three months): users disengage when emerging patterns raise concern without giving clear direction.

    Design Interventions

    • Quiet periods: confirm passive tracking is active and surface lightweight data, so users know the system is working, even when no clear direction is visible.

    • Delayed value: surface early summaries and set expectations for when patterns become clearer over time.

    • Uncertainty avoidance: avoid diagnosis or alarm, and provide gentle direction on what to observe or consider next.

  • System Diagram

  • Personas

  • Core Scenarios

  • Long-term Journey (3–6 Months)

  • Drop off Risks

    Quiet period disengagement (1st week → early weeks): users drop off when symptoms aren’t noticeable and the app feels inactive or unnecessary.

    Delayed value fatigue (1st month): users stop engaging when early check ins don’t yet lead to visible insights or outcomes.

    Uncertainty avoidance (1-3 months): users disengage when emerging patterns raise concern without giving clear direction.

    Design Interventions

    • Quiet periods: confirm passive tracking is active and surface lightweight data, so users know the system is working, even when no clear direction is visible.

    • Delayed value: surface early summaries and set expectations for when patterns become clearer over time.

    • Uncertainty avoidance: avoid diagnosis or alarm, and provide gentle direction on what to observe or consider next.

  • System Diagram

  • Personas

  • Core Scenarios

  • Long-term Journey (3–6 Months)

  • Drop off Risks

    • Quiet period disengagement (First week → early weeks): users drop off when symptoms aren’t noticeable and the app feels inactive or unnecessary.

    • Delayed value fatigue (First month): users stop engaging when early check ins don’t yet lead to visible insights or outcomes.

    • Uncertainty avoidance (One to three months): users disengage when emerging patterns raise concern without giving clear direction.

    Design Interventions

    • Quiet periods: confirm passive tracking is active and surface lightweight data, so users know the system is working, even when no clear direction is visible.

    • Delayed value: surface early summaries and set expectations for when patterns become clearer over time.

    • Uncertainty avoidance: avoid diagnosis or alarm, and provide gentle direction on what to observe or consider next.

  • System Diagram

  • Personas

  • Core Scenarios

  • Long-term Journey (3–6 Months)

  • Drop off Risks

    • Quiet period disengagement (1st week → early weeks): users drop off when symptoms aren’t noticeable and the app feels inactive or unnecessary.

    • Delayed value fatigue (1st month): users stop engaging when early check ins don’t yet lead to visible insights or outcomes.

    • Uncertainty avoidance (1-3 months): users disengage when emerging patterns raise concern without giving clear direction.

    Design Interventions

    • Quiet periods: confirm passive tracking is active and surface lightweight data, so users know the system is working, even when no clear direction is visible.

    • Delayed value: surface early summaries and set expectations for when patterns become clearer over time.

    • Uncertainty avoidance: avoid diagnosis or alarm, and provide gentle direction on what to observe or consider next.

  • System Diagram

Usability Testing

8 participants with recurring symptoms tested onboarding, check ins, AI chat, insights, and export flows.

Task 1: Onboarding

• Feature explanation felt dense

• Medical record upload felt premature

Task 3: AI Chat

• Advice felt generic

• No visible connection to personal history

Task 5: Health Summary Export

• Authority unclear

• Viewed as helpful for doctors

Task 2: Watch Check in

• Trigger logic unclear

• Users unsure how answers affect insights

Task 4: Insights & Pattern

• Next steps felt vague

• 30 days charts misread as single day data

Task 1: Onboarding

• Feature explanation felt dense

• Medical record upload felt premature

Task 3: AI Chat

• Advice felt generic

• No visible connection to personal history

Task 5: Health Summary Export

• Authority unclear

• Viewed as helpful for doctors

Task 2: Watch Check in

• Trigger logic unclear

• Users unsure how answers affect insights

Task 4: Insights & Pattern

• Next steps felt vague

• 30 days charts misread as single day data

Task 1: Onboarding

• Feature explanation felt dense

• Medical record upload felt premature

Task 2: Watch Check in

• Trigger logic unclear

• Users unsure how answers affect insights

Task 3: AI Chat

• Advice felt generic

• No visible connection to personal history

Task 4: Insights & Pattern

• Next steps felt vague

• 30 days charts misread as single day data

Task 5: Health Summary Export

• Authority unclear

• Viewed as helpful for doctors

Iteration

I tested every flow to find friction in user understanding. These updates focus on improving the setup process and data readability.

1. Restructuring onboarding to reduce cognitive load and build trust

Early testing showed onboarding felt confusing and asked for too much too soon. People didn’t really get the features before trying it. So I let them see the value first, then moved account setup and data connection later.

This shows product value first, lowers decision pressure, and makes data connection feel useful instead of forced.

2. Improving pattern clarity with step by step details

Testing showed users thought the 30 day chart was just one day of data and didn’t understand how patterns were found. The original layout did not have clear hierarchy or enough context.

The updated design makes the charts easier to understand, reduces misreading.

Design Elements

The visual design balances clarity and comfort. A clear structure builds trust and supports accurate data, while lighter colors reduce visual heaviness. This balance supports emotional comfort without reducing clarity.

Reflection

Designing Foresee shifted my focus from building tracking screens to helping users interpret health signals. In early health stages, people are not looking for diagnoses. They want to know if a change in their body is worth paying attention to. Because of this, the design helps users see patterns across symptoms, lifestyle, and time so they can better judge when it may be worth talking to a doctor.

Next Steps

• Long term testing: Test the system over a longer time to see how trust, engagement, and understanding change over weeks or months, not just in one session.

• Long term testing: Test the system over a longer time to see how trust, engagement, and understanding change over weeks or months, not just in one session.

• Long term testing: Test the system over a longer time to see how trust, engagement, and understanding change over weeks or months, not just in one session.

• AI insight explanation: Explore ways to make AI insights easier to understand by showing the reason behind each insight, the confidence level, and the signals or data that helped the system detect the pattern.

• AI insight explanation: Explore ways to make AI insights easier to understand by showing the reason behind each insight, the confidence level, and the signals or data that helped the system detect the pattern.

• AI insight explanation: Explore ways to make AI insights easier to understand by showing the reason behind each insight, the confidence level, and the signals or data that helped the system detect the pattern.

• Clinical collaboration: Work with healthcare professionals to test the doctor ready summary and check if the information is organized in a way that helps doctors quickly understand the user’s condition during a medical visit.

• Clinical collaboration: Work with healthcare professionals to test the doctor ready summary and check if the information is organized in a way that helps doctors quickly understand the user’s condition during a medical visit.

• Clinical collaboration: Work with healthcare professionals to test the doctor ready summary and check if the information is organized in a way that helps doctors quickly understand the user’s condition during a medical visit.

• Adaptive personalization: Study how the system can gradually adjust signals and guidance based on each user’s past patterns and logged data, while keeping clear limits so the system does not give medical diagnosis or treatment advice.

• Adaptive personalization: Study how the system can gradually adjust signals and guidance based on each user’s past patterns and logged data, while keeping clear limits so the system does not give medical diagnosis or treatment advice.

• Adaptive personalization: Study how the system can gradually adjust signals and guidance based on each user’s past patterns and logged data, while keeping clear limits so the system does not give medical diagnosis or treatment advice.

Create a free website with Framer, the website builder loved by startups, designers and agencies.