The text came in at 6:40 on a Tuesday. A deputy one hundred miles away wanted to know if there was still a seat on the June trip, and the answer lived in exactly one place. My own head.
Not a shared calendar. Not a second person who could have handled it in ten seconds. Just me, half awake, thumbing a reply before the coffee finished and feeling good about how fast I turned it around. It took most of a year to see that the speed was the problem.
I co-founded a nonprofit that takes first responders into the backcountry. Frontline Freedom. You build a thing like that at night, after the full-time job, on weekends, in the cracks between everything else you already carry. For the first long stretch I did all of it. I wrote the grant language, answered the donors, called the outfitter, built the intake form, and sat on the phone with the guy who wasn’t sure he should come, the one who needed to hear that the trip was not soft and was not a trick. There is almost nothing built for these people specifically. That is why we started, and it is also why a seat on the June trip was not a small thing to the man asking. Every thread ran through me, and I called that commitment.
It felt like love. It looked like work ethic. People praised it. The board thanked me for carrying so much. And every word of that praise was another brick in a wall around the thing nobody wanted to say out loud. An organization where every decision routes through one person is not an organization. It is one person with a logo.
The first time I tried to hand off the calls, I lasted about nine days before I took them back. What I was protecting was not the quality of the call. It was the feeling of being the one the call needed. You have to be honest about that part, because the organization never will. The organization loves a founder who can’t let go. It runs on you for free.
I had watched this before, in a different line of work. Two decades in public safety teaching leadership development, and I sat in rooms with people who built teams that ran beautifully right up until the morning they transferred out. Inside a month, those teams came apart. The team was never the system. The team was the person. When the person left, the system left with them, because there had never been a system, only a very good individual everyone mistook for one. I used to think that was a failure of the people who stayed. It was a failure of the person who left, made years earlier, on the quiet day he decided being needed felt better than being replaceable.
So at 6:40 on a Tuesday, when I caught myself as the single point of failure for whether an exhausted deputy got a seat on a trip that might have been the thing that kept him in the work, I stopped feeling proud. The sector has a name for this. Founder’s syndrome. Almost everything written about it is addressed to a board, about a founder who has already become the problem, written from the outside, after the thing has hardened. Nobody writes it to the founder, early, while the grip still feels like devotion. That is the version I needed and could not find, so I am writing it.
Here is the part that the how-to guides skip. The same total commitment that lets you build something from nothing is what will eventually strangle it. The eighty-hour weeks. Answering every message within an hour. Being the face in every room. Closing every donor yourself because nobody does it the way you do. That devotion is real, and it is a slow-motion single point of failure with your name on the paperwork.
Being indispensable feels like winning. It is the most seductive trap in the building, because the whole way down, the work rewards you for it. More responsibility. More gratitude. More proof that you matter. And the number you are quietly running up is how fragile you have made the mission. If the place falls apart the week you get the flu, you did not build resilience into it. You built dependence and called it leadership. If it can’t run a week without you, you didn’t build an organization. You built a monument to yourself and put a cause on the sign.
This is harder if you came up in a world that trained you to be the one who handles it. In public safety, being the person everyone can count on is the whole identity. You carry it into everything after, including the thing you build to help. But a mission is not a tour of duty. It is supposed to outlast the person who started it. The point of building something is that it keeps running when you stop. And you will stop. Everyone does.
The shift is to design for your own absence in the first month, not the fifth year. Most founders treat succession as something you handle once the organization is big enough to matter. By then, the patterns are set, and you are the patterns. Start while it is small, and the stakes are low enough to fail safely. Name the few things only you can do, then spend a month making each one doable by someone else, even when they do it worse than you would. Especially then. The first time the board meets without you, the first time someone else closes the donor, it will go worse than if you had been in the room. Let it go worse. Worse is the tuition.
Be honest about what you are handing off, too. Most founders give away the errands and keep the decisions, then wonder why no one around them can lead. The errands were never the problem. Hand off a decision. Give someone the call where being wrong has a cost, and stay close enough to catch the fall but far enough back that the catch is theirs. That is the only delegation that builds a person instead of a helper.
There is a test for this, and it is simpler than any strategic plan. Pick a week. Put it on the calendar the way you would a trip you actually intend to take, and take it. Go dark. No approvals, no email, no being the answer to anything. If the June trip still runs, the donor still gets called, the board still meets, and the next exhausted deputy still gets a real reply, you built an organization. If it grinds to a halt, you did not, and you just found the job that matters more than the next grant. That job is building the people and the systems that answer the 6:40 text when you are gone. Which, one way or another, you will be.
I ran that test on myself, and then I did the harder thing. I stepped down as director. I am still a co-founder, still close to the work, still someone who will pick up when the mission calls. But the organization runs through other people now, and the 6:40 text goes to someone whose job it actually is. I am glad it does. Not glad the way you are supposed to say it from a stage. Glad because I have watched the place start to become things it never could have while I was the bottleneck with the best intentions.
If you are sitting where I was, here is the part that takes the longest, and it is not operational. You can write the procedures and train the people in a season. What takes longer is grieving the version of yourself that was needed. The grip was never about the calls or the donors. It was about what being indispensable did for me, the way it kept answering a question about whether I mattered. You do not get through founder’s syndrome by getting more organized. You get through it by admitting the feeling you are protecting is yours, not the mission’s, and choosing the mission anyway.
The mission needs that from me. So do the people it serves. They do not need a founder who is a monument. They need something that stays standing, still running trips, still answering the hard calls, long after I have left the room. The next time a deputy texts at 6:40 on a Tuesday asking if there is still a seat, I will not see it. Someone else will, and they will have it handled before the coffee finishes.