The Playbook
How to Present Numbers to Someone Who Does Not Read Numbers
Meghan Garcia, CPA · 3 minute read
What's Working
- Strong opening hook about compartmentalized thinking
- Excellent PowerCPA voice with hard stops and direct language
- Great practical framework (Excel brain dump, three rules)
- Perfect closing line about making numbers understand them
- Good concrete examples throughout
- Clear section structure that builds logically
What Needs Work
- Opening could be punchier after the strong hook
- "That is not their failure. That is our failure" feels slightly preachy
- Excel section buries the lead and could be more actionable
- "Three rules that work every time" overpromises - sounds like clickbait
- Some transitions between sections are weak
- Missing some bite in the methodology section
Redraft
How to Present Numbers to Someone Who Does Not Read Numbers
They are not going to learn the model. You have to learn the translation.
Accountants are compartmentalized thinkers. We see rows and columns and know exactly what each one means.
The person across the table sees a wall of numbers and waits for us to tell them what to think.
This is a design problem. Not a user problem.
Start messy in Excel. End clean everywhere else.
Brain dump in Excel first. Create columns as you think. Add rows as questions surface. Let it be ugly.
Excel is the best thinking tool in finance because it works like your brain works. In pieces you can move around.
Take that mess and build structure. Not a finished report yet. A skeleton. Something a non-accountant can follow from A to B to decision.
One clear answer to the question they actually asked. Everything else is noise.
Find the decision hiding in the data request.
Before you touch Excel, ask what decision this person needs to make. Not what data they want. What choice they face.
Every number in your report should point to that choice. If it does not help them decide, cut it.
The biggest mistake in financial reporting: giving them everything and hoping they figure out what matters. They will not. They will call another meeting and ask you to walk through it.
Skip that meeting. Build the answer into the report.
Three rules that never fail.
One insight per section. "Are we on budget?" gets one answer in one place. "Where did we miss?" gets another section. Do not mix questions.
Conclusion first, proof second. Put the answer at the top. Show supporting numbers below. They want the answer. The numbers just prove you are right.
Their words, not yours. They say "overhead," you say "overhead." Not "SG&A." They talk about "burn rate," you show "burn rate." Not "monthly cash flow variance." Match their language or lose their attention.
Nobody cares about your methodology.
Skip the explanation of how you built the model. They care what it tells them to do.
Save methodology for the appendix. Better yet, save it for when they ask. Which they probably will not.
Your job is translation, not education. Make complex simple. Not prove you understand complexity.
Everyone knows you understand the numbers. That is why you are in the room.
Make the numbers understand them.
More from The Playbook
How to Reconcile When There Is No Process to Follow →