New Product Development

Opportunity Identification and Selection

Opportunity identification is the process of spotting unmet needs, gaps, or potential new product directions. Opportunity selection is the subsequent filtering — choosing which opportunities to pursue based on strategic fit, feasibility, and market potential. Together they form the front end of product development, bridging the firm’s product portfolio (covered in Module 1) and the detailed concept generation that follows.

How it fits into product development

flowchart LR
    A[Product Portfolio<br/>(Module 1)] --> B[Opportunity Identification<br/>& Selection]
    B --> C[Concept Generation<br/>& Evaluation (this module)]
    C --> D[Development & Launch]

The previous module established the product portfolio — which products the organisation invests in, and the overall process. Now we zoom into the front-end funnel: first spotting opportunities, then deciding which ones deserve further investment.

Identification vs. Selection — two linked activities

Activity	Purpose	Key question
Identification	Cast a wide net to uncover potential opportunities	“What could we do?”
Selection	Evaluate and prioritise based on criteria	“What should we do?”

Exam tip: This module focuses on the process of going from raw opportunity to a concrete concept. Distinguish identification (divergent, creative) from selection (convergent, analytical) — many exam questions hinge on this difference.

Why it matters

• Without systematic identification, firms miss high-value ideas.
• Without rigorous selection, resources scatter across too many weak opportunities.
• The quality of the front-end funnel directly determines the success rate of new products.

Key takeaways

• Opportunity identification and selection are the first systematic steps in new product development.
• Identification is about discovering possibilities; selection is about choosing the best ones.
• These activities connect the product portfolio (Module 1) to concept generation (Module 2).
• Both are necessary: identification without selection leads to wasted effort; selection without identification leads to missed opportunities.

Lego’s Story

Lego (Danish; leg godt = “play well”), founded in 1932, enjoyed 60 years of steady growth. In the late 1990s–early 2000s it faced near bankruptcy — a textbook case of how complacency can kill a dominant firm.

The Crisis

• External threats: new competitors (Mattel’s Barbie & Hot Wheels, Hasbro’s Transformers) and the digital onslaught (PlayStation, video games) drew children away from basic building blocks.
• Internal rot: Lego had become costly, complex, and hard to assemble.
• CEO’s diagnosis: “We had become a company that did not listen to our customers.” Successful firms often fall into complacency — failure to innovate, ignore customers, resist technology change. Analogous to Kodak, Xerox, Nokia.

The Reboot: Listening & Co‑Creation

Management acknowledged the problem and invested in market research — focus groups with kids and background research on brand identity.

Rediscovered Core Purpose

Kids valued creativity, the joy of building, and simplicity of bricks. This clarified Lego’s real product: creativity through building, not just plastic bricks.

Key Actions

Action	Mechanism	Outcome
LEGO Ideas platform	Fans submit original designs (MOCs: “My Own Creation”); community votes; Lego produces top designs	Fans become co‑creators and brand ambassadors
Super-fan community	AFOL (Adult Fans of Lego) recognized as a segment; adult content creators (YouTubers) emerge	Viral marketing, idea pipeline
Strategic partnerships	Tie‑ins with Star Wars (Oscar/Globe‑nominated film), then Harry Potter, Batman	Merged diehard fan communities → cross‑sales
Legoland theme parks	Disney‑style parks leveraging Lego universes	Brand extension, immersive experience
Embrace digital technology	Used digital tools to support physical play, not replace it	Technology as a friend, not threat

Outcome

Lego revived into the fastest‑growing toy company with ~$10 billion revenue. Success factors: community engagement, strengthened feedback loop, new partnerships, and technology as enabler.

flowchart TD
    A[Crisis: near bankruptcy] --> B[Diagnosis: complacency, lost touch]
    B --> C[Market research: kids value creativity, simplicity]
    C --> D[Rediscover core purpose]
    D --> E{Execution}
    E --> F[LEGO Ideas / MOCs / AFOL]
    E --> G[Partnerships: Star Wars, Harry Potter]
    E --> H[Digital engagement: movies, Legoland]
    F & G & H --> I[Revival: $10B, fastest growth]

Exam tip: The Lego turnaround is a classic user-centered innovation and co‑creation case. Be ready to explain how listening to users and turning them into co‑designers generates ideas when a firm faces disruption.

Key takeaways

• Complacency from past success can kill innovation — firms must continuously listen to customers and adapt to technology.
• Lego revived by rediscovering its core: creativity, simplicity, building.
• Co‑creation platforms (LEGO Ideas, MOCs) and super-fan communities (AFOL) turned fans into brand ambassadors and idea sources.
• Strategic partnerships with existing fan bases (Star Wars) merged communities and expanded reach.
• Technology was used as a friend to amplify the physical product, not as a threat.

Identifying New Product Opportunities

Identifying new product opportunities starts with systematically listening to the market. Rather than waiting for ideas to surface, organisations must actively scan multiple sources: changes in customers, competitors, technology, and internal records. Each source provides distinct clues about unmet needs or emerging demands.

Sources of Opportunity

1. Changing lifestyles & demography
Demographic shifts (e.g., Gen Z) bring new preferences for health, sustainability, and convenience. A snacks company must pivot from fried to baked or protein-based snacks to align with health-conscious consumers. Stay alert to shifts in behaviour, values, and spending patterns.

2. Competitor products
Continuously study what competitors are launching: new varieties, ingredients, labels, or features. A competitor’s move reveals a direction the market is heading and highlights gaps in your own portfolio.

3. Feedback from existing users
Use mobile surveys, product reviews, and in-app feedback to collect likes, dislikes, and frustrations. Frustrated customers are especially valuable — they pinpoint exactly what needs to change, offering clear signals for new product ideas.

4. Documentation of ideas
Maintain a living record of every idea evaluated, even those rejected. An idea that is not viable today (due to cost, technology, or market readiness) may become feasible later. Revisit the archive periodically.

5. Lead users
Lead users are advanced, proactive users who innovate on their own to solve needs ahead of the market. Identify and track them — their workarounds and modifications are blueprints for commercial opportunities.

6. Emerging technologies
Track the maturity of relevant technologies (AI, robotics, digital tools). When a technology becomes cheaper or more capable, previously infeasible ideas become viable. Being alert to technology curves allows timely product launches.

Exam tip: All six sources are distinct and testable. Memorise them as a checklist: Lifestyles, Competitors, Feedback, Documents, Lead users, Technology.

---

Buyer Utility Map

The Buyer Utility Map is a structured tool that systematically reveals where a company and its competitors provide value — and where they do not. It uses a 6×6 grid to plot customer experience stages (horizontal) against utility levers (vertical).

The grid

Stages of customer experience	Purchase	Delivery	Use	Supplements	Maintenance / Service	Disposal
Utility levers
Productivity
Simplicity
Convenience
Risk reduction
Fun & image
Environmental friendliness

• 36 cells total (6 stages × 6 levers).
• Plot your own offerings: for each stage, which utility levers does your product satisfy?
• Plot competitors’ offerings on the same grid.

Red vs. Blue Ocean

flowchart LR
    A[Map company & competitors in grid] --> B{Cells where both are present?}
    B -- Yes --> C[Red ocean: high competition, price wars, low margins]
    B -- No, empty cell --> D[Blue ocean: unmet need, freedom to price, innovation space]

• Red cells – highly competitive spaces where many firms fight for the same value proposition. Leads to margin erosion and “bleeding” competition.
• Blue cells / blank spaces – unmet customer needs. These are the richest opportunities for new products because the company can set its own terms without direct rivals.

Exam tip: The Buyer Utility Map is blue-ocean strategy applied at the product-opportunity level. Be ready to explain why companies cannot fill all 36 cells — limited resources and capabilities force focus.

---

Product Frustrations

Observing how customers struggle with existing products reveals direct opportunities for new or improved offerings. Frustrations fall into two broad categories.

Customer-side frustrations

• Complexity & difficulty of use – products with too many buttons (e.g., hotel shower panels, car controls) force users to consult manuals. Target users either cannot figure it out or find the process irritating.
• Inability to use as designed – the product is used for a purpose different from its intended design, indicating a mismatch.
• Inadequacy – product fails to meet user expectations (e.g., utensils that are awkward to hold, apps with missing features).

Design-side frustrations (organisational flaws)

• Inappropriate design – product does not suit the user (e.g., too large, too small, wrong shape).
• Short lifespan – does not last as long as the customer expects.
• Product interaction – using one product prevents simultaneous use of associated products (e.g., conflicting charger ports).
• Size / shape mismatch – a square object where an oval would fit better.
• Fails to meet application – does not deliver the full set of outcomes for the intended use.

Listening to customers’ pain points (e.g., side stand vs. centre stand on motorcycles) directly motivated design changes: many modern EVs eliminated the centre stand because users found it difficult to operate.

Exam tip: Product frustrations are a rich source of incremental innovation. Categorise them as customer-side (usability, expectations) vs. design-side (ergonomics, durability). Real-world examples like side stands vs. centre stands are high-yield for essays.

---

Key takeaways – Identifying New Product Opportunities

• Scan six sources systematically: lifestyles, competitors, feedback, idea archives, lead users, and emerging tech.
• The Buyer Utility Map is a 6×6 grid of customer experience stages × utility levers.
• Plot your offerings and competitors’ to find red cells (crowded) and blue cells (empty opportunities).
• Product frustrations arise from complexity, inadequacy, inappropriate design, or poor fit — both from the customer’s and the designer’s perspective.
• Frustrated customers are often more informative than satisfied ones.

Lead Users

Lead users are individuals or organizations whose current needs foreshadow those of the broader market – they experience a problem earlier or more intensely. Intuitively: instead of asking the average customer (who may not even know what they want), talk to the power users who already hack together workarounds. Their insights reveal latent needs and drive product refinement.

Types of Lead Users

Type	Description	Example (scissors)
Lead users in the target application area	Heavy, frequent users who experiment with the product itself.	Barbers, tailors – use scissors for hours daily; can report ergonomic pain points.
Lead users in analogous markets	Users in a different market with a very similar application or process.	Lawn-mower or grass-cutter operators – blades that require sharpness and durability; ideas transferable to scissors.
Lead users specialising in problem areas	Users who face extreme versions of the same problem the target product addresses.	Surgeons (precision cutting) or book publishers (straight, sharp cuts through stacks of paper).

Worked Example: Scissors Innovation from Lead Users

• Target lead user (tailor): Frustrated by having to mark cloth with chalk to cut straight lines.
• Idea derived: A laser pointer mounted on the scissors projects a straight cutting line, eliminating chalk marks and improving accuracy.
• Analogous inspiration: Industrial blades (lawn movers) suggest ways to achieve sharper, longer-lasting edges.

Service & Industrial Examples

• ICICI Bank & Infosys Finacle: When Infosys implemented its core banking product at a large, complex bank (ICICI), the real-world nuances – cheque processing, treasury management, KYC edge cases – were uncovered. The product gained features and robustness through this lead-user engagement, making it easier to sell to smaller banks.
• Boiler / Turbine Manufacturer: A first large contract (e.g., with a steel plant) forces the supplier to handle complex requirements, demonstrated competence, and added product capabilities that smaller contracts cannot provoke.

Lead User Project Stages (Rough Timeline)

Each stage ≈ 5–6 weeks:

1. Project Planning – scope, team, budget.
2. Identify Trends & Customer Needs – search for lead users and emerging patterns.
3. Preliminary Concept Generation – develop initial ideas using lead-user input.
4. Final Concept Generation – refine and select concepts based on deep lead-user feedback.

Limitations of Lead User Research

• Hard to identify – lead users are not always obvious; expansive search and convincing are required.
• Small sample – lead users are few; their feedback cannot substitute for conventional market research with large samples.
• Best used together – lead user insights complement broad market surveys; never replace them.

---

Building Superior User Experience – Peter Morville’s Honeycomb

The honeycomb framework evaluates product experience across seven facets. The core question: Is the product valuable to the user? Surrounding questions:

Facet	Question to ask
Useful	Does the product solve a real problem?
Desirable	Do users want it – is it appealing?
Accessible	Is it available through appropriate channels (stores, online)?
Credible	Can users trust the product’s quality and longevity?
Findable	Can users locate the product and its features (including relevance)?
Usable	Is it easy to use in practice?
Valuable	Does it deliver net benefit to the user and the organisation?

Exam tip: Morville’s honeycomb is a checklist for user-experience completeness. Be ready to list the six outer facets around “valuable”.

Key Takeaways

• Lead users are ahead of the market (heavy users, experimenters); they reveal needs ordinary users can’t articulate.
• Three types: target-area, analogous-market, problem-specialist.
• Real-world examples (scissors laser pointer, ICICI Finacle, steel-plant turbines) show how lead users refine products.
• Lead user projects are structured in four stages (~20–24 weeks total); they complement – not replace – market research.
• Morville’s honeycomb (useful, desirable, accessible, credible, findable, usable) plus valuable ensures a well-rounded user experience.

Market Research in New Product Development

Market research for new product development (NPD) differs fundamentally from research on existing products. The goal shifts from measuring satisfaction with a current offering to identifying unmet needs—gaps between what customers desire and what is currently available. This requires different methods, sample strategies, and interpretation.

Lead Users

Lead users are customers who face a need earlier than the mainstream market and are often positioned to benefit significantly from a solution. They provide rich, early feedback that supplements conventional market research.

• When lead users work well: Experience is high (e.g., large corporate clients, professional barbers, auto enthusiasts). They can articulate nuanced needs.
• When experience is low (or hard to articulate): Observation replaces direct questioning. Example: watching children play with toys to see enjoyment and difficulty, rather than asking them.

Exam tip: Lead-user research is not a replacement for market research; it is a subset — a focused, qualitative tool for early-stage insight.

Focus Groups and Observation

Focus groups reveal insights that individual interviews may miss through group interaction. Example: Lego used children in focus groups and observed their play behaviour to identify the gap in community and storytelling (e.g., missing “Marvel-like” experience).

• Interviews = individual, structured.
• Focus groups = open discussion, cross-stimulation, unanticipated ideas.

Market Research: New vs. Existing Products

Dimension	Existing product research	New product research
Purpose	Measure satisfaction, usage frequency, likes/dislikes	Identify unmet needs, gaps, missing features
Questions	Specific, easy to answer	Open-ended, exploratory: “What do you wish existed?”
Sample size	Large (e.g., mall surveys, hundreds or thousands)	Small (e.g., 30 users can capture 90–95% of needs)
Cost	Low per respondent	Higher per respondent (detailed interviews)
Difficulty of access	Easy (existing customers available)	Harder (need specific users/non-users)
Typical owner	Marketing / sales	Design / product management

Exam tip: 30 carefully chosen users (or even fewer) are often enough for new product research because you are after the gap, not statistical generalisation. Beyond that, you hit saturation – the same ideas repeat.

Saturation and Sample Strategy

• Saturation: After ~30 detailed interviews, additional interviews yield few new needs (~90–95% coverage).
• Selection: Choose users and non-users; focus on those with high involvement or dissatisfaction. Not every customer is useful.
• Iterative feedback: Because the sample is small, you can return to the same users with a prototype to test whether the solution meets their expectations.

Sources of Ideas for New Products

Ideas can come from anywhere — internally or externally. The organisation must stay alert.

flowchart LR
    A[Internal Sources] --> B[Employees, R&D, Sales, Marketing]
    C[External Sources] --> D[Lead users, End customers]
    C --> E[Resellers, Dealers, Auto enthusiasts]
    C --> F[Crowdsourcing, Competitions, Consultants]
    C --> G[Government regulations, Market trends]
    A & C --> H[Multiple ideas enter funnel]

Specific mechanisms:

• Case competitions (e.g., Asian Paints, L’Oreal, HUL) – low engagement but wide reach; companies collect tested ideas.
• Crowdsourcing – larger scale, diverse demographics. Example: Dell’s IdeaStorm collected ~10,000 ideas.
• Annual contests (e.g., Pillsbury Bake-Off) – focused collection from enthusiasts.
• Observation of competitors – e.g., other IIMs launching BBA programs → IIMB considers a similar program.

Exam tip: The execution differentiates, not the source. Many organisations get the same initial idea; what matters is how you refine and implement it.

User Toolkits

When customer needs are highly heterogeneous and difficult to capture via surveys, user toolkits let customers design or customise their own product. The company provides a “menu” of options and the customer experiments to find their ideal configuration.

• When to use: high variety, mass customisation desired, company cannot pre‑produce all variants.
• How it works: Toolkit enables users to experiment with features → they create a prototype → company delivers the final product.
• Examples:
  • Paint colour shade card – customer selects exact shade; company mixes base colours.
  • Dell laptop configurator – choose processor, RAM, storage → one‑off build.
  • Airline booking – pick connections, layovers, times → custom itinerary.
  • Jewellery – mix and match designs from a catalogue.
  • Hairstylist – choose from picture gallery; stylist personalises.

Exam tip: User toolkits are a way to access hard‑to‑articulate needs. If customers can’t tell you what they want, let them build it.

Key takeaways

• Lead users provide rich feedback; observe when experience is low.
• New product research is qualitative, small‑sample, gap‑focused; saturation occurs around 30 interviews.
• Idea sources are internal and external; stay alert to competitions, crowdsourcing, and dealers.
• User toolkits enable mass customisation when demand is heterogeneous; they shift experimentation to the customer.
• The innovation funnel starts with many ideas (from all sources) and progressively filters them through testing and refinement.

Requirements for Effective User Toolkit

A user toolkit is a set of design options, components, or modules that allows the customer to perform trial-and-error learning — experimenting, mixing, and matching — to arrive at a personalised solution. The company provides the palette; the user paints.

Core Requirements

Requirement	What it means	Example
Adequate options	The toolkit must contain enough pre-defined solutions/modules to cover all feasible design choices.	Paint shade card with all colour variants; frame catalogue on Lenskart.
User‑friendly	Users should be able to use their own design language and simple skills; no special training needed.	Drag‑and‑drop interface for configuring a laptop.
Configurable without company effort	The user’s design must translate directly into a product without requiring the company to re‑engineer or develop new components.	Modular laptop: slots for RAM, storage, GPU – just snap in.
Library of modules	A ready stock of standardised building blocks that can be assembled in many ways.	A furniture kit with pre‑cut boards and connectors.

Exam tip: The core principle is that the user does the design work. If a toolkit requires significant custom intervention from the company, the whole point of the toolkit (reduced cost, speed) is lost.

Why Companies Use Toolkits: Strategic Advantages

flowchart LR
  A[User toolkit] --> B[Trial-and-error by user]
  B --> C[Reduced development time]
  B --> D[More variety at lower cost]
  A --> E[Competitive advantage]
  E --> F[Difficult to copy]
  A --> G[Learn user trends]
  G --> H[Identify new features without formal market research]

• Competitive advantage – A well‑designed toolkit is hard to replicate, giving the company a sustainable edge.
• Reduced development time – The company spends minimal effort on design; it only configures and packages the user’s choice.
• Cost reduction – More product variations can be offered with less internal effort → economies of scope.
• First‑mover benefit – The pioneer (e.g., the first paint company to install an automatic tinting machine) gains a head start; competitors take time to learn.
• Learning about user trends – The pattern of user choices reveals what features or designs are popular, acting as a real‑time market research channel.

Exam tip: Toolkits shift the trial‑and‑error burden from the company to the user. This is the fundamental trade‑off: less company design effort, more customer control.

Key takeaways

• A user toolkit must offer enough options, be user‑friendly, and enable easy configuration without company rework.
• Toolkits reduce development time and cost while increasing product variety.
• They create competitive advantage (hard to copy) and can reveal user trends.
• If the company must intervene heavily, the toolkit model fails – it becomes a costly custom product instead.

Kano Model

The Kano model classifies user needs (product features) into five categories based on how they affect customer satisfaction. It answers: Which features must be included? Which will delight customers? Which are neutral or harmful?

Category	Description	If present	If absent
Must-have	Bare minimum; customer expects it.	Satisfaction only reaches baseline (no gain).	Extreme dissatisfaction; product fails.
One-dimensional	More is better; linear relationship.	Satisfaction increases proportionally.	Dissatisfaction increases proportionally.
Attractive	Not expected; surprises the customer.	Satisfaction spikes (delight).	No dissatisfaction (customer doesn’t miss it).
Indifferent	Customer does not care.	No effect.	No effect.
Reverse	Feature is actively disliked.	Dissatisfaction.	Satisfaction (its absence is preferred).

The Satisfaction Curve

• Must-have starts far below the baseline (dissatisfaction) at low implementation. As the feature is fully provided, satisfaction rises only to neutral (baseline). Not having it is a deal-breaker.
• One-dimensional is a straight line through the origin: as implementation increases, satisfaction increases linearly.
• Attractive starts at baseline with no implementation. As the feature is added, satisfaction shoots up dramatically, creating delight.
• Indifferent stays flat at neutral.
• Reverse decreases satisfaction as implementation increases.

Prioritization with Kano

1. Must-have – absolute minimum; include first.
2. One-dimensional – add incrementally; these drive price and willingness to pay.
3. Attractive – add after the above; differentiate and justify premium pricing.
4. Indifferent – ignore; avoid unnecessary cost.
5. Reverse – actively avoid.

Exam tip: A common mistake is treating attractive features as must-haves. Remember: attractive features delight but their absence does not cause dissatisfaction.

Key Takeaways

• Kano model has five need types: must-have, one-dimensional, attractive, indifferent, reverse.
• Must-haves are non-negotiable; their absence kills the product.
• One-dimensional features follow “more is better” and enable price tiers.
• Attractive features drive delight and premium perception.
• Indifferent and reverse features should be minimized or omitted.

---

Product Variety Matrix

The product variety matrix is a tool to design a product line – multiple variants of the same product that cater to different customer segments. It is built by combining satisfier levels (horizontal axis) with delighter levels (vertical axis).

Structure

	No delighter	Delighter 1	Delighter 2
Minimum satisfier	Base variant (must-have only)	Base + first delight	Base + second delight
Satisfier 1	Upgrade 1 (one-dimensional upgrade)	Upgrade 1 + delighter 1	Upgrade 1 + delighter 2
Satisfier 2	Upgrade 2	Upgrade 2 + delighter 1	Upgrade 2 + delighter 2

• Satisfier levels represent one-dimensional features (e.g., processor power, RAM, storage). Each level is a step-up that increases price.
• Delighter levels represent attractive features (e.g., slim design, long battery life, premium finish). Adding a delighter increases satisfaction without customers explicitly demanding it.

Real-World Examples

• Cars (e.g., Maruti Brezza or Vitara): Base engine with manual transmission (minimum satisfier, no delighter). Then variants with automatic transmission (satisfier 1), 4WD (satisfier 2), and delighter features like LED lights, sunroof, etc. Usually 4–9 variants.
• Laptops:
  • Apple: few variants (e.g., 14″ vs. 16″ screen – one-dimensional; M4/M5 chip – one-dimensional or attractive; slim design – delighter). Usually 4–5 options.
  • Dell: many variants – multiple processor tiers (i3/i5/i7), RAM sizes (8/16/32 GB), screen sizes, colours. Often >9 options.

Identifying Feature Categories via Survey

To classify features into Kano categories, ask paired positive and negative questions.

• Positive question: “How would you feel if the product has feature X?” (like / somewhat like / neutral / somewhat dislike / dislike)
• Negative question: “How would you feel if the product does not have feature X?”

Map the responses to a Kano evaluation table:

Positive response →<br>Negative response ↓	Like	Somewhat like	Neutral	Somewhat dislike	Dislike
Like	Reverse	Reverse	–	–	–
Somewhat like	Attractive	Attractive	–	–	–
Neutral	One-dimensional	One-dimensional	Indifferent	Indifferent	Reverse
Somewhat dislike	Must-have	Must-have	–	–	–
Dislike	–	–	–	–	–

Simplified example – actual grids are more detailed. The output tells you whether a feature is must-have, one-dimensional, attractive, indifferent, or reverse.

Worked Example: Laptop Variants

Consider two one-dimensional features (processor and RAM) and two attractive features (slim design, long battery life).

	No delighter	Delighter 1: Slim design	Delighter 2: Long battery life
Minimum: i3, 8GB RAM	₹50,000	₹55,000	₹58,000
Satisfier 1: i5, 16GB RAM	₹65,000	₹70,000	₹73,000
Satisfier 2: i7, 32GB RAM	₹85,000	₹90,000	₹95,000

The matrix suggests 9 possible variants. A company may choose to launch only a subset (e.g., 4–5) to avoid internal cannibalization while still covering the main price/satisfaction segments.

Why Use a Product Variety Matrix

• Clarity on where to position each variant.
• Pricing can be set per cell (higher satisfier/delighter → higher price).
• Customer choice – prevents customers from switching to competitors by offering an upgrade path within the same brand.
• Risk of cannibalization – some variants may eat sales of others, but this is acceptable if it retains the customer.

Key Takeaways

• The product variety matrix combines satisfier (one-dimensional) levels with delighter (attractive) levels.
• Horizontal axis = increasing one-dimensional performance; vertical axis = increasing delight.
• Each cell represents a distinct product variant with a unique price.
• Use Kano classification to decide which features go into each axis.
• Typical products (cars, laptops) have 4–9 variants; too many can overwhelm customers, too few may miss segments.

Evaluation of Innovation

After identifying customer needs and classifying opportunities, the next step is to evaluate which innovation ideas to pursue. Evaluation means systematically judging concepts, risks, and payoffs before committing resources. The goal is to reduce uncertainty and increase the probability of market success.

Scoring, Screening, and Concept Testing

Scoring and screening of product concepts turns subjective judgment into a prioritised list. Rate each concept against a set of parameters (e.g. strategic fit, market potential, technical feasibility) and compute a weighted score. Higher scores get priority.

Concept testing uses trials and market research to gather early feedback. One powerful method is giving lead users (early adopters who helped generate the idea) access to a prototype. Their evaluation provides direct improvement feedback before full-scale development.

At every stage, a cost‑benefit analysis should be performed for each feature or decision. Every feature involves a cost and a benefit; managers must be cognisant of both.

Exam tip: The ATAR model (Awareness, Trial, Availability, Repeat) is a classic framework for evaluating new product adoption — be ready to apply it to a case.

Risk‑Payoff Matrix

Any go/no‑go decision involves two possible actions (stop / continue) and two possible outcomes (fail / succeed). The resulting 2 × 2 risk‑payoff matrix clarifies the types of errors managers can make.

Decision \ Outcome	Project would fail if executed	Project would succeed if executed
Stop the project	AA — Correct decision (no error).	AB — Error of omission (opportunity cost). A competitor might succeed with a similar project.
Continue the project	BA — Error of commission (go error). Resources wasted on a failing project.	BB — Correct decision (no error).

• AA and BB are correct decisions.
• BA (continue but failure) is a costly mistake.
• AB (stop but it would have succeeded) is the error of dropping a good idea.

Managers must understand that they cannot always be 100 % right. The matrix forces explicit consideration of probability of success and the value at stake.

Four General Risk‑Management Strategies

Once risks are listed, choose one of four strategies to handle them.

Strategy	Definition	Example
Avoidance	Eliminate the risky project entirely. Incur opportunity cost but avoid potential failure.	Stop a risky project after initial investment; do not proceed to next stage.
Mitigation	Accept the risk but reduce it to an acceptable threshold. Redesign, add features, use multiple channels.	Launch a product only online if unsure of traction; add backup options; improve reliability.
Transfer	Shift responsibility to another organisation (joint venture, subcontractor, franchise).	McDonald’s franchise model — royalties collected, local partner bears operational risk.
Acceptance	Make no changes now; have a contingency plan ready.	Passive acceptance: wait and handle issues as they arise. Active acceptance: develop a contingency plan (e.g. enhanced customer service, crisis communication).

Planning Pitfalls

Many plans fail because they remain tentative — goals, costs, and targets lack clarity. A clear product charter or mission statement is essential. Watch for roadblocks (potholes) that emerge during execution, and anticipate people issues (interpersonal conflicts) that can derail progress.

Key takeaways

• Evaluate innovations via scoring, concept testing (with lead users and prototypes), and ATAR modelling.
• The risk‑payoff matrix (stop/continue × fail/succeed) reveals two types of error: go error (BA) and omission error (AB).
• Four risk strategies: avoidance, mitigation, transfer, acceptance (passive or active).
• Always perform cost‑benefit analysis per feature.
• Planning fails when it is tentative; a clear mission statement and anticipation of roadblocks are vital.

Concept Testing

Concept testing is a prescreening step within the evaluation process, performed before committing to the execution or development stage. Its twin goals are:

1. Identify and eliminate very poor concepts early, saving resources.
2. Roughly estimate market potential — perfect precision is impossible at this stage, so the focus is on high-level signals.

Estimating Intention to Use

The most common estimation method is to gauge buying intention via survey questions. For a new smartphone, for example:

“Will you buy this product?”
Answers are collected on a 5‑point scale:

Score	Intention	Label
5	Definitely will buy	Definitely buy
4	Probably will buy	Probably buy
3	May or may not buy	Indifferent
2	Probably will not buy	Not likely
1	Definitely will not buy	Definitely not

Exam tip: Only the first two categories (“definitely buy” and “probably buy”) are treated as target customers. Follow up only with these respondents. Weights can be assigned (e.g., 5 vs. 4) to refine estimates.

Methods of Concept Presentation

Method	Description	Cost / Complexity	Use Case
Verbal description	Pure text outlining product benefits, features, packaging, price.	Low; can test many ideas quickly.	Early screening, many concepts.
Description with sketch	Text + a visual (e.g., a can with colorful flavor branding).	Moderate	Better consumer reaction than pure text.
Prototype / model	Physical sample, e.g., a drink for tasting.	High; requires trials, multiple flavours, time.	Late-stage validation; costly but realistic.

Typical Questions Asked

• Buying intention (the 5‑point scale above)
• Uniqueness: “How different is this product from existing ones?” (Very / Somewhat / Slightly / Not at all)
• Usage frequency: “How often would you buy?” (e.g., More than once a week / Once a week / Twice a month / Once a month / Never)
• Believability: Does the claim (e.g., “healthy drink”) seem realistic?
• Problem importance: Does it solve a genuine need?
• Reaction to price (if included)
• Practicality, usability, heat, portability, etc.

Keep surveys short – one or two key questions per concept.

Key Choices in Concept Testing

Include price or not?

• For including price: The customer evaluates the full offer – a ₹100 vs. ₹50 drink changes the decision.
• Against including price: Price biases the feedback. You want pure product insights (e.g., taste, quality) first; pricing can be decided later.

Define the respondent group clearly (e.g., Gen Z, college students).
Mode of reaching them depends on the group: events, Instagram, email, focus groups (like the Lego case). Decide between individual interviews and group sessions.

Worked Example: New Diet Soft Drink

Verbal description given:
“A tasty sparkling beverage that quenches thirst, represses hunger, and blends orange and lime flavours. Helps control weight by reducing cravings for sweets and between‑meal snacks. Comes in 240 ml cans and 500 ml bottles. Costs about ₹40–₹50.”

Questions asked:

1. How different is this from existing drinks? (Very / Somewhat / Slightly / Not at all)
2. How often would you buy? (More than once a week / Once a week / Twice a month / Once a month / Never)

Key takeaways

• Concept testing is a prescreening tool to eliminate poor ideas and roughly estimate demand.
• The core metric is buying intention on a 5‑point scale; only top‑2 categories matter.
• Presentation modes range from verbal description (fast, cheap) to prototypes (costly, rich).
• Debate: include price to get realistic reactions, or exclude to avoid biasing product feedback.
• Respondent group and outreach mode must align with the target user profile.

---

Dimensions for Concept Evaluation

Beyond testing consumer reaction, a concept must be evaluated on several broader dimensions to decide whether to proceed.

Dimension	Key Questions
Strategic fit	Does the concept align with the corporate vision and strategy? (e.g., Reliance Jio’s vision: “data is the new oil”)
Customer fit	Does it meet unmet consumer needs? Will it increase customer loyalty? Is the perceived value high?
Market attractiveness	Is the concept unique relative to competitors? Can the firm become #1 or #2? Can it capture significant market share?
Technical feasibility	Is the concept realistically buildable?
Protectability	Is the concept difficult to copy? Can a competitive advantage be sustained?
Financial returns	What is the break‑even timeline? Will it achieve required earnings in the desired period?

Illustrative Example: Reliance Jio

Reliance’s move from oil/chemicals into telecom illustrates how these dimensions interact:

• Strategic fit: Oil’s long‑term advantage was declining; the company redefined “new oil” as data. Entering telecom aligned with this corporate logic.
• Customer fit: Offered free data and calls initially – huge perceived value, especially for first‑time smartphone users.
• Market attractiveness: The free pricing created a unique offer; within 3 months Jio gained 40 crore subscribers, catapulting it to #1 or #2 in a highly competitive, price‑sensitive market.
• Technical feasibility: Yes, network infrastructure was deployed.
• Financial returns: Break‑even took longer, but the massive subscriber base allowed faster recovery later. The strategy avoided heavy advertising spend – free service itself was the marketing.

Exam tip: The Jio case is a classic example of how a radical pricing approach can short‑circuit the typical slow market share growth. Use it to illustrate strategic fit, customer fit, and market attractiveness.

Key takeaways

• Evaluate concepts along six dimensions: strategic fit, customer fit, market attractiveness, technical feasibility, protectability, financial returns.
• Strategic fit ties the concept to the firm’s long‑term vision (e.g., data as new oil).
• Customer fit is about meeting real needs and delivering perceived value.
• Market attractiveness can be achieved through unique pricing (e.g., free) to rapidly gain market share.
• Financial returns may be delayed if the concept builds a large base first.

ATAR-Based Forecasting

ATAR stands for Awareness, Trial, Availability, and Repeat (or Recommendation for big-ticket items). It is a forecasting model that estimates the likely success of a new product by decomposing the adoption process into four sequential hurdles. Intuitively: a product can only succeed if people know about it, are willing to try it, can actually buy it, and then come back (or tell others).

The model yields a market‑share or revenue forecast as a multiplicative chain:

$\text{Market share} = \text{Awareness} \times \text{Trial} \times \text{Availability} \times \text{Repeat}$

Each factor is a proportion (0 to 1).

Component	Description	Example
Awareness	Percentage of target market who know the product exists.	First‑year advertising reach.
Trial	Percentage of aware consumers who purchase (or intend to purchase) – often derived from concept‑test “definitely buy” + “probably buy” (top‑2 boxes).	Respondents who say they will try.
Availability	Percentage of trial‑ready consumers who can actually find the product in stores or online.	Distribution coverage (online 100%, offline estimated 60%).
Repeat	For small‑ticket items: proportion of triers who make a second purchase. For big‑ticket items: proportion of triers who recommend the product to others (word‑of‑mouth).	Soft‑drink monthly repurchase; laptop user tells five friends.

flowchart LR
    A[Awareness] --> B[Trial]
    B --> C[Availability]
    C --> D[Repeat or Recommendation]

Forecasting Difficulties & Mitigation

Forecasting is easier for product‑line extensions (e.g., a new flavour of an existing soft drink) because historical data and known market segments provide a baseline. It is harder for radically new products (e.g., a novel degree program like BBA DB) where no analogous market exists.

Strategies to handle forecasting risk:

• Forecast only what you know – focus on situational understanding, not exact numbers. For example, availability may be easier to estimate than trial.
• Ignore poor forecasts – do not base critical decisions on unreliable numbers.
• Use a low‑cost, gradual launch – start with one variant, gather real data, then scale. This reduces commitment and improves subsequent forecasts.
• Assume the forecast is sound but prepare for risk – acknowledge uncertainty and have contingency plans.
• Adopt a lifecycle perspective – initial stages are hard to predict, but over the full product lifecycle (S‑curve) forecasts become more stable.

Exam tip: ATAR is useful for identifying where the bottleneck is (e.g., low awareness vs. low repeat). The multiplicative nature means a weak link drags down the entire forecast.

Key takeaways

• ATAR = Awareness → Trial → Availability → Repeat/Recommendation.
• Each stage is a proportion; multiply all four to estimate market share.
• Extensions are easier to forecast than completely new products.
• Mitigate risk by gradual launch, focusing on what you know, and not over‑relying on single numbers.

---

Conjoint Analysis in Concept Testing

Once concept‑testing responses are collected, the next step is to interpret them to understand how consumers perceive the product relative to competition and to identify the benefit segment it belongs to.

Identifying Benefit Segments

Responses are plotted on perceptual dimensions (e.g., fashion vs. comfort for a dress). Using cluster analysis, consumers are grouped into segments:

• High on both fashion and comfort
• High on comfort only
• High on fashion only
• Low on both

The product’s location on these axes – the joint space map – shows which segment it appeals to. This may differ from the designer’s original intention. For example, a product designed as “fashionable” may actually be perceived as “comfortable” by customers.

Joint Space Map & Competitive Positioning

A joint space map plots the product and competitors on the same axes (derived from factor scores and regression). This reveals:

• Direct competition – products in the same cluster.
• Opportunity gaps – empty regions of the map.
• Strategic adjustments – price, features, or messaging to target a specific segment.

Example – Automobile segments: Concept testing can reveal whether customers see the product as appealing to experience seekers, performance seekers, safety‑conscious, or price‑conscious buyers. If the designer aimed for “all‑rounder” but customers cluster it as “safety‑conscious”, that becomes the core positioning.

Pricing & Offering Design

Concept testing can also inform pricing models. Example – Fastag toll collection: by testing the concept of electronic tolls, one might discover whether a price discount vs. cash is needed, or whether a monthly pass (vs. usage‑based) would be accepted. The test reveals customer preferences that guide execution.

Key takeaways

• Cluster analysis groups consumers into benefit segments based on concept‑test responses.
• Joint space maps visually position the product vs. competitors on key dimensions.
• Concept testing can reveal mismatches between intended and perceived positioning.
• Pricing and offering models (discounts, subscriptions) can be validated through concept testing.

---

Product Protocol

The product protocol (also called product requirements, product definition, or deliverables) is the final outcome of the new‑product process. It synthesises the concept‑testing insights into a clear specification.

A protocol articulates:

• Target market – who the product is for.
• Positioning – how it is to be perceived relative to competition.
• Attributes – the benefits, functions, and features customers will experience.

Example – healthier soft drink for youth:

• Target: youth segment.
• Positioning: a healthier alternative to traditional soft drinks.
• Attributes: lower sugar, natural ingredients, refreshing taste.

The protocol serves as the guiding document for subsequent development, marketing, and launch decisions.

Key takeaways

• Product protocol = final definition of what the product will be.
• Includes target market, positioning, and attribute list.
• Derived from concept testing and prior stages; aligns the organisation on a shared vision.

Quality Function Deployment (QFD)

Quality Function Deployment (QFD) is a structured, documented process that translates customer needs (the “what”) into engineering characteristics (the “how”) at every stage of product development. Invented in Japanese automobile industry (mid‑20th century), it ensures that the voice of the customer (VOC) stays central from concept to production.

The core visual tool is the House of Quality – a single diagram that captures all relevant information: customer requirements, technical responses, competitive positioning, inter‑relationships, and priorities.

---

Structure of the House of Quality

flowchart TD
    A[Left Wall: Customer Requirements & Importance] --> B[Body: Relationship Matrix<br>9/3/1 or 5/3/2]
    C[Ceiling: Technical Requirements (Hows)] --> B
    B --> D[Floor: Technical Importance Weights & Targets]
    E[Roof: Correlations among Technical Requirements] --> C
    F[Right Side: Competitive Assessment] --> A

Part	Content	Purpose
Left side	List of customer requirements (Whats) with importance ratings (e.g., 1‑5)	Captures the voice of the customer.
Ceiling / Top	Technical requirements (Hows) – engineering metrics that will satisfy the Whats	Translates customer language into design parameters.
Body (middle)	Relationship matrix – each cell shows how strongly a “How” fulfills a “What”. Typical scales: 9 (strong), 3 (moderate), 1 (weak).	Quantifies the link between customer desires and technical actions.
Roof	Correlation matrix among technical requirements – symbols: ++, +, 0, –, – –	Identifies trade‑offs or synergies (e.g., weight vs. strength).
Right side	Competitive benchmarking – ratings (1‑5) of own product vs. 2‑3 competitors on each customer requirement	Shows market gaps and opportunities.
Floor (bottom)	Calculated importance weights (absolute and relative %) and target values	Prioritises which technical requirements to focus resources on.

Exam tip: The numeric scale in the relationship matrix (9‑3‑1 or 5‑3‑2) is a design choice – always check which scale the problem uses.

---

Worked Example: Pressure Cooker

Step 1 – Customer Requirements (Whats) with Importance (1‑5)

Customer Requirement	Customer Importance
Cooks fast	5
Alarm when done	4
Safe to cook	5
Safe to handle	5
Easy to use	4
Retains nutrition	4
Durable	3

Step 2 – Technical Requirements (Hows) and Relationship Matrix

Technical requirements identified: Cooking pressure, Sealing, Shape, Size, Thermal conductivity, Weight, Material strength, Pressure release, Weight (again – note duplication in lecture; keep faithful – we list distinct ones as in transcript: pressure, sealing, shape, size, thermal conductivity, weight, strength, pressure release). For brevity, we show a subset.

Fill each cell with 9 (strong), 3 (moderate), 1 (weak), or blank (no relation).

Customer Requirement	Cooking pressure	Sealing	Shape	Size	…	Weight	Material strength
Cooks fast	9	9	1	3	…	1	1
Alarm when done	9	3	1	1	…	1	1
Safe to cook	9	9	3	3	…	9	9
Safe to handle	3	9	3	1	…	9	9
Easy to use	1	3	9	3	…	3	1
Retains nutrition	9	3	1	1	…	1	1
Durable	3	1	1	1	…	3	9

(Only a few columns shown; actual matrix would be complete.)

Step 3 – Calculate Absolute Importance for Each Technical Requirement

For each technical requirement column:
$\text{Absolute importance} = \sum_{\text{all customer requirements}} (\text{Customer importance} \times \text{Relationship strength})$

Example: Cooking pressure
$= (5 \times 9) + (4 \times 9) + (5 \times 9) + (5 \times 3) + (4 \times 1) + (4 \times 9) + (3 \times 3)$
$= 45 + 36 + 45 + 15 + 4 + 36 + 9 = 190$

Similarly, other columns yield totals (e.g., weight: $4 \times 9 + 4 \times 9 = 72$; material strength: $5 \times 9 + 4 \times 9 + 3 \times 9 = 108$ – adjust as per actual matrix). Sum of all absolute importances = 999 (in example).

Step 4 – Relative Importance (%)

$\text{Relative importance} = \frac{\text{Absolute importance}}{\text{Total}} \times 100\%$

Technical Requirement	Absolute	Relative
Cooking pressure	190	19.0%
Material strength	150	15.0%
Sealing	121	12.1%
Shape	123	12.3%
…	…	…
Weight	72	7.2%

This ranking tells the team which technical parameters deserve highest investment.

Step 5 – Competitive Assessment (Right Side)

Rate own product and two competitors (A, B) on each customer requirement (1‑5).

Customer Requirement	Our product	Competitor A	Competitor B
Cooks fast	4	3	4
Alarm when done	4	4	3
Safe to cook	5	5	4
…	…	…	…

Identifies where to improve to gain advantage.

Step 6 – Roof: Technical Correlations

Example correlations:

• Weight ↔ Material strength: strongly positive (++).
• Size ↔ Weight: positive (+).
• Cooking pressure ↔ Seal: strongly positive.
• Pressure release ↔ Shape: negative (–) (certain shapes hinder release).

This reveals conflicts (e.g., increasing pressure may reduce safe handling) that require trade‑off decisions.

---

Multi‑Stage QFD Deployment

QFD is not a one‑shot tool. It cascades through four levels, each stage converting the “how” of the previous stage into the “what” of the next:

Stage	Input (What)	Output (How)
1. System / Product Planning	Voice of Customer (VOC) → customer requirements & competition analysis	Product specifications – engineering characteristics, priorities, targets
2. Part / Subsystem Deployment	Engineering characteristics from Stage 1	Critical part characteristics – specifications for each part/assembly
3. Process Planning	Part characteristics	Process parameters – process flow, key process controls
4. Production Planning	Process parameters	Production & quality controls – scheduling, inspection points, operator instructions

This keeps the original customer intent alive through every design and manufacturing decision.

Exam tip: The first stage (House of Quality) is the most tested. The cascade logic – “how becomes what” – is a key concept. You may be asked to draw a simplified QFD for a given product.

---

Key Takeaways

• QFD (House of Quality) is a matrix that links customer needs to technical requirements.
• Relationship matrix uses a 9‑3‑1 (or 5‑3‑2) scale to quantify links.
• Absolute importance = sum(product of customer importance × relationship score) per technical requirement.
• Relative importance (%) prioritises where to allocate resources.
• Roof correlations reveal synergies or trade‑offs among technical parameters.
• QFD can be applied in four cascading stages: product planning → part deployment → process planning → production planning.
• Primary benefit: a single visual document that aligns the entire team on what matters most to the customer.

Benefits of Quality Function Deployment (QFD)

Quality Function Deployment (QFD) – often captured in the House of Quality – is a structured method that maps customer requirements to technical specifications, manufacturing processes, and control plans. Its real power is providing a single, complete snapshot of what is needed, how it will be achieved, and where trade-offs exist.

Reduced design changes and earlier gap identification

Without QFD, design changes tend to emerge late and ad hoc. QFD forces upfront clarity on product features, competitor positioning, and process requirements. Gaps are identified early, so the number of late-stage design changes drops significantly.

Increased customer satisfaction and enhanced quality

By explicitly mapping customer wants (voice of the customer) to technical features, QFD reveals which features are must-haves vs. attractive (Kano model). Incorporating features that competitors already offer raises perceived quality and satisfaction.

Lower cost

Late design changes are expensive. QFD’s upfront planning reduces rework and clarifies the production process, directly lowering development and manufacturing costs.

End-to-end cross-functional view

Benefit	How QFD delivers it
Deliver on schedule	Complete picture enables tracking, accountability, and monitoring for product managers
Improved development cycle	Design and planning are integrated; cycle time shortens
Minimise startup difficulties	Visibility and accountability reduce teething problems

Easier internal knowledge transfer

The House of Quality is a single compact document containing all design rationale, trade-offs, and linkages. It becomes a shared language for cross-functional teams. Trade-offs – e.g., adding a feature requires a technology change or cost increase – are visually clear and easily communicated.

Supports flexibility and feature rework

When new features must be added or existing ones reworked, QFD helps assess the trade-offs and evaluate the impact on cost, technology, and manufacturing.

Exam tip: The key exam point is that QFD reduces late design changes and provides clarity – not just for engineers but for marketing, finance, and management.

Key takeaways

• QFD gives a complete, upfront picture → fewer design changes, lower cost.
• Customer satisfaction increases because gaps vs. competitors are filled.
• Cross-functional visibility improves schedule adherence and accountability.
• The House of Quality is a single document that makes trade-offs visible.
• QFD shortens development cycle and minimises startup difficulties.
• Knowledge transfer is easier because all information is compact and linked.

---

Financial and Managerial Analysis for Concept Selection

Once product concepts are generated and refined through QFD, the organisation must decide which projects to pursue. Financial metrics are important – but not the only factor. Managerial and strategic considerations often override pure financial projections.

Role of financial analysis

Common financial criteria:

• Return on Investment (ROI)
• Payback period
• Internal Rate of Return (IRR)

These are typically used as go/no-go stage gates. However, at early stages financial projections are estimates; they guide decisions but are not definitive.

Strategic fit: the non-financial dimension

Committing to too many projects strains finite resources – not only money but human capital, factory capacity, and management attention. Therefore, project selection must consider strategic fit.

Two broad approaches exist:

flowchart LR
    A[Strategic Fit Approaches] --> B[Top-down]
    A --> C[Bottom-up]
    B --> D[Corporate/ SBU sets strategy]
    B --> E[Allocates funds across projects]
    B --> F[Centralised resource allocation]
    C --> G[Selection tools embed strategic criteria]
    C --> H[Project teams filter using corporate logic]
    C --> I[Decentralised filtering]
    D & F & G & H --> J[Best firms mix both]

• Top-down: Organisation (or SBU) decides strategy, then allocates funds and resources to projects that align. Centralised control.
• Bottom-up: Strategic criteria are built into selection tools. Project teams apply the corporate mission, objectives, and competencies to filter ideas. Decentralised but aligned.

Well-performing organisations typically use a mix of both.

A 7-point scoring model for non-financial analysis

The lecture outlines a multi-criteria scoring model that captures both management and customer interests alongside financial ones:

1. Management interest – Does the project have top-level support?
2. Customer interest – Is there strong customer demand?
3. Sustainability of competitive advantage – Will the project strengthen or erode the firm’s competitive edge? (Monopolies often neglect innovation – a classic pitfall.)
4. Technical feasibility – Can we actually develop this? QFD maps technical requirements, revealing capability gaps.
5. Business case strength – Combines financial projections and competitive advantage sustainability.
6. Fit with core competencies – Does the project leverage what the organisation does best?
7. Impact and profitability – Expected contribution to the bottom line.

Exam tip: Financial projections are not gospel at early stages – strategic fit and competitive advantage often carry more weight. Do not memorise the 7 points blindly; understand that they cover four themes: strategic fit, technical feasibility, competitive advantage, and profitability.

Key takeaways

• Financial metrics (ROI, payback, IRR) are common gate criteria but only projections.
• Resource constraints (people, capacity) force prioritisation – do not overcommit.
• Strategic fit is assessed via top-down (centralised) or bottom-up (decentralised) approaches; best firms combine both.
• A scoring model integrating management interest, customer interest, competitive advantage, technical feasibility, business case, core competency fit, and profitability helps filter concepts.
• QFD outputs directly feed into feasibility and competency assessments.

Overview

Rubbermaid (later acquired by Newell) manufactured thousands of small, everyday functional products — plastic containers, trashcans, laundry baskets, kitchen organisers, bathroom accessories. These are not bought on impulse; customers replace them only when the old one fails. Therefore, to grow revenue the company must continuously innovate: add new features, designs, or uses that persuade customers to upgrade or buy new categories.

The company achieved ~90% success rate on new products, and 30% of annual sales came from products less than five years old.

Product Range & Innovation Pipeline

Rubbermaid offered ~500,000 SKUs at its peak. Innovations were small, clever improvements to ordinary items. Example: the evolution of a plastic bucket:

Innovation	Description	Benefit
Lid	Added a cover	Keeps contents contained, trash odour sealed
Foot lever	Lever to open lid with foot	Hands-free operation, hygiene
Wheels	Wheels attached under bucket	Easy movement of heavy loads (hotels, hospitals)
Commercial size	Larger capacity with wheels	Professional cleaning and waste handling

Idea Generation Methods

Rubbermaid’s new product strategy was embedded in the organisation’s basic vision: meet consumer need. Ideas came from:

• Customer complaints / dissatisfaction: Executives were encouraged to read all complaints. Problem-finding and -solving was everyone’s job.
• Focus groups: Customers invited to share usage problems.
• Direct observation: A Rubbermaid CEO saw a hotel doorman struggling to sweep dirt into a dustpan; the problem led to thin-lipped dustpans with a sharp edge.
• Lifestyle changes: Shrinking living rooms → smaller furniture; poolside use → shatterproof plastic glasses.

flowchart LR
    A[Customer problem / observation] --> B[Idea generation]
    B --> C[Prototype / new product]
    C --> D[Market feedback]
    D -->|Further refinement| B
    D -->|Product success| E[Revenue growth]

Acquisition by Newell – Preserving the Innovation Culture

When Newell (a large household products company) acquired Rubbermaid, the goal was to absorb Rubbermaid’s innovation capability. To protect the fragile innovation culture from being diluted by Newell’s efficiency‑focused culture:

• Newell kept Rubbermaid’s plants separate.
• Rubbermaid continued its product‑innovation focus, while Newell handled scale‑related efficiency.

Key Takeaways

• Functional products require constant innovation because replacement cycles are long.
• Ideas come from listening to customers – especially complaints and direct observation.
• High innovation success (90 %) can be sustained if the culture is protected after an acquisition.
• Even small, non‑technology changes (lid, wheel, dustpan lip) drive revenue.

Exam tip: Rubbermaid is a classic example of market‑driven (not technology‑driven) innovation. The key metric: 30 % of sales from products <5 years old.

---

Background

Steve Ells opened the first Chipotle Mexican Grill in 1993 near a university campus in Denver. His original plan was to use the burrito store as a cash cow to fund a fine‑dining restaurant. Instead, the concept took off on its own – and Ells pivoted.

What Worked – The “Fast Casual” Model

Chipotle fell into a position between fast food and full‑service dining – a segment later called fast casual. Key success factors:

Factor	Description	Advantage
Simple menu	Only tacos & burritos, limited choices	Minimal pre‑preparation; no need for processed ingredients
Made‑to‑order	Customer chooses ingredients as they go	Customisation without pre‑planning
Open kitchen	Counter and preparation visible	Visual freshness and transparency
Fresh preparation	Ingredients prepared in‑store, not pre‑processed	Aligns with “food with integrity” vision
Clean environment	Implicit hygiene and quality	Builds trust without advertising

“Food with Integrity” – Execution Over Advertising

Ells never advertised the slogan. Instead, the brand communicated it through every action:

• Open kitchen → customers see freshness.
• Made‑to‑order → customers feel quality.
• Clean, simple store → customers infer integrity.

The core lesson: let the product do the talking. Word‑of‑mouth and customer perception made Chipotle a healthy fast‑food brand without a major ad campaign.

Scaling & Ownership

• After local success, Chipotle expanded regionally, then nationally.
• McDonald’s bought 91% of the brand at one point (later divested).
• The accidental discovery of the fast‑casual niche proved that execution (simple menu, open kitchen, fresh food) mattered more than an elaborate initial plan.

Key Takeaways

• A concept can succeed even if it was an afterthought – execution is everything.
• Limited menu reduces complexity and cost, and can delight customers who want quick, customised food.
• “Food with integrity” is a vision that must be demonstrated, not declared.
• The fast‑casual segment was novel at the time; Chipotle defined it.

Exam tip: Chipotle illustrates that concept testing might not catch an accidental winner – but disciplined execution and alignment of every touchpoint (kitchen, menu, pricing) turned hunch into a category.

---

Application: Concept Testing for a New Restaurant

The lecture poses a concept‑testing exercise: if you were to launch a food truck or a fast‑food joint, how would you test decisions on:

• Menu breadth – elaborate multi‑cuisine (4‑page menu) vs. limited (4–5 items)?
• Price point – low, mid, or high relative to competitors?
• Ambience – sit‑down restaurant (casual/fast‑turnaround) vs. standing / takeaway only?
• Service style – self‑service vs. full service?

Suggested Steps (based on earlier module discussion)

1. Define the target customer – e.g., students, office workers, families.
2. Generate alternative concepts – combinations of menu, price, ambience, service.
3. Screen concepts qualitatively – using criteria like feasibility, competitive edge, cost.
4. Test with a small sample – e.g., pop‑up, survey, or taste test.
5. Measure key metrics – purchase intent, willingness to pay, perceived value.
6. Iterate – refine based on feedback.

Exam tip: Concept testing must evaluate the whole system (menu + price + ambience) because they interact. A limited menu with low price and self‑service is very different from a limited menu with high price and sit‑down service.

Introduction to the Module

This module bridges core strategy concepts (previously studied in competition/strategy courses) with the new product development (NPD) process. Rather than re‑teaching strategy from scratch, it selects elements specifically applicable to new products and examines them through a consulting lens.

The module covers three main topics:

• Blue Ocean Strategy – a framework for creating uncontested market space rather than competing in existing, crowded markets.
• New Product Business Plan – the structured document that articulates the product’s value proposition, market opportunity, financials, and execution roadmap.
• Strategy Consulting for New Products – the role and methods used by consultants to advise firms on product strategy, including how they diagnose problems, analyse markets, and recommend actions. This is presented as a generic construct, but with specific relevance to new products.

Exam tip: The transcript does not elaborate on any of these topics. You are expected to draw on your prior strategy knowledge and the NPD theory covered earlier in the course. Exam questions will likely test how Blue Ocean Strategy applies to a new product context, how a business plan differs for a new product versus an established one, and what a strategy consultant does on a typical new‑product engagement.

Key takeaways

• This module extends prior strategy work into the new product domain.
• Three pillars: Blue Ocean Strategy, new product business plan, and strategy consulting.
• Blue Ocean Strategy is presented as a starting point (likely a brief review).
• The business plan section will be practical – a concrete deliverable for a new product.
• Strategy consulting is treated generically, but the examples and framing focus on new products.
• No specific definitions, models, or numbers are given in the transcript; these will appear in subsequent lectures.

Strategy Canvas

Strategy Canvas is a visual representation of the relative levels of investment across the key competitive factors in an industry. It plots the performance of different players on each factor, revealing the current industry value curve and identifying where a new entrant could diverge.

Blue Ocean vs. Red Ocean

• Red Ocean: Existing, highly competitive market space. Intense rivalry, price wars, and a "bloodbath" as firms fight for share.
• Blue Ocean: Uncontested market space. No direct competition; the firm creates a new demand by offering something radically different.

A strategic canvas helps map the current industry landscape (red ocean) and then plot the desired model for a blue ocean strategy.

Southwest Airlines: A Blue Ocean Example

Southwest Airlines created a blue ocean by diverging from the traditional hub-and-spoke model used by full-service carriers. Their strategy:

• Point-to-point flying – no connecting passengers, no hub transfers. Reduces operational complexity, delays, and luggage handling errors.
• Avoid major airports – operate from smaller, less congested (Tier‑2) airports. Faster turnaround, lower landing fees, less competition on routes.
• Single aircraft type – all Boeing 737s. Simplifies maintenance, pilot training, and ground crew operations → higher efficiency.
• No frills – no free meals, no seat selection, no lounge access. Cuts cost and simplifies service.

Result: High airtime (planes earn money only in the air); very short turnaround times (e.g., 25 minutes); high on‑time performance.

When plotted on a strategic canvas against traditional airlines, the value curve of Southwest is dramatically different – lower on most traditional factors (price, meals, lounge, hub connectivity) but higher on speed, punctuality, and simplicity.

🔍 Key insight: Southwest’s real competition shifted from other airlines to luxury buses and long‑distance cabs – point‑to‑point travel at higher speed. The canvas revealed an entirely new market space.

The ERRC Grid (Blue Ocean Framework)

The ERRC Grid (Eliminate–Reduce–Raise–Create) is a tool for systematically constructing a blue ocean strategy. It forces a firm to challenge industry assumptions across four actions.

Action	Question	Example (Southwest)
Eliminate	Which factors the industry takes for granted can be abolished?	Free meals, lounge access, seat selection, hub connectivity
Reduce	Which factors can be reduced well below the industry standard?	Number of flight options/connections; no first class or complex fare classes
Raise	Which factors should be raised above the industry standard?	On‑time performance, turnaround speed, baggage handling time
Create	Which factors should be created that the industry has never offered?	Direct point‑to‑point routes between Tier‑2 cities (e.g., Indore–Patna)

How ERRC Works

1. Identify all competitive factors in the industry.
2. Decide which to eliminate, reduce, raise, or create.
3. The resulting combination produces a new value curve that is different from competitors’.

Exam tip: The ERRC grid is the most tested tool for constructing a blue ocean. Be able to apply it to a case – always ask: What can we eliminate? What can we reduce? What can we raise? What can we create? – and explain how the new mix reduces cost while increasing buyer value.

Strategic Canvas in Action: Plotting the Blue Ocean

After applying ERRC, the new value curve sits between the industry (traditional airlines) and substitute modes (bus/cab). The resulting offering beats substitutes on speed and convenience without matching legacy airlines on cost.

Key takeaways

• Strategy Canvas visualizes the current competitive landscape; ERRC designs a new one.
• Blue ocean = no direct competition; red ocean = intense rivalry.
• Southwest’s success came from eliminating frills, reducing connections, raising punctuality, and creating new point‑to‑point routes in smaller airports.
• The ERRC framework systematically reduces cost (eliminate/reduce) and increases buyer value (raise/create).
• A well‑executed ERRC strategy often positions the firm to compete with substitutes (e.g., buses) rather than incumbents.

Difference Between Red Ocean Strategy and Blue Ocean Strategy

Red Ocean Strategy operates in an existing market space – competing for the same customers with similar products/services. Blue Ocean Strategy creates an uncontested market space where competition is irrelevant – you offer something so different that existing rivals no longer matter.

Intuition: A street with four Indian restaurants. If you open a fifth serving the same cuisine, you fight over the same 100 daily customers – that's a red ocean. If you instead serve a unique, innovative dish not available anywhere nearby, people will travel 20km to taste it – that's a blue ocean. Your price is no longer compared to the dal-rice at ₹100.

Core Differences

Dimension	Red Ocean Strategy	Blue Ocean Strategy
Market space	Compete in existing market space	Create uncontested market space
Goal	Beat the competition	Make competition irrelevant
Demand	Exploit existing demand (zero‑sum game)	Create and capture new demand
Customer focus	Attract existing customers (e.g., local office workers for lunch)	Attract non‑customers (people willing to travel for the experience)
Value‑Cost trade‑off	Necessary – more features drives higher cost (differentiation vs. low cost)	Can be avoided – pursue differentiation and low cost simultaneously (e.g., upgrading bus travellers to low‑cost airline service)
Activity system	Aligned with either low cost or differentiation	Designed to pursue both differentiation and low cost (focus on creating new experience)

Strategic Canvas & Steps to Construct a Blue Ocean Strategy

1. Draw the "as‑is" strategic canvas – map the current model for the industry (what factors does the market compete on? How high/low are they?).
2. Go to the field – observe consumers in action, study the ecosystem: services, price points, how customers deal with changes.
3. Assess factors for elimination or change – decide which factors to Eliminate, Reduce, Raise, or Create (the ERRC grid).
   • Create something that doesn't exist in the current market space but can be delivered within your capacity.
4. Draw the "to‑be" strategic canvas – show the new strategy curve (a different profile from existing rivals).
5. Articulate a compelling tagline that captures the new value proposition.

flowchart LR
  A[Draw as-is canvas] --> B[Field observation]
  B --> C[ERRC evaluation]
  C --> D[Draw to-be canvas]
  D --> E[Articulate tagline]

Exam tip: The value‑cost trade‑off is a central concept in generic strategy (Porter). Blue Ocean Strategy challenges this by showing you can break the trade‑off (e.g., Southwest Airlines – low cost and high service on key factors). Know the ERRC framework and the strategic canvas.

Worked Example: Restaurant on a Street

• Red ocean: 4 existing restaurants serving standard Indian cuisine (dal, roti, sabji). A 5th similar restaurant opens – customers compare price, quality, ambience. Competition is a zero‑sum game over the same 100 daily customers.
• Blue ocean: The 5th restaurant offers a unique, innovative food item not available elsewhere. It attracts customers from outside the area (non‑customers). The price is not compared to the other restaurants because the product is different – competition becomes irrelevant.

Key Takeaways

• Red ocean = fight for share in an existing market; blue ocean = create a new market where you are the only player.
• Blue ocean targets non‑customers, not existing customers.
• The ERRC grid (Eliminate, Reduce, Raise, Create) is the tool to build a new value curve.
• Blue ocean often enables simultaneous differentiation and low cost, breaking the traditional trade‑off.
• The strategic canvas visually contrasts the as‑is vs. to‑be strategy profiles.

Blue Ocean Strategy Examples

A blue ocean creates uncontested market space that makes competition irrelevant. Instead of fighting over existing demand (red ocean), a blue ocean generates new demand by offering a leap in value. The two key tests: (1) are you offering something genuinely different? (2) are you eliminating the trade-offs that force customers to choose between value and cost?

Petrol pumps + EV charging stations – a mini blue ocean

Traditional petrol pumps are red ocean: little differentiation, price wars. Adding charging stations (for EVs) shifts the offering. While the car charges (~1–1.5 hours), the customer has free time. The pump can now offer a retail outlet, food joint, coffee service – turning waiting time into a separate revenue stream and a better experience. This is a small-scale blue ocean: the product bundle (fuel/charge + services) is new, and the trade-off “fast fill-up vs. convenience” is eliminated.

IPL as a blue ocean – full analysis

The Indian Premier League (IPL) launched in 2008 as a T20 franchise-based cricket league. Traditional cricket (Test, ODI) was struggling to hold younger audiences. IPL redefined the sport from a long, technical game into a 3-hour entertainment package. The following table and ERRC grid capture how it created new demand.

Comparing traditional ODI/Test cricket vs. IPL

Dimension	Traditional Cricket (ODI/Test)	IPL
Duration	~8 hours (ODI) or 5 days (Test)	~3 hours
Time slot	Daytime (morning to evening)	Evening prime time (7:30 PM start)
Season	Various, no fixed window	April–May (summer vacation, no international cricket)
Player base	Only domestic or national team	Mix of domestic and top international stars
Team structure	National/state teams	City-based franchises
Salary	Fixed category-wise salary	Market-driven via player auction
Stadium experience	Basic – watch cricket only	Music, DJ, cheerleaders, food, Bollywood owners
Target audience	Cricket purists / traditional fans	Families, youth, entertainment seekers
Technical demand	High – technique matters	Lower – aggressive hitting (4s, 6s) rewarded
Competition balance	Often weak or strong team mismatches	Balanced via auction and salary cap – every team looks competitive on paper
Revenue model	BCCI paid Doordarshan to telecast	Broadcasters (Jio, Star) pay huge fees (~₹24,000 crore)

ERRC Grid for IPL (vs. ODI/Test cricket)

Eliminate, Reduce, Raise, Create – the blue ocean strategy canvas tool.

Eliminate	Raise
• Long, boring periods (draws, slow over rate)	• Entertainment package (music, cheerleaders, family appeal)
• Technical perfection requirement for audience enjoyment	• Number of 4s & 6s (high scoring)
• Fixed salary structure	• Quality of competition (top international + domestic players)
	• Evening prime-time slot
	• Stadium experience (food, dance, Bollywood stars as owners)
Reduce	Create
• Game time (5 days → 3 hours)	• Franchise + city-based model (local connect, fan engagement)
• Number of teams (domestic Ranji has many; IPL limited to 8)	• Player auction (ensures level playing field)
• Rules that slow the game (e.g., Test field restrictions)	• Market-driven salaries (demand & supply)
	• 3-hour entertainment-sports hybrid
	• Summer vacation window + exclusive international player availability

Why IPL succeeded – key drivers

1. Timing

   • India won the 2007 T20 World Cup → massive interest in T20.
   • Launch came immediately after that win, using the popularity and star power.
   • Season set in April–May: summer vacation → children as audience; no other major cricket worldwide → international players free.

2. Learning from other sports

   • Franchise model borrowed from English Premier League (EPL), NBA, baseball.
   • City-based teams create local loyalty (unlike national teams).
   • Icon players initially assigned (e.g., Tendulkar to Mumbai, Dravid to Bangalore) to jump-start regional fanbases.

3. Player auction + salary cap

   • Prevents rich owners from buying all stars → teams balanced.
   • Creates uncertainty and drama on auction day; every team looks strong on paper.
   • Market-driven salaries: players paid by demand & supply (e.g., left-arm bowlers, all-rounders fetch high prices).

4. Prime-time evening slot (7:30 PM)

   • Viewers return from work/college/school → competes with TV serials, not other sports.
   • 3-hour duration fits modern attention spans.

5. Entertainment + sports hybrid

   • Bollywood stars as team owners (Shah Rukh Khan, etc.) → mass appeal.
   • Cheerleaders, DJ, music, food, families – stadium becomes a family outing.
   • Not purely for cricket purists: appeal to new customers who were never interested in cricket.

Impact – Blue Ocean characteristics met

• Uncontested space: No other product offered a 3-hour, city-based, star-studded cricket entertainment package.
• New demand: Attracted families, youth, non-cricket fans (city affiliation, short format, entertainment).
• No trade-off: Viewers no longer had to choose between “high-quality cricket” and “quick, fun experience” – both delivered.
• High profitability: Broadcast rights skyrocketed; league became one of the most valuable sports properties globally.

Exam tip: The IPL example is a classic case for Blue Ocean Strategy and ERRC framework. Memorise the key factors: timing, franchise model, player auction, evening slot, entertainment package. Be ready to explain why it created new demand (not just took viewers from other sports) and how it eliminated trade-offs between “technical cricket” and “mass entertainment.”

Coda – Blue oceans don't stay blue forever

As with the iPhone (which eliminated fixed keyboards, enabled touch-based internet), blue oceans attract imitators. Other T20 leagues (Big Bash, CPL) copied IPL elements. The first mover gains a lasting advantage, but competition eventually erodes the blue ocean into red.

Key takeaways

• Blue ocean = new market space with value innovation, eliminating competition.
• IPL created a new sports-entertainment category by changing duration, timing, team structure, salary mechanism, and audience experience.
• The ERRC grid shows IPL eliminated long duration, reduced technical barriers, raised entertainment, and created franchise auctions + prime-time slots.
• Success drivers: timing (post-T20 World Cup, summer vacation), learning from other leagues, player auction for balance, and evening slot.
• Blue oceans are temporary; sustained advantage requires continuous innovation.

New Product Business Plan

An effective business plan is a concise, fact-based document that convinces sponsors and senior management to fund a new product. It must align the product’s value proposition, market strategy, and financials with the firm’s goals.

Nine Components of an Effective New Product Business Plan

1. Clear, fact-based executive summary – One or two pages that state the proposal, key facts (e.g., market potential using ATAR models), justification, and a crisp communication of the opportunity.
2. Justifies the new business model – Explains the gap, unmet need, or enhancement it addresses.
3. Shows how to reach buyers and convert them – Describes the go-to-market roadmap, including whether it targets existing users or creates new ones (blue ocean).
4. Identifies who will implement the plan – Specifies stakeholders, channel partners, retailers, distributors, and the support needed from them.
5. Covers all risks and how they are mitigated – Lists potential fallouts (Plan B, Plan C) and the contingent actions.
6. Shows product fit with firm’s business goals – The new product must align with the firm’s core competence and objectives; deviation is unacceptable.
7. Shows few and only the most critical numbers – Detailed project reports can be kept aside; the business plan highlights the numbers that matter.
8. Answers obvious questions (FAQs) – Preempts the questions sponsors will ask, supporting a go/no-go decision.
9. Builds credibility of the product and the team – A well-crafted plan gives management confidence in execution and investment.

Common Mistakes in New Product Business Plans

Mistakes fall into two categories:

Customer‑Related Mistakes	Cost‑Related Mistakes
Lack of in‑depth customer understanding (insufficient field work)	Buying new facilities when borrowing or renting is possible
Choosing convenient markets over the best‑fit market	High, unjustified startup capital requirements
Me‑too product instead of value creation / value innovation	Using more office space than strictly required
Targeting a large contested segment when a niche would be better	Wasteful resource use (redundant or buffer resources)
Not looking at quality from the customer’s viewpoint (ease of use, operational fit)	Employee structure: high fixed salaries vs. low salary + bonus
Not giving sufficient price options (multiple variants at different price points)	Overspending on advertising before the market is ready
Underpricing instead of value‑based pricing (leaves margin on the table)	Fixed cost too high, variable cost too low (unbalanced ratio)
Not solving the real customer problem	Skipping or under‑budgeting trials (alpha, beta, gamma testing)

Exam tip: Underpricing is a silent profit killer. Always anchor price on customer‑perceived value (willingness to pay), not on cost-plus.

Key takeaways

• A business plan must be concise yet cover all nine elements; the executive summary is the most read part.
• Customer mistakes stem from insufficient field research and failure to segment properly.
• Cost mistakes arise from premature capital commitments and ignoring variable-cost strategies.
• The plan must demonstrate alignment with the firm’s goals and manage risk with clear contingencies.

---

Strategy Consultants

Organisations may engage strategy consultants during new product development to bring external expertise, objectivity, and structured analysis.

Why Hire a Strategy Consultant?

1. Unrecognised performance problem – The product is not meeting expectations, but the cause is unknown.
2. Known problem, but cannot fix it – The issue is clear (internal or external), yet the team lacks the solution.
3. Difficult strategic choice – Trade‑offs are critical and require an outside perspective.

What Consultants Bring

• Domain expertise – Deep knowledge of the industry and best practices from multiple clients.
• Synthesise relevant data – Turn raw market, production, and pricing data into actionable insights.
• Create new, credible options – Expand the solution set beyond the team’s initial 2–3 ideas.
• Structure strategic choices – Identify trade‑offs, cost‑benefit analyses, and the best path.
• Help implement the chosen solution – Support execution, not just analysis.

Role Throughout the Project Lifecycle

• Proposal stage (early): Identify underlying issues, interact with clients to build hypotheses, redefine the problem, and align the scope.
  Note: Many consulting firms avoid pre‑contract work; when they do engage, it can sharpen the project scope.
• Execution stage (post‑sign‑off): Conduct market/product/internal research, build quantitative models (simulations, scenario planning, sensitivity analysis), and recommend solutions with implementation paths.
• Quick wins / prototype testing: Consultants can run fast‑feedback tests, analyse prototype results, and suggest immediate fixes before full‑scale development.

Exam tip: Consultants are most valuable when the firm lacks internal capability for modelling or when an objective third‑party view is needed to validate choices. Their involvement may be limited in larger firms with strong internal teams.

Key takeaways

• Consultants are hired for unrecognised problems, known problems without solutions, or high‑stakes trade‑offs.
• They contribute domain expertise, data synthesis, option generation, and implementation support.
• Early involvement (proposal stage) is ideal but rare; consultants are typically used after contract sign‑off.
• Quick‑win prototype testing is a cost‑efficient way to leverage consultants for short‑cycle feedback.

Failures and Best Sellers in Emerging Markets

A product is appropriate when it genuinely fits the context in which it is used. In emerging markets, the same design that wins awards in a developed market can flop—while a stripped-down feature phone becomes a best-seller. The difference lies in understanding local needs, infrastructure, and user behaviour.

What Makes a Product Appropriate?

A product is considered appropriate when it:

• Meets customer needs better than the competition – customer is the starting point for strategy.
• Offers better quality as defined by users – not by engineers or designers.
• Provides unique benefits/features – solves a gap not met by existing market.
• Solves users’ real problems – addresses an essential need or pain point.
• Reduces total in-use cost over product lifetime – not just purchase price, but ongoing expenses.
• Has highly visible benefits – users can clearly see why it’s better.

Case 1: Failure – AMD Personal Internet Communicator (PIC)

Aspect	Details
Product	Personal Internet Communicator (PIC) – a low-cost, dedicated device for internet access
Target market	Emerging markets (India, China)
Launch	~2004, priced ~$250
Outcome	Failed within 1.5 years; business divested in 2006
Why it failed	Could not compete with existing low-cost alternatives:
	• Internet cafes/cyber cafes – pay per hour (~₹20-40/hr), no device investment needed
	• Recurring costs – internet subscriptions were high-priced and slow
	• Second-hand PCs – cheap, full-feature desktops available, easily serviced locally
	• Increased technology risk – buyers were locked into a single-purpose device with uncertain future
Irony	Won design awards (Business Week, Industrial Design Society of America) – celebrated as innovative, but failed in the actual market

Exam tip: Awards for design do not guarantee market success. The PIC was a masterpiece of engineering but ignored the infrastructure and usage patterns of its target customers.

Case 2: Success – Nokia Feature Phones (3310/3315 & 1100)

Nokia 3310 / 3315 series

• Extremely low priced
• Very robust – needed little maintenance
• Longest battery life, reliable
• Wide service network
• High exchange value – easy to pass on or trade
• Sold over 15 crore (150 million) units before discontinuation

Nokia 1100 – evolved from field research
Nokia designer Raman Saxena (NID graduate) spent three weeks in rural India studying how users lived with their phones. Based on the findings, Nokia added:

• Torchlight – solved a real problem in areas with unreliable electricity.
• Removable, cleanable surface – phones were often handled in dusty or dirty conditions.
• Better grip lines on sides – reduced slipping.
• Red on-off button – clear, simple for first-time or senior users.
• Limited features – avoided confusion; less was more.

The 1100 sold over 25 crore (250 million) units – one of the most successful phones in history.

Feature	Benefit in Emerging Market
Torchlight	No need for separate flashlight; works in power cuts
Cleanable surface	Hygiene and durability in rough environments
Grip	Prevents dropping – important for daily use
Simple UI	Accessible to less literate or older users
Low price + low maintenance	Affordable for first-time buyers

Key Lessons

Dimension	AMD PIC (Failure)	Nokia 1100 (Success)
Target context	Developed-market product pushed into emerging market	Product designed for emerging market
Customer research	None mentioned	Field research (3 weeks in rural India)
Competition	Cyber cafes, second-hand PCs, high subscription costs	Other feature phones – but Nokia’s specific features created advantage
Pricing	$250 + recurring subscription	Very low one-time cost, no subscription needed
Feature set	Single-purpose device (internet only)	Purpose-built for basic communication + local needs
Risk to user	High – technology lock-in, no resale value	Low – durable, exchangeable, easy to repair

A critical insight: sometimes fewer features are better. Over-engineering can confuse users and raise costs. The Nokia 1100 succeeded because it solved real, observed problems with a simple, cheap, and robust design.

Exam tip: The AMD PIC vs Nokia 1100 contrast is a classic example of why “good design” must be defined by the customer in context – not by industrial design awards. Always ask: What alternative solutions already exist in that market? and What is the total cost of ownership for the user?

Key takeaways

• Product appropriateness = meets customer needs better than alternatives, with visible benefits and low lifetime cost.
• Emerging markets may have very different infrastructure (e.g., cyber cafes, second-hand markets) – ignoring them leads to failure.
• Field research reveals unarticulated needs (e.g., torchlight, grip, cleanable surface) that drive product success.
• A “simple” product can outperform an award-winning design if it fits the local context.
• Continuous adaptation is necessary – even a winner like Nokia eventually failed by not responding to the smartphone wave.

Emerging Markets – Product Design Considerations

Designing products for emerging markets (e.g., India) requires a fundamental shift in mindset. The typical textbook models are built for developed markets; success in emerging markets demands adaptation to local constraints – cost sensitivity, infrastructure gaps, labour realities, and social structures. The core lesson: minimalist design and value-consciousness often win over sophistication.

The Minimalist Design Trade-Off

Emerging-market customers often prefer simpler, durable, low-cost products over feature-rich ones. The Nokia 3315 vs 1100 case illustrates this:

• Nokia 3315 – bulky, robust, excellent battery, simple interface. Still sought after even after the 1100 launch.
• Nokia 1100 – more advanced design, integrated torch, extremely popular, yet many customers still searched for the older 3315.

Trade-off: Making a product smaller, more elegant, or feature-rich can reduce font size, battery life, or ease of use – hurting the value proposition for key segments (senior citizens, semi-literate users).

Minimalist design is not “low-end”; it is appropriate design for the user’s context. Examples beyond phones:

• Restaurant menus: 20-page menus overwhelm; fast-food chains offering 5–6 items succeed by keeping choices limited.
• Bread varieties: stocking 20 types vs. 2–3 basic options; many customers just want white or brown bread.
• Mutual funds: Parag Parikh Flexi Cap Fund became India’s largest by limiting offerings – no sectoral/thematic funds, only one equity fund for 15 years. Consumers get confused by 100+ fund options; 3–4 well-chosen categories provide ideal choice.

Key Considerations for Emerging Markets

Consideration	What it means for product design
Cost-driven design	Extreme price sensitivity. Products must hit low price points.
Value-consciousness (not just price-sensitivity)	Customers evaluate quality + price together. They avoid both ultra-cheap (low quality) and ultra-premium (overpriced). The sweet spot is “good enough” quality at a fair price. E.g., an Amazon shopper will pay 10–20% more for a branded T‑shirt that lasts longer.
Infrastructure constraints	Poor roads → need local availability or home delivery. Unstable electricity → battery‑powered or non‑electric alternatives (e.g., Hindustan Unilever’s Pureit water filter with candles, no electricity). Low internet bandwidth → apps must work offline or with minimal data.
Labour cost	Labour is cheap; investing heavily in automation (robots, high‑tech sorting) is less advantageous. Last‑mile delivery by humans is viable.
Real estate limitations	Smaller homes → compact appliances (smaller refrigerators, washing machines). Products designed for developed markets often need downsizing.
Social & cultural differences	Community‑oriented (vs. individualistic). People seek validation from friends, want to share purchase decisions (e.g., trial room with video calling). Product positioning must emphasize social proof and group usage.

Worked Example: Water Filter for Rural India

Problem: RO filters require steady electricity; power cuts are frequent in rural areas. Solution: Non‑electric water filters (Pureit by Hindustan Unilever, Swach by Tata) use candle‑based filtration. They deliver safe drinking water without electricity, serving a large untapped market at the bottom of the pyramid.

How the Ideas Connect

flowchart LR
    A[Emerging Market<br>Characteristics] --> B[Cost & Value Sensitivity]
    A --> C[Infrastructure Gaps]
    A --> D[Labour Abundance]
    A --> E[Small Homes]
    A --> F[Community Culture]
    B --> G[Cost-driven design + adequate quality]
    C --> H[Local delivery, battery/offline products]
    D --> I[Labour-intensive last-mile, low automation]
    E --> J[Compact, space-saving designs]
    F --> K[Products that enable sharing & social validation]
    G & H & I & J & K --> L[Minimalist, appropriate products]

Exam tip: The Nokia example is a classic case of trade‑off between form and function in emerging markets. Be prepared to explain why a “worse” product (3315) remains desirable – because its simplicity and durability match user constraints.

Key takeaways

• Minimalist design (limited features, fewer choices) often outperforms feature bloat in emerging markets.
• Customers are value‑conscious, not simply price‑sensitive – they seek the best quality–price ratio.
• Infrastructure (roads, electricity, internet) forces product adaptations: offline capability, battery life, local distribution.
• Cheap labour makes automation less urgent; small houses require compact products.
• Community‑oriented culture influences marketing and product features (e.g., shareability, social approval).

Building Base of Pyramid Markets

Base of pyramid (BOP) markets consist of low-income, price-conscious consumers in emerging economies. The challenge is to deliver usable products at price points these consumers can afford, while still maintaining profitability.

Product design principles for BOP

Principle	What it means	Example
Minimal features	Remove all non-essential functions to lower cost and reduce confusion	Basic feature phone (Nokia 1100) vs. smartphone; only 5–10% of features are ever used
Intuitive & self‑explanatory	No training required; dealer can sell without long explanation	Simple financial products: 3–4 mutual funds with SIP option, not 100 products
Essential packaging	Bundle only what is needed; avoid over‑choice	Blood test packages with 3–4 core tests instead of a panel of 100
Easily demonstrated utility	The customer can quickly see what the product does and why it matters	—
Robustness	Withstands harsh conditions, misuse, sweat, heat, dirt	Nokia base phones built for physical labour and outdoor weather
Low trial risk	Easy to try without elaborate setup; modular structure allows adding features later	Basic phone → add storage or processing power as needed
Innovative financing	Payment plans aligned with customer cash flows (EMI, subscription, loans)	Bajaj Finance, micro‑loans
Long‑term support	Warranty, spare parts, repair service; customers cannot afford frequent replacement	Longer warranty, service network
Migration support	Facilitate upgrades with trade‑in or exchange bonuses	Higher exchange value on old phone to encourage next purchase
Tight price‑performance control	Deliver high perceived value (performance / price) – customers are value‑sensitive, not just price‑sensitive	They want both high quality and low price; balance is essential

Exam tip: BOP consumers are value‑sensitive. A product that is too cheap may be perceived as low quality (see “latent demand – too cheap” below). Branding and store ambience can overcome this — e.g. Zudio’s premium-looking store at low prices.

---

Key takeaways – BOP product design

• BOP products must be functional, simple, robust, and easy to finance.
• Remove all features that are not essential; every extra feature adds cost and confusion.
• Value = performance ÷ price – customers demand both, not a trade‑off.
• Support infrastructure (warranty, spare parts, trade‑in) is critical because replacement is not affordable.

Winning Customers in Emerging Market

Six strategic options for targeting BOP consumers, ordered by feasibility (first option has highest take‑off potential):

Option	Situation	Action	Example / Logic
1	High intent to buy, but cannot find it or afford it due to high price	Create product at lower price point (keep essential features)	Basic phone at ₹1,000 vs. smartphone at ₹10,000
2	High intent to buy, cannot afford due to high price and high features	Reduce features and reduce price	Feature phone instead of smartphone
3	High demand exists, but users can be moved to a more appropriately designed product	Design specifically for their needs; use unique financing / advertising to switch	Targeted health insurance product with low premiums
4	Latent demand (not yet conscious), but appears too expensive and inappropriate	Lower price and improve appropriateness to reveal demand	Solar lanterns in off‑grid villages after price drop
5	Latent demand, but product appears too cheap → dubious quality	Signal quality through branding, packaging, store ambience	Zudio: low‑price fashion in a high‑end‑looking store
6	High demand, customers already using a competing product	Aggressively reach out to convince that your product is better	Aggressive comparison advertising, free trials

Key insight: latent demand traps

• Option 4 and 5 both involve latent demand – but the barrier is perception (too expensive / too cheap), not lack of need.
• Overcoming the “too cheap” stigma requires deliberate brand positioning (analogy: Zudio’s store experience).

Exam tip: Option 1 (price issue) and Option 2 (price + feature issue) are the most straightforward. Option 5 (too cheap) is a common mistake – never assume low price alone wins; value perception must be managed.

---

Key takeaways – winning BOP customers

• Always target users with high intent first; they are easiest to convert.
• If price is the only barrier → reduce price; if features also excessive → strip features.
• Latent demand must be surfaced by changing either price or perception.
• Too cheap can be as harmful as too expensive – invest in brand signals of quality.
• For crowded markets, aggressive switching strategies (option 6) are needed.

Design Thinking for New Product Development

Design thinking is a human-centered, iterative approach to problem-solving that combines analytical reasoning with creative exploration. Unlike pure analytical (cause‑effect) logic, design thinking starts by understanding the customer’s needs, asking the right questions, and rapidly testing low‑fidelity prototypes to arrive at unique solutions. It bridges the gap between logic and creativity.

Left Brain vs. Right Brain in Design Thinking

Left Brain (Analytical)	Right Brain (Creative)
Linear, logical, sequential	Contextual, synthetic, pattern‑based
Structured analysis, cause‑effect reasoning	Big‑picture thinking (“symphony”)
Formulas, frameworks, technical skills	Empathy, storytelling, aesthetics, playfulness
Highly trained in formal education	Often underdeveloped but increasingly valuable

The product manager must integrate both sides: analytical rigour with creative, context‑sensitive design.

Key Right‑Brain Abilities for Design

• Design ability – crafting novel, unique solutions and gaining fresh insights.
• Storytelling ability – connecting dots, weaving a context, and appealing to emotions (e.g., telling the origin story of a product to increase consumer appreciation).
• Symphony – strategic, big‑picture thinking.
• Empathy – seeing from the user’s perspective.
• Playfulness – using available resources in unexpected ways (related to effectuation).
• Meaning – giving the product significance, purpose, or motive.

Formal Definition of Design

Design is the creative organising of human, physical, technical, and knowledge elements toward the creation of an object or system—balancing functional, aesthetic, ergonomic, and economic goals, while respecting constraints (resource position, technical feasibility, organisational vision and value system).

Connection to New Product Development (NPD)

Design thinking strongly overlaps with NPD: understanding customers, mapping requirements, generating breakthrough ideas, and iterating rapidly. The lecture encourages linking lessons from a dedicated design‑thinking course to NPD exercises.

Key Takeaways

• Design thinking merges analytical (left‑brain) and creative (right‑brain) thinking.
• Right‑brain abilities—storytelling, empathy, playfulness—are essential for product differentiation.
• Design is a holistic balancing of functional, aesthetic, ergonomic, and economic goals under constraints.
• Rapid iteration and customer empathy are core to both design thinking and NPD.

---

Economics of Soft Innovation

Soft innovation means creating product varieties that affect aesthetic or intellectual appeal rather than functional performance. It changes look, feel, smell, touch, or intangible attributes without necessarily altering the product’s core function.

Examples of Soft Innovation

Type	Example
New book title	A clever or trend‑aligned title that increases appeal
New packaging	Redesigned bottle, box, or label
Marketing innovation	Memorable advertisements, storytelling campaigns
New food creations	Using the same ingredients to create different recipes
Design of delivery methods	Novel ways to reach customers (e.g., subscription boxes)
Pricing variations	Multiple data‑plan options, combo offers, free‑delivery bundles

Soft innovation can be protected by design registration (not patents) because it does not involve novel technical function.

Economic Logic

Commodities obey standard supply‑and‑demand pricing. Soft innovation does not shift the supply‑demand curve; it adds variety and perceived distinctiveness. Consumers who value distinctiveness are willing to pay a premium, yielding higher margins even though the base product cost changes little.

Relation to Hyper Competition

Hyper competition occurs when all firms in an industry launch new products at very high frequency (e.g., mobile handsets every few months). In such markets:

• Launching new products is costly and risky, but not launching is even riskier (loss of market share).
• Soft innovation becomes a primary differentiation tool.

Two types of hyper competition:

Type	Duration	Outcome
Episodic hyper competition	Short‑term	Temporary gains via fads (e.g., fancy packaging, new labels). Dies out quickly.
Transformational hyper competition	Long‑term	Driven by major shifts in consumer tastes or technology. Leads to a post‑hyper competition era where new bases of competition emerge (e.g., feature phones → smartphones; health‑conscious segment).

• With few players, hyper competition dies out; with many players, it persists longer.

Exam tip: Distinguish episodic (short fads) from transformational (structural shifts) hyper competition. Transformational hyper competition ultimately reshapes the industry’s competitive landscape.

Key Takeaways

• Soft innovation focuses on aesthetic/intellectual appeal, not functional performance.
• Protected by design registration, not patents.
• Allows premium pricing without altering supply‑demand fundamentals.
• Hyper competition forces firms to launch new products even when profitability is low; soft innovation is a common response.
• Transformational hyper competition leads to lasting changes in consumer behaviour and competition.

Luxottica Case Study: Vertical Integration and Market Power in Eyewear

The eyewear industry appears competitive (many brands: Ray-Ban, Oakley, designer labels) yet one firm—Luxottica—controls nearly the entire value chain, enabling price markups up to 1000%. This is a stark contrast to hyper competition; here, strategic vertical integration has created a near-monopoly.

The Problem: Why is eyewear so expensive?

A branded pair of glasses (prescription or sunglasses) often costs ₹5,000–₹10,000 or more. The typical margin on a single pair is extremely high. The question: do manufacturing costs justify that price? Without market power, competition would drive prices down to a fraction. Luxottica’s strategy shows how a firm can eliminate competition by owning every layer of the industry.

Luxottica: From Manufacturer to End-to-End Monopoly

Luxottica (Italian, founded 1961, Milan) started as a sunglasses manufacturer under its own brand. Founder Leonardo Del Vecchio pursued vertical integration to control the value chain. The evolution occurred in four phases:

1. Backward integration into distribution – bought companies that distribute sunglasses to retail outlets.
2. Brand licensing – signed licensing agreements with luxury brands to manufacture their frames and sunglasses (first: Giorgio Armani, 1988). Today includes Chanel, Prada, Burberry, Versace, Dolce & Gabbana, Michael Kors, Coach, Tory Burch.
3. Outright ownership of iconic brands – acquired and operates Ray-Ban, Oakley, Persol, Oliver Peoples, etc.
4. Acquisition of lens manufacturer and retail chains – bought SLR (the largest lens company) in 2018 (now EssilorLuxottica), and retail chains: LensCrafters, Sunglass Hut, Pearle Vision, Target Optical, Glasses.com. Also owns one of the largest vision‑related health insurance providers (EyeMed).

Result: a fully vertically integrated firm – designs, manufactures, distributes, and retails eyewear through 5,000+ own stores, with near‑monopoly on lenses, retail outlets, and brand manufacturing.

How Licensing Works: The Brand “Sticker”

When a customer buys a Versace or Armani branded sunglass, Luxottica manufactures the entire product. The luxury brand contributes only its logo and brand name. Luxottica has the pricing power – it sets the wholesale and retail prices. Luxury brands outsource to Luxottica because it is more efficient and has invested in quality; they focus on brand image.

The Pricing Power Mechanism

Market power allows Luxottica to charge markups up to 1000%. Without competition, a pair that could be manufactured and sold at one‑tenth the price is sold at full retail. This is the opposite of hyper competition – it is a near‑monopoly.

Comparison: De Beers in Diamonds

Aspect	Luxottica (Eyewear)	De Beers (Diamonds)
Vertical scope	Design, manufacture, distribution, retail, lens, insurance	Mines, processing, cutting, retail
Market control	Near‑monopoly on brands, lenses, retail channels	Historically ~80% of mines, controlled supply
Outcome	Extreme price markups, little competition	Control over diamond supply and pricing

Both firms demonstrate that end‑to‑end vertical integration can create an almost unassailable market position.

flowchart LR
    A[Luxottica owns: Manufacturing] --> B[Luxottica owns: Brand Licensing & Ownership]
    B --> C[Luxottica owns: Lens Production (SLR)]
    C --> D[Luxottica owns: Retail Chains & Insurance]
    D --> E[Result: Near‑monopoly → 1000% price markup]

Exam tip: The key insight is that vertical integration, when spanning the entire value chain, eliminates competitive pressure. This case is often contrasted with hyper competition; be ready to compare the two strategies.

Key Takeaways

• Luxottica achieved near‑monopoly through sequential vertical integration: distribution → brand licensing → owning brands → lens & retail.
• It controls design, manufacture, distribution, and retail, plus insurance.
• This gives Luxottica extreme pricing power (markups up to 1000%) – the exact opposite of hyper competitive markets.
• Luxury brands outsource eyewear to Luxottica because of scale and quality; they contribute only the brand logo.
• Comparison with De Beers shows a similar model in diamonds.
• The case illustrates that end‑to‑end control can be a more durable competitive advantage than battling in a hyper competitive market.

Expert Insights: Sameer Sawarkar – Rural Healthcare Innovation (Part 1)

Neurosynaptic Communications is a venture focused on digital healthcare for the last mile – rural areas where 69–70% of India's population lives. The company develops technological solutions (medical devices, software, workflows) and implements projects to deliver healthcare access, either as a service for partners or through its own clinics.

Founder Background and the Original Idea

• Sameer Sawarkar and his partner Rajiv Kumar are both electrical communication engineers from the Indian Institute of Science (IISc) and former Motorola colleagues.
• Sawarkar’s earlier entrepreneurial stint (Dax Software) taught him what entrepreneurship meant.
• Inspired by an article on brainwaves used to detect driver alertness and the concept of neural plasticity (the brain re-wires itself when one sense is lost), they formed Neurosynaptic in 2000 as a neurotechnology company.
• Early project: a vision-substitution device for the blind. A camera fed visual data to a 16×16 electrode array mounted on a denture placed on the tongue. The tongue has the highest neuron density; the brain learns to "see" through taste-related areas. Tested successfully with the National Association of Blind.

The Pivot to Rural Healthcare

• A chance meeting with Professor Ashok Jhunjhunwala (IIT Madras) revealed a massive, unsolved problem: healthcare access in rural India. Sawarkar and Kumar, both from rural backgrounds, immediately connected with it.
• IIT Madras had built an ecosystem of rural kiosks using DECT-based wireless connectivity (CoroDECT, 32–64 kbps, 30 km radius). These kiosks provided tele-education, e-governance, and later were the forerunners of the Common Service Centres (CSCs).
• The core philosophy: profit-making, not profiteering – a system must be self-sustaining through profit to scale, but profits should not come at the expense of others. This bridges shareholder (maximising value) and stakeholder (social welfare) views.

The Rural Healthcare Problem

• 31% of the rural population must travel >30 km for nominal healthcare; in remote areas, up to 100 km.
• Result: avoidance of care, delayed treatment, catastrophic expenses – ~100 million people fall below the poverty line every year due to healthcare costs.
• Government runs a vast network (sub-centres, PHCs, CHCs, district hospitals) but faces disconnects: doctors and infrastructure are hard to sustain in scattered villages (6 lakh+ villages, ~1,200 population each).
• Attempts to post doctors to rural areas have repeatedly failed for genuine reasons.

Initial Product and Pilot

• Sawarkar and Kumar aimed to plug into the existing kiosk ecosystem. They consulted doctors (Apollo, Vellore) who specified required parameters: temperature, blood pressure, pulse oximetry, stethoscope, ECG.
• The operator (local entrepreneur) assisted the patient and operated the device. The remote doctor conducted a video/audio consultation, viewing vital signs and an electronic medical record.
• Early prototypes had to handle:
  • Electricity fluctuations (rural power supply with surges, limited hours).
  • Fear of electric shocks among villagers – device was designed to run on battery, charged off-grid.
  • Low bandwidth (32–64 kbps) – they built a stamp-size video conferencing (QSIF, 15 fps) that worked on that constraint.
• Pilot in Tamil Nadu: technology worked well, but traffic collapsed after the first week. Reason: no medicine at the kiosk. Patients had to walk 3 km to a pharmacy anyway, so they bypassed the teleconsultation. Ecosystem was missing.

Exam tip: A product can be technically perfect but fail if the surrounding ecosystem (pharmacy, lab, referral) isn't in place. This is a classic "ahead of its time" case.

Realisations and Evolution

• The company faced a critical decision: abandon or solve the ecosystem gap. They chose the latter, shifting from a pure business mindset to working with the development sector.
• Discovery of Janani (later World Health Partners – WHP), an NGO that used cross-subsidisation and private providers to deliver non-incentivised services (e.g., contraceptives). This taught them that processes are technology – not just hardware.
• Key insights:
  • Aggregation of services: land records and healthcare don't mix (different populations, sensitivities). Health + education works better.
  • Quackery risk: operators began diagnosing and prescribing on their own. Solution: usage-aware devices that work only when connected to the system, recording every use and preventing standalone operation. All Neurosynaptic devices are connected devices.
  • Medicine delivery: studied what reaches villages daily – not newspapers, but Coca-Cola supply chain. They set up bus-route pharmacies (tie-up with Piramal Group) where prescriptions were sent via bus to a central pharmacy and delivered back.
  • Lab integration: tied up with local labs to pick up samples and upload results online for follow-up visits.
  • Doctor incentives: a mix of social motivation and financial payment. Many doctors wanted to contribute but needed a convenient platform. The biggest hurdle was acceptability of telemedicine by the medical community – resolved only after COVID-19.

The Bihar Program (2008–2016)

• With WHP and funding from the Susan Thompson Buffett Foundation, Neurosynaptic implemented the first large-scale telemedicine program: 1,300 centres in 21 districts of Bihar.
• Operated through Registered Medical Practitioners (RMPs) and their spouses, who were private providers cross-incentivised.
• Core disease pillars: leishmaniasis, childhood pneumonia, diarrhoea, tuberculosis – all linked to government referral systems.
• Telemedicine was the incentive for RMPs: one out of ten RMPs was selected to run the Sky Health Clinic (telemedicine centre), raising their prestige in the community.
• Entire ecosystem built:
  • Sky Meds: 10,000+ pharmacy supply chain.
  • 500–600 labs integrated for sample pickup and online results.
  • Referral hospitals (secondary and tertiary) linked via training and patient flow.
• Connectivity used BSNL DSL lines under the Universal Service Obligation Fund (USOF), providing 64 kbps uplink/downlink – enough for Neurosynaptic’s low-bandwidth system.
• Two central medical facilities (Delhi, Patna) each housed 20–30 doctors (GPs and specialists) providing continuous care.
• Checks and balances were built into the entire system to prevent misuse, with product evolution from peer-to-peer (one doctor, one clinic) to a centralised multi-centre model.
• Program wound down in 2016 when the disease-specific goals ended, but it proved the technological and operational model.

Key Takeaways

• Neurosynaptic started as a neurotechnology venture but pivoted to rural telemedicine after recognising a larger, unmet need – healthcare access at the last mile.
• Profit-making, not profiteering is the guiding philosophy: systems must be self-sustaining via profit, but profits must not exploit stakeholders.
• Ecosystem > technology alone: the first pilot succeeded technically but failed because medicine and labs were missing. Solving the entire ecosystem (pharmacy, lab, referral, training) was essential.
• Usage-aware connected devices prevent quackery by requiring constant online connection – a key product innovation.
• Low-bandwidth innovation (video conferencing at 32–64 kbps) was critical in an era of poor rural connectivity.
• Cross-incentivisation and private provider models (learned from WHP) allowed large-scale, efficient deployment without relying on government infrastructure.
• Telemedicine acceptance was a major barrier until COVID-19 changed perceptions.

Product Evolution: From Cabled Box to Wireless Kit

Intuition: Building a medical device for rural India is not a one-shot design. The product must evolve through continuous field feedback — what works in a lab often fails when handled daily by operators with varying skill levels.

Neurosynaptic’s first device (ReMeDi) started as a single box with 4–5 parameters, each measured via a dedicated wired connector (USB-like, but with different connectors per measurement). This led to frequent cable failures: operators would pull cables, insert them into wrong slots, or damage connectors. The result was an excuse for non-use — when a device is non-earning, operators quickly blame hardware.

Hardware iterations:

Version	Key Change	Rationale
V1 (metallic box)	Cable-based, lead-acid battery	Initial prototype, no product experience
V2 (plastic)	Lighter casing	Cheaper, easier to produce
V3 (ready-made moulds)	Used off-the-shelf box	Moulding custom boxes was prohibitively expensive
V4 (no battery, USB power)	Removed internal battery	Reduced cost and failure point
V5 (wireless hub)	Hub connected to sensors via USB cables	Intended to fix cable problems but introduced more wires between hub and sensors — failed in field
V6 (fully wireless, separate devices)	Each sensor is an independent Bluetooth Low Energy device	Eliminated cables entirely; each device has own processor, connectivity, mould. More expensive but gives customer choice

Key learning: The wireless hub version (MDoc) was a failed experiment that taught the team what not to do. The next wireless version succeeded because they had clear understanding of failure modes.

Software evolution: Peer-to-peer → client-server (on-premise) → cloud-based SaaS (by 2017). SaaS enabled pay-per-use and remote management.

Exam tip: In low-resource settings, “reported problems” may be excuses for lack of revenue. The real test is whether the problem disappears when the device becomes profitable. Always cross-validate user feedback.

Key takeaways

• Product design must account for operator behaviour – cables are fragile, connectors are misused.
• Feedback filtering is critical: distinguish genuine problems from excuses by testing alternative designs.
• Wireless solved cable failures but required separating devices → increased cost but added flexibility.
• Software architecture evolved from peer-to-peer to cloud SaaS to support scale.
• Each iteration was driven by field experience, not pure engineering.

R&D Strategy: Grants as a Risk-absorbing Fuel

Intuition: For a deep-tech health startup with long cycles, equity dilution is painful. Grants provide non-dilutive capital to develop risky innovations while preserving ownership.

Neurosynaptic’s model:

• R&D funded entirely by grants – never from debt or equity.
• Revenue from device sales + software licenses used for operations, not product development.
• Equity used only for market development and scaling.

Concrete grant journey:

Grant / Award	Use	Outcome
Grand Challenges Canada (Stars in Global Health)	Funded 3 technology developments	One led to Millennium Alliance, one to DBT
Millennium Alliance	Automated motorized microscope	Prototype built, but not launchable – operator could not focus slide reliably due to internet delay; scanning time too long
Department of Biotechnology (DBT) – Spurge grant	Optical rapid test reader + third version of ReMeDi	Successful product iterations
DBT – later grant	Fully wireless kit	Completed product now in field

Why grants work for this sector:

• High risk of failure (many products discarded).
• Long time to market (regulatory, clinical validation, field usability).
• Government grants also provide brand credibility (e.g., DBT funding signals quality to other stakeholders).

Exam tip: In impact sectors, grants are a strategic tool, not charity. They allow you to “fail fast” without destroying the company. Always apply for grants that align with product development milestones.

Key takeaways

• Grants are the primary R&D fuel for many health-tech startups.
• Multiple failures are expected – only 1 in 3 grant-funded ideas becomes a viable product.
• Government grants also serve as endorsement for later fundraising.
• Separate financing sources by activity: grants for R&D, debt for working capital, equity for market expansion.

Product Failure & Abandonment Decisions

Intuition: The hardest entrepreneurial skill is knowing when to kill a project. Attachment to sunk cost is dangerous when resources are limited.

Neurosynaptic’s approach to abandonments:

1. Conduct usability studies in adaptable centers.
2. Define parameters: ease of use, utility vs. cost, stakeholder needs.
3. If the product will not be accepted by the market → put it in cold storage rather than launch a failure.
4. Key mantra: The market decides.

Example – Automated Microscope:

• Goal: Enable remote pathology (TB, malaria) by attaching a camera to a low-cost microscope, with doctor guiding operator via video.
• Problem: Internet delay → operator overshoots focus; scanning entire slide for TB takes enormous time.
• Outcome: Working prototype, but not “happy” → never launched.

Example – MDoc wireless hub:

• Attempted wireless by having one hub connecting to many sensors via USB.
• Result: more wires, more failure points → sold a few units, but not field-worthy → abandoned.

Emotional dimension: Founders do get attached, but limited resources force ruthlessness. It's better to preserve cash for future opportunities than to waste it on a doomed launch.

Exam tip: “Pivot” is overused. Sometimes the right decision is to stop a product line entirely. Ask: Is the market ready? Is the unit economics viable? If not, shelve it.

Key takeaways

• Abandonment decisions should be data-driven (usability, time, cost, stakeholder acceptance).
• Sunk cost fallacy is dangerous – the market, not past investment, determines the future.
• “Cold storage” allows keeping IP for later when technology or ecosystem matures.
• Multiple failures are part of the innovation process; celebrate learning, not just launches.

Shift from Technology Provider to Service Provider

Intuition: Selling a device once generates 1× revenue. Running a service (telemedicine + diagnostics) using that device generates 12–13× annual recurring revenue, plus deep customer insight.

The transition:

Phase	Business Model	Revenue Nature	Customer
2004–2019	Device + software license	One-time + recurring license	Partners (NGOs, hospitals)
2019 onwards	Full-stack service (nurse + doctor + devices + medicine)	Annual per-center revenue (SaaS + O&M)	Government / Foundations

Catalyst for change:

• HCL Foundation project (2019) insisted on operationalization – they wanted a partner to run centers, not just supply tech.
• Neurosynaptic took the leap: set up 2 centers, then 13, serving >1 lakh patients/year, 35 teleconsultations per center per day.
• Result: Predictable revenue, direct patient feedback, and a scalable unit model.

Why it works better:

• Customers (government, CSR) understand “we will provide healthcare” more easily than “here is a box and software”.
• Services create a stickier relationship – daily interaction means problems solved in real time.
• Technology becomes a small fraction of total revenue (3–4%), but the service annuity multiplies revenue.

Exam tip: For any hardware startup: ask if you can wrap a service around the product. Services often have higher margins, recurring revenue, and deeper moats.

Key takeaways

• Product + Service business model can generate 12× more revenue per customer than product alone.
• Services provide predictable cash flows and direct customer insight.
• The shift requires new capabilities (hiring nurses, managing field ops, logistics) – but those are learnable.
• In rural healthcare, “running centers” is more understandable and fundable than “selling devices”.

Regulatory Environment for Medical Devices

Intuition: Medical devices are not like consumer electronics. They require certification to ensure safety and efficacy. In India, regulation was absent, then gradually formalized – a huge shift that now provides a level playing field.

Timeline of Indian medical device regulation:

Year	Event	Impact
Pre-2017	No CDSCO framework; DGFT issued “free sale certificates” loosely	Uncertified devices sold alongside certified ones – no comparison
2017	CDSCO began registration process	Manufacturers had to self-register
2019	Formalization of regulation	Standards (ISO 13485, IEC 60601) became mandatory
2021–22	Active enforcement; time given for compliance	Level playing field; earlier uncertified devices cannot claim equivalence

Risk classification:

• Type A & B (low risk): certified at state level (~6 months).
• Type C & D (critical care): certified at central level (~1 year).

Global standards:

• FDA (USA) and CE (Europe) are the most widely accepted.
• India’s base standards (ISO 13485, IEC 60601) are aligned with FDA/CE.
• Some countries (Russia, China, Japan) have their own standards – need separate registration.

Practical lesson:

• Start regulatory planning from Day 1 – it can make or break your product.
• Example: A company making a vaccine cold-chain device was stopped from selling because they lacked certification – only later realizing they didn’t need it for that customer.
• Free sale certificate (FSC) – needed for export; until 2022, issued by DGFT, now by CDSCO (properly recognized as medical device).

Exam tip: In any regulated sector (health, energy, transport), certification timelines and costs must be baked into your product roadmap. Underestimating regulatory can kill your startup.

Key takeaways

• Medical device regulation in India became formalized from 2017 – previously a free-for-all.
• ISO 13485 (quality management) and IEC 60601 (safety) are core standards.
• Risk classification determines approval level (state vs. central) and timeline (6–12 months).
• Regulatory runs behind innovation – always expect gaps (e.g., no AI framework yet from CDSCO).
• Compliance is a competitive advantage – it validates quality against uncertified rivals.

Healthcare Market Dynamics: Primary Care vs. Tertiary Care

Intuition: Healthcare spending is inverted – people will pay any amount for ICU, but almost nothing for prevention. Primary care is a “distributed market” competing with government, making it unattractive for traditional investors.

Continuum of healthcare:

flowchart LR
    Wellness --> PrimaryCare
    PrimaryCare --> SecondaryCare
    SecondaryCare --> TertiaryCare
    TertiaryCare --> CriticalCare_ICU
    CriticalCare_ICU --> Palliative

• Spending: Increases exponentially as you move right. Prevention (left) has lowest spend.
• Investor perception: Primary care = government’s job; low margins; long payback; competing with free/subsidized public services.
• Neurosynaptic’s response: Persisted because they believe solving India’s biggest problem (rural health access) will eventually be recognized.

Key external enablers (pre-COVID):

• National Health Authority (NHA) – established ~2016–18; mandate for digital health interoperability.
• Universal Health ID (UHID) – now ABHA under Ayushman Bharat Digital Mission (ABDM).
• Milestones (M1, M2, M3):
  • M1: Generate universal health ID.
  • M2: Generate health records in interoperable format.
  • M3: Read any patient’s interoperable record.
• RSBY / PMJAY – insurance for workers → expanded to Ayushman Bharat.
• Jan Aushadhi – affordable generic medicines.
• Ayush bridge course – allows Ayush doctors to practice allopathy partially.
• Telemedicine guidelines (March 2020) – gave legal standing, removed fear.

Why COVID changed everything:

• Doctors overcame fear of telemedicine – they had to use it.
• Telemedicine became legally recognized.
• Patient acceptance surged.
• But opportunistic players (post-COVID startups) often collapsed because they lacked the long-term infrastructure (like bamboo – grows underground for years before shooting up).

Exam tip: In impact sectors, the market may not be ready when you start. You must survive until the ecosystem catches up. That requires financial discipline and patience.

Key takeaways

• Primary care is under-monetized but essential – the spending curve is the opposite of value.
• Policy changes (insurance, UHID, telemedicine guidelines) are major tailwinds.
• Surviving until “right time” requires grants + conservative growth + multiple revenue streams.
• Many startups collapsed post-COVID because they were opportunistic, not foundational.

International Expansion Model

Intuition: Entering regulated foreign markets alone is expensive. A partner-based model reduces risk.

Neurosynaptic’s approach:

• Technology partner for overseas territories – local company handles liaison, business development, implementation.
• Neurosynaptic provides: product, SOPs, training, train-the-trainer programs (local language).
• Example – Panama: Product registered via CDSCO + CE certification → local partner won a ministry project → 25 centers now, expanding to 40+.
• Papua New Guinea: initial deployment, scaling statewide.

Key enabler: Indian regulatory compliance (CDSCO, CE) is accepted in many countries, reducing duplication.

Exam tip: International expansion is not a revenue shortcut – it requires prior regulatory work and a reliable local partner.

Key takeaways

• Use local partners for distribution and implementation.
• Regulatory certifications (CDSCO, CE) open doors to many countries.
• Start small: one country project, then scale based on results.

AI in Healthcare: Process vs. Diagnostics

Intuition: AI is not a magic wand. For a rural health startup, the most valuable AI improves processes (quality, efficiency) before it replaces diagnostics.

Two AI tracks at Neurosynaptic:

1. Process AI (launching soon):

   • Assistants for nurses, doctors, medical directors.
   • Audit quality of care – how well are consultations being done?
   • Tune service delivery.

2. Diagnostic AI (in development, partnering):

   • Use retinal images to detect retinopathy/glaucoma.
   • Oral cancer screening via phone camera (partner with Niramai, IISc).
   • Neuropathy, nephropathy assessment.
   • Philosophy: Not reinventing the wheel – partner with best-in-class AI companies.

Key partnership: National Centre of Excellence for AI in Healthcare (IISc) – focus on high-sensitivity screening (detect all possible cases, even at cost of false positives).

Exam tip: In resource-constrained settings, high sensitivity (catch all potential cases) is more important than high specificity. Missed diagnoses are more harmful than unnecessary follow-ups.

Key takeaways

• AI should first improve operations (auditing, assisting) before replacing clinical judgment.
• Partner for diagnostic AI rather than building in-house.
• Screening applications prioritize sensitivity over specificity.
• Avoid the “AI bubble” – build useful, focused solutions, not hype.

Entrepreneurial Lessons from a 20-Year Journey

Intuition: Building a venture in a difficult sector requires patience, humility, and a long-term perspective. Quick riches are the exception, not the rule.

Key mental models:

Lesson	Practical Implication
Survive until the market is ready	Use grants, conservative growth, multiple revenue streams
Cash is king	Cash flow management is the #1 skill
Market decides	If product isn’t accepted, shelve it – don’t force it
Moderate growth	“If you grow too fast, you collapse too fast.” Grow the whole organism (delivery, support, systems)
Unit economics first	Before scaling, prove one unit is profitable and sustainable
Bamboo tree	Years of underground root growth → then explosive visible growth
Solve our own problems	Imported solutions don’t fit India; we must build indigenous models
Different financing vehicles	For-profit, Section 8, NGO – pick the right vehicle for each activity

On giving up: Founders often have unrealistic expectations. The win and defeat can feel the same – you trade one set of problems for another. Persistence is key, but must be directed by validation from the field.

Exam tip: When evaluating a startup opportunity, ask: “What is the unit model? How long can the company survive without external funding?” The answer reveals risk.

Key takeaways

• Persistence is mandatory, but it must be paired with learning from failures.
• Financial discipline (grants for R&D, debt for working capital, equity for market) is a strategic choice.
• Growth must be balanced – scale capacities alongside market reach.
• Impact sectors require long time horizons – the bamboo tree analogy is accurate.
• India’s startup ecosystem is now supportive (recognition, MSME benefits, grants) – ideal for solving homegrown problems.

Product Management vs. Project Management

Product management answers what to build—understanding customer pain points, defining features, and setting the product roadmap. Project management answers how to build—scoping deliverables, timelines, and ensuring execution follows plan.

Aspect	Product Management	Project Management
Focus	What to build (features, strategy)	How to build (timelines, resources)
Core activities	Customer discovery, prototyping, roadmap	Scheduling, task tracking, delivery
Key question	Why build this? For whom?	When will it be done? Who does what?

The two roles are converging. Most product managers now also handle project management tasks. When you understand both the product and the team’s capability, you give better timelines and feasibility assessments.

Key takeaways

• Product management = “what to build” (strategy, customer needs)
• Project management = “how to build” (execution, timelines)
• Industry trend: roles merging; PMs increasingly own both.

---

Real-World Product Examples

Lending Product (NBFC – Riya)

A credit product involves deciding which customers to lend to at scale. The core challenge is risk underwriting – determining creditworthiness using data.

• Data sources: bureau data (credit score), behavioral parameters (spending habits, past records), and account aggregators (cross-institutional loan history).
• Product-to-customer fit happens via multiple channels:
  • Direct lending (B2C)
  • Partner cross-sell (e.g., Bajaj Finance + Reliance Digital → no-cost EMI customers)
• Customer journey stages: offer, data collection (PAN, bank account), final approval – each stage runs checks.
• Risk signals are data points (e.g., previous default) inserted into the journey. Steps:
  1. Data scientists analyze sources → identify significant variables.
  2. Test on historical data (improve detection of defaulters or upsell opportunities).
  3. Locate where in the journey the data is available → place the check.
  4. Check redundancy with existing signals.
• Live refinement: After launch, analyze rejection rates per segment → adjust thresholds or provide alternate offerings. Balance risk vs. business: too tight → no loans; too loose → defaults.

Capital Planning Product (B2B Government – Aviral)

A capital planning product helps US government agencies forecast budgets, enter funds, and identify shortfalls. Key priority for public sector: utilise allocated funds (avoid lapsing) rather than ROI.

• Legacy product (20+ years) being broken into next-gen products (capital planning, build phase, etc.).
• Prototyping approach: End‑to‑end prototype (99% of product – frontend, backend, database) built in 6 weeks; sales teams demo it to customers before the actual product is ready. This accelerates onboarding.
• Feature discovery: Government clients issue RFPs (Request for Proposals) – these reveal requirements. Product managers demo the prototype, collect feedback, and shape the roadmap.
• Example AI feature: Natural‑language scenario planning – user prompts “prioritise projects with ROI >15% within budget” → AI returns a prioritised list.
• Compliance: Government customers require compliance checks (e.g., accessibility for disabled) – PMs run scans, fix issues, and iterate.

Key takeaways

• Lending PM: risk signals, data-driven policy, scale, compliance‑first.
• Capital planning PM: fund utilisation, RFP-driven, end‑to‑end prototypes, AI enhancements.
• Both roles require deep data understanding and stakeholder management.

---

Product Development Process

From Idea to Launch

1. Identify need: Customers (directly or via RFP), legacy product insights, or market observation.
2. Build prototype: Rapid, end‑to‑end (not just UI) – used for demos before full product is ready.
3. Demo & feedback: Sales team sets calls; PM presents prototype; customer feedback defines roadmap.
4. Iterate: Monthly releases; continuous customer touchpoints.
5. Compliance & scale: For government – security, accessibility; for lending – regulatory compliance (e.g., data privacy).

PRD (Product Requirements Document)

A PRD scopes all requirements for a feature – constraints, actions, what user should/should not be able to do. In a lending context, it covers:

• Functional requirements (from business team – balance risk vs. business)
• Data requirements (from data science – available data points, feasibility)
• Technical design (from engineering – integration with existing systems)

All three must align to achieve the product goal.

---

Team Structures

Structure	Description	Example
Pod structure	Cross‑functional team (engineers, PM, designer, QA) working on one product/feature.	Aviral’s experimental team → replicated to whole org after success.
Functional + divisional	Functions (product, tech, data science, HR) each divided by product line.	Riya’s company: analytics team has sub‑teams for product one, product two, etc.

Stakeholder management is critical – PMs interact with business, risk, data science, and CXO levels to align on product decisions.

Key takeaways

• Pod structure enables fast, cross‑functional execution.
• Functional+divisional provides deep expertise per product.
• PMs must navigate multiple stakeholders to achieve consensus.

---

Evolving Role: Technical & Data Skills

Modern product managers increasingly need hands-on technical or data capabilities:

• Aviral: codes end‑to‑end prototypes (uses Cursor, Claude Code). Technical understanding earns engineers’ respect, improves communication, and helps manage AI products.
• Riya: data engineering background → works as data product manager. Queries databases, performs analysis, and can substitute for data analysts when needed.

Exam tip: The PM role is shifting from “product specifier” to “product builder” – especially in startups and AI‑focused teams. Expect interview questions testing technical depth (system design, AI concepts).

---

Impact of AI on Product Management

AI affects PMs in two dimensions:

1. Personal workflow (how PMs work)
2. Product features (what PMs build)

And can be classified by augmentation (human‑in‑the‑loop) vs automation (AI alone):

	Augmentation	Automation
Personal workflow	AI‑assisted meeting notes, drafts, research	Fully automated transcript → structured document → Notion
Product features	User interacts with AI to explore options	Agent performs task autonomously (e.g., scenario planning)

AI in Personal Workflow (Aviral’s Example)

• Meeting transcription: Recordings → Claude Code → structured document in Notion (via MCP server). PM can later query: “What was decided about feature X?”
• PBI (Product Backlog Item) creation: Claude Code, using meeting context, generates PBIs and pushes to Azure DevOps.
• Workshops: Aviral conducted training for 20+ PMs to adopt Claude Code.
• Key principle: Human must be in the loop to validate AI output (non‑deterministic).

AI in Products

• Scenario planning agent: Uses legacy data (golden datasets) to validate AI responses. Requires evals (evaluation), latency/cost monitoring, and explainable AI to build trust.
• Agent architecture: Orchestrator agent breaks task into sub‑tasks → sub‑agents execute → report back. PM manages cost, latency, trust, and monitoring.
• Pricing challenges: AI costs are high; even big players (ChatGPT) are not yet profitable. PMs must rethink pricing models.
• Build vs. buy: Organisations should experiment with closed models but also build open‑source infrastructure to avoid vendor lock‑in (e.g., Anthropic restricting third‑party tool usage → switch to Codex + orchestrator).

Shelf Life Changes

• Products ship faster (execution has become cheap).
• PM role is not disappearing but evolving into agent manager – managing AI agents, their costs, latency, and trust.
• Judgment is the new moat – AI cannot yet replace product judgment.

Key takeaways

• AI impacts PMs both in workflow automation and product capabilities.
• Human‑in‑the‑loop is essential; full automation risks losing differentiation.
• PMs must understand agent architecture, cost management, and evals.
• Don’t depend on a single AI tool or vendor – build flexibility.

---

Advice for Aspiring Product Managers

Foundational Skills

• Product fundamentals: Solve cases (e.g., “What is your favourite product and how would you improve it?”). Use case books from product clubs.
• Stay updated: Follow AI news daily (Anthropic, OpenAI, etc.). Use agents (e.g., OpenClaude) to curate updates.
• Build unique perspectives: Leverage your background – psychology, data, coding, economics – to differentiate.

Practical Roadmap (for young students)

1. Identify a daily pain point (e.g., meeting context loss).
2. Use an AI tool (Lovable, Cursor, Claude Code) to build a rough prototype.
3. Iterate with feedback from friends/colleagues.
4. Scale – host, add authentication, handle multiple users.
5. Research existing solutions – don’t build in isolation; improve upon what’s out there.

Personal Journey Insights

• Riya: Try multiple fields and discard what doesn’t work. Civil engineering → data engineering → finance → product management. Narrowing down by elimination is effective.
• Aviral: Passion from early age (web development) → clear clarity. Built technical foundation (IIT Kanpur, Bajaj Finserv, cloud certification) then moved to product management to answer “what to build.”

Exam tip: For product management interviews, be ready to discuss your unique angle (e.g., “I bring a psychology perspective to customer experience”). Also, demonstrate how you use AI tools to build and validate ideas.

Key takeaways

• Fundamentals (cases, design thinking) still matter, but AI knowledge is now expected.
• Differentiate by combining product skills with a specific domain or technical depth.
• Practical building (even small prototypes) teaches the product lifecycle faster than theory.
• Stay adaptable – avoid over‑reliance on any single AI tool or vendor.

Introduction to the Module

The development phase is the execution stage that follows idea generation, concept testing, and financial forecasting. At this point the product concept has passed all screening criteria, so the focus shifts from what to build to how to build it – and who should build it.

Prerequisites: The product must satisfy three requirements

Requirement	What it means
Customer requirement	Meets target user needs as validated during concept testing
Organisational requirement	Aligns with company capabilities, strategy, and resources
Financial requirement	Projections (sales, cost, profit) are acceptable and within budget

Only when all three are confirmed does the project enter the development phase.

Three core topics in development

1. Design and architecture – exploring different ways to structure the product, its components, and their interactions.
2. Prototype development and testing – building an early, incomplete version (the prototype) to test real use cases before a full launch.
3. Organisational and team management – structuring the team and processes to execute the project effectively.

How development fits into the overall product process

flowchart LR
    A[Idea generation] --> B[Concept testing & forecast]
    B --> C{Requirements met?}
    C -->|Yes| D[Development phase]
    D --> E[Design & architecture]
    D --> F[Prototype & testing]
    D --> G[Team management]
    C -->|No| H[Rethink / kill project]

The transcript does not specify what “design and architecture” or “team management” entails in detail; the notes above represent the only content present.

Key takeaways

• The development phase starts only after a product passes customer, organisational, and financial checks.
• Its three main activities are design/architecture, prototype development/testing, and team management.
• Prototyping is a first stage – many products are tested via prototype before full launch.
• The module assumes earlier stages (ideas, concept testing, forecasting) are already completed.

Product Design

Good product design is hard to define academically—it relies on intuition, experience, and creativity. A well-designed product feels right: it “disappears” in use, while a poorly designed one frustrates through bulk, weak performance, unclear controls, or clutter.

Signs of Poor vs. Good Design

Poor Design	Good Design
Too heavy / bulky (e.g., vacuum cleaner a senior cannot move)	Look and feel are inviting (e.g., car dashboard that is clean, not cluttered)
Underpowered (e.g., grinder that stalls)	Buttons and switches are easy to locate and operate while driving
No clear marking (e.g., coffee machine where to place the cup)	Back support in furniture (ergonomic)
Overloaded with unnecessary information	Information shown is exactly what the user needs (Apple fonts, keyboard placement)

Definition of Design

Design is the synthesis of technology and human needs into manufacturable products.
It involves art, sensibility, and a deep understanding of the customer’s situation.

Design‑Driven Innovation

Design‑driven innovation creates new meanings—it does not come from the market (no customer asked for it). Examples:

• iPod / iTunes – introduced a new way of using music.
• Steve Jobs’ philosophy: “The customer doesn’t know what they want; I will tell what they need.”

This creates a blue ocean (non‑existing market), generates love‑at‑first‑sight loyalty, and lets the firm compete on meaning rather than technology. It contrasts with market‑driven innovation, which reacts to existing complaints and trends.

Exam tip: Design‑driven innovation ≠ market‑driven innovation. The former pushes new purpose (e.g., wearable tech as a lifestyle), the latter pushes incremental improvements (e.g., faster processor because customers complained).

Key takeaways

• Good design is intuitive, usable, and uncluttered; bad design is bulky, underpowered, confusing.
• Design = technology + human needs → manufacturable product.
• Design‑driven innovation creates new meanings and markets (blue ocean), not responses to customer requests.
• Examples of design‑driven firms: Apple, boutique dress designers who set trends.

---

Product Architecture

Product architecture determines how a product is broken into physical parts. Two main types:

Modular Architecture

Each part is an independent module that can be removed, upgraded, or replaced.
Example: desktop computer – RAM, hard drive, GPU are standard, swappable components.

Advantage	Disadvantage
Flexibility and customization	Larger size / volume
Easy repair, upgrade, replacement (e.g., RAM 512 MB → 1 GB)	Less optimized for performance per size
Parts from different brands can be mixed	Lower integration of functions
Enables product variety (many configurations)	—

Integral Architecture

Components are tightly integrated; single parts perform multiple functions.
Example: laptop – CPU, memory, display are soldered; upgrade is very difficult.

Advantage	Disadvantage
Compact size, low volume	Limited post‑purchase change / upgrade
Higher performance (optimised form over flexibility)	Pre‑designed product variety only (fixed models)
Higher quality in small space	Repair may require entire replacement

Trade‑off: Modularity gives flexibility; integral architecture gives form and performance. Choose based on product purpose (e.g., a space‑constrained mobile phone → integral; a configurable workstation → modular).

Six Types of Modularity

Type	Description	Example
Component sharing	Same component used across multiple products	Intel i5 processor used in many laptops
Component swapping	Interchangeable components between products	EV battery that can be swapped; same charging cable
Cut‑to‑fit	One component adjustable in size or length	Trousers with alterable length; extension cords
Mix	Combine different base materials to create variety	Paints – mix 2–3 base colours to get many shades
Bus	Standardised platform with ports where modules plug in	Computer motherboard (PCIe slots for different cards)
Sectional	Sections that fit together to form larger structures	Lego bricks – each section clicks into another

Key takeaways

• Architecture is modular (flexible, customizable) or integral (compact, high‑performance).
• Trade‑off: flexibility vs. form/quality.
• Six modularity types: sharing, swapping, cut‑to‑fit, mix, bus, sectional.
• Real‑world products often use hybrid architectures (e.g., car is integral overall but has modular gearbox, battery, tyres).

Design for Manufacturing (DFM)

Design for Manufacturing (DFM) means designing a product so it can be made quickly, cheaply, and reliably. The core intuition: every extra part, fastener, or adjustment step adds cost, time, and risk of error during production. DFM aims to strip away unnecessary complexity while keeping the product functional.

Core DFM principles

• Minimize the number of parts — fewer parts means less assembly, lower inventory, and fewer potential failure points.
• Use common parts across products — sharing parts (e.g., same steering wheel, gearbox across car models) simplifies supply chain, reduces lead times, and lowers cost.
• Eliminate fasteners — screws, bolts, and clips add assembly time. Replace with snap-fits, welding, or adhesive where possible.
• Eliminate adjustments during assembly — standardise assembly fixtures; avoid custom fitting or on-the-fly adjustments (e.g., same-door fittings regardless of colour).
• Error-proof by design — use colour coding, asymmetry, or keying so parts can only be assembled correctly (e.g., left vs. right door parts coded differently).
• Leave assembly to the customer (if feasible) — IKEA-style DIY shifts labour to the customer and simplifies transport and storage.
• Minimise system complexity — make modules simple and standalone; isolate parts that need frequent replacement (e.g., EV scooter battery, mobile‑phone battery) so they are easy to take out and swap.

Modular vs. Integral Architecture

A central DFM decision is whether to use modular architecture (distinct, interchangeable parts) or integral architecture (parts blended into a single, sealed unit). The choice depends on where value is created.

Aspect	Modular architecture	Integral architecture
Parts	Distinct, replaceable individually	Fused, hard to separate
Repair/upgrade	Easy – swap a module	Difficult – often replace whole unit
Customisation	High – mix and match modules	Low – base design is fixed
Manufacturing cost	Higher (more parts, more assembly)	Lower (fewer parts, fully automated)
Reliability	More joints → potential failure	Fewer joints → higher reliability
Typical use	Luxury/premium, need variety	Commodity, mass‑market, sealed devices

Trade-off: Designers can go modular → integral to lower cost and improve ease‑of‑use (e.g., Shimano gears) or integral → modular to offer premium customisation (e.g., Swatch dials). This is a strategic design choice.

Exam tip: DFM is not just about cost – it also shapes product reliability, reparability, and the customer’s perception of quality. Know the two archetypes (modular vs. integral) and when each is preferred.

Key takeaways

• DFM minimises parts, fasteners, adjustments, and assembly complexity.
• Common parts across products reduce lead time and cost.
• Error‑proofing via design (colour coding, keying) prevents assembly mistakes.
• Modular architecture enables customisation and easy repair; integral architecture lowers cost and improves reliability.
• The choice between modular and integral is a strategic trade‑off, not a fixed rule.

---

Swatch – From modular to integral (and back)

• Traditional Swiss watches: modular architecture – distinct, hand‑crafted parts, unique cases, artistic dials. High cost, luxury positioning.
• Japanese quartz watches (Casio): integral architecture – standardised, mass‑produced, sealed commodity. Low cost, high reliability.
• Swatch’s response: adopted integral architecture for the entire watch except the dial. The base (movement, case, assembly) was fully automated and sealed – cannot be repaired. Only the dial remained modular, allowing visual variety. Result: drastic parts reduction, lower cost, higher reliability, and a new mass‑market segment.

Shimano – From modular to integral

• Before Shimano: bicycle gear systems were modular – handlebars, gears, brakes from different brands, assembled by local mechanics. Fragmented, no single brand identity.
• Shimano’s innovation: introduced the integrated click‑shift gear system – a complete, optimised set that included cranks, brakes, and gears. Users preferred the ease‑of‑use and reliability of the integrated system over loose parts.
• Outcome: Shimano could brand the whole system, represent quality, and dominate the market. By the late 1990s, they held ~98% market share in integrated gears. They converted a fragmented modular industry into a consolidated integral one.

Exam tip: Both examples show that architecture choice can redefine an entire market. Swatch created a new segment by making the base integral and the dial modular; Shimano killed the modular gear market by making the whole system integral.

Key takeaways

• The same company (Swatch) deliberately chose integral for most parts and modular for the dial – a hybrid approach.
• Moving from modular to integral can give better performance, lower cost, and strong brand identity (Shimano).
• Moving from integral to modular can enable customisation and premium positioning (traditional Swiss watches).

---

Design for New Product Process (Other DFx Approaches)

Beyond DFM, several other design philosophies guide product development, each with a different goal.

Design for Speed to Market

• Create a product quickly by using existing internal capabilities and simple geometry changes.
• Example: Ingersoll’s ergonomically shaped, lighter grinder – different shape/size but no radical new technology. Gets to market faster.

Design for Differentiation

• Design features that clearly distinguish the product from competitors.
• Often involves unique user‑oriented features.

User‑Centric Design

• Design specifically around how the customer will use the product.
• Example: Modern SUVs blending SUV ground clearance with car‑like low entry and easy handling – not purely off‑road, but more comfortable for daily use.
• Another example: JCB forklifts and earth‑moving equipment – shapes and attachments (forks, buckets) designed for heavy‑duty customer tasks.

Universal Design

• Design that works for every age group and ability – no specialised operation.
• Example: Automatic sliding doors at malls, hospitals – open without pushing, button, or effort. High‑frequency use.

Design for Corporate Identity

• A consistent design language across all products of a company to build brand recognition.
• Examples: Tata cars vs. Mahindra cars – distinctive grille, logo placement; Nokia feature phones had a recognisable shape/colour; Rolex watches carry a philosophy of luxury; Apple products have a minimal, clean identity.

Design for the Environment (Green Design)

• Use recycled materials, reusable parts, reduce plastic.
• Example: Companies committing to recycled paper, recyclable packaging, and green materials.

Key takeaways

• Design philosophy (DFx) can target speed, differentiation, user needs, accessibility, brand identity, or environmental sustainability.
• These approaches are not mutually exclusive – a product may combine several.
• The choice depends on the company’s strategy, target market, and competitive landscape.

Prototyping

A prototype is an initial product approximation — a small-scale or partial version built before full launch. Its purpose is to test, learn, communicate, and integrate feedback early, reducing time, cost, and risk. Every error discovered later in development is far more expensive to fix; prototyping catches mistakes when changes are cheap.

Why prototype?

• Testing & learning – get a look and feel, check feasibility, uncover hidden issues.
• Communication – show stakeholders (investors, customers, teams) a tangible version.
• Funding milestones – prototypes demonstrate progress, especially in long projects (e.g., 18-month development: show a version at 3, 6, 9 months).
• Risk reduction – both technical (will it work?) and market (will customers like it?).

Form of prototypes

Type	Use case	Advantage	Limitation
Computer-based models (CAD, simulations)	Crash tests, safety, comfort, mileage, non‑destructive testing	Flexible, cheap, fast iteration	May miss unanticipated physical issues
Physical prototypes	Road tests, customer handling, real-world feedback	Detects unanticipated problems, allows direct user evaluation	More costly and time-consuming

Both have a place — simulations for early-stage trade-offs, physical models for final validation.

Role across product types

Product type	What the prototype tells you
Breakthrough products	Feasibility — is the core idea stable, reliable, executable? May reveal it’s not feasible at all.
Derivative products	Problem detection — find defects in the enhanced/tweaked design.
Platform-based products	Planning — helps set timelines, volumes, and product roadmaps across variants.

Multiple prototypes: learning cycles

In complex or long-gestation projects, use multiple staged prototypes spaced out (e.g., every 6 months). Each cycle delivers in-depth learning that feeds into the next prototype, systematically reducing flaws. The core objective is learning, not perfection.

Exam tip: A key exam point — prototypes are learning tools, not final deliverables. The iterative cycle (build → test → learn → rebuild) is what saves cost and time.

Prototype strategies: build vs. buy

The decision to develop prototypes in-house or through vendors depends on trade-offs:

Factor	In‑house	Vendor/outsource
Secrecy	High — especially for breakthrough products (e.g., Apple’s next phone battery specs). Critical for competitive advantage.	Risk of information leak.
Skill requirements	Needed when workers are highly skilled; design not yet standardised.	Easier to scale production later because vendor’s workers follow clear specs.
Knowledge transfer to production	Difficult — skilled in-house workers → less skilled vendor workers slows transfer.	Smoother handoff; vendor already understands the design.
Objectivity & problem detection	Team may overlook issues.	Vendor’s fresh scrutiny forces clearer specifications and uncovers production problems earlier.

Participants in product design

Direct participants (core team)	Support participants (internal/external)
R&D team	Design consultants
Industrial designers / stylists	Marketing personnel
Engineering / product designers	Resellers, vendors, suppliers
Manufacturing engineers / system designers	Government regulators (e.g., fuel mandates)
Manufacturing operations team	Customers
...	Company lawyers, technical service teams

The distinction between direct (who create the design) and support (who inform or constrain it) is often tested.

Key takeaways

• Prototypes are early, testable product approximations that reduce cost, time, and risk by catching errors early.
• They serve as milestones in long projects and funding checkpoints.
• Computer models (simulations) are flexible but can miss real-world problems; physical prototypes capture unanticipated issues.
• For breakthrough products: test feasibility. For derivative: detect problems. For platform: plan roadmaps.
• Learning is the fundamental goal – multiple staged prototypes enable iterative improvement.
• Build vs. buy trade-off: in-house protects secrecy and handles non‑standard designs; vendors improve objectivity and later production scaling.
• Participants split into direct (R&D, design, manufacturing) and support (marketing, suppliers, regulators).

Innovation Strategy

Gillette’s core strategy for decades was simple: work on the blade. Each product generation replaced the blade technology with a better one – more blades, improved materials (steel, platinum), and different cartridge formats (replaceable or disposable). The goal was to retain market leadership by making continuous innovation the norm, forcing customers to upgrade and keeping competitors at bay.

Mach 3: Breakthrough from Twin-Blade

In the late 1990s, Gillette moved from the twin‑blade Sensor Excel to a three‑blade pivoting cartridge system called Mach 3. The transition was not trivial.

Design challenges of adding a third blade

• More blades cause higher irritation on the skin.
• The prototype (code‑name Manx) was built to test blade positioning: each blade had to be placed closer to the face and closer to each other than in the twin‑blade system. This patented design actually reduced irritation.
• Pivot point moved from the middle to the bottom of the cartridge to change pressure distribution.
• Handle re‑positioned for a “paintbrush” feel; cartridge stability enhanced.
• The existing wide lubricating strip from Sensor got a blue indicator – a gel that gradually faded, telling users when to replace the blades.
• Engineers simultaneously worked to make each blade thinner and harder (a continuous R&D effort independent of the product cycle).

Incremental vs. breakthrough debate

Some managers argued for a less risky, incremental upgrade: simply add a third blade to the existing Sensor Excel design. Gillette chose the breakthrough path – a completely new product (Mach 3) with distinct look, feel, and features. This decision increased cost and risk but opened the door for higher margins.

flowchart TD
    A[Move to 3 blades?] --> B{Which path?}
    B -->|Incremental| C[Add 3rd blade to Sensor Excel - low cost, low risk]
    B -->|Breakthrough| D[Design new Mach 3 with optimized positioning, handle, indicator - high cost, high risk]
    D --> E[Premium pricing possible, large market share gain]
    C --> F[Limited differentiation, price competition likely]

Development timeline and cost

• Concept to launch: ~6 years.
• Active development phase: 1995–1998 (3 years).
• Total investment: $750 million (four times the Sensor launch cost).
• Most manufacturing machinery had to be specially designed, adding internal resistance.

Consumer Testing & Pricing

Product‑use tests with consumers gave decisive results:

• Mach 3 outperformed Sensor Excel 2:1 in customer satisfaction.
• Users were willing to pay a 45% premium over Sensor Excel.
• Gillette set the introductory price at a 35% premium – slightly below willingness but still high.

The test validated the breakthrough strategy: an incremental upgrade would not have commanded such a premium.

Launch and Success

• United States: April 1998.
• Canada: July 1998.
• Eastern & Western Europe: September 1998.
• Reached 100 countries by end of 1999.
• Strong demand forced capacity expansion to 1.2 billion cartridges per year.
• Mach 3 became a massive success, confirming Gillette’s innovation model.

Competition and the Next Generation: Fusion

After Mach 3’s launch, competitor Wilkinson Sword introduced a 4‑blade system, eating into Gillette’s market share. Gillette’s response was to skip 4 blades entirely and jump directly to a 5‑blade system – Fusion (launched 2006, 8 years after Mach 3).

Key features of Fusion:

• Five blades placed even closer together to keep cartridge size manageable.
• Lubricating strips on both sides of the cartridge.
• An extra trimming blade on the back.
• A battery‑powered version (Fusion Power) with vibrating action for easier trimming.

Gillette repeated the same process: extensive R&D, prototyping, and a massive global marketing campaign. For the Fusion launch they used top‑tier athletes (Tiger Woods, Thierry Henry, Roger Federer) in high‑budget TV advertising to position the brand as premium and innovative.

Exam tip: The Gillette case illustrates the classic tension between incremental innovation (lower risk, lower reward) and breakthrough innovation (high cost, high potential payoff). The choice to skip 4 blades and go straight to 5 shows how competitive dynamics can drive leapfrogging. Always connect design decisions to market outcomes – here, the willingness to pay a premium justified the heavy investment.

Key takeaways

• Gillette’s core strategy: continuous blade technology upgrades to maintain market leadership.
• Mach 3 was a breakthrough (not incremental) product, requiring 6 years and $750M.
• Prototyping (Manx) solved the irritation problem by repositioning blades closer together and moving the pivot point.
• Consumer tests showed 2:1 preference over Sensor Excel and 45% willingness to pay a premium → priced at 35% premium.
• Competition (Wilkinson’s 4‑blade) drove Gillette to leapfrog directly to Fusion (5‑blade).
• Both launches used massive advertising with celebrity endorsements to reinforce premium positioning.

Developing New Services

Pure services are fundamentally different from physical products: they are intangible, making them hard to develop, measure, and sell. Clients cannot see or touch the output before purchase, leading to scepticism and difficulty evaluating quality. For example, implementing a banking solution is invisible until testing; there is no "look and feel" like a laptop or car.

Productizing a Service

Productizing a service means packaging it to resemble a tangible product, making it easier for customers to understand, budget for, and trust. This reduces the buyer's perceived risk and allows the seller to lower costs through templatization.

Key steps to productize a service:

• Give the service a descriptive name (e.g., "Account Opening Module").
• Standardize the scope and deliverables (e.g., "this module will handle checking, savings, and fixed deposit account opening").
• Define a clear timeframe (e.g., "implementation in 3 months").
• Provide clear pricing regardless of customisation.
• Develop a demo to show what the final output will look like.

Benefit for buyer	Benefit for seller
Tangible expectations; lower uncertainty	Reduced cost by reusing templates
Easier to budget and compare offers	Faster deployment across clients
Clearer performance criteria (e.g., "process an account in 30 minutes vs. 3 days")	Competitive advantage via standardised modules

Example: A banking software provider takes the core service of "account opening" and turns it into a standard module with defined workflows, screens, and processing speeds. Each bank gets a similar version, but the provider can quickly adapt it.

Exam tip: Intangibility is the root cause of service-marketing challenges. Anything that makes a service more tangible (productizing, bundling) reduces buyer uncertainty.

Customised Service Packages

Beyond standardised modules, firms can also offer customised service packages tailored to different user groups. Examples include annual maintenance contracts (AMC) for water purifiers or washing machines, where the service becomes a predictable, packaged offering. These packages can be interlinked with product purchases (e.g., "buy a car, get 3 free services").

Key takeaways

• Services are intangible → difficult to evaluate quality → clients are sceptical.
• Productizing a service = giving it a name, scope, timeframe, pricing, and demo to make it tangible.
• Productized services reduce cost via templatization and increase buyer confidence.
• Customised service packages and interlinked models (e.g., free services with product) help manage demand and lock in customers.

---

Product Service Systems (PSS)

A Product Service System (PSS) is a marketable combination of products and services that together deliver more value than either alone. It is a hybrid between a pure product and a pure service. The goal is to create, deliver, and capture higher value by bundling.

Why Use PSS?

• Reduces product commoditisation – Adding differentiating services makes it harder for competitors to copy.
• Increases customer willingness to pay – Bundled benefits (e.g., free home servicing) enhance perceived value.
• Reduces resource wastage – Planned service schedules (e.g., AMC) allow better resource allocation than ad-hoc demand.
• Attracts new customers – Solves pain points like maintenance worries.
• Builds competitive resistance – Competitors cannot quickly match a product + service bundle.

Four Ways PSS Creates Value (from transcript)

1. Cost reduction in asset utilisation – Assets used more efficiently through bundling.
2. Increased value of product/service combination – Combined offering is worth more than separate parts.
3. Enhanced customer base – New segments attracted by solving service-related barriers.
4. Resistance to competition – Bundles are harder to replicate than standalone products or services.

Types of Product Service Systems

The lecture describes three distinct models based on ownership and usage:

Type	Ownership	User pays for	Examples
Product-oriented PSS	User owns the product	Maintenance/ service	AMC for washing machine, water purifier
Use-oriented PSS	Firm owns the product	Temporary use (rental)	Bicycle sharing, tent rental, library membership, furniture rental (can be self-service or delivered)
Result-oriented PSS	Firm owns or provides	Specific result or usage (pay‑per‑use)	Voicemail service, pay-per-view movie; subscription (e.g., Netflix monthly) is more like use-oriented

Intuition:

• Product-oriented = "I own it, you fix it."
• Use-oriented = "You own it, I borrow it for a while."
• Result-oriented = "I don't care what you use; I pay for the outcome (e.g., per movie, per voicemail)."

The transcript notes that subscription models (Netflix) are closer to use-oriented PSS because the user rents access over a period, whereas pay-per-view is result-oriented.

Exam tip: Be able to classify an example into one of the three PSS types. Focus on ownership and payment basis (ownership vs. usage vs. outcome).

Key takeaways

• PSS = bundled products and services that increase value for both firm and customer.
• Creates value via cost reduction, higher perceived value, customer expansion, and competitive moats.
• Three types: product-oriented (user owns, firm services), use-oriented (firm owns, user rents), result-oriented (pay for outcome/usage).
• PSS is a strategic tool to differentiate, reduce risk, and manage resources efficiently.

Platform Thinking for Services

Platform thinking for services means building a reusable product platform—a set of service subsystems with a common architecture, common subsystems, and subsystem interfaces—that can be leveraged to offer high service variety across multiple clients and contexts. Instead of developing each service from scratch per client, the platform holds important capabilities and insights, and it can be extended to address new markets with new business models.

Old Approach vs. Platform Thinking

Aspect	Custom‑build (old)	Platform‑thinking
Trigger	Client gives specification → build that product	Proactively build a platform with reusable modules
Reuse	Minimal; each project isolated	Common subsystems and interfaces used across services
Lead‑user role	Client provides requirements only	First client becomes lead user; feedback improves the platform
Scalability	Difficult to replicate for new clients	Base platform easily extended; only customization needed
Organizational impact	No architectural reuse	Platform shapes organisation structure

Connection to Lead Users

When a platform is first implemented, the first client acts as a lead user. Example: Infosys develops a core banking solution for ICICI Bank. The corrections and enhancements from that deployment get built back into the platform. Later, when the platform is taken to other banks (e.g., Yes Bank, IDFC), those new clients can adopt the base platform with only minor customisation. The platform “holds important capabilities and key insights” and saves the organisation from re‑developing each module for every client.

Example: SuperSeva (Bangalore Concierge)

SuperSeva operates a desk in IT company buildings, offering 87+ services (bill payment, cab booking, proof processing) at low prices. Key platform features:

• Shared modules: Multiple services use the same modules (e.g., service tracking, SLAs, error‑proof data collection). This reduces cost per service.
• Process refinement through failures: Every service failure becomes a learning opportunity; the process is refined and made robust. Well‑defined modules ensure that adding a new service requires minimal new process changes.
• Pricing mix: 11 popular services (e.g., phone, electricity bill) are offered free to drive regular cash flow and user engagement; the remaining 76 services charge a minimal fee (value pricing).
• Competitive moat:
  • Scale: Replicating 87+ end‑to‑end services is very difficult.
  • Scope: Variety of services under one roof.
  • Cost: Shared modules keep per‑service cost low.
  • Quality: Continuously refined processes are hard to match.
  • Barriers to entry: High setup cost, near‑monopoly, and entrenched learning make competition extremely difficult.

Exam tip: The SuperSeva case illustrates how platform thinking creates scale and scope advantages that are extremely hard for competitors to duplicate—especially when combined with a free tier that locks in users.

Key takeaways

• Service platforms use a common architecture with reusable subsystems and interfaces.
• Platform thinking moves from one‑off custom builds to proactive, modular development that scales across clients.
• The first client acts as a lead user; enhancements from that client are built into the platform for all future clients.
• SuperSeva shows how shared modules, failure‑driven refinement, and a freemium pricing mix create a defensible business.
• Barriers to entry (cost, quality, network effects) make it extremely difficult for competitors to replicate the platform’s scale and scope.

Identifying the Product Development Team

Once product development begins, organising the team is essential because new product development (NPD) is inherently cross‑functional. Conflicts arise over who owns the product, who has accountability, and which department leads. The lead is determined by the degree of change: the functional area driving the largest change takes ownership.

• Example: In a pharma company with heavy R&D, the R&D department leads the project and the product manager comes from R&D. In a furniture company where ergonomics and aesthetics are key, the design team leads.

Key organisational challenges for NPD teams include:

• Interdependent integration / coordination – complex, long‑gestation projects require more coordination across multiple departments.
• Communication and collaboration – stage‑gate decisions and design specifications must be clearly communicated across functions.
• Incentive and reward systems – different teams (e.g., R&D vs. shop floor) need tailored incentives to support unusual or high‑skill tasks.

Types of Team Structures

Three primary structures exist, each with distinct advantages and drawbacks. The choice depends on product type, required expertise, and project duration.

Functional NPD Structure

The product moves sequentially from one functional department to the next (e.g., blueprint → casting → forging → assembly). Each department performs its specialised task and then hands off.

Aspect	Description
Suitable for	Customised development projects with clearly marked stages (e.g., thermal power plant, steel manufacturing).
Advantages	Deep functional expertise; clear stage ownership.
Limitations	Poor coordination between stages; longer lead time; no single person owns the full product; end‑to‑end visibility is low.

Project‑Based NPD Structure

A dedicated team is assembled from the start and works exclusively on the new product until launch — like a startup.

Aspect	Description
Suitable for	Breakthrough projects, startups, radical innovation.
Advantages	Shortens time to launch; excellent coordination; full ownership.
Limitations	Functional expertise is limited to the team; knowledge is not shared across the organisation; team members are siloed for the project’s duration.

Matrix NPD Structure

A hybrid of functional and project structures. Team members have dual reporting: to a functional manager (technical/skills oversight) and to a project manager (new product activity). It allows resource sharing across projects.

Two sub‑types:

• Heavyweight matrix – The product manager has discretionary power over resources (e.g., can override a functional manager’s request to reassign a designer). Closer to a project structure.
• Lightweight matrix – The product manager plays only a coordination role; the functional manager retains control over resourcing and scheduling.

Aspect	Description
Suitable for	Complex, long‑gestation projects (e.g., aerospace, new car launch, Gillette razors).
Advantages	Combines functional depth with project focus; key specialists can work on multiple projects; core team stays for duration.
Limitations	Dual reporting can create confusion; requires strong project management.

Choosing the Right Structure: Product Type → Structure Fit

flowchart TD
  A[Product type] --> B{Breakthrough / Radical?}
  B -->|Yes| C[Project-based structure]
  B -->|No| D{Deep technical expertise critical?}
  D -->|Yes| E[Functional structure]
  D -->|No| F{Platform / system solution?}
  F -->|Yes| G[Heavyweight matrix]
  F -->|No| H[Derivative / enhancement?]
  H -->|Yes, long & complex| I[Lightweight matrix]

Firms typically adopt one dominant structure (e.g., Maruti uses a functional structure for incremental projects; Apple uses a project‑heavy design structure). Switching between structures is difficult due to organisational rigidities.

Exam tip: Remember the fit: radical → project, deep expertise → functional, platform/systems → heavyweight matrix, derivative/long → lightweight matrix. Product manager’s ownership varies accordingly — highest in project and heavyweight matrix.

Key takeaways

• The functional area with the greatest degree of change should lead product development.
• Functional structure – sequential handoffs, good for custom projects, but poor coordination.
• Project structure – dedicated team for breakthrough, fast but isolates expertise.
• Matrix structure – dual reporting, best for complex long‑gestation projects; heavyweight gives PM power, lightweight keeps power with functional manager.
• Structure must fit product type; switching structures is organisationally difficult.

Structuring the Team

A new products team differs from a traditional hierarchical team. The right structure depends on the situation — there is no single "best" way. Effective product managers adapt based on context, experience, and understanding.

Two starting dimensions from earlier discussion:

• Functional / project-based / matrix — basic organizational forms.
• Lightweight vs. heavyweight — reflecting how much control the product manager has over the team.

Why structure matters

New product development is inherently cross-functional. The team must integrate marketing, R&D, manufacturing, sales, design etc. This requires:

• A culture of collaboration — intense, complex integration of functional areas.
• A culture of creativity — space for innovation.
• Clarity and ownership — each function knows its deliverable, works toward a shared mission. No hidden agendas or functional silos.

When these succeed, the result is synergy: $2+2=5$, i.e., the collective output exceeds the sum of individual capabilities.

Example: Pixar
Pixar's value proposition combined advanced computer graphics technology with compelling storytelling. Steve Jobs (as sponsor) brought together key talents John Lasseter and Ed Catmull. The culture merged creative content creators and technical designers — a difficult but powerful integration. When Disney acquired Pixar, it preserved the team's autonomy to avoid bureaucracy killing creativity. Similarly, Newell allowed Rubbermaid's innovation-oriented units to run independently after acquisition.

Managerial takeaways

• Structure must feed the situation — adapt, don't impose rigid templates.
• Leadership style shapes culture. The product manager ensures cross-functional clarity and protects the team from organizational friction.
• Autonomy is critical for innovation-driven units; heavy control can stifle creativity.

Key takeaways

• New product teams are cross-functional by nature; require collaboration and creativity.
• Synergy = collective output > sum of parts.
• Leaders must tailor structure to context; no one-size-fits-all.
• Preserve autonomy for innovation teams to protect their culture.

---

Product Integrity

Product integrity is the consistency of all aspects of a product — form, internal design parameters, features, internal processes, and target customers. It creates a "feels just right" experience and a wow factor. Integrity is subtle, not easily measured by functionality alone; it is the harmony between the product and the user's lifestyle.

Two dimensions:

Type	Definition	Focus
Internal integrity	Consistency between functions, structure, and organizational parts — all fit and work well together.	Organization-level fit
External integrity	Consistency between product performance and user expectations.	Customer-level fit

Sources of product integrity

• Organization design — a seamless pattern of organizing that aligns everyone around the product and customer.
• Leadership — product owners/sponsors must have clarity of vision.
  • Heavyweight project managers in long-gestation projects act as a catalysing force, keeping the team focused on user expectations and product integrity.
  • Effective leaders communicate the product concept, align internal and external resources, and infuse the "soul" into the product.
• Instinct and aesthetics — leaders like Steve Jobs combine technical insight with creative sensibility; such instinct is rare but critical for achieving high integrity.

Example: Gillette Mach3
Product integrity meant the razor, cartridge, positioning, and user experience all formed a consistent whole — "getting it right".
Example: Apple — an entire design philosophy focused on integration and user sensibility, resulting in products with high integrity.

Key takeaways

• Product integrity = consistency across form, features, processes, and customer needs.
• Internal integrity: organization fits together. External integrity: product meets user expectations.
• Leadership is essential — heavyweight project managers drive integrity in complex projects.
• Integrity creates the "wow factor"; cannot be reduced to checklists.

Ownership and Empowerment

New product development (NPD) demands buy-in from every team member. Unlike routine projects, NPD requires alignment to a shared objective – a product that does not yet exist. Skilled specialists from multiple functions (design, R&D, operations, marketing) must collaborate as a team, not as individual contributors. Ownership cannot rest with one person.

Where ownership comes from:

• Training – members need to understand design thinking, product concepts, and cross-functional impacts.
• Empowerment – management grants autonomy; without freedom, creative teams cannot innovate.
• Motivation – empowerment and motivation are interlinked; both drive ownership.

Management’s role: Provide support, facilitate decisions, and avoid intervening in day-to-day execution. Let the team make decisions.

Key takeaways

• Ownership is essential for alignment in NPD.
• Derived from training, empowerment, and motivation.
• Autonomy (free hand) is critical for creative teams.
• Management should support, not micromanage.

Leadership Selection and Style

Selecting the leader (product manager):

• Acts as a general manager with breadth across functions, not a specialist.
• Must have self-confidence, empathy, and the support/trust of the team.
• Leader supports the team; team accepts the leader’s authority.

Leadership characteristics vary by stage:

flowchart LR
    A[Early stage: chaos, ideas] --> B[Creative, inspiring leader]
    C[Implementation stage: testing, timelines] --> D[Disciplinarian, action-oriented leader]

• Early stage – generation of multiple ideas; leader needs to be creative and inspiring.
• Implementation stage – product development, testing, budget adherence; leader must be disciplined and action-oriented.

It is difficult to find one person skilled at both. Options: appoint two leaders or have one leader who adapts.

Key takeaways

• Product manager = generalist with breadth, empathy, and trust.
• Leadership style must shift from creative (early) to disciplined (implementation).
• Two leaders or one adaptive leader can manage the transition.

Team Composition: Core, Ad Hoc, Extended

Members represent their functional parent group (e.g., marketing person from marketing department). They bring functional knowledge.

Three concentric team layers:

Layer	Duration	Members	Purpose
Core team	Entire project (e.g., 2–3 years)	1–2 per key function (marketing, R&D, etc.)	Continuity, complete view, learning from past iterations
Ad hoc team	Specific phase only	Additional specialists from a function (e.g., factory workers during production)	Focused work; return to functional group after phase
Extended team	As needed	External stakeholders: suppliers, dealers, marketing research firms, resellers	Ecosystem support, delivery

Why core team matters: In long projects (e.g., Gillette razor – 3 years), core members retain knowledge of previous errors and changes.

Key takeaways

• Core team provides continuity; ad hoc team adds phase-specific capacity.
• Extended team includes external partners.
• Each member brings functional skills from their parent group.

Roles in NPD Teams

Not every role is present in every project; product manager and product champion are most common.

Role	Description
Product manager	Leader with breadth; owns project execution.
Product champion	Senior/experienced member who takes ownership (formal or informal).
Sponsor	Senior executive with budget accountability; not hands-on (e.g., Steve Jobs at Pixar).
Strategist/inventor	Provides rational, objective input; invents or creates new models.
Facilitator	Manages operations, internal approvals, collaboration.

Key takeaways

• Product manager and product champion are typical; other roles depend on situation.
• Sponsor provides oversight and resources, not day-to-day direction.

Network Teams (No Dedicated Team)

For line extensions or enhancements (e.g., new Pepsi flavour or bottle size), a full dedicated team may not be needed. Instead, a network structure is used:

• Nodes – point-of-contact individuals (often from a program management office) who connect functions.
• Links – operating relationships.
• Each node connects to experts within their functional department.

The work is executed within the existing functional structure; coordination happens via nodes. This is efficient for smaller product changes.

Key takeaways

• Network teams work without a dedicated full-time team.
• Nodes coordinate across functions; suitable for incremental innovations.

Training and Mindset

Training is essential for NPD teams, with management support. Key areas:

1. Cross-functional perspective – break silos; every member must understand the product mindset (marketing orientation).
2. Marketing orientation – technical members cannot focus solely on specs; they must consider profitability, feasibility, usability.

Example: A great technical feature is useless if it is too hard to assemble or use. Training helps overcome the barrier of thinking only in functional silos.

Key takeaways

• Training shifts members from silo thinking to product/marketing mindset.
• All team members must understand how their work impacts the end product and profit.

Managing Globally Dispersed Teams (GDT)

Today’s NPD teams are often virtual and geographically dispersed (e.g., Intel, Microsoft with teams in Hyderabad, Bangalore, Seattle). Multiple locations/organizations collaborate.

Challenges:

• Different time zones – coordinating meetings, stage-gate reviews.
• Cultural differences – Asians vs. Europeans vs. Americans may interpret specifications, timelines, and communication differently.
• Control and performance measurement – harder to monitor across distance.
• Communication – relies more on written (email, chat) than verbal (shouting across the floor); less spontaneous.

Advantages (when managed well):

• Scalability – easier to add diverse skills from different regions.
• Access to specific skills – e.g., testing in India, design in Europe.
• 24/7 work cycle – leveraging time zone differences for continuous progress.

Success factors for GDT:

• Strong communication technology (Google Meet, Zoom, Teams).
• Regular scheduled meetings (e.g., daily 10-minute core team stand-up).
• Dedicated effort, mutual support, and cohesion.

Key takeaways

• GDT enables global skills and round-the-clock work but introduces coordination and culture challenges.
• Effective GDT requires structured communication and written documentation.
• Integration and trust are manager’s responsibilities.

Exam tip: Be ready to contrast co-located vs. virtual teams on dimensions like control, communication style, and cultural sensitivity. The time-zone advantage (24h work) is a common test point.

Strategic Launch Planning: Overview

Strategic launch planning is the final phase of the New Product Development (NPD) process. After idea generation, refining, prototyping, testing, full product development, and further user testing, the product exits the internal company pipeline and enters the market — where real user feedback begins. This stage is analogous to releasing a completed movie to theaters: all internal work is done, and the product now faces its true test.

The module also addresses public policy issues (e.g., product failures) and the growing importance of sustainability, ethics, and environmental concerns. A product manager must be conscious of these external forces during launch.

The NPD journey to launch

The transcript implies a process that flows through these stages before strategic launch:

flowchart LR
  A[Idea generation] --> B[Refining idea]
  B --> C[Product prototype]
  C --> D[Prototype testing]
  D --> E[Full product development]
  E --> F[User testing & feedback]
  F --> G[Strategic launch planning]
  G --> H[Go to market]

Why strategic launch matters

• Transition from internal operations to user-facing reality.
• Real-world feedback begins – success or failure is determined here.
• Public perception and policy compliance become critical.

Exam tip: Strategic launch is not just marketing; it includes anticipating regulatory, ethical, and environmental scrutiny. Be prepared to discuss how sustainability concerns influence launch decisions.

Key takeaways

• Strategic launch is the final NPD phase where the product enters the market.
• Prior stages (idea → prototype → development → testing) are internal; launch is the first external exposure.
• Product managers must consider public policy issues (failures, regulations) and sustainability/ethics.
• The movie-release analogy captures the shift from production to audience reception.
• Launch planning is not an afterthought — it integrates market readiness and societal consciousness.

Product Launch and Strategic Launch Planning

A product launch is the phase where marketing, sales, distribution, and channel management activities intensify, while R&D/operations involvement declines. The launch is expensive and risky because control shifts from the internal development team to the external market. Effective strategic planning must begin early in the NPD process; firms that neglect upfront planning discover costly problems only when the product hits the market. Well-prepared organisations have backup plans (B, C, D) because they anticipated issues.

The Role of Upfront Strategic Planning

• Marketing planning should run from the start, not be left until launch.
• Weak strategic planning shows up immediately at market entry – problems become visible and hard to fix.
• For new-to-the-world or new-to-the-firm products, clarity on commercialisation and competitive positioning is essential.
• A Product Innovation Charter (PIC) sets strategic goals; each stage should revisit those goals to avoid deviation from the original customer problem or market gap.

Strategic vs. Tactical Launch Decisions

Dimension	Strategic Launch Decisions	Tactical Launch Decisions
Horizon	Long-term, high impact	Short-term, day-to-day
Focus	Set overall tone & direction; define to whom and how to sell	Execute the marketing mix – promotion, distribution, pricing
Example	Committing to a 3-year programme (vs. skipping a single class)	Adjusting weekly study plan, choosing which promotion channel to use
Link	Strategic choice (e.g., aggressive launch) dictates tactical choices	Tactical must align with strategic direction

Example: An aggressive strategic launch demands a broad target market and a fast campaign – narrow targeting is incompatible with an aggressive plan.

Risks and the Need for Planning

• Internal control is high (you can realign teams, secure materials); external launch control is low.
• Planning, not luck or hope, manages risk.
• Product launch is the most expensive and risky part of the NPD process; structured planning replaces shooting in the dark.

Requirements for an Effective Market Launch Plan

Four key principles (a fifth is implicit from earlier discussion):

1. Central to the NPD process – the launch plan is as important as development itself.
2. Begins early – planning for launch starts at the beginning, not after development.
3. Based on good market intelligence – feedback from idea testing, prototype testing, alpha/beta/gamma testing must be incorporated.
4. Adequate resources – allocate human (sales, technical support, customer service) and financial resources. Launch team members should join the NPD team well before launch (core or extended).

In addition, revisit strategic goals (the PIC) at each stage to ensure the product stays true to its original market problem, avoiding premature launch just to beat time.

flowchart LR
    A[Strategic Launch Decision] --> B{Target market?}
    B -->|Broad| C[Fast campaign, high resource allocation]
    B -->|Narrow| D[Selective promotion, slower rollout]
    C & D --> E[Tactical Marketing Mix]

Exam tip: The four listed requirements + the revisit-goals principle are a high-frequency exam point. Understand why each requirement matters, especially the need for early planning and integration of market intelligence.

Key Takeaways

• Product launch is a high-risk, high-cost phase requiring upfront strategic planning.
• Strategic decisions are long-term and directional; tactical decisions execute the marketing mix.
• Weak planning leads to problems that surface at launch – backups (Plan B, C, D) are essential.
• Effective launch plans: central to NPD, start early, use market intelligence, and have dedicated resources.
• Continually check against the Product Innovation Charter (PIC) goals.

Strategic Platform Decisions

Strategic platform decisions are the high-level choices a firm makes before executing a product launch. They define the type of demand to pursue, the product’s intended lifespan, the intensity of the launch, the source of competitive advantage, how to handle existing and competing products, market scope, and brand image. Each choice must align with the product’s novelty and market context.

Type of Demand Sought

The launch’s primary objective depends on whether the product is new-to-the-world, an upgrade, or a line extension.

Product context	Demand type	Goal	Example
New-to-the-world (truly novel)	Primary demand	Stimulate overall category need; create buzz	Apple iPhone (2007): Steve Jobs emphasised “three products in one” to ignite desire for a smartphone
Product improvement / upgrade (existing line)	Replacement demand	Migrate existing customers to new version; poach competitors’ users	iPhone 17 launch: encourage Apple users to upgrade and win Samsung/OnePlus users
New entry / line addition in an established market	Selective demand	Persuade customers to choose this brand over others	Diet Pepsi or oat-based cereal: target health-conscious buyers who would otherwise buy regular products

Exam tip: Matching the product type to the demand type is a classic case-study question. “New-to-world” always means primary demand; “line extension” always means selective demand.

Permanence Decision

How long does the firm intend the product to stay on the market?

• Default: stay indefinitely – no planned retirement.
• Stay only if goals are met – avoid commitments that make exit difficult (e.g., long-term contracts, dedicated assets). The firm launches several variants knowing only some will survive (e.g., Maruti launching three models, retaining only the profitable one).
• Temporary / seasonal – the product has a known finite life (e.g., fashion collections, summer toys, limited-edition foods). After the season, clear and kill; next season brings something new.

Aggressiveness of Launch

Three levels of resource commitment at the outset:

• Aggressive – heavy marketing, promotions, early push for market share.
• Cautious – low initial investment, test market reaction, then expand if positive.
• Balanced – aggressive on the primary segment (e.g., Gen Z male with influencers and ads), cautious on secondary segments (e.g., millennial or female users); later extend or add product lines based on response.

Competitive Advantage (Generic Strategy)

Based on the classic cost-leadership vs. differentiation trade-off.

Strategy	Focus	Price	Features
Cost	Minimise price	Low	Minimal – essential only
Differentiation	Superior features/quality	High	Rich – justifies premium

These three dimensions form a quality–cost–speed triad: you can excel at two, but not all three. For example, high quality and low cost usually require slow speed.

Product Line Replacements & Cannibalisation

Firms with strong R&D often cannibalise their own products rather than let competitors do it.

• Leader strategy: Continuously innovate and replace existing products (e.g., Gillette: 1 blade → 2 → 3 → 5; improved materials). This prevents competitors from stealing share.
• Follower (imitation) strategy: Copy the leader’s innovation, make incremental improvements, and launch a competing product quickly.

Competitive Relationship in Launch Communications

Three stances when communicating during the launch:

• Ignore – no mention of competitors. Typical for market leaders (e.g., Asian Paints ignoring smaller players like Birla).
• Direct at competition – explicitly target a specific rival. Common for challengers (e.g., Pepsi directly competing with Coke; Birla ads referencing the “elephant” – Asian Paints).
• Avoid specific competition – sidestep direct confrontation, often by positioning in a different segment.

Exam tip: A firm’s market share usually dictates its stance. Low share → attack the leader. High share → ignore smaller players.

Scope of Market Entry

Introduce the product to a narrow part of the market first (test, observe, fix) then roll out to the full market. Closely tied to aggressiveness: narrow scope is cautious; full launch is aggressive.

Image Change Required

How much does the new product alter the brand’s existing image?

• New image – the product shifts the brand identity (e.g., Maruti’s premium Nexa dealer network vs. budget Arena). Requires separate channels, advertising, and positioning.
• Major change – significant repositioning; campaigns must address the new image.
• Minor tweak – small adjustments in perception.
• No change – the product fits the brand’s current image (e.g., another cost-effective, high-mileage car). No extra investment needed; the brand’s image transfers automatically.

Key takeaways

• Demand type (primary, replacement, selective) is determined by how new the product is to the market.
• Permanence can be indefinite, conditional, or temporary – never assume permanence is always the goal.
• Aggressiveness, competitive advantage, and market scope must be coherent choices; speed, quality, and cost cannot all be maximised.
• Cannibalisation is a strategic choice: leaders innovate to kill their own products before rivals do.
• Competitive relationship in ads reflects market position (leader ignores, challenger attacks).
• Image strategy affects distribution, advertising, and resource allocation (e.g., separate dealer networks).

Target Market Decisions

After strategic platform-level decisions, market decisions determine who the product serves and how it is positioned. These decisions follow standard marketing principles (segmentation, targeting, positioning, 4Ps) but have unique nuances for new products.

Segmentation Bases for New Products

Basis	Description	Example
End-use	Segment by how the product is used; function determines features and quality.	Shoes: running vs. walking vs. athletics; T-shirts: polo vs. workwear vs. party wear
Geographic / Demographic	Target or exclude specific geographies or demographic groups.	Unilever soap for Indian market; financial products for new job starters vs. retirees
Behavioral / Psychographic	Based on values, lifestyle, activities, or personality.	Titan/Tanishq: traditional bridal jewelry vs. Mia lightweight modern designs for working women; financial products for daily traders (F&O) vs. long-term investors
Benefit segmentation	Plot products on benefit maps (e.g., ease of use vs. price, comfort vs. price) to find blue ocean spaces with low competition.	Identify empty region on the map where competitors are sparse and position the product there

Micro‑Marketing and Mass Customization

Digital technology enables targeting narrower, tighter segments than traditional mass media. Mass customization tailors products to individual preferences without sacrificing scale.

Four types of mass customization:

• Collaborative customizers – Involve the customer early, co‑create the product (e.g., Dell.com: customer selects processor, hard disk, screen size from a configurator; assembled to order).
• Adaptive customizers – Product adapts to customer choices; e.g., Chipotle / Subway: base (bread, base) + selections (sauces, toppings) made to order.
• Cosmetic customizers – Minimal product changes; standard product delivered with different presentation or packaging.
• Transparent customizers – Deep insight into customer preferences; product adjusted without explicit customer input.

Exam tip: Mass customization works best with platform‑based products where components can be mixed and matched (e.g., Dell’s laptop platform). Consider made‑to‑order (MTO) vs. made‑to‑stock (MTS) operations.

Key takeaways

• Segment using end‑use, geography/demographics, psychographics, or benefit maps.
• Benefit maps help identify uncontested market positions (blue ocean).
• Digital tools allow micro‑targeting and mass customization.
• Four customization types: collaborative, adaptive, cosmetic, transparent.

---

Diffusion of Innovation – Targeting and Adopters

Diffusion is how fast a new product spreads (diffuses) through the marketplace. The speed depends on five product characteristics.

Factors Affecting Diffusion Speed

Factor	Meaning	Example
Relative advantage	Product is clearly superior in quality or value → faster adoption	Google search: superior algorithm + clean blank start page vs. Yahoo’s cluttered interface
Compatibility	Product fits existing habits, systems, or usage patterns → faster adoption	New blade that fits an existing razor handle; microwave oven was slow because it deviated from traditional cooking
Complexity	Easy to use → fast adoption; complex → slow	Apple Newton (complex, slow) vs. iPod (simple, intuitive)
Divisibility / Trialability	Can user try a small portion before buying? → faster adoption	Detergent sachets or free samples; not possible for cars or home appliances (need test drive or full purchase)
Communicability / Observability	Benefits are easy to see and explain → faster adoption	Tangible advantage (time saved, acceleration) is easier to communicate than emotional benefits (satisfaction, comfort)

Adopter Categories

Not all consumers adopt a new product at the same time. The standard diffusion curve splits adopters into five groups:

Category	% of Market (approximate)	Behaviour
Innovators	5–10%	First to try; fascinated by novelty; willing to experiment
Early adopters	10–15%	Next to adopt; opinion leaders; spread word‑of‑mouth
Early majority	~30%	Adopt after positive reviews and trusted feedback
Late majority	~? (remainder)	Wait until product is well‑established; risk‑averse
Laggards	~?	Last to adopt; only adopt under social pressure (FOMO) or necessity

The first two groups together represent 15–25% of the market. For a successful launch, focus marketing resources on innovators and early adopters; they will influence the early majority.

Exam tip: Do not waste energy on laggards or late majority during launch. They will adopt only after the product is proven. Target the early adopters to build momentum and word‑of‑mouth.

Key takeaways

• Diffusion speed = how fast the product spreads; driven by relative advantage, compatibility, complexity, trialability, and observability.
• Adopter categories: innovators (5–10%), early adopters (10–15%), early majority (~30%), late majority, laggards.
• Launch strategy: aim first at innovators and early adopters; rely on them to pull in the early majority.
• High trialability and clear observable benefits accelerate diffusion.

Product Positioning

Product positioning answers why a buyer in the target market should choose your product over competitors’. It communicates the unique value the user gets. Originally an advertising concept, positioning is now an integral part of product strategy and feeds directly into the product charter.

A positioning statement must align all elements of the marketing mix—product, brand, price, promotion, distribution. If the product is positioned as “value for money,” every element (packaging, ad tone, channel) must reinforce that. Inconsistency confuses customers and can kill the product’s takeoff.

The Feature–Function–Benefit Triad

Every positioning message rests on three linked layers:

Layer	What it is	Example (toothpaste with crystals)
Feature	What the product has	Red crystals, mint flavour
Function	What that feature does	Kills germs, provides longer-lasting fresh breath
Benefit	What the customer feels	Confidence, whiter teeth, no bad breath

Effective advertising communicates all three: the feature, its function, and the resulting benefit.

Alignment Check

Exam tip: If any mix element contradicts the positioning (e.g., premium branding with discount pricing), the product will likely fail. Consistency is non-negotiable.

Key takeaways

• Positioning = the “why” a target buyer chooses your product.
• Feature → function → benefit triad must be clearly communicated.
• Everything in the marketing mix must be consistent with the positioning.
• Misalignment leads to customer confusion and market failure.

---

Brand vs. Trademark

Every new product needs identification so customers recognise it instantly. Two related but distinct concepts:

Trademark	Brand
Legal protection for a distinctive sign (logo, shape, colour).	The feeling, image, and associations built around the trademark.
e.g., McDonald’s golden arches, Apple’s half-eaten apple, Nike’s tick mark.	e.g., Apple = innovation, design, quality; Nike = performance, athleticism.
Legally enforceable – copying can lead to a lawsuit.	A marketing strategy concept; not legally protectable itself.
Registration required in some countries; others use first‑user principle (the first to use it in commerce gets rights).	Built over time through product portfolio, communication, and consistent experience.

Trade dress protection extends to the shape or packaging of a product – e.g., the Coca‑Cola bottle shape is protected because it instantly signals the brand.

Exam tip: Do not confuse trademark (legal) with brand (image). Many exam questions test the distinction.

Key takeaways

• Trademark = legally protected identifier (logo, shape).
• Brand = the set of perceptions and emotions attached to that trademark.
• Trade dress protects distinctive product shapes/designs.
• Legal frameworks vary (registration vs. first‑user).

---

Brand Naming

A good brand name automatically communicates something about the product’s image, feature, or benefit. If the name itself carries meaning, half the marketing job is done—but the product must deliver on the implied promise.

Common Naming Pitfalls

Pitfall	Explanation	Example
Not anticipating future use	A name that works in one region may sound different or lose meaning elsewhere.	“EZ” in the US (pronounced “easy”) vs. “EZ” in India/Europe (pronounced “ee‑zed”).
Negative meaning in another language	A name may be slang or offensive in a local language.	Failure to check multiple Indian languages before naming a food item.
Too little time allocated	Deciding the name at the last minute leads to a weak, uninspired identity.	Naming the product the day before launch.
Wrong emotion/connotation	The name evokes an inappropriate feeling (e.g., aggressive, sad).	“Killer” (intended to kill competition) – instead “killed itself.”
Too many people involved	Endless debate delays decisions and often yields a suboptimal name.	A committee of ten unable to agree.

Brand extension – using an existing strong brand to launch a new product (same or new category) – is a common alternative to inventing a new name. It works well when the parent brand has positive associations and high quality. Examples: Maggi (noodles → other ready‑to‑eat foods), Parle‑G (biscuit → sub‑brands), Ashirwad (atta → masala, ghee, other flours). However, if the original association is too strong, extension may fail.

Exam tip: Brand extension can save marketing costs but risks diluting the parent brand if the new product is inconsistent with its image.

Key takeaways

• A name should communicate product attributes; aspirational/vague names fail.
• Avoid pitfalls: cultural/linguistic issues, insufficient time, wrong emotion, too many decision‑makers.
• Brand extension leverages an existing strong brand, but must be used carefully.

---

Global Branding: Standardisation vs. Adaptation

Two main strategies for taking a brand across markets:

Strategy	What stays the same	Examples
Standardisation	Product, name, and positioning identical worldwide.	Gillette blades, Coca‑Cola, Kellogg’s cereals.
Adaptation	Product may be identical but positioning adjusted for local markets.	Honda: “quality/premium” in the US vs. “speed/youth/adventure” in Japan. Canon AE‑1: “So advanced, it is simple” (US) vs. “high‑tech for experts” (Japan).
Name adaptation	Product similar but name changed per market.	Procter & Gamble’s detergent: “Tide” in the US, “Ariel” in Europe/Asia. Unilever’s dishwashing liquid: “Cif” in some markets, “Vim” in India, “Vish” elsewhere.

Some companies blend both: Unilever uses uniform names for brands like Lipton, Knorr, Dove, Vaseline, but adapts names for other products.

Exam tip: Adaptation is not just for language – it can also be for cultural positioning (e.g., Honda’s different messages in US vs. Japan). Standardisation works when the brand’s core appeal is universal.

Key takeaways

• Standardisation: same name, product, positioning everywhere.
• Adaptation: same product but different positioning or name per market.
• Many global firms use a hybrid approach.
• Choosing between them depends on cultural fit, brand strength, and market maturity.

Brand Communities Myths

A brand community is a group of diehard fans or followers who share a common interest in a brand, its status, messaging, or lifestyle (e.g., Royal Enfield, Harley-Davidson). In the world of social media, a strong community signals a powerful brand and is a key criterion for new product launch success. However, several myths surround what brand communities really are and how they work.

#	Myth	Reality
1	Brand community is a marketing strategy.	It is a corporate/business strategy — a company-wide investment in identity, early adopters, feedback, brand ambassadors, and crisis management.
2	The brand community exists to serve the business.	The community is created to serve the people — help each other, share authentic feedback. Negative feedback strengthens authenticity, even if it hurts short-term business interests.
3	Build the brand, and the community will follow.	Community is not automatic. The company must invest in creating the community; community and brand reinforce each other in a virtuous circle, not sequentially.
4	Brand communities are for faithful brand advocates only.	Smart companies embrace conflicting interests — negative opinions and complaints make the community authentic and thriving. A fan-only echo chamber lacks credibility.
5	Opinion leaders build strong communities.	Communities become strongest when everyone plays a role, not just influencers or celebrities. People join to be part of a like-minded group where they have a voice.
6	Online social networks are the key to community strategy.	Online networks are a tool, not a strategy. The community channel (physical, outdoor, etc.) must align with the product category and user benefits.
7	Successful brand communities are tightly managed and controlled.	Communities should be democratic, organic, and free — “of the people, by the people.” Managerial control destroys the sense of belonging and expression.

How brand and community reinforce each other (Myth 3)

flowchart LR
    A[Invest in community creation] --> B[Stronger brand]
    B --> C[More engaged community]
    C --> B

Exam tip: The “serve the people” principle (Myth 2) is the most frequently tested idea. Authenticity gained from user-centric feedback (including negative) builds long-term community trust — a key differentiator from simple fan pages.

Key takeaways

• Brand community is a cross-functional business strategy, not just marketing.
• Communities thrive when they serve members, not the business — authenticity matters.
• Community and brand develop in parallel, each reinforcing the other.
• Successful communities welcome dissent and are not controlled by management.
• Online social media is one tool — the channel must match the product experience.
• Every member matters more than a few opinion leaders.

Implementation of Strategic Planning: Pre-Launch & Launch Stages

The strategic platform and market choices set the direction. The tactical phase — execution — is where the product actually hits the market. This execution splits into two stages: pre-launch (building capability to compete) and launch (the beachhead and early growth). Marketing expenditure peaks around the launch stage.

Two Major Stages

Stage	Purpose	Typical Activities
Pre-launch	Build preparation & capability before the product hits the market	Training sales/promo staff, building service capability, pre-announcement, arranging reseller stocking
Launch	The exact date/time when the product is announced and hits the market	Full-scale advertising, press releases, product reviews, public release

Within the launch stage, two sub-phases exist:

• Beachhead (the initial launch event)
• Early growth (the immediate post-launch period)

Six Stages of Announcement Sequence

The process of revealing a new product to the outside world follows a typical sequence of six stages, from total secrecy to full public broadcasting:

1. Non-disclosure – Kept secret within the core design/development team. No information leaks.
2. Product testing – First outside exposure. Beta testers sign confidentiality agreements.
3. Anticipation – Build market buzz. Release statements or press releases describing the problem the product solves, creating excitement. Think: movie trailers before the release.
4. Influentials – Use influential users, industry researchers, press kits, or key customers to generate early credibility (e.g., limited trials for car reviewers).
5. Broadcast (PR) – Full press releases, product released for reviews. Formal announcement.
6. Promo – Start of full-scale advertising campaigns (may also include teaser ads earlier, but often held until launch).

Exam tip: The first two stages (non-disclosure, product testing) occur during development. Stages 3 & 4 (anticipation, influentials) are part of pre-announcement. Stages 5 & 6 (broadcast, promo) are the actual launch.

Pre-Announcement in Detail

Pre-announcement uses subtle signaling to create interest before the actual launch. Its main goals:

• Hype interest in the upcoming product.
• Keep current customers warm – prevent them from switching to a competitor while waiting.
• Encourage prospective buyers to wait – especially effective for big-ticket items (e.g., cars, electronics) where buyers are willing to delay purchase for months. Not effective for low-cost impulse items (e.g., ₹10 chips).
• Block competitive entry – by making competitors hesitate or rush, or by occupying customers’ “mental space.”

Tools for Pre-Announcement Signaling

• Advertising (teaser campaigns)
• Participation in trade shows
• Comments by salespeople (e.g., “Something exciting is coming next month”)
• CEO speeches at economic or trade forums
• Tips from vendors (e.g., suppliers ordering extra materials) or distributors (e.g., booking shelf space)
• Field activity (hiring new sales staff)

Factors Influencing the Decision to Pre-Announce

Two key factors are discussed:

1. Firm Size

Firm Type	Likelihood of Pre-Announcing	Rationale
Small firms / startups	More likely	Need traction, lead time, and awareness. Use teasers on social media, YouTube, Instagram.
Large firms	More circumspect, less likely	Risk of government regulation, competitive copying, overhyping expectations, or creating excessive anticipation.

2. Industry Competition

Industry Type	Likelihood of Pre-Announcing	Rationale
Highly competitive	Less likely	Want to keep product a surprise to preserve lead time. Premature signaling gives competitors a head start to copy or react.
Less competitive / niche	More likely	Less risk of competitive response; can build customer wait-and-see.

Exam tip: Pre-announcement is especially relevant when network externalities exist — the announcement creates a buzz that draws users into the ecosystem, making them wait or join early.

Key Takeaways

• Tactical execution splits into pre-launch (preparation) and launch (the event).
• Announcement stages progress from secrecy to full publicity; pre-announcement covers stages 3–4.
• Pre-announcement is a strategic tool to lock in customers and block competition, particularly for high-involvement purchases.
• Small firms and less competitive industries are more likely to pre-announce; large firms and highly competitive industries are more cautious.

Beachhead Stage (Launch)

The beachhead stage is the second phase of the launch cycle, following pre‑launch. The term originates from military operations: the moment a force lands on enemy soil, the battle begins. In product launch, pre‑launch is the observation phase; the beachhead is when the product actually meets the market. No amount of anticipation or risk planning guarantees success – the real test begins at launch. Conditions are never ideal; some failures (e.g., communication breakdowns, supply delays, public confusion) are inevitable. The key is to break inertia: set a date and launch, then make adjustments later rather than waiting for a perfect moment.

Exam tip: The beachhead stage is decisive – it determines whether the product becomes a blockbuster or fails. Pre‑launch planning only reduces the severity of failures, not eliminates them.

Lean Launch

Lean launch applies the broader lean philosophy (flexibility, delayed decisions, resource optimization) to the product launch. Instead of committing large inventory upfront, the launch is kept small and flexible; the supply chain is designed for rapid ramp‑up if demand takes off.

• Supply chain remains flexible – minimal inventory early, quick response to sales data.
• Lead time minimized – from raw material to consumer, coordination across sourcing, manufacturing, and delivery.
• Uncertainty reduced – avoids costly write‑offs if the product fails.
• Operational flexibility – can expand production or distribution rapidly.

Example	How lean is applied
Dell	Customised laptops – only assemble after order; component stock at factory allows quick scaling.
Benetton	Customers design or match garments; customised and delivered within a day; no over‑stocking.

Key takeaways (Beachhead & Lean Launch)

• Beachhead = launch day when the product meets the market; perfect conditions never exist.
• Launch requires a go‑ahead despite possible failures; adjustments happen after.
• Lean launch delays full commitment, keeps supply chain flexible, and reduces risk of excess inventory.
• Examples: Dell’s build‑to‑order model, Benetton’s custom clothing offer.

---

Launch Tactics Planning

Tactical planning for the launch covers distribution channels, pricing, marketing communications mix, and sales training. These decisions directly affect new product performance – execution quality (e.g., product availability and awareness alignment) matters as much as the product itself.

Copy Strategy Statement

The copy strategy statement is the brief given to an advertising agency (or internal marketing team) to guide the ad campaign. It must include:

• Market segment being targeted.
• Product positioning statement.
• Communication mix and the pieces covered.
• Major copy points – the key messages (e.g., “largest insurer in the world”, “5G‑enabled smartphone”, “Make in India”).
• Product attributes – features, functions, and benefits.

Exam tip: The copy strategy statement is the link between product planning and advertising execution – exam questions often ask for its components.

Personal Selling Organisation

The sales team can be organised by:

• Product level – e.g., dedicated salespeople for hygiene products vs. food & beverage.
• Geographic level – e.g., territorial sales managers for districts or states.

The choice depends on the new product’s scope and the team’s bandwidth. If existing salespeople cannot handle the new product, new hires may be needed.

Strategic Alliances

No company has all necessary capabilities. Strategic alliances bring in external stakeholders:

• Universities, government units, private research centres – for technical capabilities.
• Competitors – for licensing or co‑development.
• Trade channels – franchises, dealer networks (part of the extended organisation).
• Ad agencies – to create copy.
• External warehouses – for inventory storage.

Alliances are broad strategic arrangements; here the focus is on collaboration to fill capability gaps during launch.

Key takeaways (Launch Tactics)

• Launch tactics include channel selection, pricing, communication, and sales training.
• Copy strategy statement: target segment, positioning, communication mix, major copy points, product attributes.
• Sales team can be product‑based or geographic‑based.
• Strategic alliances provide access to capabilities not held internally (universities, competitors, trade channels, agencies).

---

ATAR Requirements During Launch

The ATAR model stands for Awareness, Trial, Availability, Repeat. At the launch stage, planning must ensure each element is addressed.

ATAR Element	What it means	Car launch example
Awareness	Creating buzz and knowledge about the product	Full‑page newspaper ads, TV commercials on launch day.
Trial	Giving consumers a chance to experience the product	Test‑drive cars available at major dealerships.
Availability	Enough stock to meet immediate demand	If customers have to wait six months, they switch to competitors.
Repeat	Encouraging consumers to come back and/or recommend to others	Build community forums, word‑of‑mouth campaigns, post‑purchase satisfaction programmes.

These four requirements are interdependent – for example, high awareness without trial or availability is wasted. The launch plan must coordinate them.

flowchart TD
    A[Awareness] --> B[Trial]
    B --> C[Availability]
    C --> D[Repeat]
    D -.->|Word-of-mouth| A

Exam tip: ATAR is a high‑yield framework – be ready to apply it to any product launch scenario, identifying gaps in the four elements.

Key takeaways (ATAR)

• ATAR = Awareness, Trial, Availability, Repeat.
• Launch success hinges on addressing all four simultaneously.
• Example from car launch: ads (awareness), test drives (trial), sufficient cars (availability), community/forums (repeat).
• Missing any element (e.g., awareness without availability) creates market failure.

The Core Trade-off: Early vs. Late Testing

Market testing decisions revolve around a fundamental tension: early feedback saves cost and time but has limited accuracy; late feedback (e.g., from a finished product) is more accurate and concrete but expensive to act on. The earlier you detect a flaw, the cheaper and easier it is to fix; the later you test, the richer the learning but the higher the cost of change.

Timing	Advantage	Disadvantage
Early (concept testing)	Low cost, fast iteration	Low accuracy; customer may not visualise final product
Late (actual product testing)	High accuracy; detailed refinement possible	Expensive changes; delayed feedback

Critical insight: The choice to test – and when – must be made at early planning stages and depends heavily on product type.

When to Test Depends on Product Type

• Consumer products (e.g., a new cola flavour) can be tested early via concept tests, prototypes, or samples. A simple “would you like this?” yields meaningful feedback because the product is simple and familiar.
• Big-ticket / complex products (e.g., cars, refrigerators, ACs) need a near-final product before testing. Early concept tests are meaningless – “it cools faster” is not experiential. Customers must see, touch, or experience the product to give useful responses.

Product Category	Example	Testing Timing	Reason
Simple consumer goods	Soft drink, snack	Early (concept / prototype)	Easy to visualise; low commitment
High-involvement durables	Car, AC, fridge	Late (final product)	Needs sensory evaluation; high decision involvement

Purposes of Market Tests

Market tests serve two main objectives:

1. Solid forecast – Estimate sales over e.g., 3–6 months or a year, enabling production planning, raw material procurement, and revenue projections.
2. Diagnostic information – Revise and refine product, packaging, or other marketing elements before a full-scale national or international launch.

Types of Tests Throughout Development

Each test feeds into both the product and the marketing plan:

Test Type	Stage	What Is Tested	Refines
Concept test	Early idea	Product concept, positioning	Target, positioning
Product use test	Prototype	R&D features, usability	Product features
Production-level prototype test	Near-launch	Manufacturing viability, final specs	Product finalisation
Marketing components test	Before launch	Ad copy, pricing, package size, distribution	Marketing plan (price, promo, distribution)

All these inputs converge into the final market test, whose output is a fully refined product and a detailed marketing plan ready for large-scale launch.

Factors for Deciding Whether to Market Test

Not every product needs a formal market test. Key considerations:

• Special twist at launch – If late-stage adjustments or additions were made, a market test may be needed to validate them.
• Missing information – If the marketing plan (target, positioning, price, promotion, distribution, packaging, services) still needs refinement, testing can fill gaps.
• Cost of the market test – Expensive tests may be skipped or made optional.

Example: Low-cost digital market testing

Procter & Gamble tests new products by listing them on a website with prices and enabling customer feedback, reviews, and click tracking. Simple metrics like number of clicks or follow-up inquiries gauge interest. Similarly, a car manufacturer can list features online, offer a virtual demo, and then schedule test drives only for genuinely interested leads.

flowchart LR
    A[Product ready?] --> B{Product type?}
    B -->|Simple consumer| C[Test early]
    B -->|Complex durable| D[Wait for final product]
    C --> E[Cheap feedback; iterate]
    D --> F[Late test; high accuracy]
    E & F --> G[Refine product & marketing plan]
    G --> H[National / international launch]

Key takeaways

• Early testing saves cost/time; late testing gives accuracy. The trade-off must be managed.
• Consumer goods can be tested early; big-ticket items require near-final prototypes.
• Market tests provide sales forecasts and diagnostic info for product and marketing plan refinement.
• Test types (concept, product use, production prototype, marketing components) are sequenced across development; each refines both product and plan.
• Deciding whether to test depends on launch twists, remaining information gaps, and test cost.
• Digital tools (website listings, click tracking) offer low-cost market testing alternatives.

Methods of Market Testing

Market testing exposes a new product to a limited, realistic buying situation before a full-scale launch. The goal is to gather diagnostic data — Will people buy? At what price? How will the trade react? — without committing massive resources. Three broad categories exist, ordered by increasing realism and cost: pseudo sale, controlled sale, and full sale.

1. Pseudo Sale

A pseudo sale is not a real transaction. The buyer imagines purchasing or selects a product in a make-believe store; no money changes hands and the buyer assumes no risk. It can be done very early in development.

Speculative Sale

The firm asks potential buyers directly, "If we made this product with these features at this price, would you buy it?" This method works best in B2B and consumer durables where the seller has a close, ongoing relationship with a small number of key clients.

• Example: A battery supplier developing a longer-life battery calls an automotive client (e.g., Maruti) and asks, "We can improve battery life by 20% if we charge 10% more. Will you commit?" Positive feedback justifies R&D investment.
• Use cases: Industrial firms with entrenched technical expertise, high-volume contracts, and few clients (e.g., paint supplier to a car manufacturer). Feedback is detailed, continuous, and focuses on technical requirements.
• Advantage: Very low risk; helps discover alternative use cases and refine product features before heavy investment.

Simulated Test Market (STM)

A simulated test market creates a false buying situation — often a computer simulation or a controlled game — where the firm models advertising, pricing, distribution, and competitor responses.

• Key inputs: The ATAR framework — Awareness, Trial, Availability, Repeat purchase. For example, set awareness at 50%, trial at 30%, availability at 60%, and project sales via Monte Carlo simulation.
• Advantages: Cheap, confidential, fast. Allows "what-if" scenario testing (e.g., "What happens if customer response drops 10%?").
• Disadvantages: Mathematically complex; managers often distrust the output as too idealised. Predictive power may be weak in real markets.

Exam tip: STM is especially common for packaged consumer goods where the variables (awareness, trial, repeat) can be estimated from analogous products.

2. Controlled Sale

In a controlled sale, the buyer does make a real purchase, but the sale occurs in a deliberately limited, controlled environment — not a full market release. The transaction is real, but the conditions are still part of the research stage.

Informal Selling

Train a small salesforce, give them the product and sales materials, and have them make direct sales calls — bypassing normal distribution channels (retailers, wholesalers).

• Typical venues: Trade shows, road shows, book launch events. Real cash changes hands; fulfilment may be delayed (order now, deliver later).
• Value: Immediate, unfiltered feedback from end users about product appeal, pricing, and messaging.

Direct Marketing

The manufacturer contacts consumers directly via email, telephone, TV infomercials, social media, or a company website. No retailer or wholesaler is involved. Common for consumer products testing.

Minimarkets

The product is placed in one retail chain (e.g., DMart in India, Walmart in the US) rather than across all outlets. This gives the firm tight control over display, promotion, and stocking.

• Benefit: Easier execution, clearer sales data, and the ability to fine-tune the marketing mix before broader distribution.

3. Full Sale (Test Marketing)

A test market is a full-scale launch in a representative subset of the total market — typically two to three selected cities or even a whole country. It serves as a dress rehearsal for the national (or global) launch.

• Procedure: Choose "treatment" cities where the product is sold, and comparable "control" cities where it is not. Monitor sales, distribution, and competitive reaction. The purpose is not to predict final profits, but to fine-tune the national launch — adjust advertising, pricing, promotions, and logistics.

Advantages and Disadvantages

Advantages	Disadvantages
Most abundant, actionable real-world data	Very expensive
Reveals unforeseen marketing problems	Results may not project to other geographies (local peculiarities)
Allows correction of mistakes before full launch	Competition gets a full view of the product
Tests the entire marketing mix together	Long test periods give competitors time to respond

Competition Can Spoil a Test Market

If a large incumbent (e.g., Pepsi) sees a new entrant (e.g., Reliance's Campa Cola) test-marketing in a single city, it can flood that city with coupons, price promotions, or free samples — distorting the test results. The large player suffers only a small revenue loss in that city, whereas the new entrant loses its clean data.

Exam tip: The two most important decisions in test marketing are (1) which test market(s) to pick and (2) how long to test before the full launch. A common alternative is the rollout method — a tiered, gradual launch (e.g., West India first, then North, then Central) that provides dress-rehearsal value without the full cost or competitive exposure of a single test market.

Worked Example: Pepsi Kona

• Product: A cola–coffee hybrid (cola flavour + coffee).
• Test market: Philippines (a single country used as a test market).
• Outcome: The test market revealed that consumers did not accept the mixed flavour — classic cola associations were too strong. The brand extension would likely fail globally, so the product was killed.
• Key learning: Dominant brand associations (Pepsi = classic cola) make flavour extensions risky. Better to launch such products under a new brand name (e.g., Mirinda, Fanta, 7UP) to avoid confusing consumers.
• Subsequent example: Pepsi One (a one-calorie version of regular Pepsi) succeeded by not emphasizing the diet aspect — it was positioned as a version of classic Pepsi, not a variant of Diet Pepsi.

Key Takeaways

• Market testing progresses through three stages: pseudo sale (no real money), controlled sale (real money in limited conditions), and full sale (representative dress rehearsal).
• Pseudo sale includes speculative selling (B2B, asking "will you buy?") and simulated test markets (model ATAR with Monte Carlo).
• Controlled sale methods — informal selling, direct marketing, minimarkets — give real purchase data without full distribution.
• Test marketing (full sale) provides the richest data but is expensive, slow, and vulnerable to competitive disruption.
• The rollout method is a pragmatic alternative: launch region by region, learning as you go.
• The Pepsi Kona failure shows that test marketing can prevent a costly global flop; the lesson is to protect core brand associations when extending into new flavours.

Launch Management System and Effective Innovation Metrics

Launch management treats a product launch like a NASA rocket launch or a movie release — a concentrated burst of coordinated activity. The post-launch assessment has one purpose: learn from the experience and correct mistakes. Whether the launch succeeded or failed, the knowledge feeds back into the organisation’s continuous NPD cycle.

Gap Analysis Metrics

Gap analysis metrics act as a feedback system for the product roadmap. They reveal where reality diverges from plan.

• Market window accuracy: If the product’s market window or profitability is shorter than forecast, the next product’s development must accelerate. The product portfolio is a sequence — a shortened window triggers the next development cycle.
• Senior executive support: A hardworking, knowledgeable product champion and clear senior management vision ensure good coordination and execution.
• Business case validation: Launch validates the original product charter, business model, price points, and target segments.
• Sales preparedness validation: Any execution gap in sales or distribution triggers corrective action or is absorbed as learning for the next product.
• Cross-functional alignment: Good communication across functions is essential because product development is a multi-functional system.

The Four-Step Launch Management System

flowchart LR
    A[1. Spot Potential Problems] --> B[2. Select Control Events]
    B --> C[3. Develop Contingency Plans]
    C --> D[4. Design Tracking System]
    D -->|Feedback| A

Step 1: Spot Potential Problems

Four techniques to generate a list of potential problems:

1. Situation analysis – Review the problem section of the marketing plan (which is refined at each testing stage). List risks like government regulation changes or a competitor launching a similar product first.
2. Role play competitors – Simulate competitive responses using game‑theory thinking. Example: IPL auction teams role‑play which team will bid for which player up to what price. Apply the same logic: “If I do X, what will competitor Y do?”
3. Look over all data – Review concept test results, market test data, etc., to identify patterns that signal potential failure.
4. Hierarchy of effects (reverse) – Start with a satisfied customer and ask: “What could make this customer dissatisfied?” Work backwards to identify red flags. Particularly useful with B2B partners or close collaborators.

Step 2: Select Control Events

Only a limited set of problems can (and should) be tracked and controlled. Use a risk matrix with two dimensions:

Potential Damage ↓ \ Likelihood →	Low	Moderate	High
Noticeable	Ignore or keep a watch (resource‑dependent)	Keep a watch	Alert & track
Harmful	Keep a watch	Alert & track	Control variable – develop contingency plan
Devastating	Alert & track	Control variable – develop contingency plan	Immediate action – highest priority

• Immediate action (bottom‑right cell): High likelihood + devastating damage — respond at once.
• Control variables (the two adjacent cells): Devastating + moderate likelihood, or harmful + high likelihood — must develop contingency plans and track.
• Alert & track (diagonal: high+noticeable, moderate+harmful, low+devastating): Monitor closely so they do not escalate into the red zone.
• Ignore: Low likelihood + small damage (and similar low‑priority combinations) can be deprioritised.

Step 3: Develop Contingency Plans

Once control events are identified, prepare Plan B (or C) for each. Examples from the transcript:

Problem	Contingency Plan
Negative buyer reaction (e.g., poor user manual)	Rectify the manual and ship corrected version to customers.
Shelf space at retail is too small	Negotiate more display space or add demo units.
Offline channels cannot meet demand	Open an online direct‑selling channel.
Competitor drops price by 30%	Pre‑planned pricing response or value communication.

The principle: anticipate the problem, keep the plan ready, and execute as soon as the trigger occurs.

Step 4: Design the Tracking System

Select actual tracking variables and define trigger points (e.g., at the store, at the distributor, at the factory). Monitor those variables and take corrective action when triggers are hit.

Variables that cannot be tracked should be ignored – what gets measured gets executed.

Effective Innovation Metrics

Metrics can be grouped into three categories – input, process, and performance.

Category	Examples
Input	R&D spending; number of employees devoted to innovation; number of new ideas in pipeline; number of projects in development; percentage of ideas from outside vs. inside the firm.
Process	Number of new products introduced; average time to market; number of patents filed/commercialised; budgeted vs. actual time and cost; percentage of projects that lead to a launch.
Performance	Percentage of sales from new products (e.g., in 1‑3 years); ROI on innovation; breakeven time; improvement in customer satisfaction.

Exam tip: Do not collect too many metrics – analysis paralysis kills execution. Align metrics with business goals and adjust them throughout the process. Smaller firms must brutally prioritise (e.g., track only 2–3 problems); larger firms can handle 10–12.

Ways to improve metrics design:

• Learn from best‑practice firms – observe leaders in the industry and adapt (do not copy).
• External validation – have metrics reviewed by external consultants or experts.
• Continuous fine‑tuning – metrics should evolve as the launch unfolds.

Key Takeaways

• Launch management is a continuous feedback system; its four steps are spot → select → develop → track.
• Spot problems using situation analysis, competitor role‑play, data review, and the hierarchy‑of‑effects reverse technique.
• Select control events with a likelihood‑vs‑damage matrix: focus on the three high‑priority cells (control variables + immediate action).
• Develop contingency plans only for the selected events; keep them ready for immediate execution.
• Design tracking around measurable variables and trigger points; ignore what cannot be tracked.
• Innovation metrics fall into input, process, and performance categories. Too many metrics cause paralysis; adapt them to firm size and business goals.

Product Failure and Deletion of Product

Despite exhaustive planning, contingency measures, and launch efforts, a product may fail—either because the market is not ready, the product is fundamentally flawed, or internal development cannot keep pace. The challenge is to recognise failure early and decide the best course: repair, freeze, abandon, or sell.

Responding to Market Failure

When the market situation is particularly difficult and the fix requires significant longer-time product changes, several options exist:

• Pull the product out temporarily – Stop promotions, let existing sales run down, freeze all marketing spend, and return to the drawing board.
• Freeze the product – Cease further resource investment in marketing or development while corrections are made.

Key principle: If the failure arises from basic product characteristics or lack of customer appreciation, do not sink more money into marketing. That money is wasted. Instead, correct the product first.

• Contingency actions – If the problem is positioning (e.g. training manual error, availability issues), execute the pre-planned contingency fixes. These are “control events” from the launch plan.
• Withdraw – If the problem is deeper than what contingency can address, withdraw the product entirely.

Responding to Development Failure

If the development side stalls—the team cannot move fast enough or overcome internal hurdles—abandoning the product (and the market opportunity) is often necessary.

Abandonment decision is complex and has organisation-level ripple effects (questions, morale, resource reallocation). Yet it is often better to cut losses and invest freed resources into a new product vector.

The Product Deletion Process (Four Stages)

The decision to delete (remove) a product follows a systematic, multi-stage process:

flowchart TD
    A[1. Recognition] --> B[2. Analysis & Revitalisation]
    B --> C[3. Evaluation & Decision Formulation]
    C --> D[4. Implementation]

Stage 1: Recognition
Identify that the product must be deleted by comparing actual performance against planned performance criteria. Common criteria include:

• Market share
• Growth rate
• Profit margin
• Sales revenue

If the product is “significantly missing” expectations, the problem is flagged.

Stage 2: Analysis & Revitalisation
Before deleting, ask: Can the product be restored? Options include:

• Quality / product improvement – upgrade features or fix flaws.
• Enter new markets – e.g. reduce price for mass market; shift from metro to semi-urban/tier-2; move to other countries.
  Example: Bajaj sells low-end bikes in Africa more than in India.
  Example: A product failing in a developed market may succeed in a price-sensitive emerging market.

Stage 3: Evaluation & Decision Formulation
Assess the consequences of deletion on:

• Overheads and fixed costs
• Firm’s policies (exit vs. rework)
• Capacity utilisation feasibility

Based on this, decide whether to delete and how.

Stage 4: Implementation
Execute the chosen deletion approach:

Option	Description
Immediate deletion	Remove product from market at once.
Milk/runout	Reduce price, let it sell until stock is exhausted. No new investment.
Sell the product	Sell the product line or technology to another firm. Example: startups sell their tech to larger players (Microsoft, IBM) when they cannot execute or meet financial targets.

Exam tip: The four-stage deletion process (Recognition → Analysis → Evaluation → Implementation) is a classic structured framework. Remember that selling is a valid implementation exit—it is not always a “failure” if the technology finds a home.

Key takeaways

• Product failure can be market-driven or development-driven.
• For market failure: pull temporarily, freeze, or withdraw if the fix is long-term.
• For development failure: abandon early to redeploy resources.
• The product deletion process has four stages: recognition (compare to plan), analysis (revitalise or pivot markets), evaluation (assess overheads/policies), implementation (delete, milk, or sell).
• Selling the product is a legitimate exit strategy—common among tech startups.

Public Policy Issues in New Product Development

New products do not exist in a vacuum; they face growing scrutiny over environmental impact, health, and safety. Public policy issues—climate change, pollution, food labelling, emissions—are now a central concern for product managers. Ignoring them can destroy both a product and a company’s reputation. The key is to understand how an issue evolves from a whisper to a regulatory hammer.

The Life Cycle of Public Concern

A public policy issue typically moves through four phases. At each stage, a company can either act to defuse the situation or watch it escalate. The cycle is rarely a surprise—early signals are almost always present.

flowchart TD
    A[State of Idleness] --> B[Stirring]
    B --> C[Trial Support]
    C -- "escalates" --> D[Political Arena]
    D -- "escalates" --> E[Regulatory Adjustment]
    C -- "dies down or company diffuses" --> A
    B -- "company diffuses" --> A
    D -- "company diffuses or dies down" --> A
    E -- "law refined, cycle continues" --> A

Phase 1: Stirring

• What happens: A few individuals, activists, or NGOs flag a concern (e.g., high sugar in baby food, emissions from cars). These are tentative expressions—letters to CEOs, complaints on social media, newspaper articles, or local political contacts.
• Typical company response: Mostly ignored. Managers cite trade-offs: reacting to every signal would halt all products. The phase can last years or decades.
• Key insight: In hindsight, every major product crisis had clear early warnings. The challenge for product managers is signal detection—monitoring complaints and regulatory trends without overreacting.

Phase 2: Trial Support

• What happens: An influential champion (political leader, celebrity, NGO head) picks up the cause. The issue gains visibility and traction. The champion may be genuinely concerned or seeking publicity.
• Outcome – two paths:
  • Escalation → moves to Phase 3 if the issue is dramatic enough to create headlines and broad social impact.
  • De-escalation → the company acts (e.g., reformulates, recalls) and the issue fades, or it simply dies from lack of broader support.
• Critical window: Phase 2 is the best time for a company to diffuse the situation before it becomes political.

Phase 3: Political Arena

• What happens: The issue enters formal politics or legal systems — debates, legislation, court cases. Example: parents in the US sued McDonald’s for contributing to childhood obesity; the court ruled in the parents’ favour.
• Company options:
  • Settle / negotiate.
  • Fight legally (e.g., the US cereal industry won many such cases).
• Consequence: Once this phase is reached, the company faces a political or legal battle it would rather avoid. Diffusing is now very difficult.

Phase 4: Regulatory Adjustment

• What happens: New laws or regulations are passed (e.g., emission norms, advertising bans on baby food). However, initial legislation is often imprecise, leading to a period of jockeying:
  • Companies interpret loopholes.
  • Regulators refine and tighten rules.
  • The cycle may restart as new issues emerge.
• Example: Nestlé’s baby food in India faced regulations on sugar levels and a ban on advertising that implied formula was superior to breastfeeding.

Key Implications for Product Managers

Phase	Company action (ideal)	Consequence of inaction
Stirring	Monitor signals; log complaints	Crisis appears “out of nowhere”
Trial Support	Respond quickly – reformulate, recall, or communicate	Issue enters political arena
Political Arena	Legal / PR battle – costly and unpredictable	Regulatory backlash
Regulatory Adjustment	Adapt to new rules; anticipate further tightening	Brand damage, market exit

Exam tip: The most testable concept is the four-phase life cycle and the idea that early intervention (Phase 2 or even Phase 1) is far less damaging than fighting in the political or regulatory arena. Memorise the sequence and the two de-escalation paths (die down on its own vs. company diffuses).

Worked Example: Maggi Noodles in India (2015–16)

1. Stirring (years before): Concerns about MSG content and lead levels were raised by some activists and food safety officials.
2. Trial Support: Coverage in media amplified; regulators took notice.
3. Political Arena: Public outcry, bans by state food authorities, legal cases.
4. Regulatory Adjustment: Nestlé withdrew the product entirely, reformulated, and relaunched after clearing new tests. The episode severely damaged Nestlé’s brand equity and stock price.

Why This Matters for New Product Development

• Design proactively: Incorporate sustainable materials, low energy consumption, health-friendly ingredients, and transparent labelling. Don’t wait for a crisis.
• Monitor weak signals: Customer complaints, activist blogs, regulatory trends. A dedicated cross-functional team can triage issues.
• Understand trade-offs: Not every signal demands action. Develop a framework to assess potential impact (dramatic? widespread?) and respond appropriately.
• Public policy risk is now standard: Future products will face even greater scrutiny. The winning strategy is to be ahead, not reactive.

Key takeaways

• Public policy issues evolve through four stages: Stirring → Trial Support → Political Arena → Regulatory Adjustment.
• In each stage, a company can diffuse the issue; the best window is Phase 2 (trial support).
• Almost every crisis was signalled earlier; ignoring those signals is a common failure.
• Proactive product design (sustainable, healthy, transparent) turns policy risk into competitive advantage.

Product Liability

Product liability holds manufacturers, service providers, and sellers legally responsible for harm caused by defective products. Intuitively: if a product hurts a user because of a flaw, the company pays. In India the Consumer Protection Act (CPA) and stricter laws in developed markets give consumers the right to claim compensation for personal injury, property damage, or death caused by manufacturing defects, design flaws, poor quality, or inadequate warnings. Injury can occur at any stage — buying, opening, or using the product. Product liability applies primarily to goods (physical products), not services, because physical harm is less likely in services.

Companies typically try to settle such suits out of court to avoid negative publicity. One proactive measure is to give adequate warnings on products (e.g., "Do not use this razor on dry skin," "Not for use as a flotation device").

Definition
Product liability = legal duty of manufacturers/sellers to compensate consumers for harm from defective products — even if no negligence is proved under strict liability.

---

Legal Bases for Product Liability

Four legal bases have evolved over time, each progressively broader:

Basis	Description	Key Feature	Example from lecture
Negligence	Error (act of commission or omission) by the company	Easy to establish – must show carelessness	Wheel comes off because not secured; paint with health hazard
Warranty	Promise by seller about product features or safety (20th century)	Breach of warranty is enough – no need to prove negligence. Two types: Express warranty (explicitly stated) and Implied warranty (inherent, understood)	Seller claims "100% safe" but product causes injury
Strict liability	Seller is responsible for not putting a defective product on the market	No negligence or warranty needed. Manufacturer can be sued by any injured party, even if no sale occurred (e.g., standing in store when battery explodes)	Mobile battery catches fire and injures a bystander
Misrepresentation	Product is not defective but is presented deceptively	Customer cannot verify safety; product may meet only cosmetic standards	Helmet box shows motorcyclist using it, but helmet fails safety standards

Strict liability imposes the heaviest burden on companies. Defenses include:

• Assumption of risk
• Unforeseeable misuse
• Natural acts (earthquake)
• Product is not defective but still causes injury (rarely successful)

Exam tip: The four bases form a ladder of legal exposure. Misrepresentation is the least intuitive – the product itself may be fine, but how it is marketed creates liability.

Key takeaways – Legal bases

• Negligence: company made an error → easy to prove.
• Warranty: promise broken → no need for negligence; express vs. implied.
• Strict liability: any defective product on market → liable even without sale or fault.
• Misrepresentation: product not defective, but deceptive presentation creates liability.
• Companies prefer settling out of court to avoid media escalation.

---

Product Recall

When a defect is anticipated or discovered, product recall is a proactive remedy. Instead of waiting for injuries or lawsuits, the company voluntarily removes the product from the market.

Steps in a recall (from the lecture):

1. Designate a recall program coordinator – a single, authorized person to manage communication and media.
2. Establish effective communication channels – inform consumers, intermediaries, and regulators of the risk and corrective action.
3. Assess safety risk and implement corrective actions (e.g., fix, replace, refund).
4. Monitor recall effectiveness – track what percentage of products are returned (e.g., 80%, 90%).
5. Restore company reputation – communicate transparency and future improvements.

flowchart LR
  A[Defect identified or anticipated] --> B[Recall decision]
  B --> C[Designate coordinator & set up communications]
  C --> D[Assess risk & take corrective action]
  D --> E[Monitor recall effectiveness]
  E --> F[Restore reputation]

Examples from transcript:

• Maggi noodles (India) – Nestlé destroyed all existing stock, invested in R&D, launched a new safe line.
• Toys with lead – recalled entire batch; replaced with new products.
• Medical devices (e.g., blood sugar monitor) – even one defect triggers recall of entire product line to prevent widespread harm.
• P&G pet food recall (2007) – after recall, P&G placed full-page newspaper ads to assure pet owners other products were safe.
• Johnson & Johnson Tylenol – after tampering incidents, company launched tamper-proof bottles and communicated the fix.

Exam tip: Recall is a proactive strategy to contain liability. The key is speed and transparency – the company communicates the risk before others (media, regulators) escalate it.

Key takeaways – Product recall

• Done to avoid multiple injuries and court escalation.
• Requires a single coordinator, clear communication, and risk assessment.
• After recall: monitor return rate and actively restore reputation.
• Even a single defective unit often leads to recalling the entire product line.
• Real-world examples: Maggi, P&G pet food, J&J Tylenol.

Environmental Concern

Environmental concern arises when a new product poses negative impacts on the environment. Product managers must identify these concerns early, as public debate and regulation increasingly penalize products that are not “green enough”.

Four Environmental Red Flags

A product can be criticized on environmental grounds at any stage of its lifecycle.

Stage	Red flag	Example
Raw materials	Scarcity or depletion of rare materials	Rare earth metals in electronics
Design / manufacture	Pollution, excessive energy or water use	Toxic by‑products from chemical processes
Use	Pollution or resource consumption during operation	High‑emission vehicles
Disposal	Non‑recyclable or hazardous waste	Single‑use plastics

Exam tip: These four stages are a checklist for evaluating a product’s environmental footprint. Any one can trigger a recall or reputational damage.

Sustainable Design

Sustainable design means creating a product or delivery system that reduces negative environmental impacts – or actively restores the environment. It is no longer optional; firms must embed sustainability at the system level.

The Manager’s Dilemma

Product managers are under constant pressure to deliver profit. Sustainable choices often increase costs (new materials, cleaner processes, recycling infrastructure). This tension – doing the right thing vs. protecting margins – often prevents action unless the firm prioritises long‑term value.

Five Actionable Strategies for Sustainable Design

1. Innovate at the system level – redesign the whole product philosophy, not just one component.
2. Use new materials – replace polluting materials (e.g., plastic) with cleaner alternatives.
3. Develop new technologies – invest in solutions like LED bulbs (less power) or reusable / renewable energy products.
4. Create new business models – e.g., car sharing instead of individual ownership, reducing total carbon footprint.
5. Restore the environment – proactively offset impacts through conservation or regeneration.

Key takeaways

• Four environmental red flags: raw materials, manufacture, use, disposal.
• Sustainable design is system‑level and non‑negotiable.
• Profit vs. sustainability is the core managerial tension.
• Five strategies: system innovation, new materials, new tech, new business models, restoration.

---

Personal Ethics

Beyond environmental concerns, product innovators face ethical dilemmas – situations where the “right” action conflicts with business goals, social norms, or individual conscience.

Ethical Dilemmas in the NPD Process

Stage / Situation	Ethical issue	Example
Ideation / concept generation	Covert observation of users without consent	Monitoring children’s behaviour without disclosure
Product launch (temporary product)	Hiding that the current product will soon be replaced	Management forbids sales team from informing customers
Safety testing	Lethal Dose 50 (LD50) test – feeding a substance until 50% of test animals die	Animal testing for chemical products
Marketing	Promoting a drug for uses not approved by regulators	Off‑label marketing by pharmaceutical sales reps

Underlying Issues in Ethical Decision‑Making

• Reasonable goals – eliminating all ethical risks is impossible; define what is achievable (like zero‑defect quality, but for ethics).
• Trade‑offs – when the organisation lacks clear guiding principles, managers must decide where to draw the line.
• Cost burden – cost pressure can tempt corners to be cut; determine where the cost of ethical compliance falls.

What Product Managers Can Do

1. Identify ethical issues at strategy and policy level – set clear standards (“no‑go” zones).
2. Establish control systems – ensure teams follow ethical guidelines during testing, marketing, and launch.
3. Educate customers – raise awareness about ethical and environmental concerns (e.g., clear food labelling for trans‑fat or sugar).

Case Example: Hybrid / Hydrogen Vehicles (General Motors)

In the early 2000s, automakers explored alternative‑fuel vehicles. Toyota’s Prius (launched 2002) sold ~40,000 hybrids; Honda’s Insight suffered negative perception. General Motors found, through market surveys, that consumers were only willing to pay ~$1,000 premium over a conventional combustion engine. The price gap had to be small for take‑off. This illustrates the real‑world conflict between environmental goals and consumer willingness to pay.

Exam tip: The $1,000 premium figure is a concrete example of the “profit vs. sustainability” dilemma. If the incremental cost of green technology exceeds what customers will pay, the product fails – unless subsidies or regulations change the equation.

Key takeaways

• Ethical dilemmas occur at every NPD stage: ideation, launch, testing, marketing.
• Key problems: lack of consent, hidden information, animal testing, off‑label marketing.
• Managers must set reasonable goals, clarify trade‑offs, and control costs ethically.
• Consumer willingness to pay for sustainability is often low (e.g., ~$1,000 for a hybrid).

Introduction to the Module: Prototypes as a Feedback Loop in Product Testing

A prototype is the first usable output of technical development — a tangible version that can be tested and exposed to users. Its purpose is not to be final, but to serve as a feedback loop that informs the next iteration of development.

The role of the prototype

• Bridges development and testing: the prototype transforms abstract design into something testable.
• Enables user exposure: real users interact with the prototype, revealing usability issues, unmet needs, or technical flaws.
• Closes the loop: results from testing feed directly back into the development process, refining the product before the next prototype or release.

flowchart LR
    A[Technical<br>Development] -->|creates| B[Prototype]
    B -->|tested| C[User Testing]
    C -->|produces| D{Feedback}
    D -->|iterates| A

Key takeaways

• A prototype is the first usable version — not a finished product.
• Its primary function is to enable testing and gather feedback.
• The feedback from testing directly informs further development (closed-loop process).
• Prototypes are an essential tool for user-centred product development.

Product Use Testing

Product use testing (also called field testing, user testing, or market acceptance testing) is the process of exposing a prototype to real users to gather feedback and refine the product iteratively. The prototype serves as a feedback loop – the team learns, adjusts, and retests until stakeholders are satisfied and specifications are met. Marketing is involved from the start, feeding insights back into development.

Why Product Use Testing Is Necessary

Customer needs are complex and cannot be fully captured through simulation or computer modelling. Only real-world use reveals:

• Diverse, unanticipated needs – users may value features designers never considered.
• Competitive reaction – how competitors respond to the product can shape its success.
• Quality assurance – the product may meet internal standards but still fail customer expectations.
• Pre-use sensory reactions – immediate responses to colour, speed, durability, ergonomics, handle, look, and feel. These are impossible to replicate in a lab.

flowchart LR
    A[Prototype] --> B[User Testing]
    B --> C[Feedback]
    C --> D[Refinement]
    D --> A
    D --> E[Approved Product]

Exam tip: Product use testing is not optional – it captures the gap between what designers think and what users actually want.

Key takeaways

• Prototype testing is iterative; each loop reduces risk.
• Customer needs are too complex for simulations alone.
• Testing reveals sensory, ergonomic, and competitive insights.
• Early feedback prevents expensive late-stage failures.

---

Alpha and Beta Testing

Two common stages of product use testing, primarily from software and hardware industries.

Alpha Testing

Alpha testing is the first stage of user testing, conducted internally (employees, colleagues, friends). It checks whether the basic product works, is easy to use, has obvious bugs, and matches initial specifications. Typically performed when only about 30% of functionality is ready – a very early, crude version.

Beta Testing

Beta testing is performed at selected external customer sites with a nearly complete product (≈ 90% of functionality). It validates the product in real-world conditions, checking for remaining bugs, usability, and market fit. Beta testing is short-term and occurs just before full commercial launch.

Feature	Alpha Testing	Beta Testing
Who tests	Internal employees	Selected external customers
Product maturity	~30% functionality	~90% functionality
Purpose	Early bug detection, basic function check	Real-world validation, usability, market fit
Location	In-house	Customer’s own environment
Risk	Low (no external exposure)	Moderate (reveals product to outsiders)

Case Study: Microsoft Internet Explorer vs. Netscape Navigator

During the late-1990s browser war, Microsoft released Internet Explorer in rapid cycles:

1. First alpha – tested with hundreds of employees; early feedback.
2. Second alpha – two weeks later, refined.
3. Third version – instead of another alpha, released as a public beta.
4. Multiple beta releases over the next six months – lead users and experts tested operations, usability, and functionality.

This allowed Microsoft to iterate fast while under competitive pressure.

Exception: Quaker Cereals

Quaker eliminated extensive customer testing to reduce cost. Executives tested new cereal flavours only through alpha testing (employees). They bypassed beta testing entirely and launched straight to market. This reduced development cost but risked missing customer preferences.

Pitfalls of Inadequate Beta Testing

Time pressure often compresses beta testing. When development runs late (e.g., final launch planned in May), the beta window shrinks. Teams rush feedback collection, leaving no time to fix discovered issues. Inadequate product use testing leads to:

• Lower customer satisfaction
• Higher defect rates in the field
• Long-term costs far outweighing short-term time/cost savings

Exam tip: Beta testing is most valuable when done thoroughly with sufficient time. Compressing it defeats its purpose.

Key takeaways

• Alpha = internal, early, ~30% done.
• Beta = external, near-complete, ~90% done.
• Real-world examples (Microsoft IE) show iterative beta releases help under competitive pressure.
• Skipping beta (Quaker) saves time but increases market risk.
• Time pressure is the biggest enemy of effective beta testing.

---

Gamma Testing

Gamma testing is the next stage after beta, where the fully completed product is evaluated by end users with no time or development constraints. The product is released to a small group of users who use it extensively (often for free) and provide detailed feedback on all aspects – functionality, reliability, cost-effectiveness, and problem-solving.

Characteristics of Gamma Testing

• Product is 100% complete – no further development is planned during testing.
• Users have ample time to test and provide detailed feedback.
• Feedback can still lead to minor adjustments (but major changes are extremely costly).
• Common in high-stakes industries where half-baked testing is impossible (e.g., pharmaceuticals, medical devices, automobiles).

Examples of Gamma Testing

Industry	Example	Description
Pharmaceuticals	New medicines	Fully developed drug undergoes clinical trials (sometimes 10+ years). Half-baked testing would be unethical and unsafe.
Medical equipment	CT scanners	Sent to test laboratories or hospitals for extensive multi-scenario evaluation before commercial release.
Automotive	New car models	Car magazines, enthusiasts, and reviewers receive early production cars for weeks of real-world driving (different conditions, roads, climates). Feedback sometimes leads to minor adjustments and serves as marketing.
Consumer electronics	Apple PowerBook notebook	Launched with faulty hinges discovered only after full market release – illustrates the cost of not doing adequate gamma testing.

Gamma testing is not feasible for all products due to high cost and time. However, for industries where failure is catastrophic or user requirements are extraordinarily complex, it is essential.

Exam tip: Gamma testing is ideal but expensive. Know which industries require it (pharma, medical, auto) and which can settle for alpha/beta (fast-moving consumer goods, low-risk software).

Key takeaways

• Gamma = fully complete product, no development time pressure, users test thoroughly.
• Catches issues missed in beta (e.g., Apple PowerBook hinge).
• Essential for high-risk, high-complexity products.
• Major cost and risk: if a gamma test kills the product, all R&D investment is lost.
• Decision to use gamma depends on industry, cost, and consequence of failure.

Decisions in Product Use Testing

Product use testing involves multiple decision points that shape how feedback is collected and interpreted. Each choice affects the validity, bias, and usefulness of results.

1. Who Should Be in the User Group?

User Type	Description	Typical Phase
Lab personnel	Internal developers, R&D staff.	Alpha testing
Experts	Industry specialists (e.g., auto engineers).	Pre-release validation
Employees	Non‑lab staff inside the firm.	Internal pilot
End users	Ultimate customers – the most realistic feedback.	Beta / field testing

Example: Graham Bell’s first phone call was to his assistant – a classic lab‑user test.

• Intuition: Choose users whose perspective matches the question. Lab catches technical flaws; end users catch real‑world usability.

2. How Should We Reach the User Group?

• Mail / personal contact – direct one‑on‑one.
• Contact within a group – e.g., a corporate panel, club, or online community.

3. Which Location for Testing?

Location Type	Description	Best For
Point of use	Product used in its actual environment (home, office, factory).	Realistic conditions, context‑sensitive feedback.
Central location	Controlled site (test kitchen, shopping mall, theatre).	Quick comparisons, standardised setup.

• Intuition: Point‑of‑use captures genuine behaviour; central location offers speed and consistency.

4. Should We Disclose the Brand? (Blind vs. Open)

• Revealed brand → brand halo effect distorts feedback – users respond to the brand name rather than the product itself.
• Blind testing → removes bias; feedback focuses purely on product attributes (e.g., taste, performance).

Exam tip: Blind testing is essential for competitive comparisons – if you want to know whether your drink tastes better than the market leader, hide the labels.

5. How Much Explanation Should We Provide?

• Too little → users don't understand the task or objective.
• Too much → information overload, biased expectations.
• Goal: Clear, concise instructions that set the context without leading the user.

6. How Should the Test Be Conducted? (Test Designs)

Four common designs, each serving a different purpose:

flowchart LR
    A[Test Design] --> B[Monadic]
    A --> C[Sequential Monadic]
    A --> D[Paired Comparison]
    A --> E[Triangular Comparison]

Design	Procedure	When to Use
Monadic	Single respondent uses one product for a period.	Simple acceptance test; services (cannot easily compare in parallel).
Sequential Monadic	Same respondent uses multiple versions back‑to‑back.	Measuring incremental improvements; “staggered paired comparison.”
Paired Comparison	Respondent uses test product + one competitor and states preference.	Direct A‑vs‑B comparison (e.g., your toothbrush vs. market leader).
Triangular Comparison	Respondent uses test product + two competitors and ranks/rates.	Positioning map; more detailed relative standing.

Example – Toothbrush test:

• Monadic: “Try this new toothbrush for a week. Do you like it?”
• Paired: “Use ours and the leading brand. Which do you prefer?”
• Triangular: “Use ours and two other brands. Rate comfort, cleaning, grip on a scale.”

7. Over What Time Period?

• Duration depends on the product’s usage cycle (minutes for a snack, months for durable goods).
• Must be long enough to gather meaningful feedback but short enough to avoid drop‑out.

8. What Should Be the Form of the Product Tested?

• Single best version – one product, no variation.
• Multiple variants – e.g., different colours, sizes, speeds; same user tests all to compare.

9. How Do We Record the Respondent’s Reaction?

Method	Description
Scale ratings	e.g., 5‑point Likert: “I definitely would use it” to “I would never use it.”
Descriptive diagnosis	Open‑ended comments on likes/dislikes, specific features.

• Intuition: Scales give quick quantifiable data; descriptions give rich context. Use both when possible.

10. How Do We Interpret the Results?

Absolute numbers are meaningless without a benchmark.
Example: 65% of users “like” the product. Is that good?

• If category winner scores 70% → 65% is disappointing.
• If past average is 50% → 65% is excellent.

Sources of benchmarks (norms):

• Internal records from previous tests.
• Market research agencies’ databases.

Exam tip: Never pull a target out of thin air (e.g., “We want 75% satisfaction”). Without a credible benchmark, the number is worthless. Interpret by comparing to a relevant norm.

Key takeaways

• User group choice (lab / experts / employees / end users) depends on test phase and realism needed.
• Blind testing eliminates brand halo; essential for unbiased product comparison.
• Four main test designs: Monadic (single), Sequential Monadic (back‑to‑back), Paired (A vs. B), Triangular (A vs. B vs. C).
• Interpret results only against known benchmarks – absolute scores are misleading.
• Clear instructions, appropriate duration, and consistent recording methods drive valid feedback.

Building Markets for New Products

Not all new products slot into existing demand. Some are genuinely novel — inventions that must create their own market. When a product offers great value yet buyers stay away, the root cause is rarely the product itself; it is a mismatch between the product and the market’s readiness. This section covers how to diagnose that mismatch and fix it through deep qualitative analysis.

Why buyers avoid a new product

Before you can build a market, identify why the product is being ignored. The superficial reasons may mislead; the core underlying problems matter.

• Product design flaws – e.g., bulky, hard to use, unclear instructions.
• Hidden substitutes – customers already satisfy the need with an alternative (e.g., a two‑wheeler instead of a car).
• Cultural mismatches – the product conflicts with user norms or values.
• Usage‑related issues – the product is too cumbersome; instructions are unclear.
• Missing supporting products/services – no dealerships, no spare parts, no trained service staff (e.g., launching an EV where there are no mechanics who can service it).
• Inability to articulate benefit – the customer does not see how the product solves a problem better than the current alternative.

How to fix each reason

Reason	Fix
Product is bulky or hard to use	Redesign for ease; provide clear instructions; make it user‑friendly
Hidden substitutes	Research what customers currently use; find the gap in the substitute
Cultural mismatch	Adapt product positioning or features to align with local values
Missing supporting services	Invest in infrastructure: training, dealers, spare‑part networks
Unclear benefits	Quantify and communicate the value (e.g., cost savings, efficiency gains)

Key questions to answer with qualitative research

Building a market requires answering a structured set of questions through in‑depth interaction with potential customers (not just surveys). There are no shortcuts.

• Who are your target customers? Equally important: who is not your target customer (e.g., a luxury product excludes price‑sensitive users). Understand why.
• What unmet needs do they have? And how are they meeting those needs today (the hidden substitute)?
• What is the gap in the current way of meeting the need? How does your product close that gap?
• How will customers benefit? Can you quantify the benefit (cost saved, time saved, efficiency gained) and communicate it easily?
• Who will pay? What is the size of the addressable market? How large is it?
• Who are the most direct competitors? How does your product compare?
• Can users be involved in creating a better product (co‑creation, user testing, customization)? Getting buy‑in early builds adoption.
• Does your product offer compelling value over competitors?
• Can it generate sustained high profits? A great product must also be a viable business.

Exam tip: The qualitative questions listed above are a diagnostic framework – treat them as a checklist. If a question is skipped, a hidden reason for non‑adoption may remain undetected.

flowchart TD
    A[Product has no buyers] --> B[Conduct qualitative research]
    B --> C{Identify core reasons}
    C --> D[Design / usability issues]
    C --> E[Hidden substitutes]
    C --> F[Cultural / supporting/ service gaps]
    D --> G[Fix product or instructions]
    E --> H[Articulate superior benefit]
    F --> I[Build complementary services]
    G & H & I --> J[Retest with target customers]
    J --> K{Buyers adopt?}
    K -->|No| B
    K -->|Yes| L[Market built]

Key takeaways

• When demand does not exist naturally, you must create it by fixing the underlying reasons for non‑adoption.
• Fixing requires qualitative analysis — superficial reasons mislead; dig to root causes.
• Common barriers: product flaws, hidden substitutes, cultural mismatches, missing supporting services, unclear benefits.
• Answer a structured set of questions (target customers, unmet needs, substitutes, benefits, competition) to guide market‑building efforts.
• Involving users through co‑creation or testing increases buy‑in and reveals unspoken issues.

Creating Demand for Existing Products

Existing products can gain new demand by addressing shortcomings or enhancing utility. The process often draws insights from product use testing.

Method	Description	Example
Add new utility/features	Introduce functions previously absent	Laptop: touchscreen, quick browsing, battery-life upgrade
Enhance utility efficiency	Make the product work better or faster	Faster processing, lower power consumption
Add safety features	Reduce risk during use	Inbuilt antivirus; more airbags in a car
Improve aesthetics	Improve look and feel	Better design, colours, finish
Improve ergonomics	Make structure more comfortable and easier to use	Better grip, lighter weight

Key takeaways

• Five levers: utility, efficiency, safety, aesthetics, ergonomics.
• All can be identified through product use testing.
• Aim is to fix shortcomings or add value to existing product lines.

Creating Product Differentiation

Differentiation expands demand by making a product distinct in the market. Two broad types:

flowchart LR
    A[Product Differentiation] --> B[Horizontal]
    A --> C[Vertical]
    B --> D["Same segment, different tastes"]
    C --> E["Different segments, willingness to pay"]

Horizontal Differentiation

• Target: Customers within the same segment who have different tastes or needs.
• Goal: Expand the customer base by offering more options (features, colours, variants) that appeal to diverse preferences within the same price tier.
• Example: Maruti offering manual vs automatic transmission, multiple colours, or SUV-style vs sedan-style body on the same platform – all in the same ~₹10–15 lakh budget.

Vertical Differentiation

• Target: Customers in different segments with different willingness to pay.
• Goal: Add higher‑quality features or more sophisticated design to appeal to a higher‑priced segment above the current base.
• Example: Moving from a ₹10–15 lakh car to a ₹30–40 lakh luxury variant with refined engine, premium materials, enhanced safety.
• Analogy: In a saree shop, the first question is "What is your range?" (vertical). Then, within that range the shopkeeper shows colours and designs (horizontal).

Exam tip: Horizontal differentiation expands within a price tier; vertical differentiation moves to a higher tier. Confusing the two is a common mistake in case‑based questions.

Key takeaways

• Horizontal: same segment, more choices → wider appeal.
• Vertical: move up in price/quality → capture higher‑willingness‑to‑pay customers.
• The two can coexist: first select a price range (vertical), then offer variants (horizontal).

Creating Demand Without Latent Needs

When there is no explicit or latent need, traditional market research is unreliable. Demand must be created through a carefully managed process.

1. Do not trust market research – without an existing need, surveys are inaccurate. Use only directional accuracy (broad yes/no) to guide decisions.
2. Derisk possible failure – limit initial budget, keep advertising low; acknowledge the product may fail.
3. Educate channel partners and retail executives about the new product’s value – they may not have a natural reason to stock it.
4. Use your own retail channel or create unique channels if existing partners resist.
5. Do not antagonize customers – do not imply their current behaviour is wrong. Instead, advocate the benefits of the new solution.
6. Use unique promotion schemes – consumer trials, free samples, word‑of‑mouth rather than direct advertising.
7. Experiment and demonstrate that the product works – correct wrong perceptions via cost comparisons, total cost of ownership, or demos.
8. Respond with agility to complaints – especially during trials; quick rectification builds trust.
9. Maintain clear internal communication about what constitutes success/failure and how long to persist. Negative results should be interpreted consistently.
10. Wait for the tipping point – the moment when the market is ready. Only then spend heavily on advertising and official campaigns. The product may be ahead of its time.

Exam tip: The “tipping point” is a key concept – spending too early on promotion wastes resources; waiting signals market readiness.

Key takeaways

• Without latent needs, market research is unreliable – use directional accuracy.
• Derisk through low‑budget launches, trials, and channel education.
• Do not antagonise customers; demonstrate value instead.
• Respond quickly to complaints and persist through multiple trial rounds.
• Scale advertising only after the market reaches its tipping point.

Creating Demand Without Latent Needs: Examples

When no explicit latent need exists, companies can still create demand by communicating a superior value proposition and enabling trial. The strategy works by reframing what the customer should value — convenience, consistency, hygiene, year‑round availability — over what they currently value (e.g., “fresh from the vendor”).

Safal Frozen Fruits & Vegetables (Mother Dairy)

• Core challenge: Consumers resisted frozen produce, believing it to be stale or inferior to fresh market vegetables.
• Advantages communicated over fresh vendors:
  • Price stability — frozen peas cost ₹200/kg year‑round, unlike seasonal price fluctuations.
  • Year‑round availability — e.g., peas only in season; frozen available always.
  • Superior ripeness — peas are picked fully ripe and sweet, then flash‑frozen at −18°C. Fresh market peas are harvested semi‑raw to survive transport.
  • Exact weight — packaged product eliminates vendor weight manipulation.
• Tactics:
  • Different packet sizes for convenience (including small packs of mixed vegetables).
  • Direct sourcing from farmers and wholesale markets.
  • Initially relied on word‑of‑mouth; later expanded into physical franchise stores selling fresh produce, leveraging the brand’s freshness image.

Real Good Chicken (Chilled Chicken)

• Core challenge: Consumers preferred “fresh” chicken from local vendors.
• Advantages communicated:
  • Chilling preserves taste — processing and cleaning are more hygienic and controlled.
  • Birds are harvested at the optimal age/size, ensuring consistent quality.
• Evidence used: Blind‑tasting tests and sponsored research showing no drop in nutritional value after freezing/chilling.
• Tactics:
  • Free eggs given as trial to drive adoption.
  • Built own retail chain (franchise model) because regular vendors would not store chilled products.

Tropicana Canned Juice

• Core challenge: Juices from street vendors were seen as “fresh” and “tasty”. Packaged juice had to overcome scepticism.
• Advantages communicated:
  • Hygiene — packaged product avoids unhygienic street‑vendor processes.
  • Taste — claimed to be better than fresh‑squeezed vendor juice.
• Tactics:
  • Cold‑section placement: Retailers were persuaded to store Tetra Packs in the cold section (even though shelf life is months) to signal freshness.
  • Trial with morning joggers — positioned juice as a healthy post‑exercise drink, building habit and association with health.
• Channels: Convinced existing retailers to cooperate; did not need own retail chain.

Exam tip: These examples illustrate the same pattern — identify a pain point in the incumbent (fresh market) that consumers tolerate or ignore, then use communication (cold storage, trial, branding) and channel creation (own stores or retailer persuasion) to make the new product’s advantage tangible.

---

Key takeaways – Creating demand without latent needs

• Demand can be built when no explicit need exists by reframing value (convenience, hygiene, consistency).
• Common levers: price stability, year‑round availability, quality control, and exact quantity.
• Communication is critical — match the packaging and placement to the value message (cold section = fresh).
• Trial is essential for adoption (free samples, morning‑jogger distribution).
• Companies may need to build their own retail channels if existing outlets (vendors) are not aligned.

---

Choosing Between Product Options

When developing new products or business models, four generic options exist based on two dimensions: resources (existing vs. new) and target users (existing vs. new).

Resource base	Existing users	New users
Existing resources	Option 1: Low cost, low risk. Leverage what you have to create new value for current customers.	Option 3: Low cost, high risk. Use existing resources to serve a new user segment.
New resources	Option 2: High cost, low risk. Add new resources/features for your existing customer base.	Option 4: High cost, high risk. Build new resources for entirely new users – the last option to try.

Decision logic

flowchart LR
  A[Start] --> B{Can existing resources\nserve the opportunity?}
  B -- Yes --> C{Are existing users\nthe target?}
  C -- Yes --> D[Option 1: Existing/existing\nLow cost, low risk]
  C -- No --> E[Option 3: Existing/new users\nLow cost, high risk]
  B -- No --> F{Are existing users\nthe target?}
  F -- Yes --> G[Option 2: New resources/existing users\nHigh cost, low risk]
  F -- No --> H[Option 4: New resources/new users\nHigh cost, high risk\n– exhaust others first]

Additional rule

• Avoid cannibalization – do not create a new product that conflicts with a product already selling well.
• Option 4 should be pursued only after experimenting with Options 1–3.

Exam tip: In case‑based questions, always map the company’s situation onto this matrix. The most common mistake is jumping to Option 4 without considering low‑risk alternatives. Look for clues about whether the company already has the resources and whether the user base is familiar.

---

Key takeaways – Choosing between product options

• The 2×2 matrix uses two axes: resources (existing vs. new) and users (existing vs. new).
• Option 1 (existing/existing) is lowest cost and risk; Option 4 (new/new) is highest.
• Option 2 is high cost but low risk; Option 3 is low cost but higher risk.
• Always protect existing profitable products from internal competition.
• Option 4 is a last resort, not a starting point.

Intellectual Property

Intellectual property (IP) protection prevents competitors from easily imitating an innovation. Without it, the competitive advantage built by a new product can erode quickly. IP rights create legal barriers – a “fence” around the idea – that competitors must either license or circumvent.

Types of Intellectual Property

Type	What it protects	Key characteristics	Example
Utility patent	A useful, novel, non‑obvious idea (including software)	Temporary monopoly granted by government; requires full disclosure	A new algorithm or chemical compound
Design patent (design recognition)	The ornamental design of an item – result of high skill and effort	Need not be novel; protects the look, not function	A unique smartphone shape
Copyright	Tangible expression (written work, art, music)	Exclusive right granted automatically upon creation; no registration required; burden of proof on alleged infringer	A book, poem, or piece of software code
Trademark	Name, symbol, or logo that identifies a brand	Exclusive right granted by government; cannot be easily revoked	Company logo, brand name
Trade secret	Proprietary knowledge kept confidential	No government registration; protection relies on secrecy	Coca‑Cola formula

Exam tip: Trade secrets are not patents – they have no expiry but are lost if the secret is revealed or reverse‑engineered.

Rights of a Patent Holder

A patent grants the holder the right to exclude others from:

• Using
• Making
• Selling
• Importing any infringing product.

This is an offensive right – the patent holder can sue infringers. The patent can also be used to defend any disclosed prior art from later patents.

Beyond litigation, patents serve as negotiation tools:

• Bartering – exchange patents with competitors so both can incorporate each other’s features.
• Licensing – allow others to use the patent for a fee.
• Signalling – a “keep out” fence that deters entry.
• Acquisition leverage – large companies (e.g., Microsoft, IBM) buy startups primarily to internalise their patent portfolios.

Creating a Patent & Patent Strategy

Process:

• File a provisional patent within one year of first disclosure.
• Delay full patent filing until the product idea is near completion and refined (the process is lengthy, expensive, and difficult).
• For multi‑country protection, use a well‑known patent attorney.
• Some companies file a provisional patent (often called “professional patent” in practice) as a low‑cost placeholder.

Patent application must cover:

• Scope of the invention.
• Prior related patents and prior art studied.
• All new claims (what the innovation adds beyond existing products).
• Description of the innovation, defended with clear claims.

Strategic objectives:

• Prevent imitation (imitation barrier) – but patents are often not very effective as barriers because litigation is difficult and costly.
• Patent fences – a wall of related patents around a core technology to block easy imitation.
• Enforce through litigation (large firms have dedicated legal teams).
• Leverage patents for bargaining: give licenses, barter, or buy out firms holding critical patents.

Exam tip: Patents do not automatically confer a market monopoly. Many are minor improvements; real monopoly requires a breakthrough innovation.

Key takeaways

• Five IP types: utility patent, design patent, copyright, trademark, trade secret.
• Patent holders have the right to exclude others from using, making, selling, or importing the invention.
• Patents can be used offensively (sue) or defensively (negotiate, barter, signal).
• Filing a provisional patent within one year of disclosure is critical; delay full filing until refinement.
• Patents are not always effective imitation barriers – litigation is expensive and time‑consuming.
• Large companies use patent portfolios for acquisition and bargaining power.

Dealing with Design and Digital Piracy

A raw idea or product concept is not valuable by itself if unproven or unsellable. Early-stage inventors file a local or provisional patent to secure rights, then develop the idea into a product through the standard new-product development process. Patents can be sold or licensed, but alone they do not guarantee commercial success.

Design and digital piracy erode competitive advantage. Firms must actively prevent, deter, or manage copying. Strategies fall into two broad categories: design-related and digital content–related.

Design Piracy Countermeasures

Product Enhancement

Make the original product difficult to copy by continuously improving it and adding unique attributes that are hard to replicate. Convert the product through locally relevant redesigns into a significantly higher-value offering targeted at upper-class or niche customers. These customers are more willing to pay a premium price for original branded goods (e.g., branded bags, sneakers) because of exclusive features (look, feel, shine) that cheap copies cannot match. The gap in willingness-to-pay reduces the appeal of pirated versions.

Service Enhancement

Leverage skilled services to create bespoke flourishes and enhancements that appeal to premium customers, building long-term lock-in through superior product-service combinations. Examples:

• Water purifier: compelling annual maintenance contracts (AMC), regular filter cleaning/replacement, factory warranty.
• Authorized service centers vs. local services – the guarantee of quality and peace of mind justifies a higher price.

Both approaches rely on niche positioning – customers who value authenticity and service will pay more, making piracy less attractive.

Digital Piracy Countermeasures

Digital piracy is widespread; legislation exists but enforcement is weak. Strategies can be grouped by mechanism:

Strategy	How it works	Example
Pricing / Pre‑publicity	Set a low price (e.g., 99¢ per song) to make piracy economically unviable. Alternatively, allow limited piracy as free publicity (concerts, albums recover revenue).	Apple iTunes (99¢ per song); Moser Baer (3 movies per DVD at very low price); Microsoft allowed piracy in China to create market → later converted users to authentic products.
Encryption & License Control	Encrypt digital data; use license keys, copyright controls, subscriber-only access.	Data encryption laws; software license keys; paid content restricted to subscribers.
Tokenization & Multi‑factor Authentication	Each user gets a unique, time-limited token (e.g., 6‑digit number valid 30‑60 sec). Multi‑factor = OTP + password or fingerprint.	Bank tokens; travel cards with preloaded currency; corporate VPN access.
Forensic Watermarking	Embed invisible watermarks that prevent copying or sharing.	Content protection for videos, images.
Web Crawling & Takedown	Automated tools scan the internet for unauthorized copies; original provider files DMCA takedowns.	YouTube content ID; anti-piracy bots.
Secure Application Development	Build security into the development process: use dedicated servers/VPNs, avoid excessive open-source/APIs, mask client data (dummy data), implement firewalls, multilayered server security, blockchain (end‑to‑end encryption).	Infosys developing for Swiss bank – developers see only dummy data, never real account info.
Frequent Updates & Patching	Release new versions regularly before rivals copy or hack.	iPhone yearly updates (even minor changes); software patches every few months.
Patents as Deterrents	Large firms keep a group of lawyers to litigate patent infringement, signaling that copying will be met with costly legal battles.	IBM, Intel, Microsoft, Meta – use patent litigation to intimidate startups.
Global Delivery Teams (Split Development)	Keep core design/architecture with a trusted core team in a strong-IP jurisdiction (e.g., US headquarters). Outsource coding/testing to extended/ad-hoc teams in weaker-IP countries (e.g., India, China) where enforcement is difficult.	Microsoft: design in Seattle, coding/testing in Hyderabad – design IP never leaves the core office.

Exam tip: Piracy cannot be completely eliminated. The goal is to reduce the incentive and increase the difficulty so that the cost/risk of copying outweighs the benefit. Always mention enforcement challenges (weak in many countries, costly litigation).

Key takeaways – Design Piracy

• Product enhancement: add unique, hard-to-copy features → target niche premium customers.
• Service enhancement: offer bespoke services (AMC, warranty) that authorized channels provide → build lock-in.
• Both strategies increase the perceived value gap between original and pirated goods.

Key takeaways – Digital Piracy

• Low pricing can make piracy irrelevant (e.g., 99¢ songs, multi‑movie DVDs).
• Encryption, tokenization, multi‑factor auth, and watermarking protect content at user/network/server levels.
• Web crawling and takedowns enforce copyright online.
• Secure development practices (dummy data, firewalls, blockchain) prevent leaks during product creation.
• Frequent updates make it hard for copycats to stay current.
• Patents are a legal deterrent, but enforcement is expensive and slow.
• Global delivery teams split design (core office) from execution (extended team) to confine IP risk.

Case Study: CarryPro Backpacks

CarryPro is a late entrant into the luggage industry – a market crowded with established players (VIP, Safari, Aristocrat) and newer competitors like Decathlon. Despite the competition, the industry is promising because of rising disposable income and a shift in consumer mindset: younger buyers (Gen Z and Millennials) spend on experience and comfort rather than just functionality (“YOLO” culture). This creates an opportunity for a well-positioned new brand.

1. Market Entry Decision – Promising but Competitive

Factor	Finding from discussion
Market growth potential	High – driven by travel culture, trekking, and increased spending
Competition	Many well-established brands + affordable players like Decathlon
Opportunity	Growing demand for specialised bags (trekking, travel, office)
Threat	Brand loyalty and low switching costs for consumers

Exam tip: Late entrants must differentiate on features, price, or experience. CarryPro’s challenge is to overcome the trust advantage of incumbents.

2. Target Customer Segments

• Primary segment: Travel-oriented individuals aged 20–35.
  • Gen Z (20–29): higher price sensitivity, open to new brands offline, require trial for high‑involvement purchases.
  • Millennials (30–35): similar travel interests, slightly more income, may be more brand‑conscious.
• Secondary segment: Business professionals on short (2–3 day) trips.
• Psychographic: Experience‑seekers, value comfort and aesthetics alongside utility.

3. Key Product Features – What Customers Prioritise

For a trekking backpack, customers demand:

• Compartments – multiple, organised storage
• Sturdiness – durable for rough terrain
• Water resistance – protection from rain
• Padding – comfort at high altitudes
• Rain cover – for sudden weather changes
• Budget‑friendly – Gen Z are price‑sensitive

For an office backpack, look and feel dominate – the bag is treated as an accessory; functionality is less critical.

4. Brand Trust and Purchase Channel Preferences

Use case	Brand trust needed	Channel preference
Trekking / high‑involvement	High – “I’ll go with a brand I trust”	Offline – must try weight, comfort, fit
Office / low‑involvement	Low – open to new brands with good quality/looks	Online or offline – trial less important

Key insight: For high‑risk product uses (trekking where failure is dangerous), physical trial is essential to overcome brand inertia. For everyday use, appearance and price can outweigh brand.

flowchart LR
  A[Buyer considers new brand] --> B{Product use case?}
  B -->|High involvement (trekking)| C[Requires offline trial]
  B -->|Low involvement (office)| D[Open to online purchase]
  C --> E{Passes trial?}
  E -->|Yes| F[Adopt new brand]
  E -->|No| G[Stick with established brand]

Key takeaways

• CarryPro enters a competitive but growing luggage market driven by travel and experience spending.
• Target is 20–35‑year‑old Gen Z/Millennial travellers and business professionals.
• Trekking bag must excel in compartments, sturdiness, water resistance, padding, and price.
• Brand trust is situation‑dependent: high for trekking (requires trial), low for office bags (style matters more).
• Offline channels are critical for high‑involvement products; online can work for low‑involvement.
• Price sensitivity is real – a new brand must balance quality and affordability to win over Gen Z.

CarryPro Origin and Market Gap

The story of CarryPro begins with its founder, Ankit—a travel blogger with prior experience as a product manager. His dual background gave him both an intimate understanding of traveller pain points and the skills to conceptualise a product solution. The central insight: existing backpacks were too bulky, poorly organised, and not functional for lightweight travel.

Founder’s background and advantage

Attribute	Relevance to product development
Travel blogger (Love Travel Party – LTP)	Passion for travel; direct exposure to user needs; built-in audience for concept testing
Product manager (NDTV)	Customer‑centric thinking; ability to identify pain points; creativity; understanding of business facets

As a travel blogger, Ankit could test his product ideas immediately by showing prototypes or posts to his audience. Likes and feedback gave him early validation—a form of concept testing—before committing to a full startup. This replaced the need for market research.

The gap in the backpack market

Regular backpacks failed on multiple dimensions for travellers:

• Too bulky – took up excessive space, inconvenient for flights, trains, or local travel.
• Poorly organised – lacked compartments or structure for efficient packing.
• Functionally unsuitable – not sturdy for check‑in luggage, not cabin‑friendly, not resistant to dust, dirt, or weather.
• Heavy – added unnecessary weight.

The market lacked a lightweight, well‑structured, durable, easy‑to‑carry backpack that handled varied travel conditions.

From gap to product

Ankit designed a 40‑litre backpack that incorporated all the features he (and fellow travellers) wanted. This aligns with effectuation and design thinking: a user who experiences a problem takes the initiative to solve it, rather than waiting for someone else.

Exam tip: The founder’s ability to test the concept through his blogger platform is a real‑world example of customer validation before launch. This reduces risk—a key point for case analysis.

Key takeaways

• Ankit’s travel‑blogger background gave him direct access to a user community for concept testing.
• His product‑manager experience enabled customer‑centric design and identification of unmet needs.
• The specific market gap: backpacks were too bulky, poorly organised, and not functional for lightweight travel.
• The initial product (40‑litre backpack) solved those gaps and was validated through audience feedback.
• The startup idea emerged from a practical, user‑tested problem, not a random notion.

Product Segmentation: Use-Case-Driven, Not Size-Driven

CarryPro’s initial three products were designed for distinct use cases, not merely different sizes. This prevents cannibalisation and gives each product a clear customer job.

Product	Use Case	Key Features	Competition Level
HOBO40 (2018)	Short travel (3–4 days)	Anti-theft design, in-built rain cover, high volume (40 L)	Moderate (fewer pure-travel backpacks)
HOBO25 (2019)	Daily utility (office, gym, college)	USB cable outlet, detachable pouch, water-repellent fabric (25 L)	High (hundreds of daily-use backpacks)
Pango (2020)	Camera gear & gadget carrying	Detachable camera cube, laptop space, multiple compartments, anti-theft	Low (specialist camera backpack – “uncontested market”)

• The 40 L–25 L gap is large enough that customers can easily distinguish them (unlike 35 L vs. 38 L).
• Segmentation is based on customer utility, not arbitrary price/colour tiers.

Why Three Products – Not More, Not Fewer

A startup’s core constraint is funding and bandwidth. As the lecture puts it: “having 20 ideas is not enough; you have to execute 1 or 2 well.”

flowchart LR
  A[Founder idea generation] --> B{Resource constraints?}
  B -->|Limited capital, team| C[Focus on 1–3 products with clear utility]
  B -->|Large company (e.g., Decathlon)| D[Launch 20+ products per month]
  C --> E[Deep execution + quality]
  D --> F[Broad market coverage]

• Three products are a “smartly thought” number – enough to test multiple segments, few enough to execute with quality.
• Overlap is avoided: no product directly competes with another in the same use case.

Competitive Feature Differentiation

Each product offers extra features that competitors at similar price points lack, often inspired by the founder’s own travel-blogger experience.

HOBO40 vs. Wildcraft/Quechua/Forclaz (Decathlon)

Feature	CarryPro HOBO40	Wildcraft/Quechua/Forclaz
In-built rain cover	✅	❌
Anti-theft design	✅	❌
Price (₹)	3,499	2,699–3,299

Positioning: affordable premium – more features than budget Decathlon bags, but not ultra-premium like Thule.

HOBO25 vs. Wenger/Thule

Feature	CarryPro HOBO25	Wenger (₹6,260)	Thule (premium)
USB cable outlet	✅	❌	❌
Detachable pouch	✅	❌	–
Water-repellent fabric	✅	–	✅
Price (₹)	6,499	6,260	>10,000

CarryPro competes at a similar price to Wenger while offering more value; it avoids Thule’s ultra-premium segment.

Pango vs. Wildcraft StarterPro

Feature	CarryPro Pango	Wildcraft StarterPro
Detachable camera cube	✅	❌
USB cable outlet	✅	❌
Anti-theft + rain cover	✅	Only rain cover
Price	₹7,999	₹7,499

• Features come from the founder’s personal user pain points (e.g., needing a camera cube, laptop space, and chargers organised).
• Quality materials (YKK zippers, water-resistant fabric) reinforce the value proposition.

Why Pango Became the Highest Revenue Product

Despite HOBO40 being popular, Pango generated the most revenue because it occupies a Blue Ocean – a less crowded market.

• HOBO25 faces the fiercest competition (hundreds of daily-use backpacks).
• HOBO40 has fewer competitors.
• Pango: only Wildcraft and Decathlon offer 1–2 products in the camera-backpack niche, and at higher prices.
• Lower competition → easier to capture market share and command margins.

Exam tip: When analysing product portfolio performance, always consider market saturation. A product in a lower-competition segment can outperform a more popular product in a crowded market.

Additional Product: CarryPro Mask (COVID)

• Launched during the pandemic as a synergistic accessory to travel products.
• Followed the same approach: quality, relevant to the target user (travellers need masks).
• Used as a differentiator and brand-extension – Wildcraft also sold masks.

Key Takeaways

• Use-case segmentation prevents cannibalisation and clarifies customer targeting.
• Startups should prioritise execution on a few products over a wide assortment due to resource limits.
• Feature differentiation (anti-theft, USB, detachable cubes) justifies competitive pricing and builds value.
• Entering low-competition niches (Blue Ocean) can yield higher revenue than fighting in saturated categories.
• Founder’s personal experience as a user drives relevant, customer-valued features.
• Even a limited product line can succeed if each product has a clear, non-overlapping utility and quality execution.

Distribution Channel and Marketing Strategy: The CarryPro Case

Omnichannel distribution and brand positioning decisions for a new entrant in the backpack/luggage market. The case of CarryPro illustrates how channel selection and promotional strategy must match product characteristics and buyer behaviour.

1. Distribution Channel Selection

Choosing a channel depends on three intertwined factors: price point, purchase frequency, and the buyer’s need for physical inspection (look and feel).

Factor	Low	Medium	High
Price point	Low value (e.g. shirts) – buyers experiment, less due diligence	₹6,000 backpack – reasonable investment, moderate research	High value (e.g. house, scooter) – thorough checking, high involvement
Purchase frequency	Frequent (e.g. shirts every few months) – willing to try new channels	Infrequent (backpack once in 2–3 years) – willing to invest time in research	Rare (e.g. house) – maximum investigation
Need for look & feel	Low – can buy online without touch	Medium – want to test weight, padding, fit before buying	High – must physically inspect before purchase

Online vs. Offline – Trade-offs

• Online – wide variety, easy comparison of features, convenience.
  Example: A trekker can browse multiple backpack brands on Amazon, Myntra, brand website.
• Offline – allows physical demonstration, builds trust for durable goods.
  Example: Specialised retail stores (DMart) or pop-up stores let customers feel weight, padding, balance.

Omnichannel – the best of both

Many intermediate products benefit from an omnichannel strategy: customers use online for awareness, information, and price comparison, then visit a physical store for look and feel before buying (or buy online after in-store trial). This fits products like CarryPro’s backpacks – medium priced, purchased infrequently, requiring some tactile evaluation.

Exam tip: When asked “should a new product go online, offline, or both?” Always consider price + frequency + need for touch. Omnichannel is often optimal for mid-range, infrequent, experience goods.

CarryPro’s actual channel mix

• Online: Amazon, Myntra, company website.
• Offline: pop-up stores, B2B gifting partnerships, specialised retail (e.g. DMart).

---

2. Branding and Promotional Strategy

Brand Identity & Positioning

CarryPro positioned the product as:

• Sturdy and lightweight
• Multi-utility backpack
• Make in India – a national-origin appeal

Despite these attributes, brand awareness was low – no student had heard of CarryPro before the lecture. Students were familiar with newer competitors like Nasher Miles and Mokobara (VC-funded, high marketing spend) and established players like Wildcraft and Decathlon.

Promotional Tactics Used

• Social media marketing
• Influencer marketing (the founder is a travel blogger, which naturally supports this channel)
• Giveaways and contests
• Product demonstrations – critical for a category where features (padding, weight balance) need to be shown; omnichannel presence (physical stores) enables live demos
• Search engine optimisation (SEO) and broader digital marketing

Why awareness remained low

Reason	Explanation
Limited product range	Only a few backpacks, not enough variety to attract diverse customers
Strong competition	Incumbents have years of trust and large product lines (Decathlon, Wildcraft); newer rivals invest heavily in marketing
High awareness investment needed	Without deep marketing spend, top-of-mind recall is hard to build in a low-frequency category

Takeaway: For a startup in a trust-driven, durable-goods category, product quality alone is insufficient. Sustained investment in brand awareness and a wider product portfolio are necessary to compete.

---

Key Takeaways

• Channel choice depends on price, purchase frequency, and need for physical inspection; omnichannel is ideal for mid-price, infrequent, tactile products.
• Omnichannel lets customers research online (wide selection, comparison) and experience offline (touch, demonstration).
• Brand awareness is low for new entrants without heavy marketing; limited product range and established competitors are major barriers.
• Promotional tactics should include product demonstrations (especially for functional goods), influencer marketing, and digital marketing.
• Top-of-mind recall matters: a good product does not automatically translate to high awareness – trust and range take time to build.

New Target Segments

Beyond the core Gen Z + Millennial audience, CarryPro can expand into niche user groups with specific needs that existing products partially address.

• Female travellers / backpackers: Women have distinct needs in bag design (e.g., security, lighter weight, organisational compartments).
• Creators, musicians & artists: These professionals carry instruments (e.g., sitar, tabla), recording equipment, and accessories. A specialised bag like Pango (originally for photographers) can be adapted with padded compartments, waterproofing, and easy-access pockets for art supplies or audio gear.
• Workation / hybrid workers: Post-COVID, many urban office-goers combine work and vacation. They need bags that transition seamlessly from laptop-carry to travel – e.g., a HOBO40 variant with a dedicated work-organiser sleeve, labelled “Worksation 40”.

Exam tip: Identifying new target segments is a classic first step in product line extension. The lecture stresses that segments must have demonstrably different use cases to justify new SKUs.

Key takeaways – New targets

• Female travellers, creators/musicians, and workation users are three high-potential segments.
• Each requires use-case-driven design (instrument padding, work-travel hybrid).
• These segments represent organic expansion of CarryPro’s existing product architecture.

Product Line Extension: Slow & Tested

CarryPro’s existing products – Pango, HOBO25, HOBO40 – serve as the foundation. New specialised variants should be introduced slowly, not aggressively.

The entrepreneur’s logic for slow expansion

flowchart LR
    A[Start with one new variant] --> B{Market ready?}
    B -->|No| C[Keep base product, build trust]
    B -->|Yes| D[Rapidly launch multiple variants + ads]

• Reason: Niche products need time to build brand trust and gain feedback. Heavy advertising before product–market fit wastes resources.
• Strategy:
  1. Test the market with a limited run.
  2. Collect user feedback, refine features.
  3. After trust is established, scale up marketing and launch additional variants.

Example: Instead of immediately releasing five workation bags, launch one (e.g., “Worksation 40”), monitor sales and reviews, then expand the line.

Key takeaways – Product line extension

• Extend from existing best-sellers (Pango, HOBO25, HOBO40).
• Add use-case-specific features (e.g., instrument padding, dedicated laptop compartment with cable pass-through).
• Move slowly: test, refine, then scale.
• Avoid heavy ad spend until product–market fit is validated.

Market Penetration: Pricing Strategy & Trade-offs

One proposed growth tactic is price reduction of Pango from ~₹10,000 to ~₹4,500 to attract beginner photographers who are price-sensitive.

Trade-offs of cutting price

Benefit	Risk
Lowers consumer trial risk (₹4,500 vs ₹10,000)	Margin compression – profitability drops per unit
Increases sales volume (if demand is elastic)	Brand dilution – low price signals lower quality in Indian market
Opens new segment (price-sensitive beginners)	Repositioning – Pango moves from premium (competing with Wildcraft ~₹7,000) to mid-range (competing with Safari/Skybag)

A better alternative: new brand / lower-feature variant

Rather than discounting the flagship Pango, launch a separate product (with a different name) at a lower price point, with fewer features. This:

• Preserves premium brand image (price = quality signal).
• Avoids cannibalising the high-margin core product.
• Targets the same price-sensitive segment without diluting brand equity.

Exam tip: Price as a quality signal is critical. Reducing price on an established premium product may cause consumers to question its quality, especially when competitors stay at higher price points. Always consider a sub-brand or “lite” variant instead.

When is price reduction justified?

• If the volume increase is substantial enough to offset margin loss and maintain overall profit.
• If the brand wants to reposition away from premium (e.g., to fight a mass-market competitor).
• If the product has low fixed costs and high scalability.

Key takeaways – Pricing strategy

• Cutting price on an existing premium product risks quality signalling and brand dilution.
• Better to launch a lower-feature variant under a different name.
• Price reduction is only beneficial if volume gains compensate for margin loss.
• Always consider the competitive landscape: matching competitor prices can avoid being perceived as inferior.

Branding & Promotion Improvements

CarryPro’s branding is currently weak. The founder is also a travel blogger – this dual identity can be leveraged.

Key actions to improve brand reach

• Influencer partnerships: Connect with other travel influencers (community-based promotion).
• Affiliate marketing: Give influencers a commission per sale; they promote with authentic content.
• Relatable content: Not just product showcases but value-added content – e.g., “What’s in my bag” for a Himalayan trek, packing tips, travel hacks.
• Regular content uploads: On Instagram/YouTube, consistency builds followers and algorithm boost.
• Collaborative content: Use the founder’s own travel blog to create “how to pack” series, subtly highlighting product features.

Content strategy example

Content type	Purpose	Example
“What’s in my bag”	Showcase product features and organisation	Unpacking a HOBO40 for a week-long trip
Travel tips	Build trust and authority	“10 things every backpacker must carry”
User-generated content	Social proof	Repost customer photos with the bag
Behind-the-scenes	Humanise the brand	Founder packing for an expedition

Key takeaways – Branding & promotion

• Move beyond pure online ads; invest in community-based influencer marketing.
• Affiliate marketing aligns influencer incentives with sales.
• Content should be relatable and value-driven, not just product-centric.
• Regular posting schedule is essential for algorithm visibility.

Sales & Distribution: Partnerships

The lecture mentions a partnership with CRED (case-exhibit evidence). Such platforms can expand awareness to new customer bases (e.g., credit-card users, premium demographics). However, the effect may be modest because most customers browse across multiple sites.

Exam tip: When evaluating distribution partnerships, consider channel overlap – if the partner’s audience already overlaps heavily with existing customers, incremental reach is low.

Key takeaways – Sales & distribution

• Partnerships (CRED, travel clubs) offer incremental reach but may have limited unique audience.
• Combine digital partnerships with the founder’s own blog/influencer reach for maximum cost-effective distribution.

Pricing Decision

A product manager must decide the price point and positioning — essentially, whether to compete on affordability or premium features. The core trade-off is between margin and market reach.

Three Pricing Options for CarryPro

Option	Description	Advantage	Disadvantage
Current pricing (₹6,199)	Quality at an affordable price	Retains existing customers; consistent brand image	Risk of being average; hard to differentiate
Reduce price	Make it cheap/affordable for price-sensitive Gen Z	Attracts new, budget-conscious buyers; volume sales	Product perceived as low quality; struggles against established competitors (Wildcraft, Decathlon)
Premium pricing (₹18,000–₹20,000)	Add more features and charge a premium	Higher profit margin; stronger brand image as high-end	Loses existing customer base; Gen Z audience may find it unrelatable

Exam tip: The biggest risk of premium pricing is alienating the existing customer base built through the influencer’s own audience. Managers must weigh brand aspiration against current loyalty.

Value Sensitivity — Not Just Price Sensitivity

Indian customers are value-sensitive — they want good quality at an affordable price. Charging too high or too low sends different signals. A price that is too high signals exclusivity but shrinks the addressable market; too low signals cheapness and undermines quality perception. The optimal price sits where perceived value exceeds price.

Tactical Alternative: Promotional Discounts

Instead of a permanent price change, use innovative promotions (e.g., 30% seasonal discounts during travel season) to create FOMO (Fear Of Missing Out) without diluting the core price point. This preserves brand positioning while driving short-term sales and brand awareness.

Key takeaways

• Three pricing paths: affordable, premium, or maintain current price.
• Premium pricing boosts margin but risks losing loyal customers.
• Promotional discounts offer a middle ground — limited-time offers create urgency without permanent repositioning.
• Indian customers are value-sensitive, not simply price-sensitive.

Distribution Decision

After pricing, the second critical choice is distribution strategy — limited store presence versus wider retail presence.

Limited Stores vs. Wider Retail

Aspect	Limited Stores (specialty stores, high-end malls)	Wider Retail (DMart, Big Bazaar, online)
Brand image	Perceived as exclusive, high-end	Diluted premium image; brand seen as mass-market
Customer experience	Can control: knowledgeable salespeople, better demo, curated environment	Uncontrollable: salespeople may not know product; store ambiance may not match brand
Reach & visibility	Low; fewer touchpoints	High; word-of-mouth and brand awareness increase
Operational constraints	Lower inventory needed; less working capital	High inventory, higher working capital; retailers demand discounts (e.g., 30% off)
Pricing control	Full control over list price	Retailers run promotions; margins compress
Customer profile	Attracts buyers willing to pay for premium experience	Attracts budget-conscious shoppers; may not buy premium products

Key Trade-off: Alignment with Pricing Choice

Pricing and distribution are interrelated:

• Premium price + limited stores: reinforces exclusivity and premium experience.
• Lower price + wider retail: leverages volume and mass-market presence.

The case discussion unanimously favoured limited stores for CarryPro, given its current brand stage (low brand loyalty) and the need to build a premium, specialised image before scaling.

Exam tip: A brand that tries to sell both in luxury malls and discount stores simultaneously confuses the consumer. The classic example: Toyota owns Lexus to maintain a separate premium identity; Maruti cannot go premium without breaking its mass-market perception.

Key takeaways

• Two distribution extremes: limited (exclusive, controlled) vs. wide (mass reach, diluted image).
• Limited stores offer brand control and customer experience at the cost of reach.
• Wide retail increases visibility but demands higher production, inventory, and discounting.
• The distribution choice must align with the pricing strategy — consistency is critical.

Strategic Alignment — How It All Connects

The entire product strategy — from idea generation to category selection, pricing, features, and distribution — must be aligned with the customer need and the use case.

• Start with the customer: identify the pain point, find the gap in the market, then position the product to fill it.
• Market testing in this case was organic — because the founder was an influencer, feedback came naturally through live product engagement. In a typical firm, structured campaigns (surveys, prototypes, test markets) are used to gather feedback and iterate.
• Brand loyalty is low initially. Without loyalty, the product must rely on clear positioning and consistent execution across pricing and distribution.

flowchart LR
    A[Customer Pain Point] --> B[Product Features & Design]
    B --> C[Pricing Decision]
    B --> D[Distribution Decision]
    C & D --> E[Brand Positioning]
    E --> F[Consistent Customer Experience]
    F --> G[Built Brand Loyalty]

Key takeaways

• Every decision (pricing, features, distribution) must serve the same customer use case.
• Indian consumers are value-sensitive: they seek quality and affordability together.
• At early stages, preserving brand integrity (via limited distribution) often matters more than raw reach.
• Market testing can be organic (influencer) or planned (campaigns); both feed back into product iteration.