Collaborating With Local Communities For Accessibility

Voices from the Village says its trust - not tech - that delivers #digitalhealth success 🩺 75% of telemedicine programs fail during implementation. But what happens when you flip the script and let communities lead? Intelehealth just released a study from Maharashtra’s tribal regions proving that the key to successful telemedicine isn’t better technology - it’s better trust. India’s 104 million tribal people face a “triple burden” of disease: 1. malnutrition, 2. communicable diseases, 3. rising diabetes/hypertension. In Nashik's remote villages, the nearest doctor is over 20 kilometers away. Women need permission from male family heads just to seek healthcare. Instead of replacing traditional healers, Intelehealth’s Nashik Arogya Sampada project worked WITH them. 🥼 They trained local Community Health Workers (CHWs) who speak the language, understand the culture, and live in the community. #Telemedicine Results That Matter: - 74% diagnostic accuracy compared to in-person consultations - Free doorstep medicine delivery eliminating travel barriers - Women can now access healthcare without seeking permission - CHWs earn sustainable income while serving their neighbors The secret sauce? A digital assistant called #Ayu that guides CHWs through 150+ evidence-based protocols, ensuring quality care regardless of education level. This is healthcare equity. When you design WITH communities instead of FOR them, you don’t just bridge the digital divide. You eliminate it. What would healthcare look like if every program started with community trust instead of cutting-edge tech?

"I have lived with this problem for 15 years, and these kids solved it in 6 days." My friend and collaborator, Fernanda was crying when she said this. She had lived with quadriplegia for years. She had to dive under her wheelchair every night to plug it in. It took 45 minutes just to get the cord connected right. If she got it wrong, she couldn't leave her room the next day. Some people might think, “well that’s too bad, but that’s just her lot in life. It’s not the best use of our time to address this,” or they may believe “there’s not much we can do,” but they’re wrong. And a group of teenagers proved it. You see, Fernanda changed the world. She changed my life and pushed me to develop a more collaborative version of human-centered design that would impact individuals and communities long after she passed away. For 15 years, no one had asked her what she actually needed. My Design the Future program: 6 days, high school kids, asking questions and co-designing solutions for and with people with disabilities. People asked me: "Do you really think 16-year-olds can handle this kind of challenge?" I said: "Absolutely. No one's told them it's impossible yet." On day 6, everything changed. Fernanda sat in front of the classroom and plugged her chair in in just 20 seconds. Perfect fit. The device the kids designed made it effortless. It didn't even take them the full week to improve her life forever. Here's why it worked - and why, if you're a nonprofit leader, it could work for your organization too: → We started with people experiencing the problem (not just statistics about it) → We designed WITH them, not FOR them → We tested with real people before assuming we had the right solution → We measured transformation, not participation Several of those kids went on to study engineering and accessibility. One launched her own consulting firm. And Fernanda, she gained greater independence, which should almost always be our goal in the social sector. You already know this truth in your heart: the people closest to the problem are closest to the solution. Most nonprofits design programs in boardrooms and then wonder why communities don't engage the way they hoped. But you didn't get into this work to make assumptions about what people need. You came to actually help them get what they need. What would change if your next program started with this conversation: "What do you actually need?" Instead of: "Here's what we think you need"?

When I was 8, I learned an unforgettable lesson about assumptions and inclusion. Growing up, I always visited family in rural Panama. (A bit removed and hardly visited by tourists.) I happened to cross paths with an American girl visiting with her family. When I asked why they were there, she said, “We’re here to help you.” I didn’t understand—help with what? My community was happy and thriving. It wasn’t until later I realized they’d come on a mission trip, assuming we needed assistance without ever asking us. That feeling of having my reality misunderstood—and being spoken for instead of spoken with—has stayed with me ever since. Now, as someone working to shorten the bridge between customer and product, I see how often organizations repeat this mistake, especially in accessibility. Designing for people without involving them can feel just as alienating as assuming they need help. Here’s what happens when we shift the approach: • Communities feel seen and valued. 👥✨ • Solutions meet actual needs, not assumed ones. ✅🔍 • Trust is built through collaboration. 🤝🏗️ This underscores that inclusion isn’t about “helping”—it’s about co-creating solutions. Actionable steps: 1. Ask before acting. Listen deeply to the community or customer. 2. Include customers in the process. Or build teams representative of your customer base. Design with, not for. 3. Challenge assumptions. True impact starts with collaboration.