Two intelligences

Two hours in, Maggie had taken a photograph of the whiteboard on her phone and was studying it like a stranger.

We had come to a reasonable end. The fourteen surfaces, named. The word fragmentation accepted, not quite comfortably. She was ready to stop. I was ready to stop. We had pushed a leader in the last decade of her career to look at something she had not wanted to look at, and she had looked at it.

Then I asked her the second question. I did not plan to. It came out.

"What about the network?"

She looked at me.

"The three hundred people in your phone," I said. "The chairs and the seed leaders and the ten peer thinkers. The endorsers. The former staff. The five foundation officers who keep picking up the phone. The graduate students you mentored in 2011 who are running two of the best programs in the country now. The ones whose names are in your phone and nowhere else. What about them?"

She was silent for a long time.

"Those aren't—" she started. She stopped. "I don't think of them like that."

"Like what?"

"Like the books. Like the frameworks." She gestured at the whiteboard. "Like assets. They're people."

I said: "They are people. And they are also the second intelligence your organization runs on. And if we only gather the first one, we have solved half your problem and scheduled the other half for the next successor."

She took a second photograph. Of the empty half of the whiteboard.

The mistake I had almost made with Maggie is the mistake almost every fragmentation conversation makes, and I want to name it before this chapter goes any further. If you miss it, the rest of the book will read as a book about information management, and this is not a book about information management.

There are two intelligences running inside every organization, every leader's life's work, every church, every institution. Most efforts to address fragmentation gather one of them. Almost none gather both. Because both have to be gathered — because the formation the reader is presumably here for happens at the seam between them, and the seam does not exist when only one side has been built — the work of integration, which Part III of this book will spend several chapters on, has to be a paired work from the first week.

I want to name the two halves now, and then walk you through what each one actually contains, and then show you the seam.

The first half is informational intelligence.

Informational intelligence is everything your organization knows, has produced, has decided, has recorded, and has lived. It is not just "content." It is not just the books you have written, the programs you have run, the sermons you have preached, the research you have published. It is also the unwritten mental model your most senior staff member uses when she reviews a grant application. It is the decision your board made in 2019 and the reason your board made it. It is the voice you use when you write, and the voice you do not use. It is the story you tell at every staff retreat about why the organization exists. It is the workflow, never written down, by which a major gift solicitation actually moves from first conversation to signed commitment. It is the theology, the philosophy, or the ethical commitment sitting underneath every choice you make. It is, in ten overlapping categories I will walk you through in a minute, the entire structured-and-unstructured record of what you know.

The second half is relational intelligence.

Relational intelligence is everyone you are connected to and the history of every connection. It is not just your donor list. It is not just the contacts in your CRM. It is the three-hundred-person graph that Maggie and every leader like her carries mostly in her phone and her memory. It is the donors and the peers and the endorsers and the alumni and the board and the vendors and the emerging leaders and the audience. It is, for every one of them, the interaction history, the trust capital, the mutual obligations, the cultural fit, and the second-order connections — who they know, who introduced them, who could open which door on their behalf.

Both halves are intelligence because both can be gathered, structured, queried, activated, and put to work.

Both are fragmented in almost every organization I have worked with.

And the asymmetry of attention between them is nearly universal.

The asymmetry of attention

Most organizations have thought about one of the two halves and not the other. Which half, in my experience, depends on the organization's primary vocation.

Movement leaders and authors, like Maggie, have usually thought about informational intelligence. Their vocation is a body of ideas. They know, at some level, that their books and frameworks need to be gathered. Almost none of them have thought of their network as an intelligence in the same category. Their relationships are relationships, carried in memory and phone, honored by attendance at dinners and conferences and the right emails sent at the right moments. The idea that the network could be structured, queryable, and inheritable usually lands as either implausible or faintly dehumanizing.

Nonprofits, like Wes's, have usually thought about relational intelligence — or, more precisely, a sliver of it. They have a CRM. The CRM tracks donors. The CRM tracks, loosely, some of the giving history and some of the interaction notes. The development team thinks about donors as an asset class. Almost no one in the organization thinks about the program staff's tacit knowledge, the communications archive, the decision log, the voice guide, or the stories trapped in the field officer's head — the informational half — with the same seriousness. When I have sat with nonprofit leaders, the revelation has almost always been the informational side: wait, all of that is intelligence, and we have none of it gathered?

Churches, like Joelle's, have usually thought about neither half as explicit systems. Pastors think about people — they have to. Pastors also think about the content of their teaching. But almost no pastor I have met has thought of the congregation as a relational graph that could be mapped and stewarded at scale, and almost none have thought of the church's own teaching, decisions, formation pathways, and theological positions as an informational layer that could be integrated. The church, as an institution, tends to carry both intelligences in the personal memory of the pastor. This is part of why the pastor tends toward burnout.

Institutions, like Elias's seminary, have usually thought about the formal layer of informational intelligence — the research, the curricula, the credentialing documents — but not the tacit layer, and they have usually had a formal layer of relational intelligence — the alumni database, the major-gift list — that is wildly under-integrated with anything else. Cross-entity institutions (denominations, multi-campus seminaries, multi-site networks) pay the fragmentation tax in a compounded form: multiple fragmented informational systems that do not talk to each other, sitting alongside multiple fragmented relational systems that do not talk to each other, with the seam between them almost entirely absent.

The four shapes are different. The underlying structural condition is the same.

Almost every organization has thought about one half and not the other. And — this is the part that matters — almost every organization, having thought about one half and not the other, has also not thought about either half in its full scope.

The scope is the next thing.

The ten categories of informational intelligence

If you opened up your organization and laid out every piece of structured-or-unstructured information it carries, you would find at least ten overlapping categories. Almost every organization I have worked with has all ten. Almost none have them integrated.

I want to walk them through Maggie, because Maggie has all ten and because walking them one by one is the only way to see that the first category — the one almost every leader defaults to when they hear the word information — is less than a tenth of the actual picture.

Documented knowledge is what Maggie reaches for first when asked what she has. The six books. The published articles. The white papers. The formal training manuals she has produced for the fellowship. The curricula. The official, citable output. It is the only category most leaders have written down deliberately, which is part of why its fragmentation across publishers and platforms is the most visible part of the problem. It is also not, by a long shot, the largest or most load-bearing part.

Tacit knowledge is larger and more load-bearing. It is the set of mental models, instincts, heuristics, and half-formed frameworks that live in Maggie's head and show up in conversation and have never been written down. It is the how she thinks about this that makes her Maggie. Almost everything she teaches in a private coaching relationship falls into this category and has never touched paper. If Maggie dies tomorrow, this is the category that dies with her. It is also the category most likely to be mis-approximated by AI systems trained on the public corpus, because the public corpus is ten percent of what she actually knows.

Operational data is the structured numerical record of what has actually happened. For Maggie, this is book sales by title by quarter, podcast downloads by episode, speaking engagement fees, fellowship application and completion data, Substack open rates, YouTube watch time. The data exists. It exists in eleven different dashboards. No one, including Maggie, can easily ask what is our healthiest channel relative to cost, over the last three years, across all categories of audience? because the numbers live in systems that do not reconcile.

Communications archive is the conversational record of how things actually got decided. Emails. Text threads. Voice memos. Slack messages. Meeting notes, when they were taken. For Maggie, who runs lean, the archive is mostly her email — which has, incidentally, three-quarters of the key reasoning behind every public-facing thing she has done in the last fifteen years. None of it is retrievable at the level of show me every conversation we had about the framework revision in 2018.

Voice, style, and identity is the rhetorical fingerprint. The specific moves Maggie makes in her sentences. The words she uses and the ones she carefully does not. The rhythm of her paragraphs. The particular way she structures an argument. For most leaders this is invisible to them because it is the water they swim in. It is also the thing an AI system most consistently fails to reproduce without an integrated voice foundation, because the voice is not in any single book; it is in the pattern across books, talks, emails, and off-hand remarks.

Decisions and precedent is governance memory. Why was the 2017 partnership with the publisher ended? Why did the fellowship curriculum change in 2019? Why did Maggie turn down the major foundation in 2021 that everyone assumed she would accept? Each of those decisions has a reason, and each reason was load-bearing at the time, and almost none of the reasons are written down. When the same kind of decision presents itself again, the organization relitigates from scratch — or, worse, makes a contradictory decision because no one remembers the old one.

Stories and narrative is the working memory of mission. The testimonies. The case studies. The founding stories. The apocryphal-but-load-bearing anecdotes that get told at staff retreats and fundraising dinners and recruiting calls. For a movement leader, this category is the entire engine of connection to new audiences. It is also almost always scattered — some on the About page, some in the back of a book, some in an old talk, some only in the memory of the staff member who was there.

Media artifacts is the talks, the podcast episodes, the video, the photography. For Maggie, this is four hundred hours of recorded content across six platforms. Not one minute of it is transcribed and tagged in an integrated way. The single most engaging thing she has ever said, on stage in 2019 in front of a room of three hundred people, exists as a seventy-two-minute YouTube video with fourteen hundred views and no transcript.

Procedural knowledge is how things actually get done. The unwritten workflow by which a major-gift conversation moves from first contact to signed pledge. The unwritten process by which a fellowship cohort gets selected. The unwritten sequence that Maggie follows every October to plan the next year. For Maggie, these live as habit. For the successor, they will live as hard-won reconstruction unless they are gathered now.

Theological, philosophical, or ethical foundations is the conceptual ground. For a mission-driven leader, this is the bedrock. What does Maggie actually believe about the nature of the work, the purpose of the mission, the ethical commitments that cannot be bent? Her books articulate this, but not in one place, and not canonically, and without noting the places where her thinking has evolved over thirty-two years. The foundation is real. The foundational document does not exist.

Ten categories. One person's intelligence, scattered across at least that many surfaces and probably more.

This is what informational intelligence actually is. Not content. Not documentation. All of it.

The ten categories of relational intelligence

I want to walk the relational half through Wes, because Wes is a professional whose entire job is one slice of relational intelligence, and because his example will make clear how much of it lives outside even the most conscientious CRM.

Donor and funder relationships. This is the slice Wes has been professionally trained on. Dean, and the three hundred other donors in the mid-tier pool, and the eighty major donors, and the forty foundation officers. For each of them, in theory, a giving history, a relationship history, a set of stated and unstated motivations, an open-commitments record. In practice: the giving history is in the CRM; the relationship history is in Wes's head and his email; the motivations are known only to whoever last had the conversation; the open commitments are tracked inconsistently. Even this one slice, the one slice Wes is supposed to have integrated, is not integrated.

Staff and internal relationships. The team itself. Who reports to whom on the org chart, and — far more important — who is actually being formed by whom. The apprenticeship lines. The coalitions. The dynamics. The unspoken hierarchies. For Wes's nonprofit, the ED knows some of this. The HR lead knows some. Most of it is not written anywhere, and most of it will be invisible to a successor for two years after taking the seat.

Network and peer relationships. The other organizations and leaders with whom there is mutual trust, occasional collaboration, shared field. For Maggie, this is the forty peer thinkers who make her work land. For Wes, this is the other nonprofits in the sector he has partnered with, competed with, or learned from. For Joelle, this is the pastoral peer group. For Elias, this is the sibling institutions. None of it is a queryable asset. All of it is in individual memory.

Endorser and influence relationships. The voices who have publicly stood behind the work — blurbs on the back of books, forewords, podcast hosts who have featured the leader, conference platforms that have handed over the main stage, social media accounts that have amplified. For a movement leader, this is reputation capital built up over decades. For most leaders, it is a list that nobody has ever actually made.

Client, beneficiary, audience, or congregational relationships. The people the organization actually serves. For a nonprofit, program participants. For a church, congregants. For a seminary, students. For a movement leader, the readers and fellowship alumni. This is usually the largest relationship by count and the most weakly tracked relationship by depth. Joelle's church has seven hundred members. The church's record of relationship with those seven hundred consists, functionally, of their giving history, their participation in one or two programs, and whatever the pastor and the elders happen to remember.

Vendor and partner relationships. Production partners, technology providers, consultants, agencies. The operational supply chain that carries the work. Often dismissed as "not relational," but it is — ask any leader who has been through a bad vendor exit what it costs to lose the intelligence the vendor was carrying about how the organization operates.

Board and governance relationships. The fiduciary leadership. The history of board service. The tenure patterns. The personalities and dynamics that shape every strategic decision. Wes knows his current board. He knows very little about the twenty-six board members who preceded them over the organization's history, including the ones who are still alive and still connected to the mission.

Alumni and former-staff relationships. The diaspora. Former employees, former board members, former program graduates, former cohort members. Often the highest-leverage and least-managed category in any organization. For Maggie's fellowship, this is one hundred and seventy alumni across fourteen cohorts, most of whom are now running programs, pastoring churches, leading organizations, writing books. She is in informal touch with maybe thirty of them. The other one hundred and forty are functionally a field she once planted and cannot now see.

Generational and inheritance relationships. The emerging leaders being prepared to carry the work forward. The mentorship lines, explicit and implicit. The succession question at every scale. For Maggie, this is the presumed successor whom she has been quietly mentoring for four years. For Joelle, this is the assistant pastor she is probably going to recommend at the end of her sabbatical. For Elias, this is the three next-generation faculty who will carry the seminary forward, and the eleven regional formation partners who will do the same in the field. In each case, the inheritance is happening informally, in the head of the mentor, with no shared map of what is being transmitted.

Public and audience relationships. The diffuse outer ring. Readers who have never written in. Social followers. Podcast listeners. Conference attendees who took a photograph but never introduced themselves. The relationship is real, though mostly one-directional. It is also the category most often confused with "marketing," and therefore most often handed to a function that is structurally unequipped to carry a relationship.

Underneath all ten of these categories, and rarely captured anywhere, sits a deeper layer of relational intelligence that is the real thing being lost when relational fragmentation compounds. The history of interactions — what we have actually said and done with each other. The trust capital — what we can ask of each other and what we cannot. The mutual obligations — what each of us owes the other. The cultural fit — how this person needs to be approached, what they care about, what offends them. The second-order graph — who knows whom, who introduced whom, who could open which door.

This is the intelligence that allows an experienced leader to walk into a room and immediately know who needs to be thanked, who needs to be asked, who needs to be deferred to, and who needs to be quietly avoided. It is enormous. It is real. It is one of the most valuable assets the organization holds.

And in almost every organization, it lives entirely in the heads of three to five senior people. When they leave, or when they simply have a busy quarter, the organization functionally loses access to it.

Both fragment the same way

I want to resist the urge to list the signs of fragmentation in both spheres, because you already know what they look like from Chapter 1 and the Preface, and because the interesting observation is not the specific signs but the structural symmetry.

Informational fragmentation and relational fragmentation are the same condition expressed in two different registers.

In both cases, the intelligence exists.

In both cases, it exists in multiple surfaces that do not talk to each other.

In both cases, it is partially captured in systems — a CRM for relationships, a file share for documents — and those systems capture a small fraction of the actual intelligence, and the fraction they capture is shallow.

In both cases, the deepest and most valuable intelligence is tacit — the why behind a decision, the history behind a relationship — and the tacit layer is almost never captured anywhere.

In both cases, the intelligence is carried, for the organization's most load-bearing questions, in the personal memory of a small number of senior people.

In both cases, when those people leave, or retire, or burn out, the intelligence leaves with them.

In both cases, the conventional response is to buy a tool or hire a junior person to "document things," and in both cases that response treats a structural condition as a discipline problem, and in both cases it fails.

And in both cases — this is the part that matters for the rest of the book — the path out is the same. Integrate. Activate. Form. Multiply. The path is the six-stage trajectory that Chapter 5 will map, and the first stage of it (integration) is the stage that has to be worked on both sides simultaneously.

Which brings me to the seam.

The seam where formation happens

I said at the top of the chapter that the two halves have to be integrated together because formation happens at the seam between them and the seam does not exist when only one side has been built.

I want to land that claim now, because it is the reason this chapter exists and the reason Part IV of this book exists.

Consider Joelle.

Joelle's vocation is formation. Not information transfer. Not relationship management. Formation — the long, patient, embodied work of shaping people over time.

Suppose Joelle comes back from sabbatical and decides to address the fragmentation of her church's informational intelligence only. She and the staff run a four-week build that produces a beautiful formation library. Sermons catalogued and cross-referenced. A clear articulation of the church's theology of formation, stated canonically in one document. Pathways written out — a first-year pathway, a second-year pathway, a discipleship pathway, a leadership pathway. Every sermon tagged to the pathway step it supports. A style guide. A decision log. All ten categories gathered.

She will have built a remarkable informational layer.

It will not produce the formation she wants.

Formation does not happen in the encounter between a person and a library. Formation happens in the encounter between a person and a relationship that is itself carrying an integrated library. The congregant in the forty-seventh month does not need the pathway handed to her. She needs a pastor, a small-group leader, a mentor, a friend-in-the-faith who can see her in the forty-seventh month — who knows where she has been, who knows what the church has already offered her, who knows what the specific step is that she needs next — and who can walk with her into it.

That kind of seeing requires the relational foundation.

Now suppose, alternatively, Joelle decides to address the fragmentation of the church's relational intelligence only. She and the staff run a four-week build that produces a beautiful pastoral care system. Every member mapped. Every small group membership tracked. Every pastoral conversation logged. Apprenticeship lines charted. The implicit knowledge living in Joelle's head made legible to her staff and her successors.

She will have built a remarkable relational foundation.

It will also not produce the formation she wants.

The pastor, the small-group leader, the mentor, the friend-in-the-faith need something to walk the person into. If the church's informational intelligence — its theology, its pathways, its sermons, its decisions, its voice — has not been integrated, then the pastoral relationship, however well-mapped, has no coherent content to carry. It devolves into generic pastoral care, which is valuable, but is not the formation-over-time that Joelle's theology names as the church's vocation.

Formation requires both halves, integrated, working together. The library, carried by the relationship. The relationship, carrying a coherent library. Neither half is sufficient. And — this is why the seam matters — they cannot be sequenced one after the other. Informational integration built without a parallel relational integration produces a beautiful resource nobody walks through. Relational integration built without a parallel informational integration produces a beautiful graph carrying incoherent content. They have to be worked as a pair from the first week, because the seam is the whole point.

This is the claim Chapter 13 will make at full length, once the trajectory has unfolded enough to support it. For now, hold it as a header over Part III of this book: both halves, together, from the beginning — or the foundation that gets built will not be the foundation you needed.

Elias, because scale matters

I want to close this chapter with Elias, because Elias's situation shows what happens when an organization tries to address one half at a time at scale, and it is not a cautionary tale I am inventing; it is a pattern I have watched play out at five institutions in the last three years.

Elias's seminary has, in the last six years, invested roughly two million dollars in a series of initiatives that were almost all addressing one half of the intelligence problem at a time.

A document management overhaul in 2020 — informational, partial. A CRM migration for advancement in 2021 — relational, partial. A learning management system replacement in 2022 — informational, partial. An alumni engagement platform in 2023 — relational, partial. A new content strategy consulting engagement in 2024 — informational, partial. An AI chatbot pilot in 2025 — which, because it was grounded in none of the above, produced the fluent misrepresentation that led to the board member's question and Elias's eleven-day reassembly project.

Each initiative was defensible. Each was led by a capable senior leader. Each delivered some value. And collectively they have left the institution approximately where it started, because none of them addressed the structural condition — the absence of an integrated foundation carrying both intelligences — that every one of them was, in different vocabulary, a symptom of.

The institution did not need six initiatives. It needed one integration. The one integration would have taken longer than any of the six, would have been less impressive at every quarterly board meeting, and would have produced, at the end, a foundation on which every subsequent tool could have been built meaningfully. That is the work Elias is about to begin, and the reason he is about to begin it is that the eighteen-month accreditation horizon has finally made the structural condition more expensive to ignore than to address.

Most institutions reach the point Elias has reached. Most of them reach it later than they needed to.

I do not want you to reach it later than you need to.

The invitation

I am not going to ask you to list, right now, the full ten-by-ten inventory of your own organization's intelligence. That is a week of work, not a page.

I am going to ask you to do something smaller.

Take a single piece of paper. Draw a line down the middle. At the top of the left half write what we know. At the top of the right half write whom we are connected to.

In the left half, write the five most load-bearing pieces of informational intelligence your organization carries — the frameworks, the decisions, the stories, the voice, the theology, the SOPs that matter most to what you actually do. Next to each, write where it currently lives. Not where it should live. Where it lives now.

In the right half, write the ten most load-bearing relationships your organization carries — the donors, the peers, the mentors, the emerging leaders, the partners. Next to each, write where the intelligence about that relationship currently lives. Not where it should live. Where it lives now.

If you do this honestly, you will notice three things.

The first is that the left half is larger than you expected. Most of what your organization runs on is not documented. You have been underestimating the informational side because the visible layer — the books, the reports, the published work — is a small fraction of the whole.

The second is that the right half is a graph, and you have never drawn it as a graph. Most of the relationships on the right side interact with other relationships on the right side — donors who know peers, alumni who know board members, endorsers who know emerging leaders. You have never mapped those second-order connections because your CRM does not ask you to.

The third is that in both halves, the answer to where does it currently live is, overwhelmingly, in the head of a particular person — usually the leader, or one of two or three senior staff.

That third observation is the thing I want you to sit with before Chapter 3.

The two intelligences are real. They are distinct. They are both load-bearing. They are both fragmented. And for almost every organization I have worked with, the primary foundation on which both intelligences currently rest is the mortal memory of two or three senior people.

We are not going to stay there.

But before we can leave, we have to name it.

The foundation you currently have is not a system. It is a person.

Turn the page.