The Meeting That’s Costing You $50,000 a Year
It’s not the meeting that goes too long. It’s the one that ends without a decision.
Here’s a number I want you to think about: $50,000.
That’s a conservative estimate of what a single chronic, unresolved operational decision costs a mid-sized nonprofit over the course of a year — in staff time, rework, delayed programs, and leadership energy spent managing around the problem instead of through it.
And most organizations have more than one.
The meeting that ends with “let’s take this back and think about it”. The initiative that’s been “in review” for eight months. The org chart question everyone has an opinion about, but no one will say. These aren’t minor friction points. They are organizational drag — and they compound.
Why Smart Organizations Stop Deciding
It’s not that nonprofit leaders don’t know how to make decisions. Most of them make hard calls every day. The decisions that get stuck are almost always the ones with one of three characteristics:
- They require someone to say something uncomfortable
- They will change the status quo for someone who has power or seniority
- They touch something the organization has avoided for so long it’s become normalized
In those cases, the default is to keep gathering information, keep consulting, and keep scheduling the follow-up meeting. Not because more data is needed. Because no one wants to be the one to name what’s actually going on.
Delay is a decision. It’s just a decision to keep paying the cost of indecision.
What Operational Drag Actually Looks Like
Operational drag rarely announces itself. It hides inside normal-looking workflows. Here are some of the ways I see it show up most often:
- Staff who know the answer to a problem but don’t feel safe saying it
- Processes that everyone knows are broken but that would require a difficult conversation to fix
- Programs that consume resources disproportionate to their outcomes because cutting them feels like failure
- Technology tools that no one uses because the real issue was never about the technology
- Roles that have grown unclear because a leadership conversation that needed to happen didn’t
In each of these cases, the operational problem has a leadership problem underneath it. Fix the surface, and it comes back. Address what’s underneath, and you’ve actually changed something.
A Simple Diagnostic
Here is a question I use with leadership teams to help surface operational drag quickly:
Name one decision your organization has been trying to make for more than 90 days. What would have to be true for you to make it this week?
The answers are usually illuminating. Not because the decision is complicated — most of them aren’t — but because the conversation that surfaces reveals exactly what’s making it feel impossible.
Usually, it’s not a process problem. It’s not a data problem. It’s the thing under the rug that nobody wants to lift the corner on.
The Cost of Waiting
Every week a decision doesn’t get made; your organization pays. It pays in staff time, program momentum, and leadership credibility. And the quiet frustration of talented people who see the problem clearly but feel stuck.
The organizations I see move fastest are not the ones with the best strategies. They’re the ones with the courage to make the call, even when it’s uncomfortable. Even when it means moving something that has been sitting in the same place for a very long time.
If you want to understand more about how to identify and move the decisions that are stalling your organization, I wrote the book on it. Literally.