DefineIt all starts here. The rest is the result.
“I need a dashboard” is not a problem. I turn it into a decision.
A sales dashboard, with everything.8 pages60 visuals2 visits✗
What do I stop buying this month?3 pages12 visualsMonday to Monday✓
Defining is turning a requestinto a decision.
What do they ask for?
I ask before building.“A sales dashboard, with everything.”
✗Built as asked, it’s 8 pages. I ask first.
✓What really hurts?
Margin by hand, every Monday“We want to see everything.”
✗“Every Monday I export to Excel and compute margin by hand.”
✓What gets decided with it?
What to push and what to stop buyingLooking at sales.
✗Deciding what to push and what to stop buying.
✓Who, and how often?
Carlos and Paula, every MondayFor everyone, whenever.
✗Carlos decides. Paula uses it every Monday.
✓How will we know it worked?
Paula stops exportingThat it looks nice.
✗Paula stops exporting and margin rises 1 point.
✓What stays out?
Reps: version 2Everything in version one.
✗Reps, to version 2. 3 pages remain.
✓What do they ask for?
I ask before building.“All the finance numbers, in real time.”
✗Built as asked, it’s 8 pages. I ask first.
✓What really hurts?
8-day close; figures that don’t match“I want more control.”
✗“Closing the month takes 8 days, and sales don’t match the commercial team’s.”
✓What gets decided with it?
Which expense to stopSeeing the numbers.
✗Deciding which expense to stop before month-end.
✓Who, and how often?
Finance manager, every FridayAll management, online.
✗The finance manager decides, every Friday.
✓How will we know it worked?
Close in 3 daysThat it’s in real time.
✗Close in 3 days and one sales figure.
✓What stays out?
Cash flow: version 2All together.
✗Cash flow, to version 2. 3 pages remain.
✓What do they ask for?
I ask before building.“A logistics dashboard, with every KPI.”
✗Built as asked, it’s 8 pages. I ask first.
✓What really hurts?
Three calls every morning“Orders arrive late.”
✗“Every morning I call three warehouses to learn what’s late.”
✓What gets decided with it?
Which order gets prioritySeeing OTIF.
✗Deciding which order gets priority today.
✓Who, and how often?
Dispatch lead, at 8Management, once a month.
✗The dispatch lead, every morning at 8.
✓How will we know it worked?
Zero calls; OTIF 96%A higher OTIF, someday.
✗Zero calls, and OTIF from 92% to 96%.
✓What stays out?
Fleet: version 2Everything in version one.
✗Fleet, to version 2. 3 pages remain.
✓What do they ask for?
I ask before building.“An HR dashboard, with turnover and everything else.”
✗Built as asked, it’s 8 pages. I ask first.
✓What really hurts?
Two weeks with an uncovered shift“Turnover is high.”
✗“Each resignation leaves a shift uncovered for two weeks.”
✓What gets decided with it?
Where to reinforce and who to hireLooking at turnover.
✗Deciding which stores to reinforce and who to hire first.
✓Who, and how often?
Store lead, every 15 daysAll of HR.
✗The store lead decides, every 15 days.
✓How will we know it worked?
From 14 to 7 daysHaving the KPI.
✗Go from 14 to 7 days with an uncovered post.
✓What stays out?
Climate: version 2All of HR, at once.
✗Climate, to version 2. 3 pages remain.
✓A dashboard nobody usescosts you twice.
Once when it’s paid for. Again when the team goes back to Excel and stops trusting the data.
What I don’t do,and what I do.
Just one person
Who decides and who suffers the data
“What reports do you need?”
The Monday Excel
“I want to see everything”
From “all” to one decision
Promise a chart blindly
Agree how it’s measured
Open Power BI
I leave with a brief
45 minutes,and not one chart.
I show no designs and don’t open Power BI. I listen and take notes.
What reports do you need?
You get a list of charts, and nobody says what gets decided.
What decision do you make with this, who makes it and how often?
You get the problem, the owner and the rhythm.
- 1Context0–5 min
I learn the business.
I askWhat’s a normal week like here?
I leave with✓Examples that fit - 2The jobs5–20 min
I listen to what hurts and write exact quotes.
I askWhat did you decide last week with numbers?
Show me how you got them.
I leave with✓3 jobs that hurt - 3Prioritize20–30 min
I propose two and ask to be corrected.
I askWhich costs more each month?
I leave with✓2 jobs, never more - 4Data and limits30–40 min
I check what sinks projects.
I askWhat time does the data arrive?
Who signs this?
I leave with✓The conditions, in writing - 5Close40–45 min
I agree on success and the next date.
I askHow will we know in three months it worked?
I leave with✓Success and a date
Before drawing:is this a dashboard?
Click, or scroll to say “Yes”. Of 8 exits, only 2 are a dashboard. Each “No” has its own solution.
Does someone specific come back to this question on a fixed rhythm?
By name, every week or every month.
Does the data exist and can it be connected?
Where does it come from today? Can you show me?
Does looking at it change what someone does?
What do they do differently when they see the number?
Do they want to see what happens, not have the system decide?
A person looks and decides.
Is there someone who decides which figure is right?
“Each team has its own sales number.”
Will they look at it, not just download the file?
What do they do after downloading it?
Are there any conditions?
Phone, who sees what, external users, late data.
An analysis, not a dashboard
It’s answered once and written down. Nobody will open a dashboard twice for this.
First, a data project
The dashboard makes sense, but today there’s nowhere to get the data. Source first, with its timeline.
An alert, not a screen
If nobody will be looking when it happens, you don’t build a screen.
A model, not a dashboard
It’s another craft and another timeline. Power BI can show the result afterwards.
First, agree on definitions
If I build the dashboard now, it’ll be the fifth version of sales.
Excel connected to the model
They stay in their Excel, but with the same number as everyone.
- The branch ends here: the other questions aren’t needed.
It could still be any of these
- Written analysis
- Data project
- Alert
- Predictive model
- Dictionary
- Connected Excel
- Dashboard
Three warehouses explain almost all the fall. Check the north one first.
1 or 2 pages, in a week. Nothing to maintain.
Two timelines, in order.
Zero pages. It costs a fraction of a dashboard.
| customer | leaves |
|---|---|
| Las Rosas | 82 % |
| El Puente | 64 % |
| Central | 31 % |
BigQuery ML or Python, with its own timeline.
| KPI | definition | owner |
|---|---|---|
| Net sales | Invoiced − credit notes | Control ✓ |
| Margin | Sales − day’s cost | Finance ✓ |
A dictionary with owner and signature. One week.
| area | Q1 | Q2 |
|---|---|---|
| North | 412 | 398 |
| South | 305 | 321 |
Insert › PivotTable › From Power BI.
A 3-page dashboard for Paula, reviewed every Monday to decide what to push and what to stop buying.
What I hear,and what’s behind it.
The request is the symptom, not the diagnosis.
“I need a dashboard with everything.”
✓I look for the decision. 3 pages come out.
“I want it in real time.”
✓I ask how much delay works.
“I want to download everything to Excel.”
✓Excel connected to the model.
“Why did sales fall in March?”
✓Two pages with the conclusion.
“Each team has its own number.”
✓A dictionary with owner and signature.
“Tell me if it drops below this.”
✓An automatic notice. Zero screens.
“Tell me which customers will leave.”
✓BigQuery ML or Python.
Saying “this isn’t a dashboard”builds the most trust.
I don’t sell what I know: I solve what’s there.
When the request is a question answered once, I say no to the dashboard and yes to the answer.
Build me a dashboard to see why sales fell in March.
What you describe is an analysis, and I can do it.
A dashboard is for looking at the same thing every week. This gets answered once.
In one week I hand you the written conclusion.
If something shows up to watch every week, that’s the dashboard.
How long6 weeks of work
What they getA dashboard opened once
What remainsThe question stays unanswered
How long1 week
What they get2 pages with the answer
What remainsNext time they call me first
They win: an answer, and sooner. I win: next time they ask me before deciding what to ask for.
One brief,on a single page.
If it doesn’t fit on one page, we still don’t understand the problem.
- Which decision?
What to push and what to stop buying.
- Who, and how often?
Carlos and Paula, every Monday.
- What’s delivered?
3 pages: margin, customers and products.
- What stays out?
Reps and stock: version 2.
- What does the team provide?
Paula tests on Fridays. Accounting validates sales.
- How will we know it worked?
Paula stops exporting and margin rises 1 point.
Week 8. Someone says…
“I asked for something else.”→The brief says what was agreed.
“And this too?”→If something enters, something leaves.
“Did it work?”→What was signed gets measured.
One case,from start to finish.
A sales dashboard for the whole company.
Distributor with 6 areas.
- On Mondays6 managers decide who to visit.
- With an ExcelIt arrives on Sunday, sometimes late.
- That doesn’t matchIt doesn’t deduct credit notes.
- In the carBetween customers.
One screen, on the phone. Each manager sees their area.
The brief is signed.Now it can be built.
Defining ends when these four things are on paper and the owner signs off.
- ✓One decisionWhat to push and what to stop buying.
- ✓An owner and a rhythmCarlos and Paula, every Monday.
- ✓Success, measured at 90 daysPaula stops exporting; margin rises 1 point.
- ✓What stays out, in writingBy rep: version 2.
With the signature, it gets built. Next comes Review: checking the data holds up.





