Start by changing the word, not the budget

Boards often hear "design" and picture fonts and colors. Arguing for more of that at the strategy stage will sound like decoration creeping into serious work. So reframe what you're asking for.

• Talk about "user-centered planning," "program design," or "testing our assumptions with the people we serve." These are what a strategic designer actually does.
• Describe the designer's role in terms of outputs the board already values: clearer decisions, fewer failed launches, programs people actually use, messages donors understand.
• Make the distinction explicit: "Right now we use design to explain decisions. I'm proposing we use it to make better ones."

Speak the board's language: risk, money, and mission

Board members are stewards. They respond to arguments about avoiding waste and protecting the mission more than to arguments about creativity.

• Risk: Strategy built without early input from beneficiaries or donors rests on untested assumptions. A designer's job is to surface and test those cheaply before money is committed.
• Cost: Changing a plan on paper is cheap. Changing a program after launch, reprinting materials, or rebuilding a website is expensive. Late design work often means discovering problems when they're costliest to fix.
• Mission: If a program is hard to access or a campaign is confusing, impact suffers regardless of how good the strategy looked in the boardroom.
• Fundraising: Funders increasingly want evidence of community input and user-tested approaches. Design methods produce exactly that documentation.

Use your own history as evidence

Outside statistics help a little (McKinsey's "Business Value of Design" report is often cited), but your strongest case is internal.

• Find two or three past projects where late-stage problems cost time or money: a campaign that confused donors, a program with low uptake, a report nobody read, a website rebuilt twice.
• Ask, for each one, "What would we have learned if we'd talked to users or prototyped this in month one?"
• Quantify where you can: staff hours on rework, reprint costs, missed enrollment targets, lower response rates.
• Pair that with a nonprofit peer that used human-centered design well. IDEO.org, the Gates Foundation, and many UN agencies have published case studies.

Propose a small, low-risk pilot

Don't ask the board to restructure how strategy works. Ask for one experiment.

• Pick an upcoming initiative that's important but not existential, such as a new program, a donor campaign, or a service redesign.
• Bring a designer in at kickoff for a defined scope: a few weeks of discovery interviews, journey mapping, and rough prototypes tested with real users.
• Agree in advance on what success looks like: insights that changed the plan, issues caught early, better engagement metrics than a comparable past project.
• Keep the cost modest and clearly bounded. Pro bono designers, design school partnerships, or organizations like Catchafire and Taproot can lower the barrier.
• Report back with before-and-after comparisons and stories from users.

A successful pilot turns an abstract argument into a precedent.

Let the board experience it

People are often convinced by participating rather than by being told.

• Run a 30–45 minute exercise at a board meeting: show a real piece of your communications or a program flow, and have members walk through it as a beneficiary or first-time donor would.
• Or bring a short video or quotes from user interviews that reveal something leadership didn't expect.
• The moment a board member says "I had no idea people saw it that way," you've made the case.

Anticipate the objections

• "We can't afford it." Reply: we're already paying for it through rework and underperforming programs. This moves the spend earlier, where it's cheaper.
• "Our staff already know our community." Reply: they do, and design methods make that knowledge visible and testable rather than assumed. It complements staff expertise.
• "This will slow us down." Reply: a few weeks of early testing typically saves months of course correction later.
• "Isn't this what consultants do?" Reply: strategy consultants analyze, while designers prototype and test with real people. The two work well together.

Find an ally on the board

• Look for a board member from tech, product, healthcare, or marketing. They've likely seen design used strategically and can vouch for it in peer terms.
• Brief them before the meeting so the proposal doesn't come only from staff.

Make the ask concrete

End with something specific and easy to approve, for example: "For our new youth mentoring program, we'd like to involve a designer from the start for six weeks, at a cost of X, and report back to the board in Q3 on what we learned and how it changed the plan."

A clear, bounded request with a built-in review point is much easier for a board to say yes to than a philosophical shift.