The monthly deck is getting longer because the results are not
Avishai Sam Bitton 4 min read
The argument
Report volume is a lagging indicator of results. When there is pipeline to show, the deck gets shorter.
I have a heuristic I have never seen fail. When an engagement is working, the monthly report gets shorter. When it is not, it grows. Slides get added, new metrics appear, the appendix thickens, and someone builds a chart of a metric that did not exist last quarter.
This is not deception. It is the natural response to having a meeting to fill and nothing decisive to put in it. A month with a clear result needs one slide. A month without one needs forty, because volume of information is the only available substitute for a result.
What a growing deck is telling you
- New metrics appearing mid engagement. Almost always because the original metric stopped cooperating. Ask what happened to the number you agreed at the start.
- Percentage changes with no absolute numbers. A 140 percent increase from 5 to 12 is a rounding error dressed as momentum.
- Activity summaries at the front. Campaigns launched, assets produced, hours spent. Effort reported first is effort standing in for outcome.
- No failures anywhere. Any real programme runs tests that do not work. A report with nothing negative in it is a report that has been curated for comfort.
Nobody has ever needed forty slides to say the thing worked.
The four slides that are worth a meeting
- 1
The number
Qualified pipeline created this period, against plan, with the previous three periods for context. Absolute values. One slide, no commentary needed.
- 2
What changed and why
The two or three decisions taken since the last meeting, the reasoning at the time, and what happened. This is the only slide that demonstrates thinking rather than activity.
- 3
What did not work
Named, with the cost and the conclusion. A team that cannot produce this slide is either not testing or not telling you.
- 4
What we are doing next, and what would change our mind
The next two or three moves with a stated expectation attached. The second half matters more than the first: a plan with no falsification condition is a plan that will never be revisited.
Everything else belongs in a dashboard
Channel breakdowns, creative performance, keyword movement, cost curves: all useful, none worth a synchronous hour. Put them somewhere both sides can read at any time and reclaim the meeting for the only thing a meeting is good at, which is making decisions that need two parties present.
Two numbers that make the padding obvious
Worked example
Reading the deck as a signal
Same engagement, two consecutive quarters, tracked on two variables nobody usually plots together.
- Q1 report
- 14 slides, 41 qualified opportunities created
- Q2 report
- 38 slides, 22 qualified opportunities created
- New metrics introduced in Q2
- Five, none agreed at kickoff
- Failures named in Q2
- Zero
Result: Nothing in the Q2 deck was untrue. The deck simply grew to fill the space the results used to occupy, and the new metrics existed to give the growth somewhere to live.
Plot slide count against pipeline created for your own last four reports. It takes ten minutes and it is usually the most informative chart anyone has made about the engagement. If the two lines diverge, the reporting is compensating for something, and the honest conversation is overdue rather than unavailable.
The uncomfortable version of this for clients
Agencies produce long decks partly because clients reward them. If the monthly meeting is where you check that you got your money's worth, you are asking for evidence of effort, and effort is what you will be shown.
Change the request and the report changes within two cycles. Ask for four slides. Ask what failed. Ask what they would stop doing. The teams that can answer those questions comfortably are the ones producing something worth reporting.
What I would do Monday
- 1Count the slides in your last three monthly reports and plot them against pipeline created.
- 2Ask for the next report in four slides and see what survives the cut.
- 3Require one slide that names what failed and what was learned.
- 4Move the working numbers into a shared dashboard and use the meeting for decisions instead.
Who wrote this
Avishai Sam Bitton
Founder, DemandBox
Avishai runs demand generation programs for B2B SaaS companies across performance marketing, SEO, and answer engine optimization. He works directly with the teams he advises, with no account managers in between.
Connect on LinkedIn
Talk to an Expert