Suffocating Autonomy: Cinderella Syndrome in Your Organization (S1E5)

Episode 5: Organizational Cinderella Syndrome

In our last episode, we followed Elena — a manager who stopped trying not because she gave up on her career, but because the system around her stopped responding to her effort. That is Organizational Learned Helplessness. Today we look at something different. Something subtler. What happens when a capable follower doesn't lose hope — but stops believing they are the one who is supposed to act on it.

This is Marcus's story. Marcus was quietly excellent — the person everyone relied on, the one whose judgment was consistently good. And then he got a new director. One who stepped in on every decision, reworked every output, and diplomatically communicated the same message in every interaction: your judgment is not the standard here. Mine is.

Over time, Marcus stopped acting autonomously. Not because he couldn't. But because the system had conditioned him — slowly, convincingly — to wait for someone else to lead the way.

That is Organizational Cinderella Syndrome. And in this episode, Dr. Ashley Newcomb breaks down exactly what it is, where it comes from, and the three types of leaders who create it — often without realizing it.

Because the goal of leadership is not to be needed. The goal is to build something that doesn't depend entirely on your presence to function.

🎧 Listen now and grab free resources at inspiredcoaching.net

---

Topics covered in this episode:
Organizational Cinderella Syndrome | Follower dependency | Employee autonomy | Over-functioning leadership | Toxic leadership | Leadership blind spots | Organizational resilience | Follower behavior | Psychological safety | Employee empowerment | Leadership development | Workplace culture | Manager vs. leader | Discretionary effort | Organizational silence

Transcript

SPEAKER_00 0:06

At the end of our last episode, I told you that during this episode, we were going to look at a pattern that was very different from organizational learned helplessness in one very important way. So with Organizational Learned Helplessness, or OLH, we explored through Elena's story and through Shannon and Bryson's team story that followers lose hope. They stop trying because experience has taught them and repeatedly taught them that trying doesn't produce results, so their effort eventually dies. Today's pattern is more subtle and in some ways more insiduous because today we're going to talk about what happens when the hope doesn't die, it just gets redirected. When a capable, talented follower stops believing in their own ability to change their situation and starts waiting for someone else to do it for them. That is organizational Cinderella syndrome. And the story I want to tell you today is Marcus's story because Marcus didn't give up. He just stopped believing in himself and stopped believing that he was the one who was supposed to try. I'm Dr. Ashley Newcomb, founder of Inspired Coaching and Leadership, and this is the Resilient Organization. And today I want to talk about the follower who is still in the building, still showing up, still capable, still hoping, but who has quietly, completely stopped acting on their own behalf. Stick a quick side note in here. So unfortunately, I've worked with a number of people that have experienced Cinderella syndrome, but for today's story, I selected one of my male coaches, and that was very intentional. You see, I want you to take away the concept of just because we're talking about Cinderella syndrome and this is a princess type name. I want to make sure that you understand that Cinderella syndrome can actually apply to both female and male followers. And that's why I selected Marcus. Marcus was an outstanding person. He was a great follower, he was capable of great and wonderful things, but even as a male, he experienced Cinderella syndrome on a phenomenal level. So let's get into the meat of things. Let me take you back to a story that you probably know better than you realize. Cinderella. Cinderella is extraordinarily capable. She works hard, she's resourceful, she's resilient, and she can get things done even without the little mice and the little pigeons and the little sparrows that come in to help her. None of that changes the fact that in a system that she's living inside of, her contributions go unrecognized and her potential goes unreleased, and her future is something that gets decided by other people. Her father, her stepmother, her stepsisters, even the prince that was supposed to be the one that came in and rescued her. Basically, by everybody that was not her, including her fairy godmother. But she doesn't fight the system. She endures it. She waits. She cleans out fireplaces. She sews buttons onto her stepsisters' gowns. Whatever she's told to do, she does it. And somewhere underneath this waiting, belief has taken root without her even noticing. It's the belief that her situation will improve when someone else with more power decides that it should. And that belief, my friends, that belief that my success and my recognition will eventually come to me when someone else grants it to me, that's the core of organizational Cinderella syndrome. OCS is what happens when otherwise very capable followers are conditioned through repeated experience of having their autonomy overridden, their initiative preempted, or their contributions controlled to stop trusting their own judgment and start depending on leadership to drive their outcomes. They don't give up, they defer. They don't disengage, they wait. And that waiting over time becomes a pattern that is extraordinarily difficult to break. Now, here's the critical distinction that I want you to hold on to, especially if you listen to our last episode. With OLH, the follower's effort dies. They stop trying because hope is gone. With OCS, the effort doesn't die. It gets redirected toward waiting rather than doing. The follower is still investing energy, but that energy is going into watching and waiting for the moment when leadership finally recognizes them, finally promotes them, finally gives them permission to step into the role they've been capable all along. Sometimes within that waiting though, followers lose the ability to actually step into a leadership role. That old adage, if you don't use it, you lose it. Well, there's a lot of truth to that, especially in organizational behavior. And here's what makes OCS particularly damaging to organizational resilience. It creates dependency, not just in the follower, but in the organization's culture. When enough followers learn to wait rather than to act, the organization loses something essential, the distributed initiative and autonomous problem-solving skills that allows the organization as a whole to respond quickly when disruption hits. A resilient organization cannot, absolutely cannot, be built on followers who are waiting to be told what to do next. This is not a performance problem. This is a system problem wearing a performance problem's clothes. So where does that system problem come from? Well, here's where I'm about to step on some toes because almost always it comes from the leader. There are three types of leaders who consistently create OCS and the followers around them. And I want to walk you through all three because one of them is going to be obvious and the other two are much harder to see, especially if you're the one doing it. So let's meet Marcus. Marcus was a natural. And then he got a new director. So this new director, and I want you to pause for a second and really notice something about how I'm describing him as a person and as leader. He was the kind of leader who believed in a way that went very, very deep that he was simply better than the people around him. Not in a performative way, not in a way that he would have or even could have admitted in a 360 review, but in the quiet daily texture of how he operated. It came through unmistakably. He was almost one of these born leader types of people that just thought that you were either born into greatness or you were born to be mediocre. And he certainly felt like he was born to greatness. When Marcus brought a solution to a problem, his director would listen and then explain why his own approach was superior to Marcus's. Not occasionally, I'm talking consistently. When Marcus made a decision within the scope of his authority, the director would revisit it in the next team meeting, reframe it, present it in a slightly different version as the better path forward. When Marcus prepared materials for senior leadership presentation, well, the director would rework them entirely, not because they were wrong, but because they weren't the way that the director would have done it. And when others praised Marcus's work, the director had a reliable habit of contextualizing. He would say things like, yes, Marcus did a good job with execution, but the strategic direction was really what made it work. And then he would somehow shift every single time the praise back onto himself. Now Marcus was a very kind person, but he was not a naive person. He saw what was happening. And at first he pushed back. He asked for clarity on why his decisions were being revisited. He requested feedback on what specifically wasn't meeting the director's standards. He made the case professionally and clearly for his own approaches. And the director's responses were smooth. You got to give him that. They were diplomatic. He never said just outright you're wrong. He would say things like, I just wanted to make sure that we were presenting the strongest possible version. Or he'd say things like, I have more context on the senior leadership expectations than you do right now. Or, and this is one that really stayed with Marcus, I know you have good instincts, Marcus, but instincts need to be developed. Let me show you how to handle this. Every one of those responses communicated the same thing underneath the polish. Your judgment is not ready to be trusted yet. I'm the one who knows best. Watch and learn. And Marcus, because he was a rational person who wanted to succeed in this organization, began to adjust. He started running decisions by the director before making them. He started framing his proposals as options for the director to choose from rather than recommendations that he was confident in. He started waiting for approval, for direction, for the signal from the director that it was okay to move forward. Part that matters most is that Marcus didn't realize he was doing it. The dependency didn't feel like surrender. It felt like learning the organization. It felt like being appropriately humble in the presence with someone with more authority and experience. What was actually happening was Marcus's belief in his own judgment was being systematically eroded and dismantled, one interaction at a time. And by the time Marcus was aware of how dependent he had become on the director's approval, the pattern was so established that acting autonomously felt genuinely frightening. What if he got it wrong? What if he moved forward without checking it and it wasn't the way the director would have done it? What if he stopped waiting and it turned out that he actually wasn't ready? There were a lot of what ifs that played into the mind that could have ruined his career, at least from his perspective. That fear, that fear of autonomous action in a follower who was once naturally autonomous, is organizational Cinderella syndrome fully formed. As I mentioned earlier, OCS is typically created by one of three leadership personalities. Marcus's story features the most clearly recognizable OCS creating leader, the one that I call the superior leader. But there are two others, and I want to walk you through all three because one of them is bound to feel very familiar, and it may not be the one that you expect. The first is a superior leader, as I mentioned. This is Marcus's leader. This is the leader who steps in consistently and habitually because they genuinely believe that their approach is better than everyone else's. Their involvement isn't primarily about protecting the outcome, it's about confirming in every interaction in front of everybody's eyes that their judgment is the higher standard available. The damage that this leader does is so significant because it's so consistent. Followers around a superior leader quickly learn that their own judgment is always going to be second-guessed, that their work will always be reworked, and that the only safe path forward is to wait for the superior leader to weigh in before acting. Dependency is not a side effect of this leadership style. It is in many ways the natural product. Our second OCS leader is the knight. Think about a knight in shining armor. This knight is a very different kind of leader and often a much more sympathetic one. The knight steps in because they genuinely want to help. They see a follower struggling or anticipate that the follower might struggle, and they move in to prevent the difficulty before it arrives. For those of you who follow parenting philosophies, think lawnmower mom meets helicopter parent. They solve problems before followers even have a chance to engage them. They rescue before the situation requires a rescue. And they do all of this because they care. They care about the outcome, they care about the follower, they care about the organization, they care about getting it right. The knight is often a very beloved leader. People feel protected around the night, but what the knight's followers are quietly learning is that protection is available on demand and that struggling through something on their own is unnecessary because the knight will always show up. Over time, followers around the night stop developing the confidence to handle difficulty independently, not because they can't, but because they never had to. And some of those minor difficulties, they actually help build organizational resilience because they help the followers build faith in themselves to autonomously address, attack, and solve organizational problems before they become major events. Back to our old adage, if you don't use it, you lose it. And if you don't give your followers the opportunity to struggle and find solutions on their own, there's going to be a day that you're not around and they're not capable of doing it on their own. Our final OCS leader is the doubter. The doubter doesn't step in because they feel superior and they don't step in because they want to help. They step in because they don't trust their followers to get it right. Our doubter, they micromanage out of their own anxiety. They need to be in the loop on everything because the alternative, trusting someone else's judgment, feels genuinely unsafe to them. Followers around a doubter learn something very specific. They learn that their judgment is not trusted here. And when a follower's judgment is consistently not trusted, they stop using it. They escalate everything. They check in constantly. They wait for approval before acting, and they begin to wonder over time whether the doubter might be right, whether their judgment is actually unreliable, whether they actually do need this level of oversight to perform well. Always keep in mind that anxiety breeds anxiety. Doubt breeds doubt. So as a leader, when you don't have faith in your followers, those followers eventually stop having faith in themselves because as a leader, they look up to you. As a leader, naturally they're assuming that you're in a position because you just know more than they do. So if you don't have faith, then maybe they don't deserve it. So as you can see, these were three very different types of leaders, three very different types of motivation, but there was one outcome that was the same. Followers who have learned to wait rather than act, followers who have been conditioned slowly, often unintentionally, to depend on someone else to drive their outcomes. Now let's be honest with one another right here. This is the point where we admit to ourselves that it's great to feel needed. It's great to feel like we are the captain of this ship and that we are steering through the storm successfully. And it might even feel good to think that, you know, maybe this couldn't be navigated as well with a different leader. But at the end of the day, the goal of leadership is not to be needed. The goal of leadership is to build something that doesn't depend entirely on your presence in order to function. And here's where I'm really going to step on some toes. The fact of the matter is that if you've built an organization or if you've groomed followers that are incapable of functioning without you, you're not a very good leader. And now that I've already stepped on some toes, let's make this really personal. And I want to start with something I mean sincerely. The leaders that are most likely to recognize themselves in today's episodes are often the ones who care the most. The doubter cares about quality. The knight cares about people. Even superior leader at some level cares about outcomes, however distorted their methods may be. OCS is very often the shadow side of a genuine investment in work and in the organization. But caring about your organization and leading in a way that releases your followers' potential, that's not automatically the same thing. And that gap is worth an honest examination. Here are a few questions for you to sit with. When a follower brings you a problem, what's your default response? Do you ask them how they're thinking about it and wait for the full answer? Or do you find yourself moving toward a solution before they finish describing the situation? Neither answer makes you a bad leader, but the pattern, repeated and consistent, shapes what your followers believe is expected of them. Think about the last significant decision a follower made in your organization. Did it stand as they made it? Or did it get revised, reframed, reworked by you or someone above you before it was fully implemented? If your fingerprints are on every single output that leaves your team, it's worth asking what your team has learned about whose judgment is trusted here. And here's the one that lands the hardest. If you stepped back, genuinely, significantly stepped back, do you believe that your followers could handle it without you? If your honest answer is no, ask yourself when that became true. Because followers who can't operate without extensive leadership involvement, they've learned that dependency somewhere, and the most likely place that they've learned it is from the leadership they've been operating under. And if that's you, then that's you. But this is not about blame. It's about honest accountability. Because if you are creating OCS and the people around you, even unintentionally, even from a place of genuine care, the path forward begins with seeing it clearly. And here are three things that you can do about it today. Now, these won't undo years of conditioning dependency overnight, but if Marcus's story landed somewhere real for you, here are three places that you can start. First, the next time a follower brings you a problem, ask before you answer. Before you share your own assessment, before you begin working toward a solution, ask them, what are you thinking about this? And then be genuinely quiet. And be quiet long enough for them to actually answer. Don't put words in their mouth, don't preemptively answer for them. You are not withholding your expertise in this space. You're creating space for them to develop theirs. And that space is where autonomous confidence begins to grow. Second, let the next piece of work go out with their fingerprints on it, not yours. Find one thing your team produces in the next week and resist the urge to rework it. If it's good enough, then let it be good enough. If it needs feedback, give the feedback and let them make the changes. The signal that you're sending here is this your work has value as your work. That signal delivered consistently begins to rebuild the belief that their judgment is trusted. The third and final tip for today: the next time a follower is about to face a difficult situation, resist the urge to prevent it. Don't rescue before a rescue is needed. Let your follower engage with the difficulty. You can stay available as a resource, but let them take the lead and then acknowledge specifically what they handled and how they handled it. Believe it or not, you are not being unhelpful here. You're actually being the kind of leader who builds followers capable of standing on their own. And that's exactly the kind of leadership that builds resilient organizations. Unfortunately, many times as a leader, we often think that if we empower our followers too much, we're going to empower ourselves right out of a job. But that's not the case. What happens instead is that we build an organization. Organization is going to be a lasting legacy for us after we've retired instead of one that needs our constant interaction or else it's gonna fail. So Marcus eventually moved to a different organization, as with most of the people that I'm gonna talk about in this podcast. And this new organization trusted his judgment from the very start. And he told me that the first few months there were genuinely disorienting for him. He kept waiting for someone to check his work, he kept looking for the approval signal before moving forward, he kept second-guessing his decisions that he was fully equipped and credentialed to make. It took time, but he finally found his way back to himself, found his way back to the level of natural confidence that he originally had with the other organization. So you see, Cinderella syndrome is actually reversible under the correct conditions. Looking at your own Cinderellas, their capability is still there. The question, the real question of the matter, is whether your leadership is releasing it or quietly teaching it to wait. In our next episode, we're going to look at how overfunctioning leadership creates both of these patterns and what it actually takes to lead in a way that builds rather than diminishes the people around you. That's where we're going next. Be sure to check out the training when followers go quiet, diagnosing hidden disengagement in your organization, and other free resources available at inspiredcoaching.net. This has been the Resilient Organization. Thank you for being here, and I'll see you next time.