The Pattern That Wouldn't Stop

I didn't set out to build frameworks. I set out to solve a few key problems.

Then I noticed I was solving the same sets of problems in Indiana. And in South Africa. And in Boston. Different situations, different cultures, different funding structures, different histories. Same problem, different clothes.

That's when I stopped thinking it was a local problem.

Indianapolis: Where It Started

I grew up in Indianapolis. Came to faith there. Started paying attention to the people around me who weren't interested in church, weren't drawn to the programs being offered, had real needs that the organizations built to serve them seemed unable to reach.

The first time I noticed what I would later learn to call a survival question, I was in a room with church leadership. The questions being asked were of the vein "How do we build our church?" The question I kept expecting to hear was "How do we reach this community?" Those aren't the same question. And the filter you're asking for shapes which one feels most natural.

Nobody in that room was bad at their job. They were asking from a real place. They were responsible for keeping an organization alive and growing. That filter produced certain questions naturally. It just didn't always produce the ones that pointed toward the wider community they were placed within.

I went to college thinking formal education would help me understand why. I studied church planting. Sat through classroom frameworks that had almost no relationship to the human realities I had been watching. The theory was clean. The people I knew weren't.

The gap between the theory and the reality of community life became my obsession.

South Africa: The Pattern Shows Up Again

I left Indiana thinking that if I could just get to a different context, I could find a different set of questions being asked. I ended up in South Africa doing mission work. Different continent, different history, vastly different everything.

Same patterns.

The missions agency I landed with was asking for a sustainability-first orientation, just like the church back home. The gap between what the organization said it existed to do and what it actually spent its time and energy doing was visible almost immediately. Not because anyone had bad intentions. Because the filter of institutional survival shapes the questions you ask, and the questions you ask shape where you spend your time.

I wanted to pursue integrated community development. Spiritual formation, ministry, relationships, and practical community restoration done together, in ways that were authentic and whole. What I kept running into was an organization whose questions were more oriented toward its own survival than toward the transformation of the communities it claimed to serve.

What South Africa gave me that Indiana hadn't was the concept of ubuntu. The Shona expression is hunhu. The idea: "I am because we are." Personhood isn't constituted by individual achievement. It's constituted by the community.

When I delved into that idea, something clicked. The filter question I had been watching wasn't limited to specific organizations. It was a question about how organizations conceive of themselves in relation to the communities they serve.

An organization asking from a self-preservation filter will generate self-preservation questions. An organization asking for a regional ecosystem filter will generate entirely different ones. Neither filter is a moral verdict. They're just orientations. And orientations produce questions. And questions produce decisions. And decisions produce outcomes.

The outcomes I was watching weren't serving the communities well. That's what I kept following.

Boston: Where the Framework Crystallized

Then Boston. A completely different world. Major metro. World-class institutions. Dense networks of sophisticated organizations with serious funding and serious talent.

I expected the questions to be different. They were more of the same, in more sophisticated language.

By the time I got to Boston, I had been watching the same five patterns for years. In different geographies. In different sectors. In organizations with $50,000 budgets and organizations with $50 million budgets. Religious organizations, secular nonprofits, government agencies, and early-stage startups. The scale changed. The sophistication of the language changed. The underlying pattern was the same.

Boston is where I finally found the intellectual frameworks to name what I had been watching intuitively. Systems change theory. Ecosystem work. Collective impact. Community development methodology. For the first time, I had language for patterns I had been seeing since Indiana.

Here's what systems thinking gave me: the insight that most organizations are perfectly designed to get the results they're getting. If the community isn't being served, if the leader is exhausted and the organization is stagnant, that's not a failure of character. It's the logical output of the system that's been built. The system is working exactly as designed. What needs to shift is the design.

And the design always starts with the questions. Which always starts with the filter from which those questions are being asked.

The Five Patterns

Across Indianapolis, South Africa, and Boston, across ministry, missions, nonprofits, and ecosystem work, I watched the same five patterns appear regardless of context.

Pattern One: Survival orientation producing survival questions.

Every organization I've watched get stuck was asking from a survival orientation while telling itself it was thinking strategically. "How do we grow our donor base?" "How do we increase attendance?" "How do we keep the board happy?" These are natural questions when institutional continuity is the primary filter. They're not bad questions in isolation. But when they become the primary questions, the organization stops generating questions that point toward the community and starts generating questions that point back at itself.

Research on nonprofit leadership finds that financial sustainability, workforce retention, and organizational capacity are consistently the top concerns of nonprofit leaders. All survival-orientation questions. The organizations actually moving the needle were the ones that had learned to start from the community's needs and work backward to the organization's design. The filter came first. The questions followed.

Pattern Two: Ecosystem blindness in decision-making.

Organizations making decisions through their own filters don't naturally account for the larger ecosystem they're part of. A church launches a program that a nonprofit two blocks away has been running for ten years. A nonprofit competes for the same grant as a school district doing identical work. A startup builds a technology solution for a problem that a community organization has already solved relationally, but doesn't have the infrastructure to scale.

I watched a partner reveal in a single unguarded moment that their primary filter in our shared work had always been donor relationships and competitive positioning. The moment I started building my own organization, they stopped returning calls. It wasn't a moral failure. It was a filter producing predictable questions. The filter just wasn't pointed at the mission we had both said we were pursuing.

When an organization shifts its filter from "what serves our position" to "what serves the whole," the questions change. Deal flow opens, new partnerships form, and the community gets served at scale. The research on collective impact is consistent on this: the highest-performing cross-sector initiatives are characterized by organizations that shifted from self-referential to ecosystem-referential decision-making. The filter changed. The outcomes followed.

Pattern Three: Leaders carrying everything that should be carried by systems.

This one shows up differently in different sectors, but the underlying dynamic is the same. The founder still approves every hire three years in. The pastor is the spiritual director, CEO, facilities manager, and chief fundraiser, all at once. The nonprofit ED that cannot take a vacation without the organization stalling.

Every decision flows back to one person. That person is exhausted. The organization is moving at the speed of that person's available attention. Which means it's moving far too slowly to serve the community at the level the community needs.

The filter here is usually something like "nobody else can hold this the way I can." Which is often true in the early stages. But when it persists past the point where it's useful, it produces questions like "how do I manage all of this?" instead of "how do I build systems that don't require me to manage all of this?" The filter produces the question. The question produces the outcome.

Pattern Four: The "finally" moment that keeps not arriving.

The "finally" moment is when a leader sees what needs to happen, has the infrastructure to act on it, and can feel the momentum shift. I have watched dozens of leaders come within arm's reach of that moment and step back. Not because they lacked vision or courage in some absolute sense. Because the filter they were asking for made the cost of moving feel larger than the cost of staying.

The filter of loss aversion produces questions about what could go wrong. The filter of possibility produces questions about what could go right. Both filters are rational. Both produce coherent questions. What differs is what they make visible and what they obscure.

The job isn't to tell someone their filter is wrong. It's to help them see what their current filter is making invisible, so they can decide whether they want to keep asking from that place.

Pattern Five: Infrastructure deficits misread as vision deficits.

The leaders I've worked with are almost never lacking vision. They can see exactly where they need to go. What they're missing is the infrastructure to get there. Systems. Processes. Hierarchy. Succession planning. Automation. Roles that exist independent of the personality currently filling them.

When infrastructure is missing, the questions that get asked tend to focus on individual performance. "Why isn't this person executing better?" "Why do I have to keep repeating myself?" "Why isn't the team moving faster?" These are reasonable questions from inside the situation. But the filter is aimed at people when it should be aimed at architecture. The infrastructure deficit produces questions about what's needed when what's needed are design questions.

What the Pattern Means

I am not the first person to notice that organizations get stuck. What I might be is the only person who has watched the same five patterns play out in Indianapolis, in South Africa, in Boston, in churches and nonprofits and startups and community development organizations, and arrived at the conviction that these are not five different problems in five different places.

They are one pattern, showing up in different costumes.

The problems are the same. The solutions are the same. We just are not learning from one another well.

The church that has spent forty years developing spiritual formation infrastructure doesn't know the startup two miles away would pay anything for a framework for organizational culture. The nonprofit that cracked the code on community trust-building doesn't know the school district across town is trying to solve the exact same problem with a fraction of the relational capital. The business leader who built a revenue engine that actually works doesn't know the ministry leader down the street is trying to figure out how to make an organization financially self-sustaining.

None of them is talking to each other. All of them are working on the same pattern, slowly, alone.

The five patterns appear everywhere because the underlying human dynamics that produce them are universal. Organizations are built by humans. Humans asking from a survival filter generate survival questions. Humans in systems that reward individual performance generate questions about individual performance. The patterns are not sector-specific. They're human.

Which means the path through them isn't sector-specific either.

Why This Matters for Your Organization

If you've been feeling like your problem is unique, unique to your sector, your size, your history, your specific constraints, I want to offer you a different frame.

Your problem is probably not unique. You're probably running one of five patterns I've watched repeat across every context I've ever worked in. That's not discouraging. It's actually freeing.

Because if the pattern is the same, the path through it is the same. The specific form it takes will depend on your context. But the underlying architecture of the shift, the filter that needs to move, the questions that need to change, the infrastructure that needs to be built, that architecture is transferable.

You see more clearly than you realize. There's an opportunity to unlock things for a lot more people.

The question is whether you're ready to look at the filter you're currently asking for, and whether what it's producing is what you actually want.