From Idea to Insight: My Data Analytics Project Journey

How I Identified a Real World Problem Worth Analysing

 Lately, I’ve been noticing a shift in how people shop for everyday items.

More and more people are turning to quick commerce platforms like Instamart for convenience. Groceries, snacks, essentials everything arrives within minutes. It’s fast, efficient, and becoming a habit.

But at the same time, I started wondering about something else.

What’s happening to small local shops?

The ones run by a single owner. The ones where everything is within reach, and service is quick because they know their store inside out. These shops used to be part of everyday life.

Now, it feels like fewer people are walking in.

This made me curious to explore the problem from a data perspective.




I want to understand:

  • Are customers actually shifting towards quick commerce?
  • What factors are influencing this behaviour?
  • What impact could this have on small retailers over time?

Blog Series: From Idea to Insight

This post is part of a series where I’ll document my full data analytics journey step by step:

  1. Identifying the problem
  2. Finding and collecting relevant data
  3. Understanding data ethics and GDPR
  4. Cleaning and preparing the data
  5. Exploring patterns and extracting insights
  6. Forecasting trends
  7. Final recommendations and conclusions


In the next part, I’ll explore how I find relevant and reliable datasets to begin this analysis.








Disclaimer:
This project is an independent analysis using publicly available datasets. The insights and interpretations are exploratory and intended for learning purposes, not as definitive conclusions or business advice.

Comments

Post a Comment

Popular posts from this blog

What Senior Data Analysts Actually Do (Beyond Dashboards)

  When people hear “data analyst,” they often imagine dashboards, SQL queries, and spreadsheets. Those skills are important. But at a senior level, the role moves far beyond building reports. A high level data analyst designs systems. They create structure. They ensure that data flows cleanly from source to insight, and that insight translates into better decisions. The focus shifts from producing outputs to building reliable decision infrastructure. This difference is subtle but critical. From Reporting to Decision Architecture At an operational level, analysts answer questions. At a strategic level, analysts define how questions should be answered. Senior analysts think in terms of: What decisions does the organisation need to make? Which metrics truly represent performance? Are definitions consistent across teams? Can this analysis scale beyond a one off request? Instead of reacting to ad hoc reporting needs, they establish frameworks that prevent fragmentat...
Read more

The Future of Food Safety Tech: How AI Driven Transparency Can Transform Global Consumer Health

Image
  Extending the FoodSense concept beyond India through responsible data systems and applied machine learning The global food safety challenge Food safety challenges are not confined to geography. They appear in different forms across countries, but the underlying risks are shared. Allergen exposure remains one of the most preventable causes of severe food related harm, yet communication failures continue to occur. Expiry dates are frequently misunderstood by both consumers and businesses, contributing to avoidable illness on one end and large scale food waste on the other. These issues place sustained pressure on public health systems worldwide. What varies between regions is not the existence of the problem, but the maturity of the systems designed to manage it. Effective food safety today requires more than compliance. It requires visibility, consistency, and decision support at the point where food is prepared, stored, and consumed. Why AI is an appropriate tool in this do...
Read more

Inside the Smart Food Safety System: Architecture, Data Pipelines, and ML Models Explained

Image
  A deep technical walkthrough of the data pipelines, algorithms, and design decisions behind my food safety prototype Architecture overview Once the prototype moved beyond experimentation, I needed a structure that could survive real-world input. Food labels are noisy. OCR is imperfect. Safety decisions cannot rely on a single model prediction. The architecture reflects that reality by separating concerns clearly and defensively. At a high level, the system flows as follows: Image / Label Input ↓ OCR + Text Parsing ↓ ETL + Validation Layer ↓ Feature Engineering ↓ Freshness ML Model ↓ Rule - Based Safety Engine ↓ Human - Readable Output Each layer can fail safely without corrupting the next. Data Engineering layer (ETL, validation, anonymisation) This layer exists to answer one question: Can this data be trusted enough to make a safety decision? ETL ingestion Raw inputs enter the system either as: OCR extracted ...
Read more