Doing good while reading good — join the Nonprofit Good News-Letter.
Lean risk management already scans for threats and opportunities. Design thinking changes where you look for them — starting with the people you serve. Run the two together and you surface openings a conference room never sees.
Lean risk management asks two questions, not one: what could go wrong, and what could go right? Done well, it catches threats and opportunities together. Design thinking asks a different kind of question: what does the person you're serving actually need? Most nonprofits treat these as separate conversations — if they have them at all. They shouldn't be.
I've spent years teaching nonprofits lean risk management — a structured, recurring process for identifying threats and opportunities and acting on the most important ones. It works. But I've noticed a gap in the process, and design thinking fills it.
Lean risk management, as I describe it in Managing Your Nonprofit for Resilience, follows a four-part cycle: identify risks, prioritize them, respond, and review. The system is built for practicality — it doesn't require a consultant or a corporate budget. A small team can run through the cycle in a half-day and come out with a risk register that changes how they make decisions.
But here's what the process doesn't do well on its own: it doesn't always get close enough to the people you serve. Risk identification tends to happen in a conference room, drawing on staff experience and organizational data. That's valuable. It's also limited. The risks you identify are the ones you already know about — filtered through your assumptions about what your clients need and how your programs work.
Design thinking starts in a different place. Tim Brown, who popularized the term, defines it as "a human-centered approach to innovation that draws from the designer's toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success." The first step isn't analysis. It's empathy — going out and understanding the lived experience of the people your organization exists to serve.
When you bring design thinking's empathy into lean risk management's structure, three things happen.
You discover risks you didn't know existed. A domestic violence shelter running a standard risk inventory might identify funding gaps, staff turnover, and facility maintenance as top risks. Send those same staff members to sit with residents and map their actual experience of the intake process, and you may surface risks the conference room never does: a safety protocol that inadvertently re-traumatizes clients, an intake form that asks questions in the wrong order, a waiting area that feels unsafe. These are real risks to mission delivery. They only become visible when you look through the client's eyes.
You find opportunities hiding inside problems. This is where design thinking's bias toward prototyping and iteration connects to the opportunity side of the risk register. Lean risk management asks you to list opportunities alongside threats. Design thinking gives you a method for finding them — by observing where the current system fails from the user's perspective, you discover where a redesign could produce dramatically better outcomes. The broken intake process is a risk. It's also the clearest map you have to a better design.
You build staff engagement into the process. Risk management can feel like a compliance exercise if it's run badly. Design thinking, by its nature, involves frontline staff in observation, ideation, and prototyping. When your case managers are the ones interviewing clients, mapping journeys, and proposing solutions, the risk register isn't a document that management produces and staff ignore. It's a shared tool that everyone contributed to.
You don't need to become an expert in design thinking to capture these benefits. You need one practice: before your next risk inventory, spend time observing and listening to the people your programs serve.
Send two staff members to shadow a client through your intake process and write down every friction point. Interview five program participants about what's working and what isn't — not with a survey, but with a conversation. Ask your frontline staff to describe the three moments in service delivery where things most often go sideways.
Then bring those observations into your risk identification session. You'll find that the risks and opportunities that emerge are different — and often more important — than what you'd have generated in a conference room alone.
The two methodologies were built for different purposes. But for nonprofits operating with limited resources, they're stronger together.
The fuller version — shadowing clients, interviewing five participants, debriefing your frontline staff — can wait. Start smaller. Pick one program. Ask one client to walk you through their experience of it, from first contact to completion. Don't ask whether they liked it. Ask them to describe what happened, step by step. Listen for the moments of confusion, frustration, or delay. Write those down.
That's the first step of design thinking's empathy phase — one conversation, not the whole of it. But it already gives you better data for your next risk conversation than any spreadsheet would. Do that, then widen: a second client, a shadowed intake, a staff debrief. The practice grows from one honest conversation.
Part of the Opportunity Series — building nonprofit resilience by hunting for openings, not just managing threats. I show how to fold empathy work into a lean risk inventory — no consultant, no new budget line — in Nonprofit Good News Premium.
Design Thinking for Nonprofits: Part 1 of 3. Next week: three use cases where design thinking changes how nonprofits operate.