Human-Centered Design in Nonprofit Projects

I asked a nonprofit CEO: "Who designed your program?" Her answer: "Our board and I spent months in strategy sessions mapping it out." "And who did you design it for?" "Families experiencing food insecurity in our community." "How many of those families were in those strategy sessions?" Silence. This is why most well-intentioned programs fail before they start. Here's the actual algorithm for lasting change: Step 1: Start with people, not problems Not data about the problem. Not assumptions about the problem. The actual humans living it daily. Step 2: Understand the system, not just the symptom Homelessness isn't a housing problem. It's mental health + addiction + economic + policy issues that show up as housing. Step 3: Design with, not for The people closest to the problem are closest to the solution. Make them co-creators, not beneficiaries. Step 4: Test small, learn fast Before you scale, make sure it actually works. For the people using it, not just the people funding it. Step 5: Design yourself out of business If your solution is working, people shouldn't need you forever. I've seen this approach reduce homelessness, cut recidivism, and save infant lives. It works because it respects the intelligence and agency of the people it serves. Most organizations skip Step 1 and wonder why their communities don't engage. What step does your organization struggle with most?

Efficiency isn’t neutral. When we design care out of services, we design loneliness in. This week I was talking to a friend who mentioned that her elderly neighbour was devastated that Meal on Wheels was no longer available in her area. In many parts of the UK, this lifeline—hot meals delivered to elderly and vulnerable people, by someone who actually stops and chats, has disappeared. In its place? Tech platforms that let people click and collect or sign up for pre-selected menus. Yes, food is still delivered. But the connection is gone. That hello, a smile, someone noticing if you're not yourself. That short exchange is sometimes the only contact people have all day. And for a lot of people, that matters. It got me thinking, What happens when we optimise people out of care? When connection is seen as “inefficient”? Designing for social impact means constantly asking ourselves: What are we solving for? If it’s only efficiency or cost, we’ll continue to build services that function but don’t care. Tech isn’t neutral, it reflects values. And when tech replaces human interaction in care systems ( instead of supporting it), we risk deepening isolation, especially among those already pushed to the margins. As service designers and nonprofit practitioners, we need to ask: • Are we designing with people, or just for them? • Can we centre interdependence over independence in our models? • What does it mean to design with care, not just for efficiency? The “solution” isn’t always an app. Sometimes, it’s a cup of tea and a conversation #socialimpact #design #community __________________________ Design for Social Impact Lab is a social enterprise on a mission to support organisations and rebellious practitioners design equity-centred, anti-oppressive programs, policies and research * We are on a mission to improve the accessibility of our website and resources ( I will be sharing an exciting collaboration coming up!). If you are using assistive technologies to read our posts, and find that something is not accessible, let us know and we can share alternative formats and see where we can improve our alt-text descriptions

HOW TO DESIGN A PROGRAM AS AN NGO (STEP BY STEP) I have seen many NGOs rush to start a program because they want to act quickly. But speed without structure usually leads to wasted resources, weak impact and frustrated beneficiaries. Before you launch your next project, slow down and design it properly. Here are ways to design a program: 1. Start with the real problem, not the activity: Don’t say, “We want to train 100 women.” Ask: What exactly is the problem? Lack of income? Limited market access? Low digital skills? If you don’t define the problem clearly, your solution will be guesswork. 2. Talk to the people affected: Many NGOs design programs from the office. Go to the community. Ask questions. Listen more than you speak. The people affected often know what will actually work. 3. Be specific about the change you want to see.: What should be different after 3 months? 6 months? 1 year? Clear outcomes help you measure success and explain your impact to donors. 4. Design activities that directly connect to the outcome: Every activity must answer one question: “How does this help us solve the problem?” If it doesn’t connect clearly, remove it. 5. Budget realistically: Under-budgeting kills programs halfway. Over-budgeting without justification scares funders away. Be practical and transparent. 6. Plan how you will measure results: How will you know the program worked? Attendance sheets are not impact. Define simple indicators you can track. 7. Think about sustainability from day one: What happens when funding ends? If the program collapses immediately, it wasn’t designed well. Strong programs are not built on passion alone. They are built on structure. If you are running an NGO and your programs feel chaotic, the issue may not be funding, it may be design.

We serve people at their most vulnerable in healthcare - during crisis, uncertainty, and profound life changes. Human-centered design lets us create spaces, operations, and technologies intentionally designed for those circumstances instead of treating vulnerability as an afterthought. Human-centered design starts with deeply understanding people's experiences before designing anything. You observe how people actually move through spaces and systems. You listen to what matters to patients, families, and staff. You test your assumptions. You iterate based on real feedback. The goal is making things work for humans under real conditions. Why Healthcare Is Unique In healthcare, people are anxious, overwhelmed, navigating unfamiliar systems while managing fear and uncertainty. Their needs evolve as their conditions change. The same patient requires different support during diagnosis than during chronic management. Care teams have deep clinical expertise, but patients and families experience things care teams can't fully see. The night shift works differently than day shift. The moments between clinical encounters - the waiting, the processing, the quiet conversations - often matter as much as the medical interventions themselves. Assumptions in this context are expensive. What seems logical to us might create confusion for patients. What works on paper might fail when people are exhausted or scared. What It Requires Human-centered design is a discipline, not a checklist: + Observing across time - 2am looks different than 2pm + Listening to multiple perspectives - patients, families, all staff roles + Testing before committing to permanent solutions + Designing for behavior under stress, not ideal conditions + Understanding that transformation requires space changes, operational changes, and behavioral changes to align Why It Matters Human-centered design creates solutions that actually work - not just at ribbon cutting, but years later when real life takes over. It builds trust. It supports both clinical excellence and human dignity. Healthcare spaces and systems shape some of life's most important moments. Human-centered design ensures we're creating experiences worthy of those moments.