Your team had a meeting last week. You discussed the same question you discussed last month. And three months before that.
No one remembered what was decided. So you decided again.
This is decision debt, and it's costing your team 8 hours a week.
The Recurring Meeting Problem
Some meetings are necessary. Some are even valuable. But many exist only because decisions weren't documented.
"Didn't We Already Decide This?"
- Topic discussed 3 months ago
- Decision was made (probably)
- No one remembers exactly
- Meeting to re-decide
"Let's Get Everyone Aligned"
- Decision made by one team
- Other teams weren't informed
- Now there's confusion
- Meeting to re-align
"Can Someone Explain?"
- New team member needs context
- Documentation outdated/missing
- Senior engineers explain again
- Meeting to transfer knowledge
"Why Does This Work This Way?"
- System behaves unexpectedly
- No one knows why
- Investigative meeting
- Reverse-engineer decisions
The Math
McKinsey found employees spend 20% of their time searching for information or finding colleagues who can help.
The Real Cost (20-person team)
Information Search Cost
20% of time finding information or colleagues
Meeting Cost from Failed Searches
Each failure triggers a 30-min meeting with 4 people
The Decision Debt Loop
Undocumented decisions create a self-reinforcing cycle:
The Decision Debt Loop
Decision made
Not documented
Time passes
Context fades
Question arises
No one's sure
Meeting scheduled
To re-decide
Decision made again
Still not documented
Return to step 2
Loop repeats
Each cycle wastes time and erodes trust in the organization's ability to execute.
Breaking the Loop
Meeting Level
- "What did we decide?"
- "Who owns documentation?"
- "When will it be documented?"
If no one can answer these, you haven't actually decided.
Team Level
- No decision is final until documented
- Documentation reviewed in same session
- Records linked to relevant systems
Documentation is a deliverable, not an afterthought.
Organization Level
- All decisions in one place
- Tagged by topic, team, system
- Searchable by anyone
Build searchable decision history.
The 30-Second Documentation Test
After any meeting where a decision is made:
Can someone who wasn't there understand what was decided?
Can someone find this decision six months from now?
Does it include the WHY, not just the WHAT?
If the answer to any of these is “no”, the decision isn't documented—it's just remembered.
The Prevention Protocol
Pre-Meeting
5 minutes- Has this been decided before?
- Is there existing documentation?
- Who would know?
Savings: 1+ hours of meeting time
During Meeting
Ongoing- Assign a decision scribe
- Capture decisions as they happen
- Note context and constraints
Savings: No reconstruction needed
Post-Meeting
Within 24 hours- Publish decision record
- Link to relevant systems/code
- Notify affected parties
Savings: Context preserved
The ROI of Not Re-Deciding
Current State
With Documented Decisions
What Good Looks Like
“Let's schedule a meeting to discuss the authentication approach. I think we talked about this a few months ago, but I'm not sure what we decided.”
“Checking the decision log... We decided on JWT with 24-hour expiry last October. The record explains why and links to the original discussion.”
The Compound Benefit
Documented decisions have positive spillover:
Onboarding
New engineers understand why things are the way they are without scheduling meetings
Cross-Team Alignment
Teams can reference other teams' decisions without coordination meetings
Strategic Planning
Leadership understands the decision landscape without executive briefings
Audit & Compliance
Decision history exists automatically, no scramble to reconstruct
Starting Small
You don't need a perfect system to start:
The meeting tax isn't paid once. It's paid every time someone asks “didn't we already decide this?” Document decisions, and stop paying the tax.