The best design thinker I ever worked with never once used the term.
Her name was Selwyna McKetney. She taught at C.A.R.E., the school where I taught during my Peace Corps service, and I watched her adjust in every single class. If a lesson wasn’t landing, she changed it on the spot. If students started drifting, she switched gears before most teachers would have noticed anything was off. The plan she walked in with was a starting point, never a script.
She wasn’t winging it. She was paying attention. She watched faces, listened to the questions, noticed who had gone quiet, and reshaped the lesson around what was actually happening in the room instead of what was supposed to happen.
That’s design thinking. She just never needed the label.
I bring her up because design thinking for nonprofits usually gets sold as something fancy. A two day workshop. A wall of sticky notes. A facilitator with a lanyard and a lot of markers. Fine, I like markers. But the real thing is simpler, cheaper, and way more familiar than most nonprofit leaders realize. You’re probably closer to it than you think.
I’ve seen this from the teaching side too. At SUNY Geneseo, I taught design thinking classes to staff and students and served as the Innovation Team Leader. The best moments in those rooms never came from the slides. They came when someone stopped defending their idea and started watching how real people actually used it. That shift is the whole point, and you don’t need a campus or a budget to make it.
What Design Thinking Actually Is (Once You Strip Off the Jargon)
The five stages in plain English
The version most people learn has five stages: empathize, define, ideate, prototype, and test. It sounds like a syllabus. In practice it’s pretty down to earth.
Empathize means you go find out what people actually experience. Define means you name the real problem, not the one written into your last grant narrative. Ideate means you come up with more than one answer before you fall in love with any of them. Prototype means you build a rough, cheap version. Test means you put it in front of real people and watch what happens.
Then you loop back and do it again.
It’s less a recipe and more a rhythm. Think of tuning a guitar by ear. You pluck, you listen, you adjust, you pluck again. Nobody tunes a guitar once and calls it done for the year.
Why it fits nonprofit work better than you’d think
Plenty of companies use human centered design to sell more stuff. You’ve got a better reason. Your whole existence depends on understanding people whose lives may look nothing like the view from your board room.
So design thinking for nonprofits isn’t some tool you borrowed from the corporate world. It’s a formal name for what your best program staff already do on instinct. The difference is doing it on purpose, out loud, and across the whole organization instead of in one person’s head.
Why Nonprofits Talk Themselves Out of Creativity
The “we can’t afford to fail” trap
Every executive director I know carries the same weight. Funders are watching. Budgets are tight. The mission is on the line. So when someone pitches a new idea, the reflex is protection. What if it flops? What will the foundation think? How do we justify the cost?
Fair questions. The problem is that the reflex treats every idea like a full launch.
Design thinking flips that. You don’t bet the building. You bet a Tuesday afternoon. Failing small is cheap and kind of useful. Failing big because you never tested anything? That’s the expensive kind, and it’s the one nobody puts in the annual report.
Creativity isn’t a department
Too many organizations act like creativity lives in the communications office. Comms makes things look nice. Everyone else does the “real” work.
I’ve spent twenty years in this sector watching that split quietly cost organizations their best ideas. The case manager who notices the intake form confuses everyone is doing creative work. So is the volunteer coordinator who rebuilds orientation because people kept leaving at the break.
Nonprofit creativity is already all over your building. Most of it just never gets permission to count.
Start With Empathy, Not Assumptions
Get out of the conference room
Most program decisions get made in rooms the people you serve never walk into. That’s the first thing to fix.
Sit in your own waiting area for an hour. Fill out your own application form on your phone, standing up, with one hand. Show up at your own event without a name tag and see how long it takes for someone to tell you where to go.
Every stretch of service I’ve done, from Peace Corps to AmeriCorps to Habitat builds, kept teaching me the same thing. You don’t understand a situation from the outside looking in. You understand it standing where everyone else stands.
Empathy here isn’t a warm feeling. It’s research. You’re collecting what people actually do, not what your strategic plan assumes they do.
Listen for the words people actually use
Pay close attention to language. If families call your program “the Thursday class” and your website calls it an “Adult Literacy Empowerment Initiative,” you’ve got a design problem and a brand problem wrapped into one.
The words your community uses are a map. Follow them. They’ll tell you what people value, what confuses them, and what they’d never bother to say in a survey. Honestly, half of good nonprofit messaging is just borrowing the vocabulary of the people you serve and giving it back to them with respect.
Prototype Like You Have No Budget (Because You Don’t)
Paper, phone calls, and one week tests
Prototype sounds like a word from a lab with expensive equipment. In nonprofit life, it can be a sketch on printer paper. A mocked up flyer. A new script for whoever answers the phone. A pilot that runs for one week with five people.
Before you overhaul volunteer onboarding, try a one page version with the next three volunteers who walk in. Watch where they get stuck. Ask them what was confusing. Change it. Try again.
It’s like cooking dinner for your family before you agree to cater a wedding. You want to find out the sauce is too salty while the stakes are still low.
Small bets beat big launches
Nonprofits love the big reveal. The website launch. The rebrand unveiled at the gala. I get the appeal, and I’ve designed my share of those moments.
But a big launch is a one shot deal. If you guessed wrong about your audience, you find out in public, with your logo on it.
Small bets let you be wrong quietly, learn fast, and walk into the big moment with something that already works. And funders tend to like that story anyway. We tested it. We learned. We adjusted. That’s the kind of nonprofit innovation that builds trust instead of burning it.
Building a Culture Where New Ideas Survive
Give the board a job besides saying no
Boards often become the place ideas go to quietly retire. Not out of bad intent. Most boards are wired for risk management, and that’s part of their job.
So give them another job too. Invite a board member to sit in on a test session. Let them hear the feedback firsthand. A trustee who watches three parents struggle with your registration form will push to fix it faster than one who reads about it in a memo.
I serve on a library board myself, and I can tell you nothing moves a board quite like seeing the problem with their own eyes.
Make it safe to bring half finished ideas
If people only speak up once an idea is polished, you’ll hear very few ideas. Make room for the rough ones.
Open a staff meeting by asking what everyone would try if it couldn’t fail. Share the pilot that flopped and what it taught you, with the same energy you’d share a win. Thank the person who pointed out the broken process instead of sighing at them.
Creativity in nonprofits doesn’t need a big budget line. It needs permission, a little patience, and a leader who’s willing to say “let’s try it small and see.”
A Habit, Not an Event
I still think about Selwyna’s classroom. No workshop, no consultant, no sticky notes. Just a teacher who kept watching and kept adjusting because her students were the whole point.
That’s what design thinking for nonprofits looks like when it’s working. It’s not a retreat you hold once every three years. It’s a habit you build into how your team notices problems, talks to the people you serve, and tests ideas before betting the budget on them. Start with empathy. Name the real problem. Try more than one answer. Build it rough. Watch what happens. Then go again.
Your organization already has the raw material. You’ve got people close to the work, a community with opinions, and more creativity on staff than anyone’s given credit for.
What would change if the people you serve got to mark up your next program before you launched it?
Frequently Asked Questions
What is design thinking for nonprofits?
It’s a problem solving approach built around the people you serve. You learn what they actually experience, define the real problem, brainstorm several possible answers, build cheap rough versions, and test them before committing time and money. For nonprofits, it’s a structured way of keeping community voice at the center of program, service, and communications decisions.
Do we need a consultant or facilitator to use design thinking?
No. Plenty of small teams practice it with nothing more than curiosity and a willingness to test ideas. An outside facilitator can help when internal politics are stuck or when a team is too close to a problem to see it clearly, but the core habits of listening, prototyping, and adjusting belong to your staff, not to anyone you hire.
How is design thinking different from strategic planning?
Strategic planning sets direction over several years and tends to work from the top down. Design thinking works from the ground up and moves in short loops, testing specific ideas with real people. They work well together. Your strategic plan tells you where you’re headed, and design thinking helps you figure out what actually works once you get moving.
How can a small nonprofit with no budget get started?
Pick one small, nagging problem, like a confusing form or a volunteer orientation people drift away from. Talk to five people who experience it. Sketch two or three possible fixes on paper, try the most promising one for a week, and ask for honest feedback. That single loop costs almost nothing and teaches your team more than any training session.

Responses
What are your thoughts on this post?