The brief
Leadership at Selfapy asked for a way to gather information about doctors already prescribing the service, since many healthcare professionals still didn’t know it existed. The legal constraint shaped the brief from the start, doctor names and details couldn’t be required, and the flow had to make that voluntary status real, not just stated somewhere.
Testing two versions
I tested two versions, each with different copy and layout, both aimed at the same problem, making a patient feel safe handing over information about their doctor. I showed both to four patients and evaluated three things: how easy the flow was to complete, how clearly they understood what was being asked, and whether they felt confident providing it. One version won out.
The catch
The compliance answer ended up being the design answer too. Input fields stayed visible, but nothing was marked mandatory, not visually, and not when a field was left empty. A patient could skip the entire section and move on. That’s what made the flow GDPR compliant, built into the interaction itself rather than added as a disclaimer on top of it.
What happened
The flow shipped. I never got data on what happened after launch. Looking back, I think there are better, more GDPR-aligned ways to gather this kind of information today. At the time, the app already had too many onboarding-style flows stacked on top of each other, and this added one more, driven by a leadership request rather than something I identified as a user need myself.
