Buttresses

I was three days into an engagement, sitting with a printed month of the leadership team's calendar, when I found it.

A ninety-minute session on Tuesday. A forty-five-minute session on Monday whose stated purpose was to prepare for Tuesday. And a thirty-minute readout on Thursday, to summarize both for the people who had not been in either.

Two and a half hours a week, eleven people, and not one minute of it touched a customer, a product, or a commitment the organization had made to anyone outside the building.

So I asked the obvious question. Why does the Monday session exist?

The answer came back quickly, and it was entirely reasonable. Two years earlier, the Tuesday meeting kept ending without a decision. Someone suggested that if the material were socialized in advance, Tuesday would move faster.

Then I asked the second question. Does Tuesday end with a decision now?

Nobody was sure.

What a Buttress Is

In architecture, a buttress is added after the fact. The wall was designed to stand on its own. It did not. So a support was built against it, and the building stayed up.

Organizations do the same thing with process. A handoff fails, so someone adds a sync. The sync generates confusion, so someone adds a pre-brief. Now two commitments exist that produce no decision on their own, so someone adds a readout to catch everyone else up. Three items are on the calendar every week, and every one of them exists to hold up another one.

That is the part worth sitting with. Every one of those additions was a reasonable local decision made by a capable person trying to solve a real problem. Nobody ever proposed a meeting to support a meeting. They proposed a fix. The fix stayed. The crack it was covering was never repaired, because repairing it was slower, harder, and more political than adding thirty minutes to a calendar.

Why This Is Debt, Not Overhead

Overhead is the standing cost of running an organization. Debt is a cost you accepted in order to avoid harder work, and it accrues interest until someone pays down the principal. Buttresses are debt, and they behave the way debt behaves.

They begin as shortcuts. The crack was a broken interface, an unclear owner, or a decision right that nobody actually held. Repairing that requires a conversation about authority. Adding a recurring meeting requires ninety seconds and a calendar invite.

The interest is paid in the most expensive currency the organization has. Not dollars. Senior attention, calendar space, and the cognitive switching cost borne by the people you most need thinking clearly. This is the attention tax in one of its purest forms, and it is charged weekly, forever, against a debt nobody has on a ledger.

The principal is never retired. There is no owner, no backlog, no review date. Nothing in the operating rhythm ever asks whether the support is still holding anything up.

And then the part most leaders miss: given enough time, they become load bearing. Real work starts routing through the buttress. Information that should move through the formal structure now travels only through the patch. Pull it out abruptly and something genuinely does fall over, which everyone then reads as proof that it was necessary all along.

A buttress is the organization admitting a structural failure in a way that never requires anyone to name it.

How to Recognize One

Buttresses are never labeled as such. They are labeled sync, alignment, prep, readout, touchpoint, working session, status roll-up, reconciliation. The label tells you nothing. The signatures do.

The first signature is that the only consumer is another process. The output of the meeting is an input to a different meeting. Nothing external sits downstream of it.

The second is that no decision rights live inside it. Everyone in the room can describe the problem accurately. Nobody in the room can resolve it.

The third is that nobody can name the original failure. Ask why it started. If the answer is that it has always been on the calendar, or that it came out of the reorg, you have found a patch that outlived its crack.

The fourth is that it exists to reconcile two things that should already agree. Two systems of record, two trackers, two versions of the plan. The recurring reconciliation is the buttress. The disagreement is the crack.

The fifth is that it was created after an incident. Post-incident processes are the most common origin and the least reviewed, because removing one feels like inviting the incident back.

The sixth is that it has grown a support structure of its own. Someone now spends hours preparing for it. That preparation is a second buttress, bracing the first.

The Authority Underneath

Buttresses look like an Attention problem, because Attention is where the bill arrives. They are usually an Authority problem, because Authority is where they are manufactured.

Look underneath almost any long-standing support and you find the same thing: a decision that nobody is empowered to make alone. The alignment meeting exists because two leaders each hold half a decision. The pre-brief exists because a decision maker will not decide without prior socialization. The reconciliation report exists because two functions each believe they own the number.

In every one of those cases, the organization responded to an unassigned decision right by building a forum around it. Which is why cancelling the forum almost never works. The decision still has to happen somewhere, so the meeting reappears within a quarter under a different name, and everyone concludes that the meeting was necessary after all.

It was not necessary. It was compensating. Knowledge accumulates at the front of the organization and authority accumulates at the top, and the buttress is the scaffolding people build across that gap so the work can keep moving. It is evidence of competence, not incompetence. It is also expensive, and it is telling you exactly where to look.

Count the supports and you have found the cracks, without interviewing a single person.

The Buttress Audit

Take one month of recurring meetings, recurring reports, and standing trackers. For each one, answer four questions in writing. In writing matters. Spoken answers stay comfortably vague.

What specifically breaks if this stops next week? Who consumes the output, and what decision does it change? What was the original failure that created it? Is that failure still present?

Most items answer the first question with some version of uncertainty and the third with silence. Those are your candidates.

The pairing of the last two questions is where the real diagnosis happens. If the original failure is gone, the buttress is pure debt and can be retired outright. If the original failure is still present, you have learned something more valuable than a free hour on the calendar. You have located an unrepaired crack in the structure and confirmed that you have been paying rent on it, in some organizations for years.

The Decommission Test

Do not pull out something that has become load bearing without first checking the load.

Suspend it for thirty days rather than cancelling it. Before the suspension begins, write down the specific failure you expect to see if the support was genuinely necessary. Then watch for that failure, and only that failure.

Discomfort is guaranteed and proves nothing. People will feel less informed for two weeks whether or not the meeting mattered. The question is narrower and more honest. Does a commitment slip. Does a decision stall. Does a defect reach a customer. If none of that happens in thirty days, you have your answer in evidence rather than in argument, and the argument was never going to end on its own.

Three Honest Dispositions

Every candidate ends in one of three places. There is a fourth option, which is to look at it, feel uneasy, and leave it running. That option is how the debt accumulated in the first place.

Retire it. The crack is closed, or it was never real. Cancel it, and say publicly why, so the same patch does not return under a new name in six weeks. Then claim the reclaimed hours deliberately, because an unclaimed hour refills on its own.

Repair the crack, then retire it. This is the expensive option and usually the correct one. If a weekly reconciliation exists because two teams maintain conflicting data, the fix is one system of record, not a better meeting. If a pre-brief exists because a decision maker will not decide without socialization, the fix is a named decision right, not a calendar block. Assign the repair to an owner with a date, or it will not happen.

Promote it to real structure. Sometimes the support is doing necessary work that the original design failed to account for. If so, stop treating it as a patch. Give it an owner, a stated purpose, a defined output, and a formal place in the operating rhythm. A buttress that gets promoted becomes a wall. A buttress that stays informal stays debt.

Three habits keep the debt from re-accumulating. Attach an expiration date to every new recurring commitment, ninety days by default, where renewal requires someone to state what would break without it. Record the crack and not just the fix, in one written sentence, because that sentence is what makes repair possible a year later. And review buttress density once a year at the executive level, not to cut meetings, but to read the map.

How a Builder Reads a Support

Buttresses accumulate in every organization that has ever solved a problem quickly. That is not a character flaw. It is physics. An organization under pressure will always brace before it rebuilds.

The discipline is not in avoiding them. It is in scheduling their removal. Builders do one thing differently from managers here: when they add a support, they write down the crack it is covering and the date they will come back to repair it. That single habit is most of the difference between an organization that patches and an organization that builds.

The cathedral builders understood something worth borrowing. A flying buttress is not a failure. It is an honest structural answer to a load the wall could not carry alone, designed on purpose, carved, maintained, and visible from the street. What organizations build instead is the unnamed version: unowned, undocumented, and quietly load bearing.

Open your calendar this week and find the meeting that exists to support another meeting. Ask what wall it is holding up. Then ask whether anyone has looked at that wall in a year.

Do not remove the support until you have found the crack, and do not leave the crack unrepaired because the support is holding.