India has more product managers in tech than any country outside the US. The unique challenge for Indian PMs: you're often building products for Bharat users — Tier 2/3 India, different needs than metro — while communicating with US/UK leadership who've never been to a tier-3 city. These 25 prompts bridge that gap.
Use them with Claude, GPT-4o, or Gemini. They're built around the actual context Indian PMs navigate: UPI flows, vernacular users, Aadhaar auth, festive season timing, and the translation layer between Bangalore engineering reality and global product expectations.
PRD and feature definition prompts
1. Problem statement writer
Write a crisp problem statement using this format: "We observe that [USER] struggles to [TASK] because [ROOT CAUSE], which leads to [OUTCOME]. We believe that [SOLUTION] will [MEASURABLE RESULT]."
My raw input: [DESCRIPTION OF THE PROBLEM YOU'VE OBSERVED]
Make the problem statement specific, avoid product-speak, and ground it in user behaviour rather than assumptions.
2. Bharat-first feature spec
Write a feature spec section that addresses Tier 2/3 India constraints for this concept: [DESCRIPTION].
Cover: intermittent internet (2G/3G), feature phone browser users, low digital literacy, vernacular language preference, cash-first behaviour, and first-time internet user patterns.
For each constraint: explain the implication and what the feature design must account for.
3. Acceptance criteria generator
Generate Given/When/Then acceptance criteria for this user story: [USER STORY].
Include: the happy path, error states, and edge cases specific to Indian usage — invalid Aadhaar format, UPI payment failure, COD preference, OTP delivery delay from TRAI DND lists, network timeout at 2G speeds.
Format each criterion as: Given [context], When [action], Then [expected result].
4. Technical constraint translator
Translate this engineering constraint into non-technical language suitable for a product roadmap or stakeholder update. The goal is that a non-technical business leader understands the trade-off without losing accuracy.
Constraint: [TECHNICAL DESCRIPTION]
Provide: (1) plain language explanation, (2) why it matters for the product, (3) what it means for timeline or scope.
5. Feature flag rollout plan
Design a rollout plan for this feature: [DESCRIPTION].
Include: control group definition, experiment groups, success metrics, rollback criteria.
India-specific consideration: propose rolling out to metro users first (Delhi/Mumbai/Bangalore), then Tier 2/3, treating the geo-split as a natural experiment to detect urban-rural behavioural differences before full launch.
6. Edge case generator for Indian users
Generate 15 edge cases for this feature specific to Indian usage: [DESCRIPTION].
Categories to cover: payment failures (UPI timeout, VPA not found, bank server down), language switching mid-flow, feature phone browsers rendering issues, OTP non-delivery (DND, slow SMSC), Aadhaar authentication errors, regional holiday timing, name/address fields with non-ASCII characters, connectivity loss mid-transaction.
7. Metric definition for Bharat product
Define success metrics for this feature targeting Tier 2/3 India users: [DESCRIPTION].
Include: primary metric, 2-3 secondary metrics, guardrail metrics.
Note: for Bharat users, activation often lags because users need more onboarding cycles. Retention patterns differ from metro. Factor this into metric targets and measurement windows.
Roadmap and prioritisation prompts
8. RICE scoring
Score each of these features using the RICE framework (Reach, Impact, Confidence, Effort).
For Reach: use Indian market size estimates where relevant. For Effort: use story point estimates from engineering input.
Features: [LIST WITH CONTEXT]
Output as a table: Feature | Reach | Impact | Confidence | Effort | RICE Score | Recommendation.
9. Roadmap narrative for global leadership
I need to present this India product roadmap to US/UK leadership who have limited India market context. Write a 3-paragraph narrative that:
- Explains what's structurally different about building for India (not a price-sensitivity pitch — the real differences)
- Explains why we're prioritising what we're prioritising
- Defines what success looks like and how we'll know
Roadmap: [DETAILS]. Avoid jargon. Use data where you have it.
10. Quarterly OKR generator
Generate Q[QUARTER] OKRs for a product team working on [PRODUCT AREA] in India.
Include 3 Objectives with 3 Key Results each. Key Results must be measurable using Indian market metrics: DAU in Tier 2 cities, UPI transaction success rate, NPS in vernacular user cohort, ARPU in INR, D30 retention for post-festive cohort.
Avoid vanity metrics. Each KR must be binary pass/fail by quarter end.
11. Now/Next/Later roadmap
Organise these features and initiatives into a Now/Next/Later roadmap for [TIME HORIZON]: [LIST].
Explain the logic for each placement. Factor in Indian market timing: Diwali/festive season (Oct-Nov), tax filing season (Jan-Mar), GST quarterly deadlines, IPL season for consumer attention.
Output: Now (0-3 months), Next (3-6 months), Later (6-12 months) with one-line rationale per item.
12. Competitor mapping for Indian market
Analyse these Indian and global competitors for [PRODUCT CATEGORY]: [LIST].
For each competitor: (1) what they do well for Indian users, (2) where they fall short specifically for Bharat markets — not just rural price sensitivity, but trust, language, distribution, payment rail issues, (3) what gap they leave for us.
Conclude with: our most defensible differentiation angle.
User research and customer insight prompts
13. User interview synthesis
Synthesise these [N] user interview notes into:
- Top 3 pain points (with evidence)
- Top 3 unmet needs (different from pain points)
- Top 3 behavioural patterns
- 3 direct quotes that capture the user voice authentically
Notes: [RAW NOTES]
Flag: anything that surprised you or contradicts our existing assumptions.
14. Bharat user persona
Create a detailed user persona for a [PRODUCT TYPE] user in Tier 2/3 India.
Include: demographics, digital comfort level (how long they've had a smartphone, what apps they use daily), devices used, payment preferences (UPI/cash/EMI), vernacular language, aspirations vs. current reality, and specifically how they'll interact with our product differently than a Tier 1 metro user would.
Ground it in what we know about [YOUR CITY/REGION] users if possible.
15. NPS verbatim analyser
Categorise these NPS verbatim responses by theme: [DATA]
For detractor responses (0-6): identify the top 3 actionable issues, estimate frequency of each, and suggest one specific change per issue.
For promoter responses (9-10): identify what we should protect and not change, and what we could amplify in our messaging.
Passive responses (7-8): identify the one unlock that would move them to promoter.
16. A/B test hypothesis generator
Generate 10 testable hypotheses for improving [METRIC] on [PRODUCT/FEATURE].
For each hypothesis: the hypothesis statement (If we change X, Y will change by Z because...), the test design (control vs. treatment), minimum detectable effect, estimated sample size based on our [X] DAU base, and confidence threshold.
Flag: which hypotheses are most likely to have India-specific results vs. ones where global benchmarks apply.
17. Customer journey map
Create a customer journey map for [USER TYPE] using [PRODUCT] for [USE CASE] in India.
Stages: Awareness → Consideration → First use → Habit formation → Advocacy.
For each stage: touchpoints, emotions, pain points, and India-specific context — if UPI is involved, include UPI flow states (initiated/pending/failed/success). If WhatsApp is the discovery channel, map that. Include where trust breaks down.
Stakeholder communication prompts
18. Engineering alignment email
Draft an email to the engineering team explaining why [FEATURE/DECISION] is being prioritised this sprint/quarter.
Focus on: the user problem (in terms engineers find meaningful), business impact with numbers if available, why now rather than later.
Acknowledge any technical debt implications honestly — don't hide known trade-offs.
19. Exec update for India business
Write a monthly product update email for India business leadership.
Include: key metrics vs. last month (with variance), top 3 wins and why they happened, top 2 misses and what we're doing about them, one forward-looking risk, and next month priorities.
Data: [METRICS]. Keep it under 300 words. No fluff.
20. Cross-border leadership narrative
I need to explain the India product strategy to global leadership who tend to think "India = same as everywhere, just cheaper." Write a 5-minute talk track that reframes India as a product innovation lab, not just a price-sensitive market.
Use: specific examples of Indian innovations that went global (UPI, Jio's data democratisation, Aadhaar auth). Connect to [OUR PRODUCT AREA].
21. Pushback response on de-prioritisation
A senior stakeholder is pushing for [FEATURE X] to be prioritised over our planned roadmap. Draft a response that:
- Acknowledges their concern genuinely
- Presents the trade-off data (what we'd have to delay, estimated impact)
- Either agrees with conditions, or respectfully disagrees with an alternative that addresses their underlying concern
Feature X request: [DETAILS]. Our current priority: [DETAILS].
22. Sprint review talking points
Generate talking points for a sprint review demo of [FEATURE].
Target audience: [STAKEHOLDER TYPE — e.g., business leadership / engineering leads / investor].
Cover: problem we set out to solve, what we built (demo flow), what we'll measure to know it worked, what comes next.
Keep it under 5 minutes spoken. Flag where to pause for questions.
23. Risk register for product launch
Create a risk register for launching [PRODUCT/FEATURE] in India.
Risk categories: regulatory (RBI/SEBI/TRAI/DPDP Act), competitive response, technical (UPI downtime, low connectivity, server load during festive traffic spikes), user adoption (trust, language barrier), and operational (support volume spike, escalation paths).
For each risk: likelihood (H/M/L), impact (H/M/L), mitigation plan, and owner.
24. Product hypothesis for fundraising
We're pitching investors on this product. Write the product section of the pitch narrative.
Cover: what problem, why now (what's changed in India's digital infrastructure that makes this possible), why us specifically, what's the defensible moat, what's the 12-month roadmap, why India first is the right bet.
Product context: [DETAILS]. Keep it direct — investors see through padding.
25. Post-launch retrospective
Structure a post-launch retrospective for [FEATURE] that launched [PERIOD] ago.
Cover: what we planned vs. what actually happened (honest accounting), key learnings organised by theme, three things we'd do differently, and concrete next steps with owners.
Metrics: [DATA]. Format for async reading — leaders who weren't in the room should understand the full picture.
💡 Want to go deeper on the prompting techniques behind these templates? The MasterPrompting curriculum covers system prompts, few-shot examples, and chain-of-thought patterns that make prompts like these actually reliable — not just sometimes good.
