Before Continuum, I worked on two healthcare product projects: SafeRange and Health Aura Skin.
And honestly, working on these projects made me think about the same problem from another angle.
I started seeing how easily care could just end.
Not necessarily because the product was broken.
But because the journey continued beyond the product.
A patient could leave an appointment.
A recommendation could be made.
A next step could be assigned.
And then what?
Who knows whether it happened?
What happens when it doesn’t?
Where does that information go?
Who is supposed to notice?
Who is supposed to act?
That was the part that stayed with me.
Because I realised I wasn’t only interested in whether a product worked at the point of interaction.
I was interested in what happened after.
What happened when the patient left the interface.
When the care team moved on.
When the next step depended on something outside the system.
When the expected path didn’t happen.
That became the question I kept returning to:
What happens beyond the interface?
And that question changed how I think about designing for healthcare.
I don’t just want to design the screen where an action happens.
I want to understand the workflow around it.
What was intended?
What needs to happen next?
What evidence should exist?
What happens when it doesn’t?
Who needs to know?
Who needs to act?
And what brings the journey to a close?
That thinking eventually led me to build Continuum.
And now, when I design health-tech products, I find myself asking the same question:
What happens beyond the interface?
Not just whether a patient can complete an action on a screen, but what happens after.
When the patient leaves the hospital, the care team moves on, and the system has to somehow keep the journey going.
That question is what led me to Continuum.
It started with something I kept coming back to:
What happens after the patient leaves?
Continuum is my attempt to turn that question into something we can actually look at, map, and design for.
It’s a self-built framework — not a client project, and not a claim that I’ve shipped this system.
It’s a demonstration of how I think about healthcare products, clinical workflows, and the gaps that appear after the encounter ends.