What I've Learned About Impact, Iteration and Imperfection at Dhwani RIS
As Dhwani turns 10, I find myself reflecting on a journey that has been far from linear—but rich with lessons on building for impact, embracing iteration, and making peace with imperfection.
After spending several years at the intersection of technology, impact, and data, I was looking to go deeper—not just working on the programmatic side, but to understand how technology could be a tool for systemic problem-solving, that’s when I joined Dhwani two years ago.
Since then, I’ve had the opportunity to lead one of our largest and longest-standing partnerships with Amazon, a role that has taught me what it truly means to balance quality, timelines, and empathy, while also mentoring a growing team.
These past two years have shown me that while impact takes time, iteration is necessary, and perfection isn’t the goal. Here’s what I’ve learned along the way.
Expectations vs. Ground Realities
One of the biggest unlearning moments for me at Dhwani was realizing that technology can solve many programmatic challenges but it doesn’t guarantee that what we expect will fit neatly into ground realities.
I saw this firsthand while working on a disaster relief program with Amazon Philanthropy in India. We were entrusted with automating how real-time needs from the ground were captured. In theory, the system worked—it was agile, robust, and connected nonprofits, frontline workers, suppliers, warehouses, and program teams.
However, we underestimated the sheer complexity of working in disaster-hit zones. A sleek dashboard is unable to address patchy internet, shifting contexts, and emotional and physical toll on field teams. Despite the “right” system, we went through the drawing board multiple times, and simplified interfaces, localized flows, and refined it for each user, from flood-hit villagers reporting needs to warehouse teams handling logistics.
We were building more than a product, a process backed by a Minimum Lovable Product. The impact was gradual and visible once the team started trusting the system, data informed Amazon’s strategy for disaster relief in India was in place. It taught me that impact is slow, and that’s okay. Because it’s in that slowness that we learn to design better, respond more meaningfully, and build systems that actually work for the people who need them most.
Building, Breaking, Rebuilding—Together
We learnt some of the most valuable lessons at Dhwani in moments of crisis.Iteration is not always a structured process, but it’s where the real work happens.
While working on the disaster relief platform for Amazon, we presumed everything was figured out—sprint demos were strong, workflows were intuitive. However, during a live load test with real users like nonprofits, warehouse teams, suppliers, field partners—the system buckled. Different networks, devices, and operating contexts exposed unpredictable issues.
When such setbacks discouraged the team, I stepped in as a leader, not to fix the cracks, but to help my team reassess our approach and question if the product is usable and serving its audience, under real conditions. Iteration is about asking better questions, redefining success, and being honest about what a product can and cannot do. It allows us to clearly call out users what to expect, when to use it, and how it can support them best.
Rebuilding with empathy, not ego, has become core to how we work. And that’s what makes the product, and the process stronger.
Fall Several Times, But Still Get Up – With the Community
One thing I’ve learned time and again is that setbacks are part of the process. It's better to fail in a demo than crash in the field. But even a successful test doesn't guarantee smooth ground execution. And that's okay. It doesn't mean the product failed. It means we're building for complex, human realities. There’s no perfect one-shot solution.
Expecting flawless tech, especially when we’re building for human-centric, high-stakes realities, is not just unrealistic, it’s unfair.
We design for extreme realities—emergency relief, health access in rural districts, data for farmer collectives, and not comfort.The goal isn’t to be flawless. The goal is to be useful, usable, and honest about our limitations. These moments are not failures, but invitations—to reflect, reframe, and refine.
We don’t work in silos. At Dhwani, the program team is just one layer. The real backbone is our product, data, and tech teams—translating complex problems into solutions that hold up on the ground. We bridge the gap, bringing community needs forward and ensuring the solutions stay rooted in them.
Over time, I’ve seen us grow in skills and culture. People who've been here longer than I have often say this has been a journey of learning, unlearning, and deep collaboration. Sure, we move fast. And yes, that sometimes brings friction or delays. But there's space here—to ask questions, give feedback, listen with empathy, and most importantly, stay transparent with each other.
We’re still building. We’re not perfect—and we don’t pretend to be. Claiming to have it all figured out often means missing what still needs work. What I value most is the humility in how we work. We understand the problems are complex, and that solutions need more than tech. They need care, constant iteration, and the quiet confidence to keep showing up.
The Real Measure: Problem Identification, Product Uptake, and Impact Strategy
One of the hardest lessons I’ve learned is that low product uptake often comes down to two things: we misidentified the problem, or the solution added complexity instead of removing it. If it doesn't make life easier for users, it won't stick
Developing tech for good values is not about instant gratification or flashy launches, it is about real satisfaction when the tool is used regularly, data flows in steadily, and that data feeds back into a programmatic strategy that actually drives impact.
If any one of these three—usage, data, or strategy—is missing, it signals a need to rethink. Designing technology for human-centered impact demands constant empathy, simplicity, and alignment with real needs. It’s a cycle, not a sprint. This cycle of identifying the problem, building solutions that truly simplify users’ lives, and watching impact grow over time is what keeps me going. Falling, learning, and rising with the community every step of the way.
Looking Ahead: A Decade of Learning, and Many More to Come
As Dhwani marks its 10-year milestone, it’s a realisation that our journey is far from over. What we’ve built so far, through the trials, triumphs, and countless iterations is a foundation rooted in humility, resilience, and a deep commitment to the communities we serve.
As we look ahead, our mission is clear: build tools and systems that truly serve people, especially in the toughest contexts. The challenges will grow, but so will our commitment to innovate with care, collaborate deeply, and center those often left behind.
I’ve learned that real impact takes time, iteration is key, and technology is only as strong as the intent behind it. As Dhwani marks a decade, I’m grateful for the journey and energized for what’s next. We’ll keep listening, breaking silos, and building products people not only use but love. With humility and grit, we’ll keep learning, falling, and rising with communities toward a future where technology empowers and uplifts all.
← All insights