Edoo
2024
How I balanced GDPR compliance with UX for a new market
Problem area
New markets require more than cultural adaptation
Entering the EU meant meeting GDPR requirements the product had never addressed. For users, this created a bigger problem: they couldn't see what data was being collected, had no way to manage their privacy, and had no reason to trust a platform that didn't explain itself. This lack of transparency wasn't just a legal risk. It was a barrier to building the trust needed for conversion.
Touchpoints lacking data transparency
Her contribution has been key to defining a cohesive, human-centered, and high-quality product vision. She stands out for her commitment and resilience, always maintaining a constructive attitude even during the most demanding moments. Her work is characterized by exceptional attention to detail, a methodical approach, and a strong ability to take on responsibilities beyond her role as a Product Designer, bringing strategic insight into both product and user needs.
Design decision 01
How are platforms handling this?
Before designing or reading the regulations, I needed to understand how different platforms across industries were handling GDPR compliance. I analyzed key screens, flows, and components to identify common patterns and opportunities for improvement. This research helped me learn from existing solutions and find ways to balance compliance with better UX.
Privacy patterns
Design decision 02
Designing for compliance without adding friction
With competitor patterns identified, I started designing new screens and adapting existing flows to meet GDPR requirements. Users expect sign-up and consent flows to be quick and predictable, so adding too many steps would break their mental model. I applied progressive disclosure and contextual information to introduce compliance elements without overwhelming users or disrupting the flow.
New privacy screens
Design decision 03
Negotiating with legal became a design skill
Once I had design concepts ready, I needed to align them with the legal team. Legal feedback often included long texts that users tend to skip or distrust, and research shows that large blocks of text increase cognitive load and reduce comprehension. I presented alternatives that balanced legal needs with usability, like breaking content into smaller sections or showing details only when relevant.
Information structure comparison
Retrospective
A matrix for future decisions
Working with the legal team pushed me to find solutions that met their requirements without adding friction. I learned how to translate dense legal language into digestible, contextual information. This process made me more confident collaborating with non-design stakeholders and pushed me to think beyond screens and flows.
I documented everything into a compliance framework that could guide future features, and if I had more time, I would have tested whether different consent patterns affected conversion rates. The biggest learning wasn't about compliance, it was about negotiation.
