A product is not just a collection of features. It is a cohesive solution that solves a real problem for a specific customer in a specific context.
Great products are not accidental. They result from deliberate choices that align user needs, business goals, and technical feasibility into a seamless whole. The trap most PMs fall into is thinking that adding more features or ticking boxes equals a better product.
The actual job is to design products that deliver clear, measurable value while maintaining cohesion and simplicity. Without this, the product becomes a jumble of disconnected parts — confusing to users and costly to maintain.
This lesson draws on patterns I have seen repeatedly across Indian startups and enterprises, where product teams struggle to move from feature lists to well-architected product portfolios.
Features, modules, and platforms are not the same
One of the most common sources of confusion in product design is mixing up these three levels:
- Features are the smallest units of user value — specific capabilities or functions. For example, "dark mode" or "push notifications."
- Modules are collections of related features that serve a broader purpose. For example, a "user profile" module that includes avatar upload, bio editing, and privacy settings.
- Platforms are the overarching systems or ecosystems that coordinate multiple modules and features, often supporting multiple user roles or business processes.
Most teams get stuck at the feature level — listing dozens of features without thinking about how they fit together. The result is a fragmented experience and technical debt.
The cleanest way to think about it: start from the platform level and work down. A platform defines the core value proposition and user workflows. Modules implement parts of that workflow. Features are details that refine the modules.
This is what week one looks like for most new PMs:
The trap of micro-level feature thinking
In many Indian startups, product teams focus on micro-level features like course selection, class scheduling, or notification settings without stepping back to see the bigger picture.
This leads to:
- Disjointed user experiences: Users struggle to understand how features fit together.
- Maintenance overhead: Engineering spends more time fixing integration bugs than building new value.
- Stakeholder frustration: Sales and marketing get conflicting messages about what the product really is.
Here is how I explain this to PMs:
"Think of your product like a building. Features are the furniture, modules are the rooms, and the platform is the foundation and structure. You cannot just fill every room with furniture without a blueprint."
A well-designed product portfolio:
- Defines the platform clearly with a cohesive vision.
- Organizes modules around user workflows or business processes.
- Prioritizes features that support the modules and platform goals.
Indian example: Swiggy’s platform evolution
Swiggy started as a food delivery app — a platform connecting users, restaurants, and delivery partners. Over time, they added modules like grocery delivery, cloud kitchens, and subscription services.
Each module bundles features into a coherent experience for users and operations. This modular platform approach allowed Swiggy to scale efficiently without confusing users or overloading engineering.
Building with ethical and sustainable design in mind
Good product design today must go beyond user and business needs. It must embed ethical and sustainable principles from the outset.
India’s startups are increasingly aware of this. Consider:
- Zerodha, which disrupted brokerage by being transparent and customer-first.
- Bare Necessities, which applies zero-waste principles in product packaging and lifecycle.
- Banyan Nation, which integrates recycling and waste management into their product and operations.
Embedding ethics and sustainability means:
- Avoiding dark patterns or manipulative UX.
- Designing for accessibility and inclusivity across India’s diverse user base.
- Minimizing environmental impact through thoughtful product lifecycle choices.
Product strategy workshop at an Indian fintech startup
You (PM): “Before we finalize the roadmap, let's embed ethical checkpoints — how will this feature affect user privacy and data security?”
Rahul (Engineering): “That means extra validation and audit trails.”
Priya (Design): “We can design the UI to make consent transparent and easy to revoke.”
CEO: “I see the long-term value. Let's make this a company standard.”
Balancing fast delivery with responsible product design
Quality checks and feedback loops are essential
Product design is iterative. Embedding rigorous quality checks and feedback loops ensures that the product evolves in response to real user needs.
This includes:
- User testing: Regular sessions with diverse users to validate assumptions.
- Data monitoring: Tracking key metrics to catch usability or performance issues early.
- Cross-functional reviews: Engineering, design, and business teams collaborating to catch gaps.
Indian companies like Postman and BrowserStack have built their success on tight feedback cycles and quality discipline, allowing them to scale globally.
Field exercise: Evaluate your product’s design cohesion (15 min)
Take a product you use regularly — it can be from Indian companies like Flipkart, Meesho, or Razorpay.
- Identify the platform — what is the core system or ecosystem?
- List the modules — what are the major functional areas or workflows?
- Enumerate the features within each module.
- Assess whether the modules and features connect logically to the platform’s core value.
- Identify any features that feel disconnected or unnecessary.
Reflect on how this exercise might apply to a product you are working on.
Avoid the “feature factory” mindset
A feature factory is a team that outputs features rapidly without strategic coherence or user focus.
The trap is:
- Building features that nobody asked for or uses.
- Prioritizing quantity of features over quality and impact.
- Losing sight of the product’s purpose and user needs.
What I tell PMs is:
"If you cannot explain how this feature moves the needle on user value or business goals, don’t build it."
Judgment exercise
You are the PM at a Series A Indian edtech startup preparing a new product launch. The CEO wants 20 new features added to the MVP, including gamification badges, a chatbot, and a social feed. The engineering team warns that adding all features will delay launch by 3 months. The marketing team insists on the features to attract users.
The call: How do you prioritize the features? What do you communicate to the CEO and stakeholders?
Your reasoning:
You are the PM at a Series A Indian edtech startup preparing a new product launch. The CEO wants 20 new features added to the MVP, including gamification badges, a chatbot, and a social feed. The engineering team warns that adding all features will delay launch by 3 months. The marketing team insists on the features to attract users.
Your task: How do you prioritize the features? What do you communicate to the CEO and stakeholders?
your reasoning:
From the field: Reflecting on product cohesion
Meeting scene: Designing for sustainability and ethics
Product design review meeting at a Bangalore-based fintech startup
You (PM): “Let's review the roadmap with an ethical lens. How does this new credit scoring feature protect user privacy?”
Meera (Data Scientist): “We use anonymized data and get explicit consent.”
Vikram (Legal): “We must ensure compliance with RBI guidelines and data protection laws.”
Rahul (Engineering): “Implementing data minimization will add complexity but reduce risk.”
You: “Let's build a checklist to embed these checkpoints into every feature.”
Balancing innovation speed with responsible product practices
The platform mindset changes team dynamics
Adopting a platform mindset means working across teams and functions more deeply:
- Engineering aligns on shared infrastructure and APIs.
- Design unifies UI patterns and user flows.
- Data teams standardize metrics and feedback loops.
- Business teams coordinate go-to-market strategies around platform capabilities.
In India, companies like Razorpay and PhonePe have embraced this approach, enabling rapid feature launches without fragmenting the user experience.
Field exercise: Draft a product roadmap with ethics and sustainability checkpoints (20 min)
Using a product you know well or are building:
- Sketch a high-level roadmap with major modules and features.
- For each module, identify at least one ethical or sustainability checkpoint.
- Define metrics or validation steps for these checkpoints.
- Reflect on how this changes your prioritization and planning.
Test yourself: The roadmap ambush
You're two months into your PM role at a B2B SaaS startup. You've spent three weeks on user research and built a roadmap focused on fixing onboarding drop-off — your biggest churn driver. Monday morning, product review meeting.
Your CEO walks in and says: "I spoke with the Jio team over the weekend. They need SSO by March. Move it to P0. They're 40% of our ARR." The room goes quiet. Your engineering lead is looking at you.
Where to go next
- If you want to master prioritization and trade-offs: Prioritization Frameworks and Techniques
- If you want to embed ethics into your product process: Ethical PM
- If you want to improve your product discovery skills: User Research Methods
- If you want to learn how to build AI-powered products responsibly: AI Product Strategy
PL alumni now work at Flipkart, Google, Razorpay, PhonePe, Swiggy, Amazon, Microsoft, and 30+ other companies.