The Founder Problem: When a Project Cannot Outlive Its Starter

This is written to be used rather than admired. Each section below is a decision about founder dependency in local projects, and each one has a default.

Why founders accumulate everything

Someone starting a project holds every relationship, every password, every arrangement with the venue and every piece of undocumented history. That concentration is efficient at the start, when speed matters more than structure and there is nobody else to tell.

It becomes the project's main structural weakness within a year or two, without any single decision having created it. Newcomers find that every question routes back to one person, which discourages them from taking responsibility for anything. The founder then observes that nobody else steps up, which is true and is a consequence rather than a cause.

Informality as a barrier

Early groups make decisions in conversations, message threads and shared assumptions rather than in recorded meetings. That works perfectly for the people who were there and is impenetrable to anybody who arrives afterwards. Newcomers cannot tell what has already been tried, what was decided deliberately and what is simply habit.

In the annual accounts, asking risks looking ignorant about things everybody else appears to know, so people ask less and contribute less. Writing decisions down is the cheapest possible intervention and is resisted because it feels bureaucratic for a small group.

The identity problem

Projects closely identified with one person attract support because of that person, which is effective and is not transferable. Funders, partners and participants form a relationship with an individual and experience their departure as the project ending.

From the receiving end, the founder often reinforces this without meaning to, since they are the one being asked to speak, write and represent. Deliberately putting other people forward for those roles early costs the project some short-term effectiveness and buys durability. The test is whether a stranger could name the project without naming a person.

When the founder should step back

The useful moment is while the project is working well, which is precisely when nobody sees a reason to change anything. Waiting until burnout, illness or a house move forces the issue means the handover happens under conditions guaranteeing it goes badly.

A planned reduction, moving from running everything to holding one defined role, is far easier than a clean break. Founders who stay involved in a limited capacity with a clear boundary generally do better than those who leave entirely or stay in charge.

Setting a date in advance and telling people about it converts an emotional question into a logistical one.

What successors actually need

A written list of recurring tasks with dates, contacts and account details covers most of what is lost when a founder goes. Access to accounts, keys and systems in more than one person's name should be arranged before it is needed, not during a crisis.

Sorting the donation bags, explicit permission to change things matters enormously, since successors otherwise treat every arrangement as sacred and freeze. The reasoning behind decisions transfers better than the decisions themselves, because circumstances change and rules without reasons get followed wrongly. A period of overlap, where the successor runs things with the founder available, is worth more than any document.

Volunteers cost an organisation time to train, so short-term help is not always help.

When continuing is the wrong answer

Some projects exist because one person wanted them to and have no constituency beyond that, which is a legitimate thing to notice. Winding up deliberately, with assets passed to another local group, is a better outcome than a slow decline into nothing.

Over a funding cycle, where the group has a legal form, there will be rules about how to dissolve and where assets must go, and these need following. Handing an exhausted project to a reluctant successor produces a worse ending than closing it cleanly. Asking whether the project would be started today, by these people, is the question that usually answers this.

The takeaway

If the project cannot survive your absence for a month, that is the problem to work on this year.

Passed on beats recycled, and both beat replaced.