Fragmentation is structural, not a content problem

On day thirty-one of her sabbatical, Joelle called me.

She had been quiet for a month. That was the deal she had made with the elders and with her husband — three months, no church email, no pastoral calls, no sermon prep, no meetings. The first ten days she had not known what to do with herself. The next twenty she had slept more than she had slept since seminary. By day thirty-one she was ready to talk.

She did not want to talk about church. She wanted to talk about the three years that had ended her up in her kitchen in November unable to stand.

"I thought I was bad at remembering people," she said. "I thought I was bad at documentation. I thought I needed a better system. I thought I needed to be more disciplined. I tried every one of those things for three years. It kept getting worse. At some point I stopped thinking it was me and started wondering if it was the job."

"And?"

"Then I thought it was the job, and tried to find a better job. But the other pastors I know are having the same collapse. So it is not the job."

"What is it, then?"

She was quiet for a while.

"I don't know," she said. "That is what the sabbatical is for."

This chapter is for Joelle on day thirty-one. It is also for Wes and Maggie and Elias, each of whom is somewhere inside the same sequence — tried the first explanation, tried the second, tried the third, and is now sitting with the suspicion that the problem is not where any of the three explanations said it was.

I want to name what the problem actually is. Not because naming will solve it — it will not. The rest of this book will take twenty chapters to propose a pathway, and the initial build on that pathway is a four-week residency for a movement leader or a four-week system build for a non-profit domain. It is not a marathon; it is a specific, time-bound residency, and what it ends with is concrete — core content ingested, a live content layer across every theme, a working course, pathways in place. The ongoing practice of running on a foundation is, of course, permanent. But the initial gathering is four weeks, not three years. Naming the problem is the minimum load-bearing move before any of the rest of the work can begin, and in my experience the naming is what is most consistently missing from how this conversation gets had in the sector.

So: fragmentation is structural.

Not a content problem. Not a tool problem. Not a willpower problem.

A condition of the foundation.

I want to defend each of those three negations before defending the positive claim, because every leader I have worked with has tried at least one of the three first, usually for years, often for hundreds of thousands of dollars or equivalent staff time. And I want to take each one seriously, because the fact that they persist — across sectors, across generations of leaders, across repeated evidence of failure — is itself a data point about how the sector has been taught to see the problem.

The content misreading

The first thing a leader tries is almost always a content fix.

The content fix says: we have not written enough of it down. If we write more of it down, with more rigor, and put it in a better place, we will solve the problem.

Maggie tried this in 2019. She hired a writer — someone good, someone expensive — to spend six months with her "organizing her body of work." The writer was a talented editor who had worked with two other movement leaders in Maggie's category. The writer read every book, listened to a sample of the talks, sat through twelve long conversations with Maggie, and produced a fifty-page document titled The Definitive Framework Statement.

The document is in Maggie's Dropbox. It is excellent. It has been read by approximately three people.

It did not solve the problem, because the problem was not that Maggie had not written the framework down. The framework had been written down many times — in six books and forty-seven talks and a Substack. The problem was that there was no shared foundation that caused the framework to carry forward. To be cited consistently. To be findable as canonical. To surface when the framework was needed. To update when Maggie's thinking evolved. To be referenceable by partners and translators and AI systems. The writer's document did not become the foundation. It became a forty-ninth surface.

The content fix fails in a specific way. It produces more good content. The good content goes into the scatter field with all the other good content. Six months later, the leader has a slightly better version of the problem they started with.

I see this particular failure two or three times a year. I see it in nonprofits that commission a theory of change document in year one, a strategic framework in year three, a brand book in year five, and a values statement in year seven. Each document is good. Each document is filed. Each document is referenced in the memo proposing the next document. None of them changes the foundation.

The content misreading persists because it feels responsible. Writing the thing down is what serious professionals do. But fragmentation is not reversed by adding a new written artifact to a field that already contains too many uncoordinated artifacts. Fragmentation is reversed by changing the relationship between the artifacts.

The tool misreading

The second thing a leader tries is a tool fix.

The tool fix says: we are using the wrong software. If we adopt better software, implemented properly, the fragmentation will resolve.

Wes's organization has tried this three times in the last eight years. A CRM migration in 2018, from a generic nonprofit product to a more sophisticated one. A constituent engagement platform in 2021, layered on top of the CRM. A donor intelligence tool in 2024, meant to surface hidden insights from the existing data. Each project took nine to fifteen months. Each involved consulting fees that ranged from forty to two hundred thousand dollars. Each was pitched to the board as the decisive move that would unify development operations.

Wes still cannot find the memorial-fund conversation with Dean.

The tool misreading fails because tools are surfaces, and fragmentation is not a surface problem. A new surface does not integrate the old surfaces; it adds to them. Nothing about buying Salesforce, or replacing Salesforce with HubSpot, or replacing HubSpot with a bespoke Rails application, makes the handwritten note in the retired officer's filing cabinet queryable. The tool promises integration. The tool delivers a new place to put the fragments.

There is a particular pattern in the first year of a major tool migration, and I want to name it because every reader who has lived through one will recognize it. The first six months are frantic — data migration, user training, workflow redesign, change management. The next six months are the honeymoon — the new tool is cleaner, the interface is nicer, small things work better. Then, at month twelve, the leadership team notices that the new tool has the same fundamental problem the old tool had, plus a one-time implementation cost, plus a per-seat license five times higher than before, plus six months of lost staff productivity during the migration.

The team does not say this out loud at the one-year retrospective. The team quietly concludes that the next migration, when it comes, will need to be done right this time. And the migration after that.

The tool misreading compounds specifically because the tool industry has an enormous vested interest in it continuing. The only people selling you the tool are people whose business is selling you a tool. The only case studies you will ever read are case studies produced by companies whose continued existence depends on the story that tools solve fragmentation. The sector has not yet produced a literature that honestly names what tools can and cannot do, so each generation of leaders re-learns the same lesson at roughly the same cost.

Tools are real. Tools matter. A good integrated foundation will run on good tools. But tools do not produce integration. They run on top of integration. The order of operations is critical, and the tool industry systematically reverses it.

The willpower misreading

The third thing a leader tries is a willpower fix.

The willpower fix says: we are not disciplined enough. If we commit harder, document more consistently, and hold each other accountable, we will solve the problem.

Joelle tried this for three years. She did it in the specific way pastors do — not with a dashboard or a Kanban board, but with a shepherd's commitment to remember each person. She kept a leather journal. She blocked two hours every Monday to pray through the congregation. She wrote notes after every pastoral conversation. She tried, harder than any human being should have to try, to carry seven hundred people in her personal memory while also doing the rest of her job.

She ended up unable to stand in her kitchen.

The willpower misreading fails for a specific reason that is worth naming bluntly: individual human capacity does not scale to the size of an integrated organizational foundation.

This is a quantitative claim as much as a qualitative one. A pastor can hold, in useful active memory, the pastoral condition of perhaps sixty to eighty people. A development officer can hold the full relational context of perhaps forty donors. A founder can hold the operational tacit knowledge of perhaps a thirty-person organization. These are not personality limits. They are human-cognition limits, and they have been documented in contexts ranging from anthropology (Dunbar's number) to military doctrine (the span of control) to primary care medicine (the panel-size literature).

When the organization grows past those limits, the individual's willpower cannot absorb the gap. The leader can try — and Joelle did try, and every exhausted pastor and burnt-out development director and hollowed-out dean and tired founder I have worked with has tried — but the attempt ends the same way. Not in a moral failure. In a biological one.

The willpower misreading is also the most morally loaded of the three, because it maps onto the leader's deepest self-image. I should be able to do this. Other people do this. If I cannot do this, I am not cut out for the work. Pastors and mission leaders, in particular, are recruited for this trait and rewarded for it for years before it kills them. The willpower misreading does not look like a misreading from inside. It looks like the job.

It is not the job. It is a structural condition misdiagnosed as a moral one.

Joelle is figuring this out on her sabbatical. It is taking her longer than the other two realizations combined, because the willpower misreading is not an intellectual mistake; it is an identity mistake. She will have to grieve the version of herself that believed the weight of seven hundred people was hers to carry alone before she can build the church that no longer asks her to.

Every pastor, every nonprofit leader, every founder, every dean who crosses into sustainable work crosses through this particular grief. Most cross it later than necessary, because the sector tells them the willpower version of the story until they collapse.

Three misreadings, one underlying condition

The three misreadings share a structure. Each one locates the problem in the wrong place.

The content misreading locates it at the level of the artifact — we have not produced the right artifact yet.

The tool misreading locates it at the level of the system — we have not purchased the right system yet.

The willpower misreading locates it at the level of the person — we have not tried hard enough yet.

All three locations are the wrong location.

The problem is not in the artifact, the system, or the person. The problem is in the foundation — the layer beneath all three, which the artifacts and the systems and the people are supposed to be expressions of, and which, in a fragmented organization, does not exist.

That is what structural means.

What "structural" means, concretely

I have used the word structural in every chapter so far, and I want to stop using it loosely and define it.

A structural condition is a condition of the underlying shape of a system that cannot be solved by changing what runs on top of the shape.

A plumber will tell you that a house with undersized main pipes cannot be fixed by installing a better dishwasher, or by running the dishwasher at a different time of day, or by asking the family to use less water. The undersized main is the structure. Every fixture runs on top of it. Until you change the main, you are only ever negotiating the symptoms.

A cardiologist will tell you that a patient with a failing valve cannot be cured by a better diet, or by a better exercise plan, or by a more disciplined morning routine. The failing valve is the structure. All the downstream health choices run on top of it. Until the valve is repaired, the patient is only ever managing the symptom.

An architect will tell you that a building with a compromised foundation cannot be repaired by renovating the interior, or by repainting the facade, or by upgrading the finishes. The foundation is the structure. Everything else runs on top of it.

Organizations have a structure too. Or rather — and this is the hinge of the chapter — organizations have a structure when they have one, and most organizations do not.

The structure of a knowledge-carrying organization is the integrated foundation of its two intelligences. It is the layer beneath all surfaces — beneath the website, beneath the communications, beneath the CRM, beneath the learning management system, beneath the content library, beneath the pastoral care system, beneath the alumni database — that holds what the organization knows and whom it is connected to, in a form that every surface can draw from faithfully and every person can inherit without loss.

Most organizations do not have this foundation. They have surfaces sitting directly on top of the personal memory of their senior staff. When the senior staff are present and well-rested, the surfaces mostly cohere. When the senior staff are absent, overwhelmed, or departing, the surfaces reveal themselves as disconnected and the organization enters a memory crisis.

Structural means this: fragmentation is the default shape the organization takes when no shared foundation has been built. It is not caused by any single artifact, any single tool, or any single person's behavior. It is caused by the absence of the load-bearing layer underneath all three.

And — this is the part the sector mostly refuses to face — every month the foundation remains unbuilt, the content keeps being produced, the tools keep being purchased, and the people keep trying harder. All three efforts accumulate on top of the missing structure. The organization becomes more elaborate, more expensive, and more fragile.

This is what structural looks like. A condition of the layer underneath, masked by frantic activity on the layers on top.

The parallel to adaptive leadership

The sibling volume to this book — the one about AI and credibility — makes a parallel move in its second chapter. That book argues that AI is not a technological challenge but an anthropological one, and that leading through it is therefore an adaptive rather than a technical task, in the sense Ron Heifetz used those words.

The two reframes rhyme intentionally. It is worth saying why.

A technical problem, in Heifetz's framing, is one that has a known solution that can be applied by the right expert. An adaptive challenge is one that requires learning, loss, and change in the people and the culture themselves — it cannot be delegated to a technician, because the problem is in the collective's way of operating, not in any particular tool or procedure.

Fragmentation is an adaptive challenge in exactly this sense.

No technical expert can solve it for you. No consultant, however well-credentialed, can install the integrated foundation in your organization, hand you the keys, and walk away. The foundation requires the organization to change what it is willing to name as intelligence, whose memory it is willing to make institutional, which relationships it is willing to steward as assets, which decisions it is willing to document, which voice it is willing to designate as canonical. Every one of those decisions is an adaptive decision. Every one involves loss — loss of implicit authority held by senior staff, loss of flexibility in how things are done, loss of the ambiguity that made certain difficult conversations avoidable.

This is why the content fix, the tool fix, and the willpower fix are so persistent, and why they fail in the same way. Each of them is a technical response to an adaptive condition. Each of them delegates the problem to a category — the artifact, the system, the individual — that cannot hold it, because the problem is not in that category.

And this is also why, when you read the pathway chapters in Part III of this book and they sound like they are asking you to change how the organization thinks about itself, rather than what software it runs, you will not be misreading them. That is the claim. The pathway is not a technical installation. It is an adaptive passage, and the passage is load-bearing, and it cannot be skipped by hiring the right consultant or buying the right platform.

You will need consultants. You will need platforms. You will need writers and developers and systems architects and, yes, AI. But all of those are technical contributions on top of an adaptive decision the organization has to make for itself.

The decision is: we are going to stop treating our intelligence as the private property of our current senior staff, and start building it as the inheritable foundation of the organization.

That decision is structural. It is not made by a vendor or a taskforce. It is made by the leader, in council with the people the decision will most implicate, and it is the door through which everything else in this book passes.

What the reframe asks of you

Accepting the reframe is not free.

The leader who accepts the reframe has to stop asking which tool should we buy? and start asking what foundation are we missing? That is a harder question, because the answers are not on a G2 review site.

The leader who accepts the reframe has to stop asking how do we get our team to document better? and start asking what integrated layer would make documentation an emergent output of the normal work? That is a harder question, because it admits that the documentation problem was never a will problem.

The leader who accepts the reframe has to stop asking what am I doing wrong? and start asking what shape has this organization taken in the absence of the foundation, and what will it cost me, personally, to let the shape change? That is the hardest question, because it exposes the ways the current fragmentation has been protecting certain forms of authority the leader is not quite ready to release.

Every one of the four people we are walking with is somewhere in that last question.

Maggie's fragmentation protects a certain kind of authorial primacy. The framework is slightly different in every source partly because she has never had to commit to a canonical version in public, and the absence of the canonical version is what allows her to keep revising without the revisions being held against the prior versions. Fixing the foundation will mean designating a canonical framework, which will mean letting it be stable enough to be critiqued, which will mean grieving the private flexibility she has held for thirty-two years.

Wes's fragmentation protects a certain kind of professional indispensability. As long as the relational intelligence lives in Wes's head and his predecessor's filing cabinet, Wes is hard to replace. Fixing the foundation will mean making his knowledge institutional, which will mean making himself, in one sense, more replaceable — and every professional of a certain age has to cross the threshold where making yourself more replaceable is an act of faith rather than a career mistake.

Joelle's fragmentation has been protecting her sense of vocation. If she is the one who holds the seven hundred, then she is the pastor in a way that no formal structure can replace. Fixing the foundation will mean that the church can hold the seven hundred without her, which will mean — she is afraid — that she is no longer necessary. What her sabbatical is teaching her, slowly, is that a pastor whose necessity is structural rather than cognitive is still a pastor, and is, in fact, the kind of pastor the seven hundred actually need.

Elias's fragmentation has been protecting the faculty's ability to hold different private versions of the institution's positions. The reason the 2011 working group memo, the 2014 textbook, and the 2023 denominational statement were never reconciled is that reconciling them would require a faculty conversation about what the seminary actually teaches, which would require a faculty willing to surface the places where they disagree with each other and with the current president. Fixing the foundation will mean surfacing those disagreements. This is why fragmentation is never just an information-architecture problem; at the institutional scale, it is always a political and theological one.

The reframe is not free. It asks something specific and hard from each person who accepts it.

The refusal of the reframe is not free either. The four protagonists have already been paying for the refusal for years. So has every organization I have worked with. So, probably, have you.

The choice this chapter leaves you with

I want to ask you one question, and I want you to actually answer it, before you turn the page.

Of the three misreadings — content, tool, willpower — which one has your organization most recently attempted?

You will know. Every leader knows. The content writer you commissioned. The CRM you migrated to. The discipline protocol you launched at the last staff retreat. The one that was supposed to fix it, and did not, and is now either a half-alive project or a document in a folder or a memory of good intentions.

Name it.

Now ask yourself a second question, which will be harder: what was that fix supposed to accomplish, and what does it tell me that the thing it was supposed to accomplish has not been accomplished?

The fix was supposed to solve fragmentation. It did not solve fragmentation. What that tells you is not that the fix was bad, or that the implementation was botched, or that the team did not commit. It tells you that the fix was aimed at the wrong layer.

The fragmentation is still there. It is still there because the layer underneath — the foundation — has not been built. And it has not been built because no one has yet framed the work as building a foundation rather than as producing content, or implementing a tool, or improving discipline.

You have the framing now. The rest of the book will spend itself proposing what it means, practically, to build the foundation — the library, the graph, the voice, the pathways, the carry-forward, the formation architecture, the multiplication infrastructure, the field.

But the framing only lands if you accept the reframe. If you read the rest of the book while still locating the problem at the artifact layer, the tool layer, or the person layer, the pathway will read as prescriptions you have already tried, and you will conclude this book is one more iteration of advice you have heard before.

It is not. But only the reframe makes that visible.

So, one more sentence.

Fragmentation is not a problem you have. Fragmentation is the shape your organization has taken in the absence of a foundation. The work is not to fix the problem. The work is to build what was never there.

Chapter 4 is next, and it is the chapter about why this particular moment — the moment AI arrived — is the moment the unbuilt foundation stopped being optional.