Decision Brief Template for Teams: One Page, Real Alignment

A decision brief is a one-page document, written before the meeting, that states the decision, the context, two to four real options, the criteria for choosing, and a recommendation. It gets alignment because people react to the same written facts instead of to whoever speaks first and loudest. Once it is signed off, it becomes the record that stops the team from reopening the question every few weeks.

Why teams relitigate decisions

Most repeated debates are not caused by disagreement about the answer. They come from people holding different versions of the question.

One person thinks you are deciding whether to raise prices. Another thinks you are deciding how to raise prices. A third missed the meeting where the budget ceiling came up. Three weeks later, someone raises it again, and nobody can point to what was agreed or why.

A decision brief fixes three specific problems:

• No shared question. The brief forces one sentence that defines what is being decided and by when.
• No shared criteria. People argue over options when they actually disagree about what matters. Writing the criteria first moves that argument to the front, where it is cheap.
• No record. A verbal decision gets reinterpreted. A written one can be pointed to.

This is not bureaucracy. A good brief takes 45 to 90 minutes to write and saves several hours of meeting time per decision, often across several meetings.

When a brief is worth writing

Do not write one for everything. A brief is worth the effort when at least two of these are true:

• The decision affects more than one team or more than three people.
• It costs more than roughly one week of someone's salary, or commits you for a quarter or longer.
• It has come up before, or you can already predict it will.
• It is hard to undo.

That last point matters most. If a choice is cheap to reverse, make it quickly and move on. Our guide to reversible vs irreversible decisions covers how to sort them. Save the brief for the choices where a wrong call hurts.

Template

Copy this into a doc and keep it to one page. If a section runs long, cut it.

DECISION BRIEF

Title: [Verb + object, e.g. "Choose our Q1 support staffing model"]
Owner: [One name]
Decide by: [Date]
Decision type: [Reversible / Hard to reverse]
Status: [Draft / In review / Decided]

1. THE DECISION
One sentence: "We need to decide [what] by [when] because [trigger]."

2. CONTEXT
- What changed or what is the problem (3 bullets max)
- Key numbers (current state, target state)
- Constraints that are fixed (budget, deadline, headcount)
- What is explicitly out of scope

3. OPTIONS
Option A: [name] - what it is, cost, time to start, main risk
Option B: [name] - same fields
Option C: [name] - same fields
(Always include "do nothing" or "keep current approach" as a baseline.)

4. CRITERIA
List 3 to 5 criteria, ranked or weighted.
Mark any criterion that is a hard requirement (must-have).

5. ASSESSMENT
How each option scores against the criteria (table or short bullets).

6. RECOMMENDATION
"I recommend Option X because [two reasons tied to the criteria]."
What would change my mind: [one or two conditions]

7. RISKS AND NEXT STEPS
- Biggest risk and how we will watch for it
- First three actions, with owners and dates
- Review date and the metric we will check

8. DECISION RECORD (filled in after the meeting)
Final decision, who agreed, who disagreed and committed anyway, date.

The sections people skip most often are "out of scope", "what would change my mind", and the review date. They are also the three that prevent the most relitigation.

How to write each section

The decision statement

Write it as a sentence with a deadline and a trigger. "Decide how to handle support volume" is a topic. "Decide by March 14 how to cut first response time below four hours, because response time over eight hours is now our top churn reason" is a decision.

If you cannot write the sentence, you are not ready for a meeting yet.

Context

Give the facts a smart colleague would need and nothing else. Three bullets of problem, a few numbers, and the fixed constraints. Resist the urge to tell the whole history of the project. Link to it instead.

The "out of scope" line deserves real thought. It is where you kill the side debates in advance. "We are not reconsidering our helpdesk vendor in this decision" saves twenty minutes of the meeting.

Options

Write two to four options. One option is not a decision, it is an announcement. Six options means nobody read the brief.

Always include the baseline of doing nothing or continuing as-is, with its real cost. Teams often discover that the status quo has a cost they never wrote down. If you want to quantify what each path gives up, the opportunity cost guide helps.

Make each option a fair version of itself. If you describe your preferred option in detail and the others in a line, readers notice, and trust drops.

Criteria

This is the section that changes the quality of the discussion. Pick three to five criteria and say which matter most. Typical ones: cost over 12 months, time to impact, risk of failure, reversibility, effect on team workload, fit with the current quarter's priorities.

Separate must-haves from preferences. "Must be live before the April 1 product launch" eliminates options. "Prefer lower cost" ranks them.

For a numeric scoring approach, see how to use a decision matrix. For most briefs a simple table with plain-language ratings is enough. Do not let a weighted spreadsheet make a close call look scientific.

Recommendation

Make one. A brief that ends with "there are tradeoffs, let's discuss" is a menu, and the meeting will become the thinking session you were trying to avoid.

State the recommendation in two reasons tied directly to the criteria. Then write what would change your mind. This invites the useful kind of disagreement: people can challenge the assumption instead of attacking you.

Worked example: a support staffing decision

Here is a condensed brief for a 22-person B2B software company at about $3.1M in annual recurring revenue. Support is two people handling roughly 1,400 tickets a month. Median first response time has drifted to nine hours. In the last two quarters, accounts that waited over eight hours for a first reply churned at roughly twice the rate of the rest.

Decision: Decide by March 14 how to get median first response under four hours by June 1, within a $60,000 annual budget.

Out of scope: Switching helpdesk software and changing support hours.

Criteria (in order): Hits the four-hour target by June 1 (must-have), 12-month cost, quality of customer experience, ease of reversing.

Assessment: Option A fails the budget and probably the date. Option C is cheap but alone does not reach the target. Option B meets the date and the budget, with a 60-day exit clause in the contract.

Recommendation: Choose Option B, with a 60-day exit clause, because it is the only option that meets both the June 1 target and the $60,000 ceiling, and it is reversible. Start a small pilot of Option C on the two most repetitive ticket types after 30 days. What would change my mind: if vendor quality scores under 85% CSAT after the first 30 days, or if the target date moves out past August, we reopen Option A.

Review: April 30, checking median first response time and CSAT.

The meeting for this took 25 minutes. Before the brief, the same topic had come up in three consecutive leadership meetings and consumed close to two hours without a decision. The difference was that the argument about criteria ("is cost or speed the priority?") happened in comments on the doc, two days earlier.

A common mistake: writing the brief to win

The most frequent failure is a brief that is really a sales pitch. The owner already decided, and the options section exists only to make the favorite look inevitable. Three tells give it away: the rejected options are strawmen, the criteria were clearly chosen after the answer, and there is no "what would change my mind."

Readers pick up on this fast, and the response is to distrust the whole document and reopen everything in the meeting. That defeats the purpose.

How to avoid it:

• Write the criteria before you score the options, and show them to one other person first.
• Describe the strongest version of each rejected option. Ask a colleague who prefers it to check your description.
• Include the downside of your own recommendation, in plain numbers.
• Check your own thinking against the usual traps in cognitive biases that hurt business decisions, especially confirmation bias and anchoring on the first option you thought of.

Running the process around the brief

The document does half the work. The way you circulate it does the rest.

1. Send it 24 to 48 hours ahead. Ask for written comments in the doc. Most objections surface there, and they are cheaper to resolve in text.
2. Start the meeting with silent reading if people did not prepare. Ten minutes of reading beats twenty minutes of summary.
3. Spend the meeting on the open questions only. Skip anything resolved in comments.
4. Agree on how you are deciding. The owner decides after input, or the group must consent, or a vote. Be explicit. The article on consensus vs consent explains why "everyone must agree" is rarely the right standard.
5. Fill in the decision record before people leave. Name who disagreed and committed anyway. That one line prevents most "I never agreed to that" conversations.
6. File it where the team looks. A shared folder or a decision log works. If you keep one, the decision log template shows how to turn the record into learning at the review date.

When someone raises a settled decision later, the response is simple: open the brief, check whether the "what would change my mind" conditions have occurred, and if not, move on. If they have, update the brief and decide again on purpose.

Keeping it to one page

Briefs bloat. A few rules keep yours short:

• Cap context at three bullets and a handful of numbers.
• Move charts, interview notes, and long calculations to an appendix link.
• Use a table for options instead of paragraphs.
• If the recommendation needs more than four sentences, the decision is probably two decisions. Split it.
• Delete adjectives. "Significant risk" becomes "a 30% chance of a two-week delay."

A brief that fits on one page signals that the owner understands the decision well enough to compress it.

Key takeaways

• A decision brief puts the question, context, options, criteria, and recommendation on one page, written before the meeting, so people react to the same facts.
• Write the criteria before you score the options, and separate must-haves from preferences. This moves the real argument to the cheapest moment.
• Always include the do-nothing baseline and a clear recommendation with a "what would change my mind" condition.
• Do not write the brief to win. Strawman options and after-the-fact criteria make people reopen everything.
• Record the final decision, who disagreed and committed anyway, and a review date, then file it where the team can find it.
• Reserve the brief for decisions that are costly, cross-team, recurring, or hard to reverse. Make everything else quickly.