Designing chronic care around a simple exchange: patient effort should return patient value.
Patient effort must return patient value.
SWEETCH relied on daily patient effort. I used research to turn that dependency into experience principles — and those principles into one coherent experience.
Digital health · chronic care
A mobile app that uses daily health context to provide personalized guidance.
The app needed data. Patients needed a reason.
At first glance
SWEETCH could provide increasingly personalized support as it learned more about a patient's daily life — medication, activity, nutrition, sleep, measurements and routines.
But that required context.
Some could arrive automatically. Some had to be actively contributed by the patient.
Some signals could enter the system through devices or integrations.
Other parts of daily life still depended on the patient reporting them.
A reciprocal dependency
Value returned becomes the reason to keep participating
Value returned becomes the reason to keep participating
Less context → weaker personalization → less useful guidance → less value
The challenge was bigger than making logging easier or making the app more engaging.
How could we make the ongoing effort of self-tracking feel worth it?
Research revealed what the experience needed to give back.
Patient effort → Patient value
Once the exchange became clear, the next question became:
What makes participation worth continuing?
Pillar 1Connect daily actions to a health goal that genuinely matters.
Pillar 2Surface patterns, insights and useful next steps.
Pillar 3Show change and consistency — now and over time.
Pillar 4Guide when it helps; stay quiet when it doesn't.
Pillar 1Connect daily actions to a health goal that genuinely matters.
Pillar 2Surface patterns, insights and useful next steps.
Pillar 3Show change and consistency — now and over time.
Pillar 4Guide when it helps; stay quiet when it doesn't.
These principles became a common lens for the product.
Does this ask the patient for effort?
If it does, how does it return value?
The next step was applying that lens to the moments that shaped the experience.
One strategy, applied across the moments that shaped the experience.
The principles only mattered if they could guide real product decisions.
Different moments in the experience created different versions of the same tension: SWEETCH needed something from the patient, and the experience needed to make that ask worthwhile.
Patient effort → Patient value
Daily tracking was where the effort happened. The question was what could make that effort meaningful.
SWEETCH needed patients to keep logging meals, medication, activity and measurements. But helping the app collect data wasn't a reason for patients to keep doing the work.
I explored what could sustain motivation over time through multiple research inputs.
Scott Nicholson — "A RECIPE for Meaningful Gamification" (2015)
For long-term behavior change, gameful systems should help people build personal meaning and connection rather than depend only on external rewards.
Research consistently shows that unless rewards connect to something personally meaningful, they fail to support long-term engagement.
Driven by outside rewards and validation
Driven by personal meaning and purpose
Research showed that sustained engagement depended on connecting daily tracking to patients' internal motivation — the health outcomes they personally wanted to achieve. I translated that insight into a new product layer: personal goals, linking daily actions, progress and guidance to those outcomes.
My goals
Define what matters most to me
Onboarding
Define what I want to achieve
Homepage
Keep my goals visible
Health domains
Connect actions to goals
Long-term progress
See how I'm doing
Personalized guidance
Help me succeed, adjust and learn
This insight did not remain a principle.
It became a concrete part of the product.
A dedicated Goals area gave users an overview of what they were working toward and insight into their progress.
GOALS became a primary tab in the navigation.
Goals page — overview of what the patient is working toward.
Users could define or shape goals and milestones in ways that reflected their own priorities.
Defining a goal and its milestones, in the patient's own terms.
The same logic extended into different health domains, making the goal layer part of the broader experience rather than a standalone feature.
The goal layer recurring inside a specific health domain.
Daily reporting still supported personalization, but it could now be understood in relation to something the user actually wanted to achieve.
Daily reporting shown in relation to the goal it serves.
The app still needed the work.
Now the work was connected to something the patient actually wanted.
Patient effort → Patient value
The homepage was where value had to come into view. It shaped what patients noticed every time they returned.
Patients could keep giving SWEETCH information without clearly seeing what mattered for them right now.
The system needed to surface the most relevant value — without overwhelming them.
What should the homepage surface so patients can quickly understand what matters now — and how it connects to progress over time?
What matters most should not be buried among everything the product can do.
Patients need to understand what matters today while still seeing the larger direction of their progress.
SWEETCH could help connect signals, surface patterns and highlight what might matter — rather than leaving patients to interpret raw information alone.
I reframed the homepage as the place where SWEETCH surfaces what matters most.
Instead of treating the homepage as a menu of everything the product could do, I used it to prioritize a personalized story around the patient's goals, current activity, progress and emerging insights.
The question became less "What can SWEETCH show?" and more "What does this patient need to see now?"
What matters to me.
What needs my attention.
What is changing.
What SWEETCH is noticing.
What may help me next.
Where I can explore when I need more detail.
The homepage, prioritized around what the patient needs to see now.
The in-progress state connects daily activity to the larger goal, helping patients see how each action adds up over time.
When a goal is reached, the experience closes the loop with a clear moment of recognition — making the value of continued effort visible.
The patient did the tracking. SWEETCH needed to help make sense of it.
The homepage made the most relevant value easier to see — now and over time.
Patient effort → Patient value
SWEETCH imagined a companion that could guide patients through daily health decisions — so support felt personal, not clinical or lonely.
The company had a vision. Now the companion needed a job description.
The vision was warm. The role it created was demanding.
Written out as a job description, the companion had to carry the brand, the guidance and the relationship — every single day, without wearing out its welcome.
High-exposure position. Long-term relationship. Must not become annoying.
Characters are not a new idea. Before designing one, I looked at where they had worked before — and what they were actually hired to do.
Great at being remembered.
Usually not responsible for helping you complete a task.
Some products successfully brought characters into the digital experience.
But persistent in-product companions were surprisingly rare.
Being a great mascot and being a great product companion were not the same job.
Why?
Clippy proved that personality alone is not enough — an assistant also has to know when to speak, when to stop, and when to stay out of the way.
The risk wasn’t personality. It was interruption.
If users don’t connect with the character, constant presence becomes friction. Even if they do, too much exposure can wear out the welcome — especially when that character is always there, talking, guiding, and tagging along.
It was putting the whole relationship on one face.
Headspace pointed to a different kind of answer: a product could feel human and expressive without putting the whole emotional load on one permanent character.
Personality did not have to come from one mascot. It could live across a cast.
The clue was not one star character. It was a more distributed kind of presence.
The research left me with two rules.
Always move the user forward. Never get in the way.
Don’t ask one character to carry the whole relationship.
Build a cast, not a star.
I recommended a different character for each health domain — keeping support human and contextual without putting the whole experience on one face.
When the patient entered a health domain, that domain’s character became the voice of support.
SWEETCH needed detailed health information to personalize the experience. The challenge was making a necessary, lengthy onboarding feel manageable.
How could we keep the depth of personalization without making onboarding feel heavy?
Personalization required a lot of context — and therefore a lot of patient effort upfront.
The willingness to invest that effort was not constant. Motivation changed as effort, progress and setbacks accumulated.
Literature review · Competitive research · A/B testing · Post-use survey
The research pointed to three ways to reduce the perceived weight of the experience.
Positive messages between questions helped give the process purpose and maintain momentum.
Previewing personalized features, support and insights gave patients a reason to keep going.
Splitting onboarding between the landing page and the app made one long process feel like two shorter experiences.
We didn’t remove the information SWEETCH needed. We changed how the effort was experienced.
One continuous ask, all upfront.
Basic information
Goals · health context · personalization
Give every effort somewhere meaningful to go.
Give the effort a reason
Turn data into something useful
Make change visible now and over time
Help in the moment that matters
A connected system that helps me focus effort where it matters and drive meaningful progress.
A connected system that helps me focus effort where it matters and drive meaningful progress.
Give the effort a reason
Turn data into something useful
Make change visible now and over time
Help in the moment that matters
Onboarding — Make the first effort manageable
Reinforce progress · Show the payoff early · Break one long experience into two
These principles became a shared lens for product decisions across the experience.
Does this connect effort to something the patient cares about?
Does it help the patient understand what their data means?
Does it make progress visible now and over time?
Is the support timely, relevant, and easy to act on?
Is the value clear enough to justify the effort?
I wish.
Much of the final product work belongs to SWEETCH and can’t be shared publicly. What I can show here is part of the research, systems, decisions, and selected product evidence behind the experience.
If you’d like to go deeper, I’m happy to walk through what I can share privately.
Let’s talk →
