avatarSonali Yadav

Free AI web copilot to create summaries, insights and extended knowledge, download it at here

1236

Abstract

data-analyst-1b2915fa548d">It is not the results but the way analysis connects to the problem in the broader context clearly enabling the stakeholder to take a decision.</a></li><li><a href="https://readmedium.com/how-data-is-misinterpreted-8551e6cca83e">Understanding the statistical construct of the data, and the biases involved in the question delivers a robust analysis.</a></li><li><a href="https://bootcamp.uxdesign.cc/what-every-analyst-needs-to-understand-about-data-and-analytics-92dcb859d89c">It is the clarity of question that drives an analysis.</a></li><li><a href="https://bootcamp.uxdesign.cc/the-fine-nuances-of-storytelling-with-data-5ccdbb79727">Interpretation of data depends on how well you understand the objective of your stakeholder.</a></li><li><a href="https://bootcamp.uxdesign.cc/10-ways-to-make-your-data-tell-a-compelling-story-e33ab0f8428a">Simplicity in the results drives an action, produces confidence in the analysis.</a></li><li><a href="https://bootcamp.uxdesign.cc/what-15-years-business-analysis-taught-me-f89e25b1e36b">Analysis is not complete until it supports a next step.</a></li><li><a href="https://readmedium.com/not-your-typical-product-manager-im-the-chief-analyst-d207fb38b3c4">Your role

Options

is not to make data ready or produce fancy charts, you are responsible for making it usable.</a></li><li><a href="https://bootcamp.uxdesign.cc/challenges-faced-by-every-data-person-117c22c57f7d">The role of helping stakeholders to ask the right questions is very undermined.</a></li><li><a href="https://bootcamp.uxdesign.cc/5-first-principle-tenets-that-can-get-you-way-better-in-your-analysis-8df8a22c0988">Break your problem in its fundamental and basic parts, to address it clearly.</a></li><li><a href="https://bootcamp.uxdesign.cc/15-overly-used-jargons-that-high-performers-avoid-68ea3836e7fa">Use easy to understand language, refrain from using jargons that help no one.</a></li><li><a href="https://bootcamp.uxdesign.cc/8-ways-to-make-your-data-analysis-excellent-00c95700a244">Evaluate the problem from top down for understanding how it affects or gets affected by the broader organizational context.</a></li></ol><p id="681a">And remember, you are not responsible for making the fanciest models and presenting cool charts. You can do that totally.</p><p id="b60a">But your primary role is make the findings into an insight instead of “an interesting observation” that’s not really useful or implementable.</p></article></body>

11 lessons for doing a successful data analysis

Analysis has lot to do with what you ask than what you deliver. Or in words of Stephen R. Covey: “Seek first to understand, then to be understood.”

Photo by Akhilesh Sharma on Unsplash

There’s no such thing as a perfect answer. You must have heard this a bazillion time. And it is true.

Well, it is especially true in case of analyzing data.

Because there are no bad answers, only bad questions.

Over the last many years, i have failed, learnt, tried and succeeded in working on some of the best analytics projects.

Regardless of the title I held, my goal was always to enable an action. So below, i am listing a few of my learnings over the years in the ever-dynamic field of analysis.

  1. It is not the results but the way analysis connects to the problem in the broader context clearly enabling the stakeholder to take a decision.
  2. Understanding the statistical construct of the data, and the biases involved in the question delivers a robust analysis.
  3. It is the clarity of question that drives an analysis.
  4. Interpretation of data depends on how well you understand the objective of your stakeholder.
  5. Simplicity in the results drives an action, produces confidence in the analysis.
  6. Analysis is not complete until it supports a next step.
  7. Your role is not to make data ready or produce fancy charts, you are responsible for making it usable.
  8. The role of helping stakeholders to ask the right questions is very undermined.
  9. Break your problem in its fundamental and basic parts, to address it clearly.
  10. Use easy to understand language, refrain from using jargons that help no one.
  11. Evaluate the problem from top down for understanding how it affects or gets affected by the broader organizational context.

And remember, you are not responsible for making the fanciest models and presenting cool charts. You can do that totally.

But your primary role is make the findings into an insight instead of “an interesting observation” that’s not really useful or implementable.

Data
Data Science
Analytics
Data Visualization
Storytelling
Recommended from ReadMedium