What Does a Data Analyst Actually Do?
I wake up in the morning, do that frog’s kingdom business we used to write about in primary school, open Power BI, and boom — insights everywhere.
No. I’m kidding.
Most days don’t start with dashboards magically answering questions. They start with conversations. Meetings. Follow-ups. Clarifications. And a lot of “what exactly do you mean by this number?”
A big part of a data analyst’s job is understanding user needs. That usually means sitting with people across departments and learning how they think about data. In one of my previous roles, I found myself in frequent meetings with the finance team. Over time, I became fluent in terms like “inclusive of VAT,” “gross margins,” and “reconciliations.”
Those weren’t just finance buzzwords. They were the language behind the numbers. And without understanding that language, any dashboard I built would have been misleading at best, useless at worst. And if I were to be perfectly honest, I’ve built many unused dashboards.
A health data analyst might not spend their days debating VAT or margins, but the principle is the same. Whether it’s finance, sales, operations, or healthcare, data doesn’t exist in a vacuum. It lives inside people’s workflows, constraints, and decisions.
And that’s the part of data analysis no one really talks about.
The Misconception About Data Analysts
There’s a popular image of a data analyst as someone who spends their day writing SQL, building charts, or tweaking dashboards. While all of that happens, it skips the most important step: why the analysis is needed in the first place.
Before the first query is written, there’s usually a conversation. Someone is confused. Someone needs to make a decision. Someone doesn’t trust a number they’ve been seeing in reports.
The analyst’s job is to slow things down and ask: What are we actually trying to answer?
What a Data Analyst Actually Does Day to Day
Understanding the question
This almost always starts with conversation. Stakeholders rarely come with perfectly framed analytical questions. Part of the job is translating business language into data language — and then translating the answer back again.
Working with messy data
Once the question is clear, the data rarely is. Cleaning, validating, and reconciling numbers takes time, but it’s essential. If the data doesn’t align with how teams understand their operations, the analysis won’t be trusted.
Analyzing and exploring
This is where tools come in: SQL, Python, Power BI — but they’re guided by context. Knowing how finance defines revenue or how operations defines “delivery” changes how you query and interpret the data.
Building reports that make sense to humans
Dashboards aren’t built for analysts. They’re built for people who need to act. That means choosing clarity over complexity and always asking:
Would this make sense to someone outside the data team?
Explaining, refining, repeating
The first version is rarely the final one. Feedback loops matter. Good data analysts listen closely, adjust quickly, and aren’t defensive about changing their work.
It’s Less About Tools, More About Translation
Yes, data analysts use Excel, Power BI, SQL, and Python. But the most important skill is translation; between data and decision-making, numbers and nuance, accuracy and understanding.
A technically correct answer that no one understands might as well be wrong.
Why Data Analysis Work Matters
When done well, data analysis builds trust. Teams feel confident making decisions because they understand the numbers behind them. In healthcare, finance, operations, or sales, that trust can shape outcomes in meaningful ways.
The impact isn’t just in the charts.
It’s in the conversations those charts enable.
Who Thrives as a Data Analyst
If you enjoy asking questions, listening carefully, and making sense of complexity, data analytics can be deeply rewarding. If you prefer clear instructions and fixed answers, it can be frustrating.
This role sits at the intersection of logic and people.
You need both.
Final Thought
So when someone asks what a data analyst actually does, I don’t say “I build dashboards.”
I say:
I listen. I ask better questions. And then I use data to help people see clearly.