Noor had the keys, the donor list, the relationship with the school caretaker, the bank login, the memory of who was allergic to sesame, and the only phone number for the person who could repair the soup warmer.
This is a composite case, built from patterns we see in small community groups. The details are invented, but the structure is familiar. A useful initiative begins because one person sees a gap and moves faster than the formal system. They know the neighbors. They answer messages late. They carry equipment in their own car. They remember which funder paid for the chairs and which volunteer cannot do stairs.
For three years, Kiezküche West ran a weekly neighborhood meal, a food-sharing shelf, and occasional form-filling afternoons. People trusted it because Noor trusted them first. Then Noor’s paid job changed. Suddenly the initiative learned that it had not only a founder. It had a single point where almost everything passed through.
Founder dependency is not a character flaw. It is often the price of starting with too little money and too much urgency. But if it is not addressed, the project becomes fragile and the founder becomes trapped.
The first sign was not crisis. It was waiting.
At Kiezküche West, small decisions started waiting for Noor.
Could the Tuesday group use the room on a school holiday? Ask Noor.
Where were the spare gloves stored? Ask Noor.
Could the grant pay for a larger pot? Ask Noor.
Who should respond to a tense message from a neighbor? Ask Noor.
The group had volunteers. It even had a small Verein structure. But the practical authority still lived in one person. Meetings produced kind words and new ideas, while the actual operating system remained private.
This is what happens when an initiative depends on one person: knowledge becomes personal memory, access becomes personal possession, and relationships become personal bridges. If that person becomes ill, moves, burns out, has a family emergency, or simply wants a smaller role, the group discovers its missing structure all at once.
The answer is not to push the founder out. Many founders carry deep trust that cannot be copied into a document. The answer is to move enough knowledge, access, and authority into shared routines that the work can breathe without them.
Step one: make the invisible work visible
Kiezküche West started with a two-hour “what Noor actually does” session. The rule was no judgment and no immediate fixing. Volunteers wrote tasks on sticky notes.
The list was longer than anyone expected:
- opening and locking the room
- food pickup coordination
- volunteer reminders
- reimbursement checks
- grant reporting
- WhatsApp moderation
- conflict conversations
- contact with the landlord
- supply shopping
- translation requests
- allergy notes
- storage decisions
- social media posts
- thank-you messages
- repair calls
- cashbox reconciliation
This exercise can feel exposing. Founders may worry it looks like they controlled too much. Other volunteers may feel guilty. Try to keep the tone practical. The list is not evidence for a trial. It is a map.
Once the work is visible, sort it into four groups: tasks only the founder can do for now; tasks someone else can learn; tasks that should be shared by rota; tasks that should stop, shrink, or be paid if funding allows.
The last category matters. Handover is not magic. If one person was doing thirty unpaid hours, splitting those hours among five people may still be unrealistic. Sometimes resilience means reducing the offer.
Step two: share access before it is urgent
The most dangerous dependencies are often boring: passwords, keys, bank access, document storage, and contact lists.
Every community organization should document where essential access lives and who has authority to use it. For a small group, this may include:
- room keys and alarm codes
- bank or payment access, with proper internal controls
- grant agreements and reporting dates
- insurance documents
- Verein registration documents, if applicable
- contracts, leases, or room-use agreements
- equipment inventory
- volunteer contact lists
- partner contacts
- email, website, and social media accounts
- data protection notes, including what personal data is stored and why
Do not solve access by giving everyone every password. That is not resilience; it is risk. Use a clear minimum: at least two authorized people for critical functions, role-based access where possible, and a written record of who can do what. Money should have more control than a cupboard key. Personal data should be handled with care and only kept when needed.
If the group holds sensitive information about children, families, violence, health, or immigration status, do not improvise. Keep less data, protect it better, and get appropriate advice for safeguarding and privacy. Community Roots Foundation stays in the funding and operations lane; deeper safeguarding design belongs with specialist support such as Safe Childhood & Family Support Network.
Step three: hand over relationships, not just tasks
Noor could forward a phone number in ten seconds. That did not mean the relationship had been handed over.
Many small initiatives depend on warm relationships: the caretaker who opens the side gate, the local grocer who donates bruised fruit, the social worker who quietly tells families about the meal, the foundation officer who understands why receipts are messy after a busy month. These relationships need introductions, not extraction.
Kiezküche West used paired handovers. Noor joined the first call or meeting, explained the new contact person’s role, and then stepped back. The new contact sent the next routine update. For a few months, Noor stayed available for context but did not remain the default sender.
This protects trust. Partners are less likely to panic when they see continuity. New volunteers are less likely to feel they are impersonating the founder. The founder can lend credibility without keeping ownership of every bridge.
Be honest with partners. “We are sharing responsibilities so the project is less dependent on one person” is a mature sentence. Good funders and partners understand it. If a partner insists on dealing only with the founder, that is useful information about a dependency you still need to manage.
Step four: delegate authority, not just chores
At first, Kiezküche West gave people tasks but not decisions. A volunteer could buy supplies but had to ask Noor which brand. Another could schedule the room but had to check every exception. This looked like delegation and felt like babysitting.
Real delegation needs a boundary around authority:
- What can this person decide alone?
- What budget can they spend?
- When must they consult others?
- What values should guide judgment?
- How will the group review decisions without punishing initiative?
For example, a meal coordinator might be allowed to spend up to an agreed amount on missing ingredients, adjust the menu for donations, and recruit two extra helpers for a busy evening. They must consult the group before changing the meal time, entering a new supplier agreement, or using personal data for a new purpose.
This can fit on half a page. It does not require a thick manual. The paperwork should be smaller than the project. But no paperwork at all often means the founder remains the only person allowed to act with confidence.
Step five: create routines that survive mood and memory
Kiezküche West chose four routines:
A monthly operations meeting with a fixed agenda: money, volunteers, space, partners, risks, next month.
A simple handover folder: current contacts, recurring tasks, key documents, templates, and deadlines.
A role review every six months: who is doing what, who needs backup, what should stop.
A decision note after each meeting: decisions made, person responsible, deadline, and where documents are stored.
None of this is glamorous. That is the point. Fragile groups often rely on emotional intensity to remember everything. Stable groups build small habits so people do not need to be intense all the time.
Do not design routines for an imaginary professional office. Design them for volunteers who read messages on buses, after shifts, between care responsibilities, and in more than one language. Short, repeated, and findable beats perfect and forgotten.
Step six: let the founder change role with dignity
Founders can make handover harder. They may correct too quickly, hold private conversations, rescue every weak point, or feel hurt when others do things differently. They may also be reacting to real history: years of being the person who had to care because nobody else did.
The group should not treat the founder as the problem. It should define a new role.
Noor became “relationship adviser” for six months. She attended one monthly meeting, supported two partner handovers, and stopped being the first contact for routine questions. Her name remained in the story of the project, but not in every operational thread.
A founder handover is safer when it has dates. Without dates, “stepping back” becomes a vague promise and the founder is pulled in whenever stress rises. With dates, the group can review what is working and what still depends too much on one person.
There may be grief. A founder may miss being needed. Other volunteers may miss the speed of one-person decisions. The project may become slower for a while. That is not failure. It is the sound of responsibility becoming shared.
The most useful question is not “How do we replace Noor?” It is “What must no longer live only with Noor?”
When the answer is written down, shared, and practiced, the initiative becomes less dramatic and more durable. That is usually a good trade.