3 min

What AI Can’t Fix: Lessons from a Cross-Industry Data Leader

AI is reshaping industries, but the fundamentals of data remain unchanged. In this conversation with Ashish Mohan, we explore why problem definition and statistical thinking still drive meaningful outcomes.

Applied AI

Data Analytics

Data Engineering

Introduction

In a time when business is being restructured at unprecedented speed due to AI, it’s easy to forget that the fundamentals of data analysis — clear problem definition, grounded statistical reasoning, and business context — haven’t gone anywhere. Generative AI and large language models are transforming what's possible, but they don't eliminate the need to understand what you’re solving for in the first place.

Ashish Mohan knows this balance well. A seasoned data science leader, Ashish has worked across insurance, retail, infrastructure, and urban planning. He blends deep technical knowledge with practical business acumen, and in our conversation, he shared what more data professionals and business leaders need to hear: Don’t start with the tools — start with the problem.

“The core of all machine learning models is just statistics,” he said. “Until you know your business problem, you won’t know what analytical method to use.”

Ashish’s insight is not a critique of AI. In fact, he sees AI as a powerful tool — but one that must be matched to a clearly articulated need. When business teams reach for LLMs before defining the core challenge, they risk building architectures that are impressive, but ultimately misaligned.

In our recent conversation, Ashish offered a rare combination: a cross-industry lens and a grounded, ROI-driven approach to data science. We covered what he sees as today’s biggest pitfalls, how to deliver meaningful insights, and the hidden edge of generalists in a specialist world.

The AI Hype Trap

Across verticals, Ashish sees business leaders pushing for AI-driven solutions without a clear understanding of the problem they’re trying to solve.

“Sometimes people default to generative AI. But what they need could be solved by regression models,” he said. “You don’t need ChatGPT to predict sales. A good linear model will do.”

He emphasized that LLMs and generative AI tools have incredible potential, especially when used to improve data accessibility and speed up exploratory work. But jumping to AI without grounding the business question risks misalignment and wasted effort.

Thinking Across Verticals: A Hidden Advantage

While some leaders recommend specializing in one vertical, Ashish sees value in moving between them. From spatial modeling in urban planning to marketing analytics in insurance, he’s transferred mental models across industries.

“Customer segmentation in urban planning isn’t that different from consumer segmentation in retail,” he said. “The concepts are portable. The labels just change.”

His ability to connect concepts across domains has given him an edge in spotting opportunities others miss. Ashish believes that exposure to different industries strengthens a data scientist's creativity, adaptability, and business judgment.

“Gone are the days where you could work in a single vertical and know it inside out. Today, people interact with data across multiple platforms and touchpoints. The ability to think cross-functionally is critical.”

Data Problems Are Still Data Problems

Ashish doesn’t romanticize the work. He sees data leaders spending too much time doing what he calls “data plumbing”: de-duplicating campaigns, standardizing offline media, and manually making taxonomy decisions. That isn’t avoidable — but it needs to be done smartly.

“You don’t need to process 100% of the data,” he said. “Start with a question. What stream of the data do you actually need?”

He recommends actively de-scoping models and working closely with clients to limit noise before handing anything off to engineering teams.

He also noted that tools like Excel, Python, and SQL Server — used well — are often sufficient for both internal analysis and presentation. While cloud-native stacks are powerful, business users often gravitate toward familiar, interpretable tools.

Communication Is the Model

Ashish emphasized the importance of midstream client check-ins. Most data scientists engage clients at the start and the end of a project. But critical value is created in between.

“Why wait until the final model to talk to them?” he asked. “Early results can help you course-correct — and help the client rethink their assumptions.”

In his view, presenting the insights well matters just as much as building a model that works. That means delivering context, not just numbers.

“You can make a fancy dashboard with heatmaps and bubbles,” he said. “But if a simple bar chart tells the story, use that.”

A Final Word for New Data Scientists

Asked what advice he’d give to someone starting in the field, Ashish didn’t hesitate:

“Don’t start with the tools. Start with the statistics,” he said. “Then learn how it applies to business. Tools come and go. But the principles stay.”

He sees too many new practitioners rushing into Python packages or LLM integrations before mastering the underlying math. Concepts like regression, multicollinearity, and PCA remain the foundation — no matter how advanced the tooling becomes.

“If you don’t understand R-squared or MAPE or the reason a variable matters, the numbers are just numbers. They won’t tell a story.”

It’s a reminder for all of us: the foundation of great data science isn’t the model. It’s the clarity behind why we’re building it in the first place.

Don’t Miss Out On Future Articles

Stay in the loop with everything you need to know.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.