How to Gather Dashboard Requirements Without Triggering a Turf War
Let’s Talk About the Real Killer of Good Dashboards:
It’s not poor design.
It’s not even bad data.
It’s giving in to bad requests like “Can you just give me a table… with all the details.”
We’ve all been there.
You’re in a kickoff call.
The senior stakeholder is confident, decisive, and absolutely convinced that a 400-row table dumped onto a dashboard is exactly what the business needs.
If you say, “That’s not a good idea” – you’ve already lost.
The Brain Doesn’t Like Being Challenged
According to neuroscientist Tali Sharot, when people hear information that conflicts with their beliefs, the logical part of their brain shuts down.
Your well-meaning correction? It triggers their defence mode.
Disagreement = rejection. And no one likes to feel rejected – especially not the stakeholder signing off your budget.
So What Do You Do?
You reflect. Then redirect.
“Sounds like people are asking for all the details. What are they using that for day-to-day?”
This question changes the dynamic.
It shows respect.
It reveals intent.
And most importantly: it keeps their brain open to better options.
Real Talk: Tables Are Not Evil
Sometimes a detailed table is exactly what’s needed.
But most of the time?
It’s a symptom.
A sign that the real question hasn’t been fully uncovered yet.
That the stakeholder is trying to protect themselves.
Trying to avoid blame.
Trying to show they’ve “covered everything.”
Or maybe they need to find some insights first, to filter the table down to the rows that really matter.
Decode the Ask
Stakeholders rarely give clean briefs. They speak in output, not outcome.
- “Can we show all the data?” = I don’t trust we’ll have what we need later.
- “Put everything in one place.” = I’ve been burned before by partial reports.
- “Just make it a big table.” = I haven’t had a dashboard that actually helped me yet.
They’re not wrong.
They’re just starting at the surface.
Your role isn’t to challenge. It’s to dig.
Use the Powerful Dashboards™ Framework
This is where the real magic happens.
1️⃣ Turbocharged Build
- Don’t say “no” to the table.
- Say: “Let’s sketch out what goes in it.”
- Scope the decisions they need to make, not the columns they want to see.
2️⃣ Fast-Track Learning
- Share 1–2 dashboards that show the same data without a massive table.
- Ask: “Would something like this still get you the same outcome?”
3️⃣ Quality Confidence
- Play back what you’ve learned.
- Build the Minimum Viable Product with a focused view – but include a ‘details on demand’ option.
- Everyone wins: simplicity up front, security in the back.
📊 Tableau Tip:
Avoid asking “What data do you want to see?”
Ask: “What do people need to decide or do differently after seeing this?”
That one shift will save you hours of building – and weeks of back and forth.
💥 The Bigger Risk?
You build exactly what they asked for.
They open it once.
Close the tab.
And go back to Excel.
✅ What to Do Instead
- Reflect, don’t react
- Seek the need, not the noise
- Design for trust, not just data
You don’t win requirement sessions by being the smartest person in the room.
You win by being the most curious.
Ready to Go Further?
If you found this post helpful, imagine what you could do with structured support.
→ Visual Analytics Best Practices
Join a small group of like-minded professionals for a hands-on, expert-led course. We cover layout, UX, stakeholder psychology, and dashboard design – all applied to your real work. You’ll walk away with immediate wins and a reusable system. Perfect if your dashboards are “working” but not wowing.
→ Tableau Insights Community (TIC™)
Think of it as your dashboard dojo. Weekly calls, design feedback, career advice, and templates that speed up your build process. It’s pay-as-you-profit, and includes support from others in the same boat. If enrolment isn’t open, join the waitlist to be first in line.
✅ See the details and join the waitlist
Appendix: Sources & Support
This article was featured in Tableau’s Weekly Roundup.
