data.day

A Simple 'Decision Page': One Slide That Forces Clarity

If your report doesn't explicitly state what needs to happen next, it's just a brochure. Here is how to build the 'Decision Page'.

The “Interesting” Meeting Trap

I witnessed a meeting last week that was tragic in its politeness. A very capable account manager presented a 40-page quarterly review. It was thorough. It was accurate. The font sizes were consistent.

At the end, the client sat back, tapped the table, and said, “That was very interesting. Let us digest that.”

The account manager smiled and left. She thought she had done a good job. She hadn’t. She had just delivered a brochure.

The client didn’t know what to do with the information. Should they increase the budget? Should they kill the underperforming campaign? Should they panic? Because the report didn’t explicitly ask for a decision, the client made the default choice: they decided to do nothing.

We treat reports as “updates.” This is rubbish. A report is a tool for getting a decision. If you walk out of the room without a “Yes” or a “No,” you have failed.

The Drag: The Passive Voiceover

The problem is that we are often too polite to be direct. We bury our recommendations in the verbal commentary.

  • What we say: “It might be worth considering a reallocation of funds from Q3 to Q4 given the current CPC trends.”
  • What the client hears: “Blah blah blah technical jargon blah.”

We hide behind nuance because we are afraid of being wrong. So we present the data and hope the client connects the dots. But the client is tired. They have ten other meetings today. They don’t want to connect dots; they want to sign off.

When we force them to infer the next step, we are adding cognitive load. We are making them work to give us money. That is a dodgy business model.

The Answer: The “Go / No-Go” Slide

I have introduced a mandatory slide in our decks. It is called The Decision Page. It sits right at the front. It is not subtle.

It has three boxes:

  1. The Context: One sentence on what changed. (e.g., “Competitor X launched a sale, increasing our costs by 20%.”)
  2. The Recommendation: What are we going to do? (e.g., “Shift 10k budget to the ‘Loyalty’ campaign to bypass the competition.”)
  3. The Ask: What do I need from you right now? (e.g., “Approval by Friday.”)

[TO EDITOR: A wireframe diagram of a slide. Title: “DECISION REQUIRED”. The slide is split into three vertical columns. Column 1: “SITUATION” (Icon of a warning triangle). Column 2: “PROPOSAL” (Icon of a path/arrow). Column 3: “APPROVAL” (Icon of a checkmark box). Large text, very little clutter.]

When you put this on the screen, the energy in the room changes. The client stops looking at their phone. They lean in. They realize this isn’t just “show and tell”; it’s a transaction.

“So, Oliver,” they say. “You need a Yes on the 10k shift?” “Yes.” “Sorted. Go ahead.”

Meeting over in 15 minutes.

It forces us to be sharper, too. If you sit down to write the Decision Page and you realize you don’t actually have a recommendation, then you know your report is weak. It acts as a forcing function for your own thinking.

Don’t be a narrator. Be a guide. Put the decision on the page and hand them the pen.

FAQs

What if there is no decision to make this week?

Then why are you having a meeting? Send an email and give them their hour back. They will love you for it.

Doesn't a 'Decision Page' feel a bit aggressive?

Clarity is never aggressive. Ambiguity is aggressive because it wastes time. Clients pay us to lead, not to loiter.

Where should this page go?

Page two. Right after the Executive Summary. Do not bury the lead.