The Executive Decision Log Explained

Every COO, VP of Operations, and Chief of Staff has experienced this: a decision made in a leadership meeting three months ago is now being relitigated as if it never happened. Someone missed the meeting. Someone changed their mind. Someone new joined the team and wants to understand the reasoning. The conversation restarts from zero.

The fix is not better meeting facilitation. It's a decision log — a durable, searchable record of what was decided, by whom, and why. Executives resist building one because it sounds like overhead. The teams that build one stop relitigating decisions. The teams that don't keep having the same conversation.

Why leadership teams avoid decision logs

The most common objection is that it feels bureaucratic — adding documentation overhead to conversations that should be fast. This objection disappears after the first post-mortem where the team can't reconstruct why a pivotal choice was made. The overhead of a decision log is four minutes per decision. The overhead of relitigating a settled question is four hours and a damaged team dynamic.

The second objection is "we'll just check Slack." Slack threads are not decision records. They are decision archaeology. Finding the relevant exchange requires knowing when it happened, who was involved, and what thread it lived in. A decision record requires knowing what was decided — and returning the answer in one click.

What executive decision logs capture that ADRs don't

Engineering ADRs (Architecture Decision Records) are the closest analog, but the executive version differs in three ways:

• Audience — ADRs are written for engineers who understand the technical context. Executive decision logs are written for future leaders, board members, and new hires who may have no context at all. Write for someone joining the company in two years.
• Scope — ADRs cover technical architecture. Executive logs cover strategy, hiring, pricing, organizational structure, go-to-market, and any high-stakes cross-functional decision. Broader scope, less technical depth.
• Reversibility definition — In ADRs, reversibility is about technical debt. In executive logs, it's about organizational and political cost. "This decision is reversible with CEO + board alignment" is a meaningful statement that shapes how people treat the decision going forward.

The five dysfunction patterns in orgs without decision logs

These are the patterns that repeat in leadership teams that don't maintain a decision record:

1. The Groundhog Day meeting. The same strategic question surfaces every quarter. The team debates it, reaches a provisional conclusion, and moves on. Three months later, someone raises it again as if the prior discussion never happened. Without a decision record, it didn't happen — there's no artifact to point to.

2. The new executive re-opening. A new leader joins the team and, reasonably, asks why decisions were made the way they were. Without a log, the answer is "that's just how we've done it" or a reconstructed narrative that doesn't match what actually happened. With a log, the new leader reads the record and either accepts it or makes a documented case for changing it.

3. The authority ambiguity. A decision was made, but it's unclear who made it and at what level. When someone wants to revisit it, there's no established authority to appeal to. The question devolves into politics rather than process. A decision log that includes "Authority: CEO, reversible with board alignment" cuts this off immediately.

4. The post-mortem without a record. Something went wrong. The post-mortem tries to reconstruct the decision-making sequence that led to the failure. Without a log, the sequence is assembled from memory, which is unreliable and subject to hindsight bias. With a log, the sequence is documented and the team can evaluate the actual reasoning, not the remembered reasoning.

5. The confident-but-wrong narrative. Leadership develops a confident narrative about why past decisions were made, which diverges from what actually drove those decisions. The narrative gets repeated in all-hands, investor updates, and hiring conversations until it becomes the official history. A decision log is the corrective — it records the actual reasoning, not the retrospective rationalization.

What goes in an executive decision record

Four fields, same as any decision record:

• Decision — one sentence, imperative, specific. "We will raise the Series B at a $120M cap with Y Combinator leading." Not "we're exploring Series B options."
• Why — the two or three factors that drove it. Not the comprehensive list of everything considered — the factors that actually tipped the decision.
• Rejected — what was considered and why it was ruled out. The most underused field. Teams that skip it find themselves re-evaluating the same alternatives in future meetings.
• Authority — who decided, and what would be needed to reverse it. Defines the decision's weight and the appropriate process for changing it.

Implementing it without creating overhead

Assign one person — often the Chief of Staff — to maintain the log. Their job is not to make the decisions but to capture them. After any meeting where a significant decision is made, they write the four fields and circulate them to the decision-makers for confirmation within 24 hours. The confirmation step is important: it catches misunderstandings about what was actually decided before they calcify.

The log lives in one canonical location. One place, always up to date, accessible to everyone who needs it. Not scattered across five different Notion databases or locked in a personal folder.

Frequently asked questions

Who should own the executive decision log?

The Chief of Staff is the natural owner in organizations that have one. In teams without a CoS, the CEO's EA or a rotating ownership among the leadership team works. What doesn't work is collective ownership with no designated person — the log gets updated by whoever has time, which means it doesn't get updated.

How often should the decision log be reviewed?

Quarterly reviews are standard practice for leadership teams. Pull up the log, scan decisions made in the prior quarter, and ask: which held, which turned out to be wrong, and which should be revisited given new information. This review also catches decisions that were made but never recorded — a gap that the review process helps close over time.

What if leadership resists the formality?

Start smaller: capture only decisions with significant financial or organizational consequences. Get one post-mortem where the log is clearly useful, and the resistance usually dissolves. The value of a decision record is most visible in hindsight; getting to that first hindsight moment is the goal of the initial implementation.