Is Design Thinking a Missing Skill?

Most nonprofits are still running on org charts and workflows built for a different era, which rewards scale, hierarchy, and doing more with less. Those methods aren't wrong, exactly. Of course efficiency and resourcefulness matter, budgets have to balance. Efficiency alone doesn't maintain an organization where people want to stay at, volunteer for, or give to. Internal efficiency doesn't build trust, and trust, more than any strategic plan, is what determines whether a mission-driven organization actually thrives in contact with reality.

The questions I keep coming back to are: “Are we getting smarter as we go? Can this organization learn? Can it adapt? Can it help the people inside it (i.e. staff, volunteers, board, community) actually grow, and not burn out?”

Treat your organization like a living-system

I spent years doing styling, brand strategy and creative direction for fashion publications and advertising agencies before I moved into nonprofit and community work. I’ve been trusted to do marketing strategy at a working ranch, communications for a farm school, curating public exhibitions, coordinating events that had to sell out on shoestring budgets. What I brought with me from the fashion world wasn't simply aesthetics. It was the discipline of treating every touchpoint, every email, or event, or even hallway conversations, as data about how people experience you.

That's design thinking, whether or not anyone calls it that. Observe closely>Prototype cheaply>Test efficiently>Get it in front of real people.>Learn from mistakes.>Iterate. Some nonprofits actually do this instinctively with their programs, though not with their own internal culture or leadership practices. We will (maybe, hopefully) A/B test a fundraising email, though we don’t ask why the same staff members are exhausted, or why the same misunderstanding keeps coming up between the board and the team.

An organization is a living system. It generates enormous amounts of knowledge every single day with, every donor conversation, every volunteer shift, every program failure, or unexpected success, and almost all of it evaporates. Nobody wrote it down. No one connected it to the decision months later that repeated the same mistake. That's not a communications flaw, but an organizational design flaw, and it's fixable with the same rigor we'd bring to redesigning a logo or a guest experience.

Quarterly reports are a design artifact

I've watched boards and funders treat reporting as the toll you pay for the privilege of doing the actual work. I'd argue it's the opposite: reporting, done well, is your organization's memory bank. It's where frontline experience gets translated into institutional wisdom instead of staying in one person's head until they leave and take it with them.

When I take on comms or ops work for an organization, one of the first things I look at is how information actually moves from one place to the other. Who's closest to the guests, the students, the patients, the farmers, the artists? How does what they know reach the people making budget and staffing decisions? Almost always, there's a translation problem. Something true and specific at the front line becomes distorted or diluted by the time it gets to a board meeting. That's not a people problem. That's a design problem, and design problems have design solutions: clearer feedback loops, shared language, tools to make pattern-recognition easy instead of heroic.

Leadership is a craft

Here's where I think a lot of well-meaning nonprofit culture gets it backwards. We've decided that professionalism means caution, that leadership means restraint, and that competence means not rocking the boat. In trying to look “stable”, a lot of organizations manage the life, the curiosity, the humor, the willingness to speak the truth, etc. right out of themselves.

I'd rather think of leadership the way I think about a good exhibition or a good brand: intentional, specific, and built to hold attention and meaning at the same time. Storytelling isn't the marketing department's job. It's how an organization keeps its people oriented toward why any of this matters when budgets are tight and everyone's tired. Programming isn't calendar management. Your workshops, events, shows, gatherings are live experiments, and they are telling you what your community actually needs versus what you assumed they needed. This may be relatively different than what your organization needs. If you're paying attention, your programming is research and development.

Now more than ever, people are hungry for connection, anything that is more than a transaction, whether they're a donor, a volunteer, a student, or an employee. They want to grow, contribute, be challenged, and to belong. Nonprofits are uniquely positioned to offer that (spoiler alert: it’s often the entire premise of the mission), but the internal culture must be designed with the same care as the external programming.

Capacity is how well people can work together

When I talk about building capacity, I don't just mean hiring more people or writing a bigger grant. I mean designing the conditions where the people you already have can actually use what they know. A front desk insight can travel to a leadership decision without losing its relevance, a hard season gets debriefed, not grieved. Capacity building means that creativity gets treated as a working method for solving budget and staffing problems, not a luxury reserved for the marketing department or the wordsmithing committee.

That's the same muscle whether you're protecting a budget, protecting your staff, or protecting your organization's reputation. It's one job, done with the same care each time. And increasingly, there are new tools that can take the administrative weight off that work, so the humans get to spend their time on what only humans can do: teaching, mentoring, building relationships, being creative, making meaning together.

We've spent a long time perfecting the mechanics of nonprofit operations. Compliance, reporting, and risk management are all necessary, but none of it sufficient. The organizations that thrive from here forward will be the ones willing to design themselves as deliberately as they design their programs: as places built to learn, to remember, to tell the truth about what's working, and to help the people inside them actually flourish.

That's the strategy!