HEALTH TECH · AI PRODUCT DESIGN · FOUNDER
63 Million People Ignored by Digital Health
Role: Founder & Designer
Research: 10 cultural interviews + 11,000 community comments
Product: WhatsApp-native AI
Challenges
63M
Hispanic people underserved by digital health
80%+
Use WhatsApp as primary communication tool
11K
Community comments analyzed ethnographically
There are over 63 million Hispanic people in the United States. Digital health adoption in this community lags significantly behind the general population. Every major health app has a Spanish language option. And almost none of them work — because translation is not design. You can translate every word perfectly and still build something that violates how this community communicates, builds trust, and makes health decisions. Plato Inteligente is my answer to that — designed from the inside, by someone from this community, for the people I grew up with.
What Every Digital Health Product Gets Wrong
THE CORE INSIGHT
Three things are failing simultaneously, and fixing just one doesn't help. Language isn't enough — apps translate to Spanish but don't understand the cultural context. Trust works differently — it's built through relationship and consistency, not credentials and privacy policies. And the delivery model is wrong — designing for WhatsApp means designing for conversation, not interfaces.
BEFORE
Apps translate to Spanish. Assume individual smartphone user. Build trust through clinical credentials.
AFTER
Design for cultural context. WhatsApp as infrastructure. Build trust by showing value before asking for anything.
Value Before Effort
THE DESIGN PRINCIPLE
The community I'm designing for is especially skeptical of products that ask for effort upfront — onboarding flows, data entry, tracking habits — before delivering any value. They've been burned before. So the product must give something useful first.
This principle drives every design decision in Plato Inteligente. The first interaction isn't an onboarding form. It's the product showing you something about yourself you hadn't articulated. Once someone feels understood, they'll invest their trust.
Archetype-Based Retention
THE 14-DAY FRAMEWORK
Not everyone is in the same place. I designed a 14-day retention framework built around three behavioral readiness archetypes — each experiencing the arc differently, all moving toward the same destination: Pride of Discovery.
The Optimizer wants structure — clear progress, measurable signals, concrete insights. The Caregiver responds to emotional tone — they're managing health for others and need the system to acknowledge that. The Navigator wants useful, non-repetitive information — they get frustrated by redundancy and respond to fresh daily insights.
Pride of Discovery is the moment when a user sees something about themselves they didn't see before — and it clicks. That's when the product earns the right to keep going.
Outcomes
Live Experiments
Behavioral testing with real users on WhatsApp — not lab simulations
Strong Early Signal
User called to say they love the system and feel genuinely understood
Archetype Framework
14-day retention loop built for cultural fit, not generic engagement
Methodology Transfer
Value-before-effort and live signal loops applicable to any underserved community
“Now I know why I feel this way.”
— Plato Inteligente user
“Designing for underserved communities isn't about translation. It's about redesigning every assumption — delivery model, trust mechanics, engagement patterns, success metrics — from the user's cultural reality.”
