Standalone Essays · Leadership

The David Problem: Why the Groups That Need You Most Will Eventually Let You Go

I’ve rebuilt failing organizations five times. A church on the verge of closing its doors. A school. A construction crew that was behind schedule, over budget, and hemorrhaging morale. A dojo. Then another church. In each case, I was brought in because things were broken, and in each case I got them turned around and growing.

And in each case, once the crisis was over, they chose someone else to lead them forward.

What’s bizarre is what happened next. Every single time the new leader crashed and burned, and the group collapsed. Every…single…time.

I’ve spent a long time trying to understand that pattern. Part of the answer, I eventually realized, is that I’m autistic — and while that gives me certain architectural abilities that are genuinely useful in a crisis, the social maintenance phase is where the friction accumulates. But the more I examined the wreckage, the more I realized the problem wasn’t just me. It was something structural. Something almost archetypal. Something that has been repeating itself for as long as human beings have organized into groups.

It looks like this: the people who call you in when the walls are falling don’t necessarily want you around once the walls are standing.

David, Solomon, and the Three-Generation Decay

The oldest version of this story I know is in the Hebrew scriptures.

David was the warrior king — combat-tested, driven by necessity, focused on survival and unity. He built the mechanics of the kingdom because without it, everyone was going to die or go broke. Solomon inherited a functional system and led Israel into its golden age: trade, prosperity, the great temple. The system reached its peak. But the friction that had made David’s brutal logic necessary was largely forgotten. And then Solomon’s son Rehoboam inherited the throne, promptly threatened to increase taxes and rule as a tyrant, and split the kingdom in two. Israel never quite recovered.

Notice that the throne was always called David’s throne, even through Solomon’s golden age. The founder’s logic was the load-bearing structure, even when no one was thinking about it anymore.

This is the Three-Generation Decay, and it haunts almost every reconstruction effort:

The David (The Architect): Driven by necessity, combat-tested. Builds the mechanics of survival because the alternative is collapse. Their primary virtue is fortitude — the willingness to do what needs doing without applause. Their hidden risk is making themselves too essential: building a system that runs on their specific internal logic without teaching anyone else how the logic works.

The Solomon (The Optimizer): Inherits a functional system and focuses on growth and refinement. The system reaches its high point under Solomon, but the memory of the struggle that built the walls begins to fade. Their virtue is prudence. Their risk is forgetting that the foundation was poured in harder times, and that the principles behind it are not optional decoration.

The Rehoboam (The Successor): Inherits the power but not the character. Sees the system as a vehicle for personal advancement rather than a service to the group. Trades the future for short-term praise and comfort. The walls don’t fall immediately — they were built well — but the neglect is compounding quietly until it isn’t quiet anymore.

What I Built, and Why It Kept Collapsing After I Left

My repeated experience in leadership is a micro-version of this cycle. I would build an efficient system, but the person who took over didn’t understand that the system only worked because of the underlying character driving it. The ethics weren’t decoration. They were structural.

When the new leader stopped serving the people — because they wanted to “do it their way” or simply be liked — they were quietly removing the keystones. And when it inevitably failed, they blamed the previous leader or the system, rather than their own lack of stewardship.

This is not unique to me. It is the Rehoboam risk in any reconstruction effort.

No set of rules can guarantee integrity. Character and virtue cannot be legislated. A leader who genuinely serves their community understands that justice has to apply even against themselves — that financial integrity isn’t negotiable, that the vulnerable don’t get sacrificed for convenience. They protect those at the margins not because it’s politically advantageous but because a community that abandons its weakest members has already started rotting from the inside. They practice the kind of self-discipline that establishes their own credibility before they demand anything from others. They understand that how they speak — whether they tell the truth, whether they create conflict or resolve it — is not a soft concern but a governance issue. And they treat the maintenance of the physical and relational environment as a form of stewardship, not someone else’s job.

When those qualities are present, the system hums. When they erode, the system fails — and it fails from the inside, invisibly, long before the collapse becomes visible.

The church people thought: “If we just sing three songs and say a few nice things, we’ve had church.” They liked the social programs, but nobody wanted to do the background work once I left. They had inherited the form and discarded the function.

The key to longevity is systematically teaching the why — not just the rules, but the reasoning behind the rules. Because the leader is not above the rules. The leader, as the chief enforcer, must become the rules. They are the avatar the group looks at to understand what the values actually look like in practice. If the avatar contradicts the values, the values are dead, regardless of what the mission statement says.

How to Know Which Leader You’re Hiring

If the David/Solomon/Rehoboam framework is useful, it should be practically applicable. A community in the process of selecting or evaluating a leader should ask which of these archetypes they are actually hiring — because the answer determines what they should expect.

The David is the crisis leader — focused on security and character, driven by fortitude, and whose primary risk is making themselves so essential that no one else learns how the system works. The Solomon is the optimizer — focused on economy and growth, guided by prudence, and whose risk is forgetting the struggle that poured the foundation. The Rehoboam is the one you didn’t see coming: focused on ego and power, carrying no real virtue, trading the community’s future for short-term personal praise or profit.

A community that is in crisis needs a David. A community that is stable and growing needs a Solomon. What no community ever needs is a Rehoboam — but Rehoboams are disproportionately good at presenting themselves as one of the other two.

Which is why the vetting process matters.

The Vetting Battery

Instead of a standard interview, a community evaluating a potential leader should look for evidence — not promises. Character leaves tracks. Here are the questions worth asking:

The Momentum Check: Does the leader create their own energy, or do they wait for the group to motivate them? A David does not require an audience to do the work.

The Brand Check: Do they respect the office of leadership enough to maintain personal and professional discipline? How they carry themselves when no one is watching is the data point that matters.

The Wisdom Check: A leader who talks too much is usually a Solomon at best, and a Rehoboam at worst. Silence is a leadership skill.

The Solution Check: Can they point to a concrete “See It, Say It, Solve It” history? Not a plan. An actual result, with mud and blood on it.

The Why Check: Can they explain how the work they’re asking people to do connects to something larger than the organization’s immediate self-interest? If the answer is “because I said so” or “because that’s how we do it,” you have a Rehoboam.

The Discipline Check: Do they demand more of themselves than of their subordinates? The leader eats last — not as a performance, but as a principle.

The Succession Check: This is the kill switch. If the leader is not actively identifying and developing their replacement, they are disqualified from leading any reconstruction effort. A leader who makes themselves irreplaceable is building a trap.

Institutionalizing the Maintenance

My specific frustration, looking back across those five groups, is that the work I was doing in the background was invisible to the people benefiting from it. And invisible work doesn’t get replicated. It just stops.

The solution to this is what I call the Liturgy of the Mundane: the leader must take the background work and make it a visible, communal ritual. If the maintenance happens in secret, the group forgets why things are clean and functional. When they forget, they stop valuing it. When they stop valuing it, they stop doing it. And eventually they hire a Rehoboam who promises them something more exciting than maintenance, which is most things.

The corollary to this is what I call the Toxic Guard. A reconstruction leader’s primary job — arguably more important than any operational task — is to identify toxic personalities before they gain traction, and remove them before they can corrupt the character of the group. The Mocker (who ridicules the mud and blood logic that built the system) and the Zealot (who wants to weaponize the system for purity enforcement) are the two most destructive archetypes in any community, and both of them are charming at the point of entry.

The Founder’s Handover Manual

If I were to formalize the single most useful thing an Architect can do before leaving a group, it would be this: write the Founder’s Handover Manual.

Not a policy document. Not an org chart. A letter to the community that says, in plain language: I built this system. Here is why it works. The principles behind it are not suggestions — they are load-bearing. If your next leader starts substituting performance for substance, or begins playing people against each other to protect their position, the system will fail. Here is exactly what that will look like, and here is what you, as a community, are authorized to do about it.

That document serves as an early warning system — a way of codifying the transition before the Rehoboam arrives, rather than after.

The Rehoboam Red Flags: A Community Oversight Guide

When the Architect leaves, the community should watch for four specific behavioral shifts. If these appear, the character pillar is failing.

1. The Shift From Service to Spoils. The David standard is that the leader is the avatar of the rules and eats last. The red flag is when the new leader begins enriching themselves or their inner circle while the people doing the actual work are neglected. Legitimacy is being traded for luxury.

2. The Chaos of Dispersed Authority. The David standard is a clear chain of command where the leader backs their people in public. The red flag is when the leader begins playing divide and conquer among the team — overlapping roles, secret instructions, internal discord manufactured to ensure no one is strong enough to challenge the leader’s ego. This is the fracture that precedes the collapse.

3. Centralized Incompetence and Mission Creep. The David standard is that the leader builds a charactocracy — a culture where authority flows to those who demonstrate competence and character, not those who perform loyalty. The red flag is when the leader begins running everything themselves out of a stated “lack of trust,” and starts taking on vanity projects unrelated to the core mission because they want the approval of a new audience.

4. The Bombastic Announcement Trap. The David standard is that the leader speaks only to reveal a real problem or improve on silence. The red flag is when the leader is spending more time on the performance than on the background work — prioritizing being liked over being trustworthy.

When the Red Flags Appear

If these patterns emerge, the community has three tools:

Go Still and Quiet. Do not validate the leader’s moral theater. Applause is fuel. Withhold it.

Refuse the Binary Trap. When the leader says “You’re either with me or against me,” the community answers: “We are with the principles this community was built on. You have departed from them.”

Exile the Mocker. If the leader ridicules the mud and blood logic that built the system — the hard, unglamorous work that made the community worth belonging to — they must be removed. The friction and conflict that follows a toxic leader dissipates remarkably quickly once they are gone. This is itself diagnostic: if the conflict disappears when a person leaves, the conflict was never about the issues. It was about the person.

A Final Note

I am, by temperament and neurology, a David. I do not say that with uncomplicated pride. It means I am most useful in conditions that no one wants to be in, and I am apparently easiest to let go of once those conditions improve. There is something clarifying about understanding that, even if it is not entirely comfortable.

But the framework is not really about me. It is about the pattern — the Three-Generation Decay that repeats itself in churches, companies, crews, dojos, and kingdoms. The question worth sitting with is not just “which archetype is our current leader?” but “have we built a community that can recognize the difference, and do something about it before it’s too late?”

The answer to that question is almost always: not yet. But it can be.