When You Stop Absorbing It
Part 4. What happens when someone finally names what the system has been hiding
Built to Absorb is a five-part series on the human patterns underneath nonprofit fundraising culture — where they come from, what they cost, and why changing them is harder than it looks.
There’s a specific kind of clarity that comes from being inside a system long enough to finally see it.
Not the clarity that arrives from the outside — clean, analytical, unburdened. The other kind. The kind that surfaces slowly, in the middle of a meeting or a budget conversation or a negotiation you’ve done a dozen times, when something you’ve accepted as normal suddenly looks different. Not wrong, exactly. Just visible in a way it wasn’t before.
That’s what happened to me.
I was head of development at an organization that, by any reasonable measure, had significant standing in its field. National reach. A clear and credible connection to the issue. Donors who cared deeply. A mission that mattered.
And we kept giving things away.
Not carelessly. Not without effort. We had a process, a deck, a negotiation sequence. But somewhere underneath all of it was a posture — a scarcity posture — that showed up in how we priced benefits, what we included without being asked, how we positioned the relationship. We were operating from need rather than from strength. The partnerships reflected that, even when the language didn’t.
Early in my tenure I saw it clearly enough to name it.
The organization had not fully accounted for what partnerships actually cost — not just the obvious expenses, but the indirect ones. Staff time. Infrastructure. The organizational capacity that quietly got allocated to deliver on commitments that were priced as if they were weightless. When I went back through it, the real cost of partnership benefits was substantially higher than what we’d been charging. And the real value — for a prominent national organization with credibility on this specific issue — was higher still.
We were undervaluing ourselves. Systematically. In a way that had turned into habit.
So I reworked it. New pricing structure. New framing for what the partnership actually represented — not a transaction between a funder and a grateful recipient, but a strategic alignment between two organizations with shared stakes in the issue. The kind of partnership a strong organization offers. Not the kind a desperate one does.
It worked. The numbers began to improve. The conversations changed.
And it created direct conflict with leadership. Things deteriorated fast. There's a difference between being seen as a disruptor and being seen as a threat — and I was the latter.
Not because the work was wrong. The numbers were right. The partnerships were stronger. The case was clear.
The conflict came from somewhere else entirely.
What I had done, without fully understanding it at the time, was introduce a new story about what the organization was worth. And that story threatened people who had built their identity, their authority, and their sense of safety around the old one. Leaders who had operated for years from a scarcity posture don’t always experience an abundance reframe as good news. Sometimes they experience it as an indictment. As evidence that something they’d been doing and leading was wrong.
Fear dressed up as resistance. Threat dressed up as strategic disagreement.
I’ve thought about that conflict a lot since then. The people involved were not trying to harm anyone. They were human. But here’s what it revealed: the scarcity posture wasn’t just a pricing problem. It was a culture. And a culture built around scarcity will protect itself — not through malice, but through the entirely human impulse to defend what feels familiar against what feels destabilizing.
Clarity is destabilizing. That’s part of what makes it clarity.
The fixer in me had spent years absorbing the system’s anxiety, carrying it into rooms, smoothing it over in negotiations, making it invisible to the people who needed to see it most. When I stopped absorbing it and named it instead, the system registered that as disruption.
Leadership registered it as threat.
That’s not a complaint. That’s just what naming things costs.
I’d do it again.
Not because the outcome was easy. It wasn’t. But because the alternative — continuing to operate from a scarcity posture I could now see clearly — would have been its own kind of cost. A slower one. The kind that doesn’t feel like a choice because it’s dressed up as professionalism.
What I’ve come to understand is that clarity isn’t the end of the difficulty. It’s the beginning of a different kind. Before clarity, the system runs on your unconscious cooperation. After it, you have to decide, consciously, repeatedly, whether to cooperate or not.
That’s harder than it sounds.
Most of the development professionals I know have had a version of this moment. Something they saw clearly and named — or saw clearly and didn’t name, because they’d already learned what naming things costs.
The ones who named it didn’t all have the same outcome. Some found organizations that could hear it. Some didn’t. But almost all of them describe something similar afterward: the sense that once you see the scarcity pattern, once you locate the system debt and trace it back to its source, you can’t unsee it.
That’s not a burden. That’s the work.
Next: What it actually takes to change the system — and why structural redesign is the easier half.