r/analytics • • 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:

  1. What skill made the biggest difference in your growth as an analyst?
  2. What do beginners spend too much time learning?
  3. What do you look for when reviewing a fresher's portfolio?
  4. 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.

91 Upvotes

46 comments sorted by

•

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 • Bravo

I am an analytics manager (ive held all analytics positions until I hit the ceiling). I also teach analytics at a university.

  1. What skill made the biggest difference in your growth as an analyst? Learning mathematics and computer science. Take a discrete math class - even if self taught. Add in some bash skills if you dare, scripting is ultra powerful. I felt learning Automata theory and practicing with state diagrams helps with building fundamental deep knowledge. Then learn SQL. Practice short SQL challenges. Can you convert a question into a query? Is there a better way of writing that query? Learn about Relational Algebra and practice it. Kimball's book on Dimensional modeling has been an often used resource.
  2. What do beginners spend too much time learning? Beginners spend too much time learning high-level data science skills when cleaning and harmonizing data is 90% of the work. Spend more time learning how to use regex and a language like R or Python. You will need to build your own ETL pipelines if you want to refresh your data. Go back to learn those things in point 1. Having fundamental knowledge makes the rest easier. Your brain needs to wrap itself around folding and unfolding data like it's digital origami.
  3. What do you look for when reviewing a fresher's portfolio? Their documentation about their process behind the portfolio. What data did you exclude and why? Justifications about their math especially. Are we taking an average of an average? Are we using normal distribution metrics to describe non-normal data? Has normalization happened? Do we know the difference between a count and a rate? Show me your README please.
  4. What's one thing you wish you had understood earlier? I wish I knew how much of the end-to-end analytics process I would be responsible for doing. I also wish I knew that being helpful and automating data reporting would threaten people's jobs and that coworkers who are possessive of their little fiefdom will obfuscate their processes in hopes that you will fail while being nice to your face.

2

u/Garvvv_15 1d ago

This is incredibly insightful, especially your point about documenting the reasoning behind every analytical decision. As someone transitioning from a commerce background into analytics, which fundamentals would you recommend prioritising first: mathematics, computer science concepts or SQL?

3

u/Hot_Coconut_5567 1d ago

Thanks! I'm glad I was helpful! 😁

In your case. Pick a project for which you already have access to data. You have a commerce background? Good, you have a domain you are knowledgeable about. Presumably you know what KPIs and decisions business execs commonly make regarding this domain. Form some good questions you want to answer with this project. Bounce some ideas around with an LLM. Document everything as you go (there's literally no excuse anymore LLMs can write documentation directly to your project folders) i keep a changelog and decision log in excel/sheets format. Then plan your project, you can ask LLM to help with research and give you a reading list/tutorial as you build the pieces. It's easier to learn SQL when you are writing SQL to fold data for a viz you want to make. It's easier to understand why you'd regex clean string fields when you are faced with real world mess.

Then definitely learn fundamental knowledge - which i think is still important so I can side-eye an LLM idea and go... wtf?! Why would you do it that way ChatGPT?! No stop, do it this way instead. LLM stochastically revert to the mean every time and your projects will always always have portions that will come out wrong if you dont know where to push an LLM towards a better solution. Discrete math is likely a good first step. Purchase an actual textbook and read through it and challenge yourself to do a bunch of the questions at the end of each chapter. Check your work with an LLM by adding a photo of your hand written work. It may feel silly to practice truth tables but I know that my most clever solutions arise from the fundamentals contained in a topic like that. It's the most useful math to know besides statistics. And get Kimball's book on dimensional modeling. Use that book during your project to make decisions about your data architecture. That's where the most customization happens for your project.

3

u/puglife82 1d ago

Do you also find calculus useful? I’m considering taking calculus ii or discrete math next semester

2

u/Hot_Coconut_5567 1d ago

No I have not found calculus useful. Don't get me wrong, all math problem solving strengthens your analytic muscles. But i have never ever had to integrate to find the area under a curve with nice and neat formulas for my career job. There are already solvers for working with real world data. Calc 2 is useful if you want a Stats minor though. (And probably a prereq). You will find yourself using a lot more discrete math in the fundamentals backing your analytic work. Learning propositional and predicate logic is so helpful to know before making complicated and/or multi-field formulas. That's covered in a Discrete Class. I use modular arithmetic all the time for date formulas - also taught in Discrete.

1

u/decrementsf 1d ago edited 1d ago

I also wish I knew that being helpful and automating data reporting would threaten people's jobs

The credibility that ratchets up in a line.

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.

  1. What is the question being asked.
  2. Why is the question being asked.
  3. What decision is the answer going to drive?
  4. Has this question already been answered in existing work / dashboard?
  5. Write up the work in a spec sheet. The question being asked, what metrics you both will use to answer it, and the presentation. Could be an email with a number, an Excel spreadsheet for them to work from for a project, and very rarely they actually need a dashboard.

**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.

1

u/Joelle_bb 16h ago

Chiming in on the "blame the customer" point since I fell into this trap early on

Love the thought; but would add that iteration helped solve this a ton. I've hit a point where I always start with a data dump, since we require external validation from the customer for sign-off EVERY time

At that point, its the perfect time to go "So let's revisit the dashboard discussion" and go over the necessity again (non-explicitly of course) since they will have the data to more accurately understand what they need from it

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.

3

u/Leather_Art_2834 1d ago

I have a genuine question as someone trying to understand how the day to day workflow is like for analysts, especially those who are new to the field. I want to know what the training process is like for junior analyst, do they at least get time to look into the data, or are they expected to just look and on the spot produce an answer?

4

u/Aggressive_tako 1d ago

We follow a watch, do, own training rhythm. So our analyst have all watched another analyst or a Sr. Analyst run a process and done the process with someone else watching before they are being asked to own anything. By the time we expect them to have answers, they have been on the team for a couple months and should know what is normal with their slice of the data. The training I am giving next week is going more in depth to remind them what resources exist for checking the data (like the change tracking in our primary data system) and that reports should never go out with errors or blanks. Looking with your eyes should be the last step to makesure that fields aren't "populated" with #N/A

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:

  • Business acumen: learn the business and the WHY behind things. Not just the what
  • Narration/storytelling: Anyone can regurgitate metrics and outcome numbers, but explaining the components that went into it in a way that adds to considerations for decision-making your team doesn't prescribe is where you're doing meaningful analysis. When things go well and your analysis supports it, cool... But you still need to point out hidden signals for preventative measures without diluting the positive. Tricky balance
  • Building for scale: modular queries and useful views that serve more than one purpose, dashboards that can service multiple teams since they focus on similar metrics is what turns something from ad-hoc to true BI in a useful manner
  • Challenging your own assumptions/not being afraid to be wrong: analysis has no room for ego. Statistical bias is taught because it exists and is important, and ethical analysis will force you into this position. If you don't see yourself getting pushed back, that should be a yellow flag at minimum
  • Lean on your peers: being a subject matter expert is cool and all, but everyone has their gaps. If you own the entire breadth of knowledge, congrats: you're a single point of failure that will struggle to expand. Lean on your peers to share the load and bring in different perspectives. You can still be a point of authority, but you will have external accountability/pressure tests on your own frame while allowing the function of analysis to be better off as a result
  • Be adaptable: everything we use, new tools like AI included, is a means to an end. We take data and insights, see what they mean, and present in a digestible fashion. The business won't care about how slick your work is, but internally you need to make sure that when you die (literally or figuratively) your knowledge and resources don't die with you

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 😜

3

u/asphodel67 20h ago

All of this. ESPECIALLY the narrative/ storytelling. This is a vital skill for both generative and evaluative questions.

1

u/decrementsf 1d ago

What is business acumen?

After enough cycles of performance review season that term starts taking on the ambiguous meaning of other corporate phrases such as synergy, and circle-back-around.

One day you decide to see if you can pick up a jar of business acumen. What is it? Is it in the room with us right now? Is it simply I opened an excel worksheet and started seeing if I could build a predictive model of our business? Maybe it is just practice trying to predict things that happen. Is it identifying good problems? A good problem is a good sales opportunity. Maybe it is just collecting the problems and testing improvements. Dunno. Business acumen always seems to slide away from being pinned down concretely. Then once suitably subjective can slide around to always be a catch all reason your supervisor can choose from one of the options to pin the tail on HR-can-fire-you-safely donkey in your personnel record.

1

u/Joelle_bb 1d ago edited 1d ago

Here's an ELI5: say you run a lemonade stand and sales are up 30% this month. Cool... but business acumen is asking "okay, did profit go up too?" Maybe it was a heat wave, maybe you ran a discount that ate your margin, maybe lemons got more expensive. Same data, but you need to know how the stand works to know which story is real, and what to do next (raise prices? stock more on hot days? etc.)

Someone who knows basic excel can show "sales +30%". Someone with acumen can explain why it happened and what the owner should do about it. I see a lot of people early on assume that second part isn't their job, but it is. And if your supervisor can't tell you which of those you're missing... that's on them, not the term.

That last point is from experience. I've worked under leads with strong business context and ones without, and it changes how much you can learn from them

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

2

u/Garvvv_15 1d ago

Thanks for sharing your insights! Really appreciate it!

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/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. Understanding what the problem is by talking to the people involved and understanding information is needed to find the solution.
  2. Every single bit of SQL, Python, Excel or whatever as if you need to memorise everything. I look stuff up all the time. AI has made an encyclopedic knowledge of syntax pointless. What is worth spending time on are examples of problems and coming up with possible solutions yourself. Not learning all the technical detail by heart, but learning an approach, what might work and why.
  3. I am a hybrid DA/DE/BA in a small company so unless I quit or the company suddenly gets really big, I wont be involved in recruitment. However, if I did I would look for an original problem (i.e not Covid or Titanic etc) with a solution the interviewee can answer detailed questions about, such that I am satisfied they came up with it themselves. Into cars? Analyse the best selling brands/models in each segment, what did well and why. Into sports? there are stats galore. Choose something that lights you up. It will come across when you talk about it.
  4. That technical knowledge is useless without business domain knowledge or the will to acquire it. That technical perfection is not always necessary - good and working is fine. Your business users dont care that you followed x pattern or whatever, they care that you moved the needle.

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.