I was in a call with a colleague yesterday and we were discussing Founder’s Syndrome. Over the years, it’s one of the more persistent patterns I have seen in non-profits and social enterprises. There are a lot of similar aspects to this pattern, and it generally unfolds like this:

A person or small group of people start something. Usually, they come from the front line and have experience working directly with people, delivering services, restoring landscapes, organizing campaigns, etc. With a little bit of success, these folks start thinking about growing their operations and stabilizing them over time. This means bringing in staff, board members, and funders who believe in them and want to support the vision. Some staff may be the same kind of front-line folks that the founder was. Still, many will be experts in another aspect of growing and operating an organization: managers, board members, marketers, finance people and so on. While these folks are all crucial to running an organization well, they don’t always share the founder’s experience with grassroots or front-line work.

Often, as the organization grows, the founder realizes that their role can no longer be directly involved in the front-line operations of the organization. They retreat to a more visionary role, and, as the holder of the core story and vision of the organization, they become an ambassador for the work, obtaining funding and support and good board members who can oversee the organization. This sounds good, but it can often generate many issues, especially as the founder begins to sense the end of their involvement with their organization.

At this stage a number of inevitable patterns begin to emerge. They don’t always work like this, but these are common enough that I see them over and over in organizations that have been around for a couple of decades, sometimes less.

The founder begins to feel irrelevant and starts getting nosy. If your whole life has been spent creating programs for vulnerable youth, you might not find yourself relishing leading an organization set up to do this. Founders often have a hard time removing themselves from the day-to-day operations because their heart lies with the activism and the work of change-making, not organizational sustaining. Sometimes founders will involve themselves too much in the front-line work, micro-managing and being unaware of their power and influence. This can lead to trust issues, where newer hires don’t feel like they can learn and grow in their jobs. The antidote to this is to establish good governance structures and good roles and for the founder to transition into a new role through learning and cultivating leadership.

Hardly anyone thinks of succession until it’s too late. This controlling dynamic affects the ability of a founder to plan well for succession. Very few founders give much thought to their own disappearance from their life’s work, especially when building and growing an organization which relies so heavily on them. If an organization successfully survives over the long term, there will always come a time when the founder will step back. I have talked with founders who occupy all points of the spectrum that range from “I can’t leave because the organization will collapse without me” to “if the organization dies when I’m gone, I’m okay with that.” Once you’ve created a structure and moved into a leadership role, it is time to think ahead about how you will get out of it. Even if that is 20 years ahead, it shapes your approach to mentorship and shared leadership. Building shared leadership early will help folks move into roles and create mutual support relationships that allow people in the organization to grow into these roles, increasing organizational resiliency over time.

Resisting change. Organizations that grow their stability also become less able to change. Board members appointed to support the founder’s vision often govern to a rigid version of what that looks like, and Boards like this are always more risk-averse than a swashbuckling social entrepreneur. Funders can enforce a kind of rigidity of approach too as funding grants can bend an organization’s operations to the funder’s theory of change rather than create the ongoing ability of social enterprises to grow and adapt. Stability is a polarity, and from the beginning, organizations need to develop resiliency rather than robustness. They must survive by being changed rather than stand as a bulwark against change. This is hard when you deliver services because clients require a continuity of care, and there are no easy answers to these questions. Managing this polarity is crucial for overcoming a founder’s syndrome, where the governance and funding are tied to an original vision and are not allowed to grow beyond the founder.

Splits between board and staff. In the early days of an organization, everyone is moving in the same direction, doing the same things and pitching in wherever they need to. However, as organizations become larger and more stable, roles become highly differentiated. Board members are often chosen more because of their connections to funding and power than to the front-line work. Staff are learning and adapting at the coal face of the work. The two groups often develop a distance between them, making it hard for them to be mutually supportive. When organizations ask me to help them with strategic planning, I always ask them to do it jointly with the board and staff and even clients and other stakeholders. Organizations that set their mandates and future plans through closed board sessions tend to suffer from a deep lack of situational awareness about the organization’s context. This can exacerbate founder’s syndrome even after the founder has left, as they will often invoke the founder’s intentions in their role as stewards and guardians of that vision. Ignoring the needs, concerns, creativity and awareness of staff and partners is a good way to dig a hole of irrelevancy for an organization.

This is just a bit of the ground I covered with my colleague yesterday. What patterns and responses do you notice?