Doing good while reading good — join the Nonprofit Good News-Letter.
Design thinking gets sold as empathy for outward-facing services. Its real value for a cash-strapped nonprofit is fixing the problems planning can't see — the patients who never show, the program nobody can attend, the internal logjam everyone blames on people. Three scenarios, and the single question behind all three.
A few weeks ago I laid out five ways a nonprofit can find opportunity, and argued that design thinking is only one of them — the lens that sends you to where the work actually happens, not the whole eye. Before that I made the case that design thinking and lean risk management are natural partners: design thinking brings empathy, a real understanding of the people you serve; risk management brings structure, a recurring process for acting on what you learn.
Fine in theory. But what does that partnership look like on a Tuesday, in a two-person shop, with no budget for a design consultant and no appetite for another framework?
Here are three places it earns its keep. Each is a scenario, not an actual case — but these are situations nonprofits face all the time, common enough that you'll likely recognize at least one.
Picture a community health center losing patients in the gap between referral and first appointment. The data is stark: forty percent of people referred to behavioral health never come to the first session. The reflexive fix — more reminder calls, more follow-up texts — barely moves the number, because it treats a no-show as a memory problem.
Design thinking asks a different question. Not "how do we get more people to show up?" but "what happens in a person's life between the referral and the appointment that stops them from coming?"
Ask that question the design way — through interviews, observation, and mapping the actual journey — and you surface barriers that are invisible from inside the system. No ride to the clinic. No childcare for the two hours it takes. The fear of what a mental-health appointment says about you. Confusion about what the visit even involves. A waiting room that feels like a hospital. Intake paperwork that reads like a deposition.
Each of those is a design problem with a design answer. A warm handoff from the referring provider straight to the behavioral-health team, instead of a cold referral and a phone number. A plain-language text that says what the first visit is actually like. A waiting area that doesn't announce "clinic." An intake that opens with a conversation, not a clipboard.
None of these require a bigger budget. What they cost is staff time and the willingness to look through the eyes of the person you're trying to reach — and in a shop where hours are the scarcest thing you have, that time is the real price. The bet is that paying it here costs less than the patients you keep losing.
Nonprofits build programs from needs assessments, funder requirements, and staff expertise. All valid inputs. All silent on the one question that decides whether the program works: does it fit the life of the person it's for?
Picture a workforce-development nonprofit with a genuinely good job-readiness program — strong curriculum, qualified instructors, real employer partners. On paper, sound. In practice, the sessions run Tuesday and Thursday mornings, which is exactly when the working parents it serves are on shift at the jobs they already have. The program plans for a hundred participants and serves thirty. The report writes itself: "demand was lower than projected."
Demand wasn't lower. The design was wrong. And a design-thinking approach would have caught it before launch — by testing the schedule with actual participants, trying evening and weekend formats, and iterating around what people can really attend rather than what the calendar assumed.
This is exactly where design thinking meets the opportunity side of lean risk management. An underperforming program is a risk sitting on your books. The same program rebuilt around how participants actually live is an opportunity — and the rebuild usually costs less than the original, because you stop paying for empty seats.
Design thinking gets sold as a tool for external services. It works just as well on the internal machinery that quietly drains a small staff.
Picture a mid-size nonprofit that can't get grant reports out on time. The data is unreliable, the reports are always late, and the development team and the program team each privately blame the other. The standard remedies — more meetings, firmer deadlines, a sterner accountability conversation — go nowhere, because the problem was never motivation.
So the organization maps the actual path a single number takes from the field to the final report: who captures it, where it lives, how it moves between departments, where it stalls. More often than not, the culprit turns out to be plumbing, not people — the same figure re-entered into systems that don't talk to each other, with the hand-offs between them swallowing the days.
The fix is rarely dramatic — often just a single shared entry point both teams can see — and the reporting delay shrinks accordingly. They find it by pointing design thinking inward: mapping the journey, marking the friction, prototyping a fix — the same discipline they'd use on a client-facing service, turned on their own back office.
In every case, the answer comes from looking at the problem through the eyes of whoever actually has to live with it — the patient, the participant, the staffer stuck re-entering the same number. And in every case, the answer is cheaper and more effective than the conventional one, because it fixes the real barrier instead of the assumed one.
That is what design thinking actually is: a discipline of attention. It makes you stop guessing what people need and start watching what they experience. For an organization running on thin margins, that discipline is worth more than almost anything you could buy — which is exactly why it belongs inside your risk work, not off in a design workshop by itself.
A caution, since this is a series about doing the work well: design thinking is not a cure-all, and the next post is about where it goes wrong. Watching users is not the same as pandering to every request; prototyping is not an excuse to skip the hard call. The lens shows you the opening. You still have to decide, and pay for, what to build.
Don't schedule a design initiative. Take one step.
Pick a single internal process that reliably frustrates your team — grant reporting, client intake, volunteer onboarding, whichever generates the most complaints. Put it on a whiteboard: every step, every hand-off, every point where information passes from one person or system to the next. Circle the places it snags. Then ask the only question that matters: if we were building this from scratch for the person who actually has to use it, what would we do differently?
You'll usually find the redesign costs less than the problem does — but "less" isn't "nothing." It costs the hours you spend mapping and testing, and now and then a prototype tells you the fix won't work. That's still cheaper than funding the broken version year after year. That's why it's an opportunity, not just a fix.
Part of the Opportunity Series — building nonprofit resilience by hunting for openings, not just managing threats. This is Part 2 of a three-part run on design thinking. Part 1 made the case that design thinking belongs inside risk management; Part 3, on doing it well without the hype, is next in the series.
About the author
Ted Bilich has helped nonprofits manage risk and build resilience for more than thirty years. He is the author of Managing Your Nonprofit for Resilience (Wiley, 2023), a frequent nonprofit-podcast guest, and a regular presenter to nonprofits and funders on resilience and governance.