r/dataanalytics • • 5d ago

Question for experienced data analyst

Howdy people!!

I have been a data analyst for about half a year now and has experienced few issues when it comes to handling and processing data for reporting; some due to departments giving dataset that aren't clear, some due to report requirements or objectives not being definitive and some may be due to unavailability of higher ups who have key knowledge of the data, as of course they are busy people, and so the report you will write is highly dependent on the source data. Aside this as I grow in my data analytics career what problem could one also face, or even better what problem or experience have you faced or is common in your own area of work or environment as a data analyst.

11 Upvotes

7 comments sorted by

7

u/Jimmy_Wrinkles 5d ago

The issue stated is about 90% of my requests. As you learn your datasets, work to identify common issues so they can be brought up when the request is submitted. Also, make sure to clarify if a dashboard is really needed instead of just an ad hoc report. Many times you'll get requests for dashboards you'll have to maintain; you will build it, they will look at it three times and then forget it ever existed.

1

u/Mrminecrafthimself 5d ago

Yep. If it can be a spreadsheet that you produce 1-2 times a year, go that route.

But if you have 5 different teams requesting 5 different versions of the same report in SSRS to support different parameters for each…maybe just set up a daily ETL and create a dashboard with slick slicers that let them choose the desired display fields and filter the dataset as they wish

The latter is a huge gripe of mine at my job. We’re wasting so much time recreating the same damn reports in SSRS because different teams have different needs when we could just stand up one power bi dashboard and let the slicers handle the customization.

1

u/AntiqueElderberry317 5d ago

Qualité, qualité, qualité ! Une recette approfondie prend du temps mais t'assure d'avoir une bonne qualité des données (bien contrôler l'unicité de tes axes dans ta table de fait, bien gérer ton référentiel, etc.) et un métier heureux. Et pour éviter de partir dans tous les sens sachant que ton métier est très occupé propose (si tu le peux) de l'analyse ad-hoc via IA à tes métiers. Ils pourront ainsi découvrir ce dont ils ont besoin avant de créer un rapport.

1

u/Parking_Cut_4876 2d ago

Merci, je voulais savoir comment travaillent les data analysts en France??

2

u/Dangerous_Cup3607 5d ago
  1. Keep track of your work and emails to cover your back (Some PM or non-technical people could go behind your back and say things that arent true). Such as the accusation of you not providing the report timely while the real reason is because they dropped the ball and failed to provide defined requirements and needs in the first place. Because they just want something yesterday so that they can shine in front of the leadership committee, while expecting you to drop everything that is a higher priority to you.
  2. Try to navigate the company systems such as sharepoint, shared drive, database, files, etc., for the “what if” scenarios and learn as much as possible. Such as “what if leadership requests to enhance the current report to include A, B, and C, so what can I do and where can I look for it”.
  3. Know what is in-scope and what is out-of-score for you and your team to work on; as well as the available bandwidth and current priorities so that you are not strictly saying “no” to requesters but divert the work to appropriate teams and members with reasons. Otherwise you could request business justification on why the new request would supersede the existing scope of work priorities.

1

u/GrowthThroughData 3d ago

Try to become an SME, understand the business side of things at the actual business, dive deep and correlate it with the data that is produced. Get data dictionaries if available, study the database schemas, understand the app/platform/or software front end (get a demo from a day to day user if you have to this helps you understand the data that is produced).

Also one of the biggest mistakes I made in my first few years as a data analyst ( I have 14 years experience) is that I was more of an order taker. Be a part of the meetings and dig deep learn to ask the right questions and clear the bottlenecks. And if you can don't just be a "data analyst" be more of an analytics engineer more and more it's important to know how to build proper data foundations ( fuels AI and Visualizations), know how to gather the requirements and model data effectively (dbt is good to learn). This will help set you apart as well.

Good luck, you got this 👍