Damned If You Do, Damned If You Don't: The Impossible Tightrope of Letting People Learn

Let's just say the quiet part out loud: there are executive directors sitting in their offices right now — good people, mission-driven people, people who got into this work because they cared — who have lost their spark. They're still showing up. They're still signing the checks and attending the board meetings and smiling at the gala. But something is missing. The fire is lower. The decisions feel harder. The vision that used to feel electric now feels… exhausting.

Here's a scenario that will be instantly familiar to any experienced nonprofit leader — and I'll bet it's especially familiar if you're a woman who's been doing this work for a while.

A staff member or board member comes to you, excited, energized, absolutely certain they've got a great idea. And you — with your years of experience, your pattern recognition, your hard-won institutional memory — look at that idea and think: that's not going to work the way they think it's going to work. You've seen this movie before. You know how it ends.

So what do you do?

If you say "No, don't do that" — you're a controlling boss who squashes creativity and doesn't trust her people.

If you say "I've seen this before and it hasn't worked, here's why" — you're dismissive, you're stuck in the past, you don't believe in them.

If you say "Okay, go for it" and it fails — you should have stopped it. Why didn't you stop it? You're the leader. That's your job.

You are, in the immortal words of every woman who has ever led anything, absolutely damned if you do and damned if you don't.

Let's talk about this. Because it is real, it is exhausting, and it deserves a much more honest conversation than it usually gets.

The Experience Paradox

One of the most disorienting things about accumulating genuine expertise is that it can start to feel like a liability. The same depth of experience that makes you good at your job is the thing that gets reframed as rigidity, negativity, or — and here it comes — being a controlling presence who won't let people grow.

Adam Grant writes in Think Again that one of the hallmarks of truly experienced thinkers is their ability to hold their knowledge lightly — to stay curious even when they're confident. That's good advice. But Grant doesn't spend much time on what happens when you do stay open, you do let the idea run, and then you're handed the bill when it doesn't work out.

Because here's what they don't tell you in the leadership books: experience isn't just knowing what works. It's knowing what doesn't work, why it doesn't work, and approximately how long it will take for a well-intentioned effort to unravel. That knowledge is valuable. And yet, in many organizational cultures — particularly when it's coming from an older woman to a younger employee — it gets read as obstruction rather than wisdom.

That's not a performance problem. That's a bias problem. And we need to name it.

Let's Name the Gender Dynamic, Because It's Real

I'm going to say what a lot of female leaders are thinking but aren't always willing to put in print.

There is a specific flavor of this catch-22 that older women in leadership know intimately. When a seasoned male executive pushes back on an idea, he is often described as experienced, strategic, or decisive. When a seasoned female executive does the same thing, the word that tends to surface — sometimes said out loud, sometimes just hanging in the air — is controlling. Or difficult. Or threatened.

Researchers at Harvard Business Review have documented this dynamic extensively. In studies on leadership perception, women who display confidence and directness are consistently rated lower on likability than men displaying the same behaviors — even when the outcomes are identical. The double bind, as they've called it, is structural: the traits that make someone an effective leader are the same traits that, in women, trigger negative social responses.

Age compounds this in ways that are almost darkly comedic if you're living them. A recent study of over 900 women leaders by researchers Diehl, Dzubinski, and Stephenson found that age is weaponized against women at every stage of their careers — too young, then too old — with no apparent sweet spot in between. As one physician in the study noted pointedly: "I am middle-aged, and men my age are seen as mature leaders and women my age as old." The double standard isn't subtle. It's structural.

This means that when an experienced female executive says "I don't think that approach is going to work" — a statement that should be received as valuable input — it is sometimes received as a threat to autonomy, a display of dominance, or evidence that she's not a supportive leader. The exact same sentence from a different body in a different demographic often lands completely differently.

I'm not saying this to be victimized by it. I'm saying it because you can't solve a problem you haven't correctly identified. And if you're an experienced female leader who has felt this specific whiplash — encouraged to be a mentor and then penalized for mentoring — you are not imagining it, and you are not alone.

And Now Let's Talk About Race — Because the Data Demands It

I've been writing about this catch-22 largely through my own lens as an older white woman, because that's my lived experience and I think it's important to speak from what I actually know. But I'd be doing a disservice to this conversation — and to the leaders reading it — if I stopped there. Because the research is unambiguous: the dynamic I'm describing gets significantly more complicated, and significantly more punishing, when race enters the picture.

White women like me face real gender bias in leadership. That is documented and true. But we also carry the partial shelter of racial privilege — and that shelter is something I don't want to take for granted or write around as if it doesn't exist.

Research from the Harvard Gender Action Portal finds that while white female leaders are evaluated more negatively than white male leaders, Black women face what researchers describe as a "double jeopardy" — the compounded weight of holding two marginalized identities simultaneously. The AAUW's landmark report Barriers and Bias found that Black women are held to higher standards of competence than those who violate only one leadership stereotype — meaning they must prove themselves more thoroughly than either Black men or white women just to occupy the same rooms we're already in.

The catch-22 I've been describing — say something, you're controlling; stay silent, you're negligent — hits differently when it's happening inside a body that the dominant culture has never fully accepted as a leadership body in the first place. Catalyst research shows that Black women in leadership contend with both hypervisibility and invisibility simultaneously: scrutinized more closely for failures, and yet still required to work harder simply to be taken seriously as leaders. They are penalized more harshly when things go wrong, and given less credit when things go right.

I want to be direct about this: if this dynamic is exhausting and demoralizing for me, the data tells us it is measurably more so for leaders who don't have the partial shelter that I do. That matters. I don't want to write about women in leadership without saying it plainly.

So when we talk about who deserves grace in this conversation — who deserves to have their experience seen and named — that circle is wider than older white women. It includes every woman leader navigating this terrain, and it includes the specific and compounded burden carried by women of color who are doing it with fewer systemic protections and higher organizational stakes.

If you are a woman of color reading this and thinking yes, but also so much more than this — you're right. And I see you.

The Real Cost of the Catch-22

Here's what's actually at stake when this dynamic goes unaddressed.

For the organization: Resources — time, money, staff energy, board attention — get spent on things that experienced leadership could have redirected. In resource-constrained nonprofits, this isn't an abstraction. A program initiative that consumes six months of staff time and then quietly folds is not a free learning experience. Someone paid for it.

For the leader: The repeated experience of being blamed for both outcomes — you stopped it and you didn't stop it — is genuinely demoralizing. It creates a kind of leadership learned helplessness where the safest move starts to feel like staying silent and letting things run their course. Which is, ironically, exactly the kind of passive, checked-out leadership we talked about in our last post.

For the staff member or board member: If no one ever helps them build the judgment to evaluate their own ideas before launching them, they don't actually grow. Letting someone fail without any scaffolding isn't mentorship — it's abdication.

Nobody wins when we pretend this dynamic doesn't exist.

So What Do You Actually Do?

There's no clean answer here — if there were, it wouldn't be a catch-22. But there are some practices that can help you navigate it with more intention and less whiplash.

Create a shared framework for evaluating ideas — before the ideas arrive. This is the strategic move that most leaders don't think to make until they're already in the middle of a conflict. If your team has agreed-on criteria for evaluating new initiatives — resource requirements, alignment with strategic priorities, theory of change, similar past efforts and their outcomes — then your pushback isn't personal. It's procedural. You're not saying I don't believe in you. You're saying let's run this through the filter we all agreed on.

Tools like a simple "idea intake" process or a lightweight feasibility checklist can depersonalize the evaluation without removing the leader's judgment from the equation. It becomes the process saying slow down, not just you.

Name your experience explicitly, and make it an offering rather than a verdict. There's a difference between "That won't work" and "I've seen something similar before, and here's what happened — I want to share that with you before you invest a lot of time." The second version is transparent about the source of your concern, positions your experience as a resource rather than a roadblock, and leaves the decision genuinely open. It respects their autonomy while not pretending you don't know what you know.

Author and leadership coach Michael Bungay Stanier, in The Coaching Habit, suggests that the most powerful thing a leader can often say is simply: "What do you know about why this hasn't been tried before?" It opens the door to shared inquiry rather than top-down judgment — and it gives the person the opportunity to discover the history themselves.

Set explicit terms for the experiment upfront. If you decide to let something run — because learning matters, because autonomy matters, because sometimes you're wrong — don't just wave it through. Have a direct conversation: "I want to support you in trying this. I do have some concerns based on past experience, which I've shared. Here's what I'd like to agree on: let's set a 90-day check-in point, these are the markers we'll use to evaluate progress, and here's what a decision to continue or change course would look like." You are not a passive bystander in someone else's experiment. You are the leader, and you are allowed to structure the learning.

This approach also gives you something crucial: a documented record that you raised concerns, that you agreed on a framework, and that you were actively engaged throughout. If the question later becomes why didn't you stop it? — you have an answer.

Ask for the grace explicitly that you need. This is the one most leaders never do, and I think it matters enormously. When you decide to give someone room to try something you're not sure about, say so out loud: "I'm going to support you in this because I believe in your growth and I want you to have the space to test your thinking. I need you to understand that I have some reservations based on experience, and I'm asking you to trust that I've shared them in good faith. If this doesn't go the way we hope, I need us to be able to debrief it honestly together — without blame in either direction."

That is not a controlling speech. That is a leader doing the relational work to set up a real learning experience. You are allowed to ask for grace. You are allowed to name the dynamic. In fact, naming it is often what defuses it.

Debrief every significant effort, win or lose. One of the reasons the catch-22 is so punishing is that the post-mortem rarely happens in a healthy way. If something worked, no one goes back to examine why the concerns were or weren't warranted. If something failed, the energy goes into blame rather than learning. Build a culture where debriefs are standard — not punitive reviews, but genuine inquiries. What did we expect? What happened? What did we learn? What would we do differently? When this is routine, any single failure loses some of its charge.

What You Are Owed as a Leader

Here is something I want to say directly, because I don't think it gets said enough:

Your experience has value. Your pattern recognition has value. The fact that you have seen this before — the fundraising approach that burns staff out, the program model that sounds innovative but ignores why the previous iteration failed, the board initiative that will absorb twelve months of everyone's energy and produce a report that no one reads — does not make you an obstacle. It makes you an asset.

Healthy organizational cultures treat experienced leadership as a resource, not an inconvenience. Boards and staff members who genuinely want to grow will, over time, learn to distinguish between a leader who says no because she's threatened and a leader who says slow down because she's paying attention. That distinction matters, and it's worth holding out for.

You deserve a team that gives you the grace to be both the person who raises the concern and the person who supports the effort. Those two things are not in conflict. They are what good leadership looks like.

And when someone comes back and asks why you didn't stop something that didn't work — and they will — you are allowed to say: "Because I believed in your ability to learn, I shared my concerns clearly, and we agreed on a process together. That's what I was supposed to do. Now let's talk about what we learned."

That's not a defensive answer. That's a leadership answer.

A Note to Staff and Board Members

If your executive director or CEO has years more experience than you, and she raises a concern about something you want to try — she is not attacking your idea. She is doing her job.

You do not have to agree with her. You are absolutely allowed to make your case and advocate for your approach. That is healthy. But dismissing her concern as controlling or dismissive — particularly if she's a woman and you're earlier in your career — is not the same as being independent or innovative. It's leaving expertise on the table.

And if your leader is a woman of color, add another layer of reflection before you push back. Ask yourself honestly whether you would receive the same input differently from someone who looked more like the default image of a leader in your head. That's not a comfortable question. It's a necessary one.

The leaders who made me better were the ones who pushed back on my ideas, made me defend them, and then either helped me improve them or let me find out the hard way why they were right. I am grateful for both. The ones who just said yes to everything were not, in hindsight, the ones who helped me grow.

Give your leader the grace to know more than you do about some things. She's earned it.

The Bottom Line

The catch-22 of experienced leadership is real, it's gendered, it's racialized, and it's not going away on its own. But it is navigable — with clearer frameworks, more explicit conversations, and a shared commitment to learning that doesn't assign blame when things don't go as planned.

You can hold your experience and hold space for others to grow. You can raise concerns and still say yes. You can give people room to fail and still lead the debrief.

What you cannot do is carry the weight of impossible expectations silently. Name the dynamic. Build the frameworks. Ask for the grace you deserve.

And then keep going — because the mission still needs a leader, and that leader is you.

Does this dynamic show up in your organization? I'd love to hear how you're navigating it. Book a consultation at yourmissionmaven.com or drop me a note — let's think through it together.

---

References and Further Reading:

• Grant, A. (2021). Think Again: The Power of Knowing What You Don't Know. Viking.

• Bungay Stanier, M. (2016). The Coaching Habit: Say Less, Ask More & Change the Way You Lead Forever. Box of Crayons Press.

• Diehl, A., Dzubinski, L., & Stephenson, A. (2023). "Women Leaders Face 30 Types of Bias." Harvard Business Review.

• Ibarra, H., Ely, R., & Kolb, D. (2013). "Women Rising: The Unseen Barriers." Harvard Business Review.

• Hill, C. (2016). Barriers and Bias: The Status of Women in Leadership. AAUW.

• Harvard Kennedy School Gender Action Portal. "Failure Is Not an Option for Black Women: Effects of Organizational Performance on Leaders with Single Versus Dual-Subordinate Identities."

• Catalyst. (2024). "Black Women Still Face a Glass Cliff, But Fixing Workplace Systems Can Change That."

• Tannen, D. (1994). Talking from 9 to 5: Women and Men at Work. William Morrow.

• Lencioni, P. (2002). The Five Dysfunctions of a Team. Jossey-Bass.