Ayush Bhatnagar | IIM Kashipur MBA (Analytics) 2025-27 | Business Analyst Intern, Tata Steel Downstream Products Limited
When I received my internship offer from Tata Steel Downstream Products Limited, I had a pretty clear picture of what my summer would look like.
I imagined myself spending long hours with Excel sheets, SQL queries, Power BI dashboards, and datasets. As a Business Analyst Intern, I thought my job would mostly revolve around analyzing numbers, building reports, and presenting insights.
I wasn't wrong, but I was only seeing half the picture.
Within the first few weeks, I realized that dashboards are actually the easiest part of business analytics. The difficult part is understanding the business behind those dashboards.
Every metric exists for a reason. Every number tells a story. And every insight is only valuable if it helps someone make a better business decision.
That realization completely changed the way I approached my internship.
The Day I Realized Data Doesn't Speak For Itself
My project focused on GenAI-based RM Ordering & Tracking Analytics, where I worked with ordering and receipt data to improve visibility into the raw material ordering process.
Initially, I believed the challenge would be technical: cleaning datasets, creating compliance metrics, and building dashboards.
Instead, most of my time went into conversations.
I found myself discussing ordering workflows with stakeholders, validating assumptions with business teams, understanding why certain exceptions occurred, and asking questions that never appeared in textbooks.
Looking at twelve months of ordering and receipt data also opened my eyes to how interconnected business functions really are.
A delayed receipt wasn't simply "late."
It could be caused by production planning, inventory availability, transportation constraints, changing priorities, or multiple factors working together.
That's when I understood something I'll probably carry throughout my career: companies don't value dashboards because they look visually impressive. They value them because they help solve real business problems.
The Mistake That Changed My Approach
One of my biggest learning moments came just before an important review meeting.
I had spent several days building compliance metrics for RM order fulfillment and was fairly confident that everything was ready.
Before the meeting, I decided to do one final validation.
That's when I noticed something strange.
Some compliance percentages for a few SKUs looked unusually high.
For a moment, I hoped it was simply a data quality issue.
Unfortunately, it wasn't.
After digging deeper, I discovered that the mistake was mine.
I had overlooked an important business rule while calculating compliance for previous-month backlog (N/N-1) orders. Technically, my formulas were correct—but they didn't reflect how the business actually measured fulfillment.
In analytics, that's the difference between being mathematically right and being business-wise right.
Instead of trying to justify the numbers, I immediately informed my reporting manager, explained the issue, and asked for help in understanding the business logic.
We walked through the process together, corrected the calculations, and rebuilt that section of the dashboard.
Looking back, that mistake became one of the most valuable lessons of my internship.
Since then, I made it a habit to validate assumptions with stakeholders before building any analysis instead of after it.
What I Wish I'd Known Before Day 1
If I could give my pre-internship self one piece of advice, it would be this:
Don't measure your success by how quickly you build the dashboard. Measure it by how well you understand the business problem.
Before joining, I believed technical skills would be my biggest advantage.
Excel.
SQL.
Power BI.
Analytics.
They were all important.
But I soon realized that asking thoughtful questions, understanding business processes, communicating clearly, and listening to stakeholders mattered just as much.
I also wish someone had told me that it's completely okay to feel overwhelmed in the beginning.
The first few weeks were filled with unfamiliar terminology, complex supply chain processes, and business scenarios that didn't always make immediate sense.
Over time, I learned that asking questions isn't a sign of weakness.
It's how you become better.
Another lesson? Share your work early.
Some of the best improvements in my project came from discussing rough prototypes, accepting feedback, and iterating instead of waiting for perfection.
One Summer, A Different Definition Of Analytics
When I started my internship, I thought business analytics was about creating reports.
I ended it with a very different perspective.
Analytics isn't about numbers.
It's about understanding the business well enough to ensure those numbers lead to better decisions.
And that's probably the biggest takeaway I'll carry into every role I take up in the future.