In 2021, a nonprofit board I sat on ran a fundraiser that failed completely.
A week before the event, nobody had built the website. Zero donations had been collected. Not a few. Zero. The failure wasn’t bad luck or bad timing. It was a project management flop, plain and simple, and I was part of the team that let it happen.
That flop changed how I operate. Not because failure is inspiring. Because I finally built a system for what to do after one.
Failure is data, not a verdict
School trains you to avoid failure at all costs. Perfect scores. Straight A’s. Gold stars.
The real world runs on a different script. Out here, the people who never fail are usually the people who never attempt anything hard enough to matter. Playing it safe for decades might land you a stable job. It can also leave you exposed the day the layoffs come or the industry shifts.
Every failure I have learned from had the same shape. Something broke. I wrote down what actually happened. I extracted one lesson. I changed one thing. Then I moved.
That is the whole loop. Attempt. Record. Extract. Adjust. Repeat.
It sounds simple. Almost nobody does it systematically. Most people do the first half, feel bad, and skip the rest. The loop only pays if you close it.
Run your failures through the loop
Here is what the loop looks like on real failures, mine included.
The fundraiser flop. What happened: no website, no donations, one week out. What it cost: the event, obviously, and credibility with donors. The lesson: check in with colleagues well before the deadline, especially when someone owns a critical piece. The change: I now verify the critical path on any project I touch, early, in writing. Trust, but verify the website exists.
The failed client pitch. I walked into a high-stakes pitch running on confidence and light on preparation. Sweaty palms. Shaky voice. It showed. The lesson: overconfidence is a trap, and preparation is the difference between nervous and ready. The change: I rehearse every important presentation now. I anticipate the hard questions. I leave room for humility. That one flop made me a sharper communicator.
The missed deadline. As a senior tax analyst, I missed a critical deadline. I didn’t just apologize. I rebuilt my workflow, automated the repetitive pieces, and cut errors by 30 percent. The lesson: a miss is a process problem wearing a personal failure costume. The change: fix the process, not just the apology.
The marathon wall. I have hit the wall in marathons, the point where your legs quit negotiating. You don’t quit. You adjust pace, hydrate, and keep moving. The lesson: most failures are pacing failures. The change: respect the distance, whether it is 26.2 miles or a multi-year career move.
None of these felt like data at the time. They felt terrible. That is the point. The loop doesn’t remove the sting. It converts the sting into inventory.
Why most people never close the loop
Two reasons.
First, ego. Writing down what happened, honestly, without adjectives, is uncomfortable. “The pitch failed because I was underprepared” is a harder sentence than “the client wasn’t ready.” The loop requires the harder sentence.
Second, speed. People rush past the failure toward the next thing. Reflection feels like standing still. It isn’t. It is the step that makes the next attempt smarter than the last one.
I keep it simple. After any real setback, I answer three questions. What happened? What did I learn? What is my next move? Three lines. Five minutes. It is the cheapest high-leverage habit I own.
The compounding part
Here is what nobody tells you about failure. One failure, processed through the loop, is a lesson. Ten failures, processed through the loop, is a system. A hundred is an unfair advantage.
Each loop makes you harder to surprise. You start recognizing patterns: I fail when I rush. I fail when I skip prep. I fail when I assume someone else handled it. Once you see the pattern, you can design around it before it costs you again.
That is what I am writing about in my book on failure. Not failure as inspiration. Failure as raw material, processed deliberately, until it becomes judgment.
Start your loop
You don’t need a journal with a leather cover. You need three honest sentences after your next miss.
What happened. What you learned. What changes.
Do that ten times and you will have something most people never build: a personal database of what doesn’t work, which is another way of saying a map of what does.
Failure isn’t the opposite of success. Unprocessed failure is.
Want to keep reading?
If this one landed for you, come read more of my work. My newsletter, Ryan’s Leadership Lessons, is where I share what I’m learning about leading teams, coaching people, and building a career with agency, every week. The blog is more my philosophy wranglings and the Substack more my practice. Sandbox vs Live if you will. Subscribe to Ryan’s Leadership Lessons