//pragmatic leaders

AMA with Jai Mansukhani, PM at Careem

Reading time
5 min
Section
Industry Videos- PLPM
5 min left0%
ama with jai mansukhani, pm at careem0%
5 min left
In product management, the toughest part is balancing stakeholder demands while keeping the customer’s real problem front and center.
Talvinder Singh, from a Pragmatic Leaders AMA session with Jai Mansukhani

Jai Mansukhani’s experience managing products at OYO and Careem offers a rare window into the realities of product management in emerging markets. His work spans critical operational tools and consumer-facing platforms, both of which serve as lifelines for their users — hotel managers relying on OYO’s booking system and drivers depending on Careem’s app for income.

This lesson grounds you in the operational and strategic challenges that come with managing products that support real-world businesses across multiple markets. You will learn how to balance competing stakeholder demands, adapt to local complexities, and lead with customer focus in fast-moving startups.

Product management is about operations, not just features

Jai’s role at OYO was managing the hotel booking system used daily by hotel managers. This is not a consumer app designed for end customers; it’s an internal tool that powers operations. The stakes are high: any downtime or confusing interface directly affects hotel managers’ ability to run their business, which in turn impacts guest satisfaction and revenue.

At Careem, Jai manages the driver app in the UAE — a consumer product, but also a platform serving thousands of drivers. The app must deliver real-time trip information, navigation, and earnings details. The trust drivers place in the app is fundamental to their livelihood.

The actual job is not just adding new features. It is ensuring the product works seamlessly within the context of the user’s daily workflow and constraints. Reliability, speed, and simplicity are often more important than flashy additions.

// scene:

Product planning meeting at Careem UAE

Jai (PM): “We can’t just push the new incentive feature without stabilizing the app first. Drivers will lose trust if the app crashes during trips.”

Engineering Lead: “Stability improvements will take two sprints. The marketing team wants incentives live next week for the campaign.”

Jai (PM): “We need to prioritize reliability. Let’s communicate clearly to marketing and ops about the trade-offs.”

Marketing Lead: “Understood. We’ll adjust our campaign timeline accordingly.”

This conversation exemplifies how product management is about balancing stakeholder demands while keeping driver needs front and center.

// tension:

The tension between feature delivery and operational stability

Multi-market complexity demands local adaptation, not one-size-fits-all

Both OYO and Careem operate in multiple cities and countries, each with distinct regulations, customer behaviors, and infrastructure challenges.

Jai explains that product decisions cannot be uniform across markets. For example, driver behavior in Dubai differs from other cities. Hotel management workflows vary by location as well.

Localization, compliance, and adaptability are core parts of the product strategy — not afterthoughts.

Indian PMs moving from single-city startups to regional or global companies often underestimate this complexity. They must learn to build products flexible enough to handle diverse market realities.

// thread: #product-ops — Cross-functional discussion on market-specific product adaptations
JaiWe’re seeing different cancellation patterns in Dubai vs Mumbai. Should we customize the driver incentives accordingly?
Operations LeadYes, Dubai drivers prefer guaranteed earnings, while Mumbai drivers respond better to surge pricing.
JaiLet’s build configurable incentive parameters per city. Compliance teams will also need to review local regulations.
EngineeringThat adds complexity, but it’s necessary for market fit.

Stakeholder demands are competing, your job is to prioritize based on customer impact

Jai shared how operations, engineering, marketing, and external partners often push conflicting priorities.

The trap is trying to please everyone. Jai’s advice is to prioritize relentlessly by focusing on customer impact and business value, not on who shouts the loudest.

For example, when operations want a quick fix for a booking glitch but engineering warns of accruing technical debt, the PM must make the call and explain the trade-offs.

Making tough prioritization decisions and owning their consequences is the core of product management.

Consumer-facing apps and platform/internal tools require different PM approaches

Jai’s experience spans both consumer products and platform tools.

  • The Careem driver app is a consumer product but also a platform supporting drivers — a two-sided marketplace. It must balance driver needs with ride matching efficiency and customer satisfaction.

  • The OYO hotel booking system is primarily a platform product designed for internal users with specific operational workflows.

These require distinct approaches:

  • Consumer apps focus on engagement, retention, and seamless user experience.

  • Platform/internal products emphasize reliability, workflow efficiency, and stakeholder collaboration.

Many Indian PMs start with consumer apps but must develop skills to manage platform complexity as they grow.

Emerging markets share infrastructure, behavior, and regulatory challenges

Jai highlighted common challenges in India and UAE:

  • Infrastructure variability: Network quality, device diversity, and payment methods differ widely.

  • User behavior: Cash payments, informal workflows, and multilingual contexts require flexible design.

  • Regulatory environment: Compliance and data privacy rules are evolving rapidly.

These factors force PMs to balance speed with caution and build adaptable, resilient products.

// thread: #product-localization — Design discussion for infrastructure and compliance challenges
JaiWe need offline booking modes for hotel managers in low-connectivity areas.
DesignCan we add data sync features that queue offline actions and sync later?
ComplianceAlso ensure data privacy compliance for each market’s regulations.
EngineeringThat’s feasible but will need extra QA cycles.

Pragmatic advice from Jai Mansukhani for aspiring PMs

  • Understand your user deeply. Spend time with real users — hotel managers, drivers, or customers — to see how they actually use your product.

  • Communicate clearly. Bridge the gap between technical teams and business stakeholders. Translate complex trade-offs into simple language.

  • Own the outcome. Be accountable for what ships and what doesn’t. Don’t hide behind “it’s an engineering issue” or “marketing wanted it this way.”

  • Learn from failures. Products serving operational users often lack glamorous launches but have higher impact. Measure success by how smoothly the user’s day goes.

// exercise: · 15 min
User empathy deep dive

Choose a product used by an operational user, such as a delivery driver app or a hotel booking system. Conduct these steps:

  1. Identify the user’s daily workflow and pain points.
  2. List how the product supports or disrupts this workflow.
  3. Note any operational constraints (connectivity, device, regulatory) affecting usage.
  4. Reflect on how product decisions could improve reliability and reduce user friction.

Supporting media

Test yourself: Prioritizing feature requests in a multi-stakeholder environment

// learn the judgment

You are the PM responsible for the driver app at a ride-hailing startup operating in Mumbai and Dubai. The operations team in Mumbai demands a new feature to display driver incentives immediately on the home screen. The engineering team warns that this will delay the upcoming stability improvements by two sprints. Marketing wants the feature live this week to support a campaign. You have limited engineering bandwidth.

The call: What should you prioritize and how do you communicate your decision to the teams?

Your reasoning:

// practice

You are the PM responsible for the driver app at a ride-hailing startup operating in Mumbai and Dubai. The operations team in Mumbai demands a new feature to display driver incentives immediately on the home screen. The engineering team warns that this will delay the upcoming stability improvements by two sprints. Marketing wants the feature live this week to support a campaign. You have limited engineering bandwidth.

Your task: What should you prioritize and how do you communicate your decision to the teams?

your reasoning:

0 chars (min 80)

Where to go next