Strategic Innovation for Product Managers: What I Learned at IIT Delhi

A fellow brand manager once told me, over chai at our favourite Bandra cafe, that she felt trapped. Seven years into her career, she had a sharp instinct for consumer behaviour, a portfolio of award-winning campaigns, and absolutely no idea how to break into product management. I knew that feeling intimately. It was exactly where I stood in late 2018, after winding down the day-to-day operations at PitchNDA, my first startup. I had built a product, raised awareness for it, spoken at conferences about it — but I could not articulate, in the structured language that hiring managers expected, how I thought about product decisions.

That gap is what led me to the IIT Delhi Executive Management Program in Strategic Innovation, Digital Marketing, and Business Analytics. Running from January to June 2019, it turned out to be the most efficient investment I have made in my professional development. Not because it gave me a certificate to wave around, but because it gave me frameworks to organise thinking I was already doing intuitively.

Why an Executive Program Instead of a Full-Time Degree

The question I get most often is: why not just do an MBA? At the time, I had co-founded PitchNDA, worked through Y Combinator Startup School, and spent years at agencies like McCann Worldgroup and Publicis Groupe. I was not looking for a career reset. I was looking for a career upgrade.

A full-time degree would have meant stepping out of the market for two years. I was 30, had already pivoted from advertising to startups, and needed to move quickly. What I needed was a concentrated programme that could fill specific gaps: quantitative analysis, digital strategy frameworks, and innovation methodology.

The IIT Delhi programme checked every box. It ran part-time over six months, was taught by faculty from the Department of Management Studies with genuine industry exposure, and covered three interconnected domains: strategic innovation, digital marketing, and business analytics. More importantly, the cohort was composed of mid-career professionals — people running businesses, leading marketing teams, and managing product lines. The classroom discussions were as valuable as the curriculum.

Three Frameworks That Changed How I Think

1. The Innovation Ambition Matrix

Before IIT Delhi, I thought of innovation as a binary: you were either doing something incremental or something radical. The Innovation Ambition Matrix introduced a third dimension — adjacent innovation — and a systematic way to allocate resources across the three.

At PitchNDA, we had been operating almost entirely in the “transformational” quadrant: building a completely new product category (secure file-sharing with auto-generated NDAs for the creator economy). That is thrilling, but it also explains why customer acquisition was brutally difficult. There was no existing behaviour to anchor to.

The framework helped me see, retrospectively, what I would do differently. If I were building PitchNDA again, I would start with an adjacent innovation — perhaps a plugin for existing platforms like Behance or Dribbble that added NDA functionality to existing workflows — before attempting to pull users into a new platform entirely. That insight about meeting users where they already are has shaped every product decision I have made since.

2. Jobs-to-Be-Done in a Digital Context

I had encountered Clayton Christensen’s Jobs-to-Be-Done theory before, but the programme’s digital marketing module reframed it for platform businesses and SaaS products. The key insight was mapping the “job” not just to the user, but to the entire value chain.

We worked through a case study on a B2B SaaS platform where the buyer, the user, and the beneficiary were three different people. The “job” was different for each. The buyer needed to justify the purchase to a CFO. The user needed to reduce their workload by at least two hours per week. The beneficiary (typically an end customer) needed faster response times.

This multi-stakeholder job mapping became the foundation for how I later approached product marketing at Spectra, where I had to design go-to-market strategies for connectivity products sold to IT managers, used by employees, and experienced by end customers. Each stakeholder had a fundamentally different “job,” and the messaging had to address all three.

3. Analytics as a Decision Framework, Not a Reporting Tool

The business analytics module was the most technically challenging part of the programme. We covered regression analysis, cohort analysis, attribution modelling, and basic predictive analytics. But the real lesson was philosophical: analytics exists to reduce uncertainty in decisions, not to produce dashboards that nobody reads.

The professor introduced us to a framework he called the “Decision Stack.” Before touching any data, you define the decision you are trying to make. Then you identify what information would change that decision. Only then do you determine what data could provide that information. It sounds obvious, but I have seen countless marketing teams (including ones I have led) start with “what does the data say?” rather than “what decision are we trying to make?”

This backward-from-the-decision approach is something I still use daily. When I later built the analytics infrastructure at Droit for our fantasy gaming platform, I started not with “what should we track?” but with “what decisions will we make in the next 90 days, and what data do we need to make them well?” That question led to a much leaner, more actionable instrumentation design than the standard approach of tracking everything and hoping patterns emerge.

The Bridge Between Brand Intuition and Product Rigour

Here is the thing that nobody tells marketers transitioning to product management: the skills are more transferable than you think, but they need to be translated.

In brand management, you develop an intuition for what resonates with consumers. You can feel when a campaign concept is off, even before focus group data confirms it. You learn to read cultural signals and anticipate shifts in consumer sentiment. These are incredibly valuable capabilities in product management, where user empathy is supposedly the core competency.

But in product management, intuition is necessary but not sufficient. You need to pair it with structured experimentation, quantitative validation, and systematic prioritisation. The IIT Delhi programme gave me the vocabulary and methods to do that translation.

For example, at McCann Worldgroup, when we were developing the #YouCannes campaign for L’Oreal Paris, my conviction that the campaign would work was rooted in brand intuition — I understood the aspiration that Cannes represented for our target audience. That intuition was correct (India ranked number one globally in digital and PR), but I could not have told you, in statistical terms, why I was confident.

After the IIT Delhi programme, when I was making product decisions at Pers Active Lab for the Skin Beauty Pal app — India’s first AI-powered skincare platform — I could combine that same consumer intuition with a structured approach: defining hypotheses, designing experiments to test them, and using analytics to validate or invalidate assumptions before committing engineering resources.

What I Applied Immediately at PitchNDA

During the programme, I was still involved with PitchNDA in a strategic capacity. I immediately applied three things:

Repositioning through Jobs-to-Be-Done. We stopped describing PitchNDA as a “secure file-sharing platform” (a feature description) and started describing it as a tool that “lets freelancers share work confidently” (a job description). This subtle shift improved our landing page conversion by a measurable margin because it spoke to what users actually cared about: confidence that their creative work would not be stolen.

Cohort-based retention analysis. Instead of looking at overall retention numbers (which were mediocre), I segmented users by acquisition channel and use case. This revealed that users who came through creative community referrals had 3x higher 30-day retention than those who came through paid channels. That finding redirected our limited marketing budget entirely toward community partnerships.

Innovation portfolio thinking. I advocated for adding a “light” version of PitchNDA that worked as a simple watermarking tool — an adjacent innovation that solved a smaller, more immediate job while introducing users to the broader platform. This was a direct application of the Innovation Ambition Matrix.

Advice for Marketers Considering the Shift to PM

Having made this transition, here is what I would tell my former self and anyone standing at the same crossroads:

Your marketing background is an asset, not a liability. Product managers who come from engineering often struggle with user empathy and market positioning. You already have those skills. What you need to add is structured analytical thinking, prioritisation frameworks, and technical literacy. An executive programme can provide the first two; the third comes from working closely with engineers and being genuinely curious about how things are built.

Choose an executive programme that forces you to apply frameworks to your own work. The IIT Delhi programme was effective because the assignments were not abstract case studies. We applied every framework to our actual businesses or roles. That immediate application cemented the learning in a way that theoretical study cannot.

Do not wait until you have the “perfect” product role to start thinking like a PM. I wrote product requirement documents for PitchNDA features. I defined success metrics for marketing campaigns at McCann. I ran A/B tests on email sequences at PitchNDA. Every one of these activities is product management practice. The executive programme gave me the terminology and structure to describe what I was already doing.

Invest in analytics literacy. The single biggest gap for most marketers moving to PM is not strategy — it is the ability to formulate hypotheses, design experiments, and interpret quantitative results. You do not need to become a data scientist. You need to become someone who can have a productive conversation with a data scientist, and who can make decisions under uncertainty using data rather than gut feel alone.

Looking Forward

The IIT Delhi programme was a bridge — not a destination. It took the intuition I had built across seven years of brand management and agency work and gave it structure. It connected the dots between consumer insight and business analytics, between creative strategy and innovation methodology.

Six months after completing the programme, I joined Pers Active Lab as a Product Marketing Manager. Within a year, I was leading product marketing at Spectra, applying those same frameworks to B2B go-to-market and growth marketing challenges at a scale I had not previously operated at.

The most valuable thing the programme gave me was not any single framework. It was the confidence that the analytical rigour product management demands is learnable — and that someone with a brand management background brings unique strengths to the discipline that purely technical product managers often lack. Understanding why people want things, not just what they do, remains the hardest part of building great products. And that is something you cannot learn from a textbook.