Concept Generation and Evaluation

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

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

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

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.

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

• 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

• 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

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:

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

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.

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

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

• 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?

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

• 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:

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).

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.

• 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.

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:

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

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.

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).

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

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)

Step 2 – Technical Requirements (Hows) and Relationship Matrix

Technical requirements include cooking pressure, sealing, shape, size, thermal conductivity, weight, material strength, and pressure release.

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

(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\%$

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).

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:

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

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:

• 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

A multi-criteria scoring model captures management and customer interests alongside financial considerations:

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:

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.

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:

“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

For a food truck or fast-food launch, 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.