//pragmatic leaders

Product Management Frameworks and the Nine Steps to Change Management

Reading time
5 min
Section
Product Strategy
5 min left0%
product management frameworks and the nine steps to change management0%
5 min left
Product management is about making sense of complexity by using frameworks that help you decide what to build, why, and how to get buy-in.
Talvinder Singh, from a Pragmatic Leaders session on product strategy

Product management is a multi-dimensional role that requires you to organize ambiguity into decisions and actions. The actual job is not just to have ideas, but to use frameworks that help you prioritize, communicate, and execute effectively.

This lesson draws on the core building blocks of product management — opportunity assessment, discovery, business modeling, and change management — to give you a structured approach to leading products from idea to market success.

Frameworks are the PM’s tools to cut through noise

Without frameworks, product decisions feel like guesswork or politics. Frameworks give you a common language to evaluate opportunities, define requirements, and align stakeholders.

For example, the Opportunity Assessment framework answers two critical questions:

  • How do we source and identify product opportunities?
  • Which opportunities deserve investment of time and resources?

This framework breaks down opportunity evaluation into three dimensions:

DimensionWhat it meansIndian context example
Product-Market FitDoes the product solve a real, unmet user need?Meesho’s focus on tier-2 resellers’ pain points
Product-Company FitDoes the product align with company strengths and capabilities?Razorpay leveraging payments expertise
Product-Business FitDoes the product support the company’s business model and revenue goals?Swiggy’s shift to hyperlocal delivery

You will learn to organize opportunity analysis into an Opportunity Brief, which explicitly recommends a Go/No-Go decision and sets the stage for discovery.

Discovery and requirements definition are where product success is made or broken

After you identify an opportunity, your next job is to lead discovery and define the minimum viable product (MVP). This is an iterative process involving:

  • Customer interviews and research
  • Prototyping and usability testing
  • Refining requirements into user stories and market requirements documents

This process is critical because early decisions shape the product’s ultimate success or failure.

// scene:

Product discovery kickoff at a Series A SaaS startup in Bangalore

You (PM): “Our goal this sprint is to validate the core user problem and test a prototype with 10 customers.”

Design Lead: “I’ll prepare wireframes and clickable prototypes for user testing.”

Engineering Lead: “We’ll scope the MVP to focus on the highest priority features.”

The team aligns on a clear, focused discovery plan with measurable goals.

// tension:

Without clear discovery goals, teams build features nobody needs.

The business model is how the product captures value

Creating a great product is not enough — the product must generate sustainable revenue and profit. As a PM, you evaluate inputs from product, customer, competition, operations, and business to define an effective business model.

Popular revenue models in Indian tech include:

  • Advertising (e.g., ShareChat)
  • Subscription (e.g., Postman)
  • Freemium (e.g., BrowserStack)

You will learn to diagnose business models and innovate where possible. This is especially important in startups trying to disrupt established industries.

Structure, people, and process matter as much as product

Product management is also about managing people and processes:

  • Organizing product teams effectively
  • Choosing between Waterfall and Agile development methodologies
  • Running Scrum ceremonies like sprint planning, reviews, and retrospectives
  • Influencing cross-functional teams without direct authority
  • Running effective meetings that drive decisions

These "soft skills" are essential to orchestrate delivery and maintain momentum.

// thread: #product-team — Coordinating sprint planning with cross-functional team
Priya (Scrum Master)Reminder: Sprint planning tomorrow at 10 AM. Please come prepared with your backlog items prioritized.
You (PM)I’ll share updated user stories by EOD today. Let’s focus on the features that unblock customer onboarding.
Rahul (Engineer)Noted. We’ll need specs by tomorrow morning to estimate.
You (PM)Understood. I’m coordinating with design today to finalize flows.

Taking products to market requires integrated planning and execution

A product launch can make or break your product. The Go-To-Market (GTM) strategy includes:

  • Positioning and messaging frameworks
  • Marketing collateral development
  • Sales enablement and channel strategies
  • Coordinated launch activities across sales, marketing, and partner teams

Indian startups like Flipkart and PhonePe have demonstrated the power of integrated GTM to capture market share rapidly.

Managing whole offers and partner ecosystems extends product value

Customers expect more than a standalone product. They want a Whole Offer — the core product plus complementary products, services, and information to create a total customer experience (TCE).

To create this, companies build ecosystems of partnerships and alliances. This involves decisions about what to build internally, what to buy, and what to ally with partners on.

This is a growing area in Indian tech, especially in fintech and SaaS.

The nine steps to effective change management in product

Product success often requires change — in customer behavior, internal processes, or organizational culture. Managing change is a skill every PM must master.

The nine essential steps to change management are:

  1. Identify the need for change
    Recognize the problem or opportunity that requires change.

  2. Define the change clearly
    Specify what will change and what the future state looks like.

  3. Assess the impact
    Understand who and what will be affected.

  4. Engage stakeholders early
    Communicate with those impacted to get buy-in and address concerns.

  5. Develop a change plan
    Create a roadmap with milestones, resources, and responsibilities.

  6. Communicate continuously
    Maintain transparency and update stakeholders regularly.

  7. Train and support
    Provide resources and coaching to those adapting to the change.

  8. Implement the change incrementally
    Roll out changes in manageable steps, allowing feedback loops.

  9. Monitor and reinforce
    Track adoption, fix issues, and embed the change into culture.

// scene:

Cross-functional change management meeting at a Hyderabad fintech startup

You (PM): “We need to update the onboarding flow to reduce drop-offs. This will impact sales and support teams.”

Sales Lead: “What changes should we communicate to customers? How do we prepare our team?”

Support Lead: “We’ll need training on the new flow and FAQs.”

You (PM): “Let’s create a detailed rollout plan with timelines, communication, and training sessions.”

The team aligns on a structured approach to manage change smoothly.

// tension:

Change without a plan leads to confusion and resistance.

Field exercise: Apply the nine-step change management process

Time: 20 minutes

Choose a change initiative in your current product or team — it could be a new feature launch, process update, or organizational shift.

  1. Identify and write down the specific change.
  2. List stakeholders affected and their concerns.
  3. Draft a simple communication plan.
  4. Outline training or support needed.
  5. Plan an incremental rollout with feedback checkpoints.
  6. Define metrics to monitor adoption and success.

Use this exercise to practice structuring change initiatives systematically.

Test yourself: Prioritizing product opportunities and managing change at a Series B startup

// learn the judgment

You are PM at a Series B SaaS startup in Pune focused on HRtech. The leadership team is debating two product opportunities: (1) building an AI-powered compensation benchmarking tool, and (2) improving the employee onboarding experience. Both have limited engineering bandwidth. Simultaneously, a new compliance regulation requires changes to the data collection process, affecting sales and support teams.

The call: How do you prioritize these product opportunities and manage the compliance-related change without derailing the roadmap?

Your reasoning:

// practice

You are PM at a Series B SaaS startup in Pune focused on HRtech. The leadership team is debating two product opportunities: (1) building an AI-powered compensation benchmarking tool, and (2) improving the employee onboarding experience. Both have limited engineering bandwidth. Simultaneously, a new compliance regulation requires changes to the data collection process, affecting sales and support teams.

Your task: How do you prioritize these product opportunities and manage the compliance-related change without derailing the roadmap?

your reasoning:

0 chars (min 80)

From the field: How frameworks saved a product launch at Razorpay

Where to go next

PL alumni now work at Flipkart, Razorpay, PhonePe, Swiggy, Amazon, Microsoft, and 30+ other companies.