Latest / Lead With Clarity: Practical Insight for Senior Leaders / The Manuscript That Got Rejected Thirty-Six Times
Transcript
- Blake Holman: Welcome to Lead with Clarity. This is a space for leaders who want to grow without losing themselves in the process. Each episode is a short reflection on leadership, influence, and the inner work that shapes how we show up for others. It's not hype, not noise, just clear thinking for the journey of leading well. Today's episode is entitled The Manuscript That Got Rejected 36 Times. Here we go. Picture a manuscript sitting in a mailbox. It's the mid-1970s. A young writer named Ariana Huffington has just finished her second book. She sends it out. A publisher reads it and says no. She sends it to another one. No again. She keeps going. Publisher after publisher turns it down. By the time someone finally says yes, thirty-six people have already said no. Most of us would have stopped much earlier. Somewhere around rejection number five or six. The story we tell ourselves usually changes. It stops being This needs more work and starts being, maybe I'm not good at this. Huffington kept going past that point. Thirty-seven tries later, the book found a home. She has talked since then about where that persistence came from. Her mother used to tell her something simple. Failure is not the opposite of success. It is part of success. Say that slowly because it does real work. Failure is not the opposite of success, it is part of success. Many people picture success and failure sitting at opposite ends of a s of a line, like a scale running from zero to done. Every rejection on that scale reads as distance lost. Every no pulls you further from the goal. Huffington's mother was offering a different picture entirely. Not a line with two ends, but a pile of material you build with. Each rejection is not a step backward on the way to the goal. It is one more piece of information about what the next version needs to be. Now, here's where a lot of leaders misread this idea when they hear it. They hear failure is part of success and they nod along. Then they go run their team exactly the way they did before. They say they want people to take risks. They say a good miss beats a safe nothing. Then a project falls short, and the reaction in the room looks like a looks a lot like the reaction to carelessness. Same tight jaw, same long pause before anyone speaks. The team notices the gap between the words and the reaction faster than any memo could ever close it. Once that happens, something predictable follows. People do not stop having risky ideas. They stop bringing them forward. The next proposal on your desk gets a little smaller, a little safer, a little more certain to survive, even if it never really tests anything. You end up with a team that looks careful and is actually just scared. That is the cost of praising failure in public while punishing it in private. It's quiet. It's slow. It rarely shows up on this quarter's numbers. The real reframe is not about tolerating failure after it happens. It's about what you decide failure means before it happens. A rejected idea is not a verdict on the person who raised it. It's a draft, something to revise, not something to bury. The question worth asking after a miss is not whose fault was this? It is what does this tell us that we did not know yesterday? Now think about where an AI tool fits into a story like this one. Ask it to draft something and it will hand you a clean, confident answer, whether this is the first time you've asked or the 500th. It has never sent a manuscript out and watched 36 replies come back no. It has never had to sit with a rejection, feel the pull to quit. And choose to send the next version out anyway. That choice, made again after being told no, is the actual skill sitting underneath Huffington's quote. A tool can produce a draft in seconds. It cannot show you what it costs to keep drafting after the world has told you to stop. That part is still entirely yours. So here's something worth trying this week. Think of the last idea on your team that got turned down, quietly or loudly. Go back to whoever proposed it. Don't ask them to defend it. Ask them what they would change about it now that they know more. Listen for what that answer teaches you about how your team actually handles being told no, not just how they talk about handling it. Carry this forward past today. The leaders worth following are not the ones who never hear no. They're the ones who have heard it often enough to stop confusing it with the end of the story. Huffington heard no 36 times. The 37th answer was yes. And it came from a manuscript that had not changed its core idea once. It had just kept finding its way back to another reader.