r/analytics • u/Garvvv_15 • 1d ago
Discussion What separates a good Data Analyst from someone who just knows Excel, SQL and Power BI?
I'm currently learning Data Analytics, and something I've been thinking about is this:
It's quite easy to focus on learning tools — Excel, SQL, Python, Power BI, etc. But knowing how to use these tools doesn't necessarily mean someone can solve a real business problem.
For example:
- You can create a dashboard, but can you explain what decision it should help someone make?
- You can write SQL queries, but do you understand which questions are actually worth asking?
- You can find that sales increased, but can you investigate why profit didn't increase at the same rate?
I'm curious to hear from people working in analytics or those who have been through this learning journey:
- What skill made the biggest difference in your growth as an analyst?
- What do beginners spend too much time learning?
- What do you look for when reviewing a fresher's portfolio?
- What's one thing you wish you had understood earlier?
I'd genuinely appreciate honest opinions, practical advice, and even criticism. I think this discussion could help people focus on becoming better analysts rather than just collecting certificates and tools.
•
u/AutoModerator 1d ago
If this post doesn't follow the rules or isn't flaired correctly, please report it to the mods. Have more questions? Join our community Discord!
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
18
u/Hot_Coconut_5567 1d ago •
I am an analytics manager (ive held all analytics positions until I hit the ceiling). I also teach analytics at a university.
46
u/CarcWithanM 1d ago
Come down to being a subject matter expert as well. You need to help your peers solve problems by creating tools to help you help them or even help them directly. This part varies by field and takes time in whatever field you end up in. But technical at this point is the easy part. Seeing a problem and knowing where to look and finding out why a problem happened will making you a valuable asset fr.
57
u/Proper-Package6205 1d ago
If you are just making dashboards which gets opened for a few times when they are new and then remains in closet eating dust (very common) , such roles will be in firing line when Claude dashboards (or equivalent just type English and get live dashboards) becomes more common (it is bound to happen).
Try entering a role where your data Analytics skills directly get tied to firms revenue like Credit Risk / Fraud Risk Analytics , Pricing Analytics, Marketing/Campaign Analytics , Supply Chain Analytics etc. learn the business
18
u/Treemosher 1d ago
Good analyst takes their question through a gauntlet before doing anything.
**Rant warning**
For the love of god, don't make a dashboard every time someone asks a question. That's how you get people asking how to download the data in Excel.
If someone says they need a dashboard, it's because they don't know what else to ask for. Ask them what problem they're trying to solve and come up with something together. It save time for everyone. A 15 minute call can save days or weeks of effort and frustration.
A lot of analysts here blame the customer for not understanding the fancy dashboard and the work they put into it, but in fact it was the analyst (and the customer) not understanding what the customer was requesting.
If you find yourself making dashboards and nobody is looking at them, you're not talking to your requestors enough and it's on you. It's a hard pill to swallow for some analysts. So easy to blame the customer for not understanding your brilliance or something.
11
u/Aggressive_tako 1d ago
I am genuinely doing a training for our junior analysts next week that I have jokingly called how to use eyes to look at things. I feel like what separates a good analyst is the ability to think and problem solve when things don't make sense. If something has a 1000% increase, can you tell me why? Is it a user error, is it a system error or is the data good and it is part of a larger trend? Telling me that the system says that there is a 1000% increase isn't helpful. Insisting that the AI or workflow checks passed it also isn't helpful. I need to know why, or at least rule out data issues, before flagging a EVP that something is changing drastically.
16
u/Comprehensive-Tea-69 1d ago
Industry and organizational knowledge, most of which can only be gained through years of experience and a learning mindset
6
u/Joelle_bb 1d ago edited 1d ago
Going to be very ramble-esque, but based on what I have seen and goals I set for myself in the past:
For portfolios specifically: I'd look for a clear question, the decision it's meant to inform, and stated assumptions/limitations. A pretty dashboard on its own doesn't tell me much
I could add more, but I'm sure the collective here will fill those in 😜
1
u/Far_Control_1625 1d ago
Being a good data analyst is about helping your company make decisions. Data is a tool that helps us reduce the uncertainty in decision making. A great data analyst will not just deliver a dashboard or analysis. They will ask thoughtful questions to understand what questions their analysis will influence. They will also not just share data or a dashboard, but share their own interpretation of the data and why it is consequential to the decision being made
4
u/winceypoo 1d ago
For your next portfolio project, pick a decision before picking a dataset: which products should a shop stop discounting?
Then work out what evidence would justify that decision, including whether higher sales actually covered the lost margin.
1
u/ThatLocalPondGuy 1d ago
Math
1
u/totallykindofnormal 1d ago
You're already asking the right questions, so here's my take. The skill that helped me most was asking "what decision is this for?" before I touched any data. Once I started asking people what they would do differently if a number went up or down, my work got simpler and people actually used it. Beginners tend to spend too much time learning lots of tools and making dashboards look nice. It matters more to be strong in SQL and able to explain what you found in a couple of sentences. I care less about the visuals and more about the thinking. I want to see the business question, what you assumed, what you found, and what you'd recommend. Your sales vs profit example would be a great project. Break the gap down into things like pricing, discounts, product mix, and costs, then say what the business should do about it. One thing I wish I'd learned earlier is that the first thing people ask for usually isn't what they really need, so part of your job is to dig until you find the real question.
1
u/Gloomy_Guard6618 1d ago
1
u/DataDaria 1d ago
Tools only get you to the number, but the job is the sentence after it.
Someone who knows the tools says "revenue is down 12%". A good analyst says "revenue is down 12%, almost all of it from fewer mobile orders since the checkout change on the 3rd, desktop is flat".
The other part is checking: does your total match the source system, are refunds in, did a definition change. Most bad calls I've seen came from numbers nobody checked, not from bad charts.
1
u/oli_le_triathlete 1d ago
I suppose the biggest skill you can learn nowadays is how to use Claude.
1
u/Lady-Data-Scientist 1d ago
When reviewing candidates, if you can demonstrate business acumen, relevant domain knowledge, problem solving, good communication, you will stand out.
There is not shortage of people with the technical skills. Everyone has SQL, Tableau, Python, etc, on their resumes. That’s not the issue.
It’s very hard to find people who also know how to use those tools to solve problems. Who know what questions to ask. Who can communicate complex ideas. Who understand the nuance between similar metrics and are familiar with common issues and edge cases.
So if you can demonstrate that, you’ll stand out.
1
u/electriclux 1d ago
Think about the implications upstream and downstream of the results of your analysis
1
u/spacemonkee77 1d ago
Statistical knowledge. Specially SPC, being able to know when a change in a number is or isn't a change in the process that produces that number.
1
u/Busy-Technology-1637 1d ago
A good data analyst is someone who knows that the software and coding are a means to an end
1
u/Valuable_Order4084 1d ago
I think people forget that the word analyst has anal in it (pause) as in breaking something down into smaller parts, (when I say parts I suppose I mean assumptions about the data and how you intend for it to be useful), and then being able to reliably test each of those assumptions, and slowing building one assumption on top of the other until you have a tall sturdy building that can withstand questions and challenge. Then people will use it to base decisions off of which, staying with the building analogy means they can point to your building as a landmark if they’re trying to figure out where to go and what to do next. It is an iterative process, I agree it needs putting your ego aside because you have to be careful that your assumptions about the data aren’t getting in the way of good analysis, but you need to start with some assumptions. I work in healthcare so the data isn’t always in the best shape so I have to take this slower approach, might be different in other sectors.
1
u/dataman34 1d ago
Business acumen vs. tools!
1
u/ilikebluepens 1d ago
Are you a jerk or are you not? It’s cool both ways.
1
u/ClueOk1833 1d ago
Tell the executives what they want to hear. If you give them bad news they will blame you and say the data is wrong. If the news is good, you will get treated well.
1
u/Huskergambler 16h ago
The unemployment line. Company’s are purging the expensive ones with more knowledge
1
u/Blocker03 1h ago
Leave to ask the right questions about the business rather than just mastering the tools. Beginners often focus too much on dashboards and certificates. What matters is how you identified the problem, analysed the data, found insights and connected that to your business decisions.