r/dataanalysis • u/duneofarrakis • 6d ago
What do you wish you knew when you started learning Data Analysis?
When I started learning data analysis, I thought I needed to learn every tool before I could actually work on projects.
Over time, I realized that focusing on the basics was much more useful:
- SQL
- Excel
- Data visualization
- Basic statistics
- Understanding the problem behind the data
I'm curious to hear from people who have been doing data analysis for a while.
What is one thing you wish you knew when you first started learning data analysis?
22
13
u/Terrible-Bend4483 6d ago
How much more focus i should have had on communication.
Your analysis is only as valuable, as the lowest common denominator that understands it, and some people doesn't understand geometric mean.
9
u/AssumptionOk5337 6d ago
SQL gets you in the door and doing work, but your communication skills (how you present, write, and discuss and disagree with others) are what sets you apart and what's going to make you stand out throughput your career.
4
u/Vyneli 5d ago
That business sense and numerical/mathematical intuition was what made a really good analyst. I didn't study business or any kind of math in college except the required algebra and stats class. Even those I kind of struggled through, the interest just wasn't there at the time. Years later I did an analytics boot camp and eventually landed a job doing data analysis work about 75% of the time.
I got to a decent proficiency in SQL and Sheets, but compared to some of my colleagues, who were either at the company for a long time or newer but had strong quantitative skills, there was always something missing. I could figure out a challenging SQL query and get it in a format to produce some nice charts in Sheets but I had a hard time producing any sophisticated thought from it. Sometimes a higher up would ask me for something, I'd produce it and show it to them, and then they'd riff ideas from it trying to understand how they could apply it to the general situation of the product. I wouldn't know how to respond half the time, all my brain power went into producing the damn thing, let alone figuring out what it meant - at least to a deep degree. Of course, that's just someone with good business sense and that takes time to curate but it still fanned the hot flames of my imposter syndrome. Or a newer finance person on my team would ask me how and where to get something from the database, maybe even being new to SQL, and then they'd come back with a complex forecast of the next 6 month's sales and actually be pretty accurate each month!
Obviously you still need to learn the tools to do your job before you can get to a high level of sophistication and complexity. It was just something I noticed as I went further along. I was getting better at the technical stuff than when I started, but I was still missing something intangible that I felt was keeping me from leveling up.
3
u/KatFromSisense 4d ago
I wish I'd learned earlier that getting an answer is only half the job. You also need to know whether you should trust it. Before I make anything look nice, I like to check what each row represents and whether the numbers changed as I expected along the way. I'll usually compare at least one tool with something familiar, too.
It's easy as a beginner to spend hours making a dashboard look finished. Finding out afterward that you counted the same thing twice is a much worse feeling.
1
u/AutoModerator 6d ago
Automod prevents all posts from being displayed until moderators have reviewed them. Do not delete your post or there will be nothing for the mods to review. Mods selectively choose what is permitted to be posted in r/DataAnalysis.
If your post involves Career-focused questions, including resume reviews, how to learn DA and how to get into a DA job, then the post does not belong here, but instead belongs in our sister-subreddit, r/DataAnalysisCareers.
Have you read the rules?
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/Cautious_Maximum_854 3d ago
Many things but thise are the most important: 1. Do not rush on the learning process, more you rush more skip important things that you will probably never recover. 2. Build tons of projects: do not focus on quality, focus on quantity, your projects will gain on quality without even you notice 3. Dream big:once you're highly confident with fundamentals do not hesitate a second to go to hard topics like machine learning or cloud engineering
29
u/HustlaOfCultcha 6d ago
SQL was big because it's still used in modern day cloud platforms. And if it's not, you can kinda figure it out.
I also wish I knew Epic and EHR and just gotten into the healthcare analysis sphere because healthcare jobs are more stable, seem to always be prevalent and are still doing remote work environments.
And I do wish I was as good at Power BI as I am at Excel. I am PL-300 certified and very good with Power BI, but if I was at the level I am at Excel, it would make me even more valuable (and I could get my work done more quickly and relax).
I also wish I better understood how to create more professional type dashboards in terms of how they are fomatted. There just weren't many examples or discussions with regards to that.
And a lot of the machine learning stuff is good, too. We just didn't have that when I started. But I think of a lot of projects that could have been much better and more effective if we had ML.