Writing
Prime Minister as Product Manager
Applying the RICE Framework to National Governance 🗳️
2025-10-12
- Social
PM as Product Manager: Applying the RICE Framework to National Governance 🗳️
Politics is often a messy world of ideology and gut feelings. But what happens when you strip that away and analyze a political leader’s tenure like a product manager would assess their product? It’s a sensitive exercise, but it offers a fascinating, data-driven lens on what’s working, what isn’t, and why.
Let’s use a popular product management framework, RICE, to prioritize the “features” and “bugs” of a national administration.
What is RICE?
It’s a scoring system used to determine what to work on next. It stands for:
- Reach: How many people does this feature impact?
- Impact: How much does this impact each person? (e.g., massive, high, medium)
- Confidence: How confident are we in our data and the projected success?
- Effort: How much time and resources will this take to build?
The formula is: (Reach x Impact x Confidence) / Effort. You work on the things with the highest scores.
Now, let’s apply this to Prime Minister Narendra Modi’s tenure, treating “India” as the product and the PM as the CEO/Product Head.
Features with High RICE Scores (The Successes)
These are the initiatives that, from a product perspective, were massive wins because they delivered huge value to a vast user base.
- Feature: Digital & Financial Infrastructure (UPI, Jan Dhan)
- Reach: Massive. Touches nearly every citizen, from street vendors to corporations.
- Impact: Transformational. This isn’t just a feature; it’s a new operating system for the national economy. It enabled direct welfare payments, cut corruption, and created a world-class digital payment ecosystem.
- Confidence: 100%. The data on adoption and transaction volume is undeniable and globally recognized.
- Effort: High, but the payoff was astronomical.
- RICE Score: Extremely High. This is a foundational, “platform-level” success that will deliver value for decades.
- Feature: Basic Amenities as a Service (Toilets, Electricity, Water)
- Reach: Hundreds of millions of India’s poorest citizens.
- Impact: Life-changing. For the “users,” this feature provides basic dignity, safety (especially for women), and better health outcomes. It fundamentally improves their daily “user experience.”
- Confidence: 100%. The number of toilets built and villages electrified are hard, verifiable metrics.
- Effort: Immense logistical and administrative effort.
- RICE Score: Very High. A huge win in improving the core “quality of life” metrics for a massive, underserved user segment.
Bugs & Risks with High RICE Scores (The Failures & Trade-offs)
No product is perfect. These are the critical bugs or strategic risks that score highly on the negative side of the ledger.
- Bug: High Unemployment Rate
- Reach: Affects millions of “users,” especially the youth, creating widespread dissatisfaction.
- Impact: Critical. This is a “showstopper” bug for many. It prevents users from achieving their goals, causes immense frustration, and can lead to “user churn” (i.ve., social unrest).
- Confidence: 100%. Multiple data sources confirm this is a persistent, high-severity issue.
- Effort to Fix: Extremely high. Requires deep, structural changes to the entire “codebase” of the economy.
- Negative RICE Score: Critically High. This is the biggest unsolved problem in the product.
- Strategic Risk: Erosion of Democratic Norms
- Reach: Indirectly affects all 1.4 billion “users” by changing the rules of the platform they operate on.
- Impact: Severe. This is a risk to the long-term health of the entire “ecosystem.” While centralizing power (the “trade-off”) may have allowed for faster feature deployment (like infrastructure projects), it weakens the system’s core stability and accountability mechanisms.
- Confidence: 100%. The decline is measured and documented in multiple global indices.
- Effort: The effort to cause this was low, but the effort to reverse the damage is monumental, making it a high-cost risk.
- Negative RICE Score: Very High. A long-term architectural risk taken for short-term execution speed.
The Product Roadmap Verdict 🗺️
So, is the “product” good or bad?
A product manager doesn’t think in terms of “good” or “bad.” They think in terms of the product vision.
If the vision was to rapidly build a modern state with foundational digital and physical infrastructure while providing basic dignity to the poorest, then the product has been a resounding success. The high-scoring successes directly align with this vision.
However, if the vision was to create a prosperous, harmonious, and open society with strong democratic institutions, then the product has critical bugs and has taken on dangerous long-term risks that contradict that vision.
This exercise shows that by applying a neutral framework, we can move beyond emotional reactions. We can see governance as a series of high-stakes trade-offs, where prioritizing one massive feature might mean deprioritizing—or even breaking—another. And just like with any product, the final verdict on its success depends entirely on what the user, or in this case the citizen, values most.