The SPADE Framework for Team Decisions

Most team decisions don't fail because the team is dumb. They fail because nobody was clear on how the decision would get made.

Who actually decides? What are we even choosing between? Did we decide, or just talk? And three weeks later: "wait — what did we land on?"

SPADE fixes that. It's a simple framework (popularized by Gokul Rajaram, who used it across Google, Facebook, and Square) for group decisions that actually stick. Five letters, five steps.

(We met it briefly when we ran through the simple frameworks that make decision-making easier — here's the full version.)

S — Setting

Frame the decision precisely: what exactly are we deciding, by when, and why now?

Most bad decisions are fuzzy at the root — people argue past each other because they're quietly answering different questions. Nail the setting and half the confusion disappears before it starts.

P — People

Name the roles, out loud:

• ✓The Decider — one person who owns the call. Not the committee. One.
• ✓Consulted — those whose input genuinely shapes it.
• ✓Informed — those who just need to know the outcome.

This is the step teams skip, and it's the most important. When nobody knows who decides, the decision defaults to whoever's loudest or most senior — and everyone else quietly disengages. Naming the Decider kills the popularity contest.

If you want the long version of this one letter, it's the entire subject of the decision-rights frameworks guide — RAPID, RACI, DACI and SPADE side by side, all answering the same question with different letters.

A — Alternatives

List the real options — at least a couple of genuine ones, not one favorite flanked by two strawmen.

Good alternatives are distinct and plausible. If every option but one is obviously bad, you haven't given the team a decision — you've given them a rubber stamp.

D — Decide

Now actually decide. Gather input first — a written round, even an anonymous vote, beats a live free-for-all where the first voice anchors everyone. Then the Decider makes the call.

The key is that there's a moment. "We sort of agreed" is how decisions die. Someone owns the call and says it plainly.

E — Explain

Communicate the decision and the reasoning to everyone affected.

This is what stops it getting relitigated next week. "Here's what we decided, here's why, here's what we considered and rejected" — written down, visible. People accept decisions they disagreed with far more readily when they can see the reasoning was sound.

Written down and visible, kept where anyone can go back to it later, is exactly what a decision audit trail is.

Why it works

Look at what SPADE actually does: it makes the whole process explicit and visible — what's being decided, who decides, what the real options are, when the call happens, and why.

That's the same principle under every good group decision: structure beats vibes, and visible reasoning lets the best argument win instead of the loudest voice. SPADE is just a clean, memorable way to install it.

You don't need it for every choice — reserve it for decisions big enough that "wait, what did we decide?" would be expensive. For those, it's the difference between a team that decides once and one that argues forever.

Think of a team decision that went sideways recently. Which SPADE letter was missing — unclear who decided (P)? fake alternatives (A)? no real moment of decision (D)?

Reply and diagnose one. It's almost always a missing letter.