The framing
The design challenge was to clarify how patient health, care plan, reminders, progress, doctor review, caregiver support, and long-term health relate to each other.
Case Study · Digital Health / Care Management
CareSync
Keeping every step of care in sync.
A shared care-management concept connecting the patient, care plan, daily activities, progress, and care team in one continuous journey.
- Role
- Product Designer · concept framing, IA, journey, UX direction, design-system foundation
- Tools
- Figma
- Stage
- Product concept and interface design
- Duration
- Not specified in project materials
Outcome summary
A connected structure for the care journey.
I structured the concept from a health change and diagnosis through care-plan follow-through, progress review, recovery, and long-term health management. It brings instructions, daily activities, reminders, results, and care-team support into one coordinated experience.
This describes the documented concept and design outputs—not improved adherence, patient health, or business performance.
Add a real CareSync screen export or composed set of Figma screens.
01 · Problem context
Care is a journey, not a collection of isolated tasks.
A person managing a health condition may need to coordinate a care plan, medication, diet, exercise or physiotherapy, tests, appointments, reminders, progress updates, and conversations with the care team.
Who is affected?
- Patients following a care plan over time.
- Doctors and care teams reviewing progress and follow-up needs.
- Caregivers or family supporting selected activities.
Why it matters
When information and actions are disconnected, people may have to remember instructions, switch between sources, or work out what to do when a task is missed. These are problem hypotheses that require validation with patients and clinicians.
How might we help patients follow a personalised care plan while keeping progress, doctor oversight, and caregiver support connected—without overwhelming them or implying the app replaces clinical advice?
02 · Project history
From a care-management idea to a connected product structure.
The concept focuses on continuity between health context, prescribed care, daily follow-through, monitoring, and longer-term health.
Constraints
- Represent an ongoing journey, not a one-time appointment.
- Give patients a clear view of care activities and progress.
- Keep prescribed-care changes under appropriate clinical oversight.
- The supplied evidence does not establish a launch or real-patient evaluation.
Add a genuine timeline, early concept, or flow if available.
03 · People and place
Design for the context in which care happens.
The intended environment is repeated use across a care journey: checking activities, reviewing reminders, recording completion, checking progress, and returning to care information over time.
Target user
A patient managing a health condition and following a doctor-provided care plan, with optional caregiver support.
Supporting users
Doctors or care-team members reviewing progress and results; caregivers helping with selected activities.
Usage environment
A recurring experience for care activities, reminders, progress, and follow-up information.
To confirm
Target geography, healthcare market, languages, primary device, connectivity, accessibility, privacy, and regulatory requirements.
No specific country, clinic network, insurance model, or regulatory framework is assumed.
04 · Product structure
How the experience is meant to work.
The product mechanics connect what the patient sees and does with the status that changes and what the care team may need to review.
Primary care journey
- 01Health change
- 02Diagnosis and evaluation
- 03Care plan
- 04Follow care
- 05Reminders and tracking
- 06Monitor
- 07Clinician reviews and adjusts
- 08Recovery and long-term health
Information architecture
Patient Health
Keep current condition and relevant health context together.
Care Plan
Connect doctor-provided instructions with activities and appointments.
Reminders
Surface due activities and make their status understandable.
Progress
Review recorded activity and available results with context.
Doctor
Support clinical review, follow-up, and plan updates.
Caregiver / Family
Support selected activities with clear permissions.
Long-Term Health
Continue care management beyond the immediate episode.
Add the actual CareSync IA or flow export; no diagram is fabricated here.
Questions to validate
Where could the journey create friction?
- Can the patient find the next action quickly?
- Is each activity clear about what to do and when?
- Are upcoming, due, completed, and missed states distinct?
- What happens after a missed task?
- Can patients interpret a progress chart?
- Who can access the health information?
Recording an activity should make its new status understandable. Clinical escalation, rescheduling, and plan-change rules need qualified clinical input—not interface inference.
05 · Trust and emotion
Make care feel clear without offering false certainty.
Care management can involve uncertainty, worry, effort, and a need for reassurance. The design direction should orient people without replacing professional advice.
Clarity
“What do I need to do next?”
Confidence
“Did I record this correctly?”
Trust
“Who can see my health information?”
Control
“Can I correct a mistake or ask for help?”
Safety
“What if I miss an activity or do not understand?”
Trust risks
Clarity is part of safety.
- Progress visuals could imply medical improvement without context.
- A missed-task message could suggest an unsafe action if it gives generic clinical advice.
- Unclear doctor or caregiver permissions could create privacy uncertainty.
- Colour-only status indicators could be difficult to interpret.
Visual direction: calm hierarchy, plain language, readable type, explicit status text, and visual reassurance that does not imply an unproven clinical outcome.
06 · Use over time
Support routines without adding avoidable effort.
CareSync is intended for repeated use through a care journey, not only at sign-up. The concept should avoid unnecessary data entry and notification fatigue.
- 01Cue
- 02Orient
- 03Act
- 04Record
- 05Feedback
- 06Review
- 07Continue or follow up
Research prompts
Habits to investigate, not assume.
- Do patients rely on paper notes, alarms, family messages, or memory?
- Do they record activities later?
- Do repeated notifications become easy to ignore?
- Can users distinguish task completion from a health outcome?
- Do caregivers need shared access?
The product should acknowledge an action, preserve understandable status, and help users recover from mistakes. Engagement alone is not evidence of improved adherence or health.
Add a real behavior-loop diagram or reminder flow if available.
07 · Evidence and validation
What is known, what is simulated, and what must be measured.
Project materials support a description of the concept and design structure; they do not provide real participant testing, clinical outcomes, or measured business impact.
Real usability-test participants
Not provided
Task completion, time, and errors
Not measured
SUS or patient confidence rating
Not measured
Direct patient quotes
None supplied
Adherence or patient health outcomes
Not measured
Business impact or launch results
Not provided
Simulated patient walkthroughDesk-based role-play · fictional persona “Meera” · not a research participant
The walkthrough considered access recovery, finding today's care plan, recording an activity, interpreting reminders and progress, missed activities, sharing permissions, and returning later. These are prompts for evaluation, not observed user findings.
Preliminary review priorities
01Critical
Missed-care safety
Use clinician-approved guidance and clear escalation boundaries; do not invent medical instructions.
02High
Find the next action
Make today's plan and next due activity easy to locate.
03High
Understand activity status
Use explicit labels and accessible visual states, not colour alone.
04High
Interpret progress
Explain the measure, time period, source, and limitations.
05High
Understand sharing
Explain doctor and caregiver access in context.
06Medium
Recover from mistakes
Explore clear confirmation, correction, and efficient repeat-use patterns.
Proposed validation · not yet conducted
Start with a formative round.
A first round of 5–8 representative participants is a proposed sample size, not completed research.
- 01Find today's care activity and explain it in their own words.
- 02Record completion and correct a deliberate mistake.
- 03Identify upcoming, due, completed, and missed activities.
- 04Explain a progress visual and locate test-result context.
- 05Describe who can access shared information.
- 06Identify a safe next step for a missed task using clinician-approved content.
Capture task success, time, errors, help required, comprehension, confidence, comments, hesitation, accessibility concerns, and safety issues. Use fictional scenarios and clinician-reviewed safety-sensitive content.
08 · Design engineering
Turn the concept into a structured experience.
The documented design direction connects care roles and organizes the experience around the care plan.
Role relationship
Doctor sets the care plan Patient follows the plan Caregiver supports when needed Doctor reviews progress
Ideation and framing
A shared care-management journey, with the care plan connecting health context and daily follow-through.
Information architecture
Patient health, care plan, reminders, progress, doctor oversight, caregiver support, and long-term health.
Wireframes and interface
Show only actual Figma wireframes and screens; connect each to a design question and trade-off.
Testing and iteration
No real usability test or measured iteration outcome is documented in the available materials.
Design-system foundation
The supplied design-system notes describe token collections and component properties. The type reference is Figtree; the supplied notes also include color, spacing, radius, borders, elevation, icon size, and component tokens.
- Color · primitive and semantic
- Typography · Figtree
- Spacing
- Radius and borders
- Elevation and icon size
- Component tokens
Add a real CareSync token or component screenshot.
Proposed experience
Patient health context · care-plan timeline · reminders and activity status · progress and test-result review · doctor follow-up and plan updates · caregiver support where appropriate · long-term health management.
This describes the proposed product structure, not evidence of launch or clinical effectiveness.
09 · STAR summary
A concise view of the work.
The documented outputs establish a product concept and a basis for prototyping and formative evaluation.
Situation
Patients may need to coordinate instructions, daily activities, reminders, progress, and follow-ups across an ongoing care journey.
Task
Define a coherent product structure and primary journey that connects patient follow-through, progress, doctor oversight, and caregiver support.
Action
Framed the journey, organized its product areas, and established a Figma design-system foundation across color, typography, spacing, radius, borders, elevation, icon size, and component tokens.
Result
A defined concept, primary care journey, structured product areas, and design-system foundation. Outcomes remain to be validated.
10 · Before and after
The intended transformation.
Before represents the problem framing; after represents the proposed design response—not a measured comparison of real-world performance.
01Care activities can feel like separate tasks.
A connected journey links the plan, daily actions, and progress.
02Several information areas need to relate to one another.
A structured set of product areas gives each part a place.
03Daily follow-through needs to relate to clinician instructions.
The care plan is positioned as the connective layer.
04Missed tasks require careful handling.
Missed-care guidance is identified for clinical review.
05Care continues beyond a single visit.
The journey includes recovery and long-term health management.
11 · Final screens and prototype
Explore the actual design work.
The design file and interactive prototype are available from the links below. Use real exports for any portfolio gallery; no fictional interface screens are shown here.
Entry / sign-inAdd real screen export if available
Screen goal, design decision, and open question to be documented from the corresponding Figma screen.
Patient overviewAdd real screen export if available
Screen goal, design decision, and open question to be documented from the corresponding Figma screen.
Care plan and activity timelineAdd real screen export if available
Screen goal, design decision, and open question to be documented from the corresponding Figma screen.
Reminder or activity statusAdd real screen export if available
Screen goal, design decision, and open question to be documented from the corresponding Figma screen.
Progress or test resultsAdd real screen export if available
Screen goal, design decision, and open question to be documented from the corresponding Figma screen.
Doctor / caregiver supportAdd real screen export if available
Screen goal, design decision, and open question to be documented from the corresponding Figma screen.
12 · Learnings and future scope
Make the next step clearer—and validate it with people.
These are design principles from the product framing and desk review, not claims of observed patient outcomes.
What this project reinforced
- Make the next action and its context understandable.
- Connect clinical instructions, patient actions, and progress review through the care plan.
- Clarify status without relying on colour or ambiguous visuals.
- Separate recorded activity from clinical interpretation and medical advice.
- Explain access and sharing permissions.
- Evaluate comprehension and safety with intended users and clinical stakeholders.
What I would improve next
- Validate the journey with patients or representative users.
- Review reminders, missed-task handling, and escalation copy with qualified clinicians.
- Test accessibility, plain-language comprehension, and responsive layouts.
- Validate doctor and caregiver permissions.
- Test progress summaries and test-result context.
- Run a second round and report measured results transparently.
Future scope
Clinician-reviewed missed-care guidance · role-based sharing controls · accessible reminders and status · transparent progress summaries · appropriate patient and operational measures, if the product is implemented and evaluated.
Evidence boundary
Concept documented. Outcomes not yet validated.
No real patient outcomes, usability improvements, business impact, or launch results were supplied. Simulated review observations remain hypotheses to evaluate—not user quotes or measured findings.
Closing
Designing care experiences that make the next step clearer.
CareSync explores how a connected care journey can help patients, doctors, and caregivers stay aligned. The next stage is to validate the experience with intended users and clinical stakeholders.
Next project
Snap Automation