When the Right Questions Matter More Than the Right Reports
In my previous two articles, I introduced the concept of what I simply call the Golden Dataset—a centralized data platform designed to bring together multiple data sources under a single, consistent business logic.
I showed how different systems can be unified into one trusted source of truth, creating a solid foundation for countless reports and dashboards.
At this point, a perfectly reasonable question comes to mind:
That’s great… but what difference does it make in real life?
I’d like to share a story.
A story that fundamentally changed the way I think about the true value of Power BI.
An Exciting Challenge
One day, an organization approached me with a complex business question.
At first glance, the objective sounded straightforward.
They wanted to know whether every completed piece of work was properly reflected in the billing process.
It seemed like the kind of problem that could be solved by building a few reports.
Reality, however, turned out to be very different.
There was already a simple report available containing a handful of basic data points.
The problem wasn’t that the report was wrong.
It simply wasn’t designed to answer the questions management actually needed answered.
That was the moment I realized something important.
We didn’t need another report.
We first needed better questions.
Searching for the Right Questions
Before creating a single dashboard, I took a step back and asked myself:
What are we really trying to understand?
Questions like:
- Which completed activities should appear in the billing process?
- Which ones actually do?
- Where do discrepancies occur?
- What is the current status of the related project or task?
- Is it still in progress, or already completed?
- Has the work actually been performed?
- If so, has every required step successfully passed through the entire business process?
As more and more questions emerged, one thing became increasingly clear:
The answers were scattered across multiple systems.
This Is Where the Golden Dataset Proved Its Value
Earlier, I had invested considerable effort into building a centralized data platform that was designed to grow over time.
Now I finally understood why that investment mattered.
There was no need to redesign the architecture.
No need to start over.
Instead, I could simply identify and connect the data sources capable of answering these business questions.
Project management systems.
Time tracking records.
Financial information.
Billing data.
Each new source became another piece of the puzzle.
The Golden Dataset made it possible for all of those pieces to come together within a single business model.
KPIs Don’t Exist Because Dashboards Need Them
Once the data started coming together, I began creating simple comparison tables.
Not polished reports.
Not executive dashboards.
Just views that helped me think.
Each new insight raised another question.
What caused this discrepancy?
Where did the process break down?
Is something genuinely missing, or has the process simply not reached its final stage yet?
Gradually, every important question evolved into a KPI.
To me, a KPI has never been just another number displayed on a dashboard.
A KPI is a business question translated into the language of data.
Once a KPI exists, the answer to that question becomes available automatically.
We Were Never Looking for Someone to Blame
This may have been the project’s most important lesson.
Whenever I discovered a discrepancy, my first question was never:
Who made the mistake?
Instead, I always asked:
What can we learn from this?
Which process is missing?
Where can we simplify?
What could be automated?
How can we make everyday work easier for the people responsible for these processes?
I strongly believe that identifying problems should never be about assigning blame.
It should be about creating opportunities for improvement.
Perhaps this is where Lean thinking had the greatest influence on my work.
Continuous improvement.
Continuous learning.
Continuous optimization.
A Dashboard Alone Changes Nothing
The real transformation didn’t begin when I finished building the dashboard.
It began when the people doing the work started using it.
The dashboard wasn’t created to monitor them.
It was created to support them.
Our conversations generated valuable feedback.
New ideas emerged.
Additional validation steps were introduced.
Gradually, the dashboard became more than a report.
It became a daily operational tool.
Looking back, that was probably the most rewarding moment of the entire project.
Not because another dashboard had been delivered.
But because a team had started thinking together about how to improve the way they worked.
A Good Data Platform Creates New Opportunities
Once the foundation was in place, building additional solutions became dramatically easier.
Executive dashboards were created to present the most important KPIs on a single page.
Specialized analytical reports supported different business functions.
Operational dashboards helped teams manage their day-to-day activities.
Later, the same platform also enabled faster and more accurate responses to customer inquiries.
Everything was built on the very same data platform.
Not by starting over.
But by continuously building upon what already existed.
What Did I Learn?
When I think back on this project today, I don’t remember the dashboards.
I don’t even remember the KPIs.
What I remember is realizing that the true power of Power BI isn’t found in beautiful visualizations.
Its real strength lies in helping people think together.
Helping them ask better questions.
Helping them understand their processes.
And ultimately, helping them improve those processes together.
What About You?
Let me leave you with one final question.
The next time someone asks you to build a new report…
Do they really need another dashboard?
Or would it be more valuable to first ask:
What question are we actually trying to answer?
Perhaps that’s where the next breakthrough begins.
Key Takeaways
📦 Behind the Solution
This project demonstrates
- Business problem decomposition
- Turning business questions into measurable KPIs
- Enterprise data integration
- Cross-functional data analysis
- KPI framework design
- Root cause analysis
- Lean process improvement
- Building sustainable reporting solutions
- Stakeholder collaboration
- Data-driven decision making
Coming Next…
The next challenge was much bigger than building another report.
An organization needed to ensure that every employee recorded their working hours accurately and on time.
Visibility was only the beginning.
A lasting solution required the right KPI, a clearly defined process, assigned responsibilities, and a way to keep the system working every single week.
In the next article, I will share how a simple reporting request became a sustainable operating model.