The meeting debt problem

Technical debt has a good PR team. It's in every engineering post-mortem, every sprint planning session, every architecture review. Engineers understand intuitively what happens when shortcuts compound.

Meeting debt doesn't have anyone advocating for it. But it compounds just as fast.

### What meeting debt is

Meeting debt is the gap between decisions that were made in meetings and decisions that were recorded somewhere durable. Every meeting that ends with unclear action items, every whiteboard that gets erased before anyone documents it, every "we decided this in Q2" that nobody can prove adds to the pile.

Like technical debt, meeting debt is often invisible in the short term. The team that lost the Q2 pricing decision will re-litigate it in Q3. The team that didn't write down the architectural trade-off will have the same debate six months later when the consequences arrive. The action item that died in the action item graveyard will reappear in the next planning session as a new "discovery."

The cost is hard to see because it shows up as wasted time in future meetings, not as a visible deficit today.

### How to measure yours

There's a rough diagnostic I use. Ask yourself these questions about your last ten meetings:

1. Can you name the three most important decisions from each meeting?
2. Do you know who owns the top action item from each meeting?
3. Are any of those action items visible right now in the system where your team actually tracks work?

If you answered yes to all three for every meeting: your meeting debt is low.

If you answered yes to some but not others: you're accumulating. The debt is manageable but growing.

If you can't answer the first question reliably: you're in a debt spiral. Each meeting is expensive, but you're not retaining the value.

### The compounding mechanism

Meeting debt compounds because lost decisions create more meetings.

A decision that gets properly recorded and connected to work is done. It might be revised later, but it has a clear history. Anyone can look it up.

A decision that gets lost comes back as a question. "Wait, what did we decide about the pricing model?" That question becomes a Slack thread. The Slack thread turns into a sync call. The sync call reconstructs the original decision — or makes a different one, because the context is gone — and produces another decision that might also not get recorded.

I've watched teams have the same architectural argument three times in twelve months because nobody wrote down the outcome of the first discussion. Each instance cost 2–3 hours of senior engineering time. The original decision probably took 45 minutes. The decision was free. The forgetting cost 6+ hours.

### The interest rate on meeting debt

Here's a rough model: every unrecorded decision creates a ~15% chance of being re-litigated within 90 days. For a team that makes 20 meaningful decisions per week in meetings, and captures 50% of them, that's 10 lost decisions per week, 1.5 of which come back as re-litigation within 90 days.

1.5 re-litigations per week doesn't sound catastrophic. But each re-litigation costs the original decision time plus the cost of the re-litigation plus the coordination overhead of figuring out what was previously decided. At senior team rates, you're looking at 2–4 hours of loaded cost per re-litigation.

3–6 hours per week of senior time, every week, from failing to record decisions. That's the interest on meeting debt.

### How to stop accruing

The fix isn't better meeting hygiene, though that helps. The fix is making the output of meetings cheaper to capture so that capture actually happens.

If capturing a decision requires a dedicated note-taker, a post-meeting transcript review, and 30 minutes of Notion editing — it won't happen consistently. If it requires pointing your phone at the board for 10 seconds — it will.

BoardSnap exists because the gap between "we made a decision" and "that decision is somewhere findable" is the source of a real, compounding, measurable cost. Close the gap before you leave the room.