The First Thing Power BI Taught Me Had Nothing to Do with Dashboards

When I decided to learn Power BI, I had one picture in my mind, beautiful dashboards.
I imagined creating interactive reports with colorful charts, KPIs, and slicers that would impress anyone who looked at them. Like many beginners, I thought the magic of Power BI started with visualization.
I couldn't have been more wrong.
The first thing Power BI taught me had nothing to do with dashboards.
It taught me that before you can tell a story with data, you must first clean the data.

My First Surprise

On my very first day, I expected to import data and immediately start building charts. I imagined dashboards coming together within minutes.
Instead, I found myself spending most of my time in Power Query, cleaning and preparing the data before I could do anything visual.
At first, I was confused. I kept asking myself: "Why am I spending so much time cleaning data? I thought Power BI was about building dashboards."
But when I looked more closely at the dataset, everything started to make sense.
I noticed something simple, yet very important.
Some names that were meant to represent the same person were written in different ways:

- Josephine
- josephine
- JOSEPHINE

To a person, these are clearly the same name.
But to Power BI, they are treated as three completely different values.

I also discovered several data quality issues that I hadn’t expected.
There were empty cells where important information was missing, and some text columns had things like errors, null and N/A, which I had to standardize by replacing them with consistent values such as Unknown, Not Provided, depending on the context and data type. For example, I used Unknown or Not Provided for text fields, and handled numeric fields differently by replacing error cells with null since Power BI recognizes null as a special value that represents missing or undefined datas to ensure they remained valid for calculations.

I also encountered duplicate records, which inflated totals and could easily lead to misleading results if not corrected.
Again, some dates 01/02/2026 were stored as text instead of proper date formats, making it impossible to perform time-based analysis until they were converted correctly and also IDs were treated as numbers when they should be text.

I found extra spaces and inconsistent formatting, which made identical values appear different and affected grouping and filtering. For example, "Uganda" vs "Uganda " You can say Some values looked identical but weren’t—hidden spaces made Power BI treat them as different entries.
I also realized that the dataset had incorrect data types, where text, numeric, and date fields were not properly assigned. This meant some columns that should have supported calculations were treated as plain text, while others that should have been categorical or date-based were misinterpreted, affecting accuracy and performance.

Then Came My Next Challenge: DAX

After spending time cleaning and preparing the data, I thought I was finally ready to build visuals.
But Power BI had another lesson waiting for me. This is where I met something called DAX (Data Analysis Expressions).
At first, it looked simple just formulas, right? I quickly realized it was not that simple.
DAX wasn’t just about writing calculations. It was about thinking in logic and asking the right questions of my data.

Instead of just “adding numbers,” I had to start thinking like an analyst:

- What is the total cost of production?
- What is the total profit value?
- What is the total revenue?
- What is the total planted area?

Suddenly, I wasn’t just clicking around Power BI anymore, I was reasoning with data.

My First DAX Moments

My first simple functions felt like a breakthrough:
SUM() to calculate totals
AVERAGE() to find mean values
COUNT() and DISTINCTCOUNT() to understand records
Even though they looked basic, they opened a new way of thinking.
I remember realizing something important:
Cleaning data prepares it.
DAX gives it meaning.

My First Encounter with Logical Functions in DAX

This is where Power BI started to feel less like a tool and more like a way of thinking.
Logical functions are what allow Power BI to make decisions based on conditions. Instead of just calculating values, I could now tell Power BI:

- “If this condition is true, do this…”
- “If not, do something else…”
The first logical function I used was IF().
It helped me answer simple questions like:
If a value is above 50, return “Pass”
Otherwise, return “Fail”
Result = IF([Score] >= 50, "Pass", "Fail")

Then things got more interesting with nestedIFs.
Instead of just two outcomes, I could handle multiple categories and also take care of the blanks:
Excellent
Good
Average
Poor
Forexample;
Grade =IF([Score] >= 80, "Excellent",IF([Score] >= 60, "Good",IF([Score] >= 50, "Average", "Poor") At this point, I realized

Data analysis is often about classification, not just numbers.

One of the biggest challenges I faced was missing data.
That’s where ISBLANK() came in handy.
Example:
Revenue Category Nested IF =IF(ISBLANK('Kenya_Crops_Dataset'[Revenue (KES)]),"Not Provided",IF('Kenya_Crops_Dataset'[Revenue (KES)] > 500000,"High Revenue",IF('Kenya_Crops_Dataset'[Revenue (KES)] > 100000,
"Medium Revenue",IF('Kenya_Crops_Dataset'[Revenue (KES)] > 0,"Low Revenue","Not Provided"))))
This helped me handle empty values instead of ignoring them.
I learned that missing data is still data you just need to label it properly.

Sometimes one condition was not enough. So I learned how to combine conditions: AND/OR Example:
High Revenue and Profitable =IF(AND('Kenya_Crops_Dataset'[Revenue (KES)] > 100000,'Kenya_Crops_Dataset'[Profit (KES)] > 0),"High Revenu Profitable Farm","Other Farm")

Maize or Rice =
IF(OR('Kenya_Crops_Dataset'[Crop Type]"Maize",'Kenya_Crops_Dataset'[Crop Type] = "Rice"),"Priority Crop","Other Crop")

I realized something that Logical functions don’t just process data they simulate thinking and they made me think like an analyst, not just a tool user.

This is just the begining

As I look back at my first steps in Power BI, I realize something important.
I didn’t start by building dashboards. I started by cleaning messy data, fixing inconsistencies, and learning how to think logically about information.
Then came DAX where numbers stopped being just numbers and started becoming decisions. And finally, logical functions taught me that data is not just something you display, but something you interpret.
What I thought would be a journey about visuals turned out to be a journey about thinking.
And I am still at the beginning. Every dataset I touch now reminds me of one thing, before insights, there is understanding. Before understanding, there is preparation.
Power BI is not just teaching me how to analyze data it is teaching me how to see it differently.