5 Leadership Lessons from Serving 31 Million Meals

Start Before You're Ready

The biggest lie that keeps purpose-driven leaders stuck is the idea that they need to be fully prepared before they begin. They're waiting for the right funding, the right team, the right moment. Meanwhile, the people they're called to serve are still waiting.

When I started Minnie's Food Pantry, I had no 501(c)(3) status, no staff, no facility. I had faith, a trunk full of food, and a stubborn refusal to wait for perfect conditions. That imperfect beginning was the seed of everything that followed.

Here's what I've seen over and over again in the leaders I coach: the ones who start messy, learn fast, and iterate quickly consistently outpace the ones who plan endlessly. You cannot steer a parked car. Action creates information. Information creates clarity. Clarity creates strategy. But none of it happens until you move.

Starting before you're ready doesn't mean starting recklessly. It means having a clear conviction, a minimum viable version of your vision, and the courage to put it in front of real people. Let reality refine it.

Build Systems, Not Just Passion

Passion got me started. Systems got us to 31 million meals.

Early on, Minnie's Food Pantry ran on pure energy — mine, my volunteers', our community's. And for a while, that was enough. But passion is not a sustainable operating model. Passion burns out. Passion gets sick. Passion has a bad week. Systems keep running.

The transition from passion-powered to systems-powered was the most important — and most uncomfortable — evolution we made. It required me to stop doing everything myself and start documenting, delegating, and building repeatable processes. It meant hiring people who were better than me at certain things and trusting them to carry the mission.

For nonprofit leaders especially, this feels counterintuitive. We got into this work because we care deeply — and building systems can feel clinical, like we're trading heart for efficiency. But I'd argue the opposite: robust systems are how you honor your mission at scale. They're how you ensure that the quality of care you give person number one is still intact when you're serving person number 31 million.

If your organization cannot function for two weeks without you, you don't have an organization — you have a dependency. Build the systems that let your mission outlive your direct involvement.

Let Your Mission Attract Partners

One of the questions I get asked most often is: "How did you get the Rihanna Foundation involved? How did you attract corporate sponsors and national attention?"

The honest answer is that I didn't go hunting for them. I stayed obsessively focused on the work, made sure that work was visible and documented, and let the mission speak for itself. Partners don't write checks for potential — they write checks for proof. Every meal we served was proof.

Too many leaders spend enormous energy pitching before they have results to point to. They're in every networking event, every conference, every DM campaign — and they're getting polite nods because they don't yet have a story that compels. The shortcut is actually the long game: do exceptional work at whatever scale you can, document it relentlessly, and let the results pull partners toward you.

When the Rihanna Foundation reached out, it wasn't because I'd pitched them. It was because the work we were doing was undeniable. That's the kind of magnetism you build by being relentlessly mission-focused, not by chasing every shiny partnership opportunity.

That said — once the right partners show up, know your worth. Have clear agreements. Understand what you're exchanging and what you're protecting. Partnership is a two-way street, and healthy boundaries keep it that way.

Resilience Isn't a Personality Trait — It's a Practice

There is a version of "resilience" being sold to leaders right now that I want to push back on. It's the idea that some people are just built tough — that they bounce back because of who they are, not what they do. That framing is both inaccurate and quietly harmful, because it implies that if you're struggling, it's a character flaw.

Resilience is not a personality trait. It's a practice. It's something you build, deliberately, through habits of recovery and systems of support.

I have faced opposition that should have ended Minnie's Food Pantry multiple times. Funding gaps. Community resistance. Moments of profound personal loss while trying to show up for thousands of other people. What kept me going wasn't some innate toughness — it was a set of practices: my faith community, physical movement, trusted advisors who could tell me the truth, and the discipline to take real rest even when it felt irresponsible.

If you're leading a mission-driven organization and you're running on empty, you are not being faithful to the mission. You are depleting the most critical resource it has — you. Resilience requires you to treat your own restoration as a non-negotiable operational priority, not a reward you earn after you've done enough.

Build your resilience practice before you need it. Because when the crisis comes — and it will — you won't have time to build it from scratch.

Scale Means Letting Go of Control

This one cost me the most. And I suspect it might be the one that costs you the most too.

The version of Minnie's Food Pantry that lived inside my head — every detail exactly right, every interaction perfectly aligned with the vision, every volunteer trained and operating exactly as I would — that version couldn't serve 31 million meals. It couldn't even serve 31,000. Because it was limited by one person's bandwidth: mine.

Scale requires surrender. Not of the mission — never the mission — but of the method. It requires trusting that the people you've trained, the systems you've built, and the culture you've cultivated can carry the work forward without you being in the room for every decision.

This is where so many nonprofit leaders stall out. They've built something meaningful, they have people who believe in it, but they can't bring themselves to release the control that got them this far. And so the organization grows to the size of their personal bandwidth — and then it stops.

The leaders who break through that ceiling are the ones who recognize that their job is to set the vision, build the team, create the conditions for others to lead, and then get out of the way. That transition — from doing to enabling — is the hardest and most important move any founder ever makes.

31 million meals didn't happen because I served every one of them. It happened because I built something that could serve them with me or without me. That's what real scale looks like.