The NPD Mindset Insights and Takeaway

Design Thinking Framework

The Design Thinking Framework provides a structured, human-centered approach to innovation. The 4D Design Thinking Framework (created by the UK Design Council) splits the process into two broad phases and four stages: the what/why phase (Discover, Define) and the how phase (Develop, Deliver).

The 4D Process

Phase 1 – What & Why Starts with a question, vision, or statement of intent.

• Discover – Map all stakeholders, understand people’s daily experiences, and identify causal influences that impact the process.
• Define – Extract major themes and synthesize findings into a clear opportunity brief that will guide ideation.

Phase 2 – How Begins with the opportunity brief from Phase 1.

• Develop – Rapidly test ideas and concepts. Seek user feedback, iterate, and refine the business model to align with field realities.
• Deliver – Measure impact on actual users. The outcome is a functioning, proven concept that works with real users.

Nature of Design Thinking

• Aim is an acceptable solution that satisfies user requirements effectively — not perfection.
• Solutions are developed interactively with all key users through iterative cycles.
• Complex goals are met via rapid, many user feedback loops, not by adding complex technical resources.

Exam tip: Design thinking is not a linear waterfall. The iterative, feedback-driven nature is what distinguishes it from traditional engineering design. Expect questions contrasting “iterative closure” with “spec-driven completion.”

Key Takeaways

• 4D = Discover, Define, Develop, Deliver — split into What/Why and How phases.
• Every stage is user-involved; the process converges to an acceptable solution through feedback loops.
• The opportunity brief is the bridge from problem-framing to solution-testing.
• Design thinking prioritizes rapid learning over comprehensive upfront planning.

---

New Product Development (NPD) Introduction

New Product Development (NPD) is a multi-disciplinary process spanning Strategy, Design, Marketing, and Operations. It covers the full journey from idea to launch, aiming to create both business value (profit, market share) and social value (societal benefit). Effective NPD requires balancing technical development with user communication.

The BottleLoft Case Study

The product BottleLoft (by STRONG LIKE BULL Magnets) is a plastic strip with three magnets, attached via adhesive to the inside roof of a refrigerator. Bottles hang from the magnets, freeing shelf space below.

• Key components

  • Flat magnets (made by the company)
  • High‑bond 3M adhesive (outsourced)

• Kickstarter video Emphasized strength of the magnets (company’s own product) while largely ignoring the critical role of the 3M low‑temperature adhesive.

• User dissonance Users care equally (or more) about the adhesive holding three bottles on one strip as they do about the magnet holding one bottle. The video’s product‑centric focus on the company’s magnet created a gap in user confidence.

The Implication: Two Mindsets for Two Phases

Exam tip: The BottleLoft example illustrates a common NPD pitfall: what you emphasize internally (your core technology) may not match what users need to hear. Always test your marketing message against user priorities — the adhesive was as important as the magnet from the user’s perspective, so it should have been equally prominent.

Key Takeaways

• NPD integrates multiple disciplines: strategy, design, marketing, operations.
• Process covers idea generation → launch, with both business and social value goals.
• Product‑centric mindset drives development; user‑centric mindset drives communication.
• Ignoring user priorities in marketing creates “dissonance” that undermines adoption.
• The BottleLoft video’s overemphasis on magnets (company’s own) and under‑emphasis on adhesive (3M) is a classic case of failing to shift mindsets at launch.

Why Study NPD?

New Product Development (NPD) focuses on identifying existing or latent user needs and translating them into products or services. It covers:

• Innovation and technology-led new products
• Adapting existing products for new users
• Adapting business models to new contexts
• Using both product-centric and user-centric viewpoints

Product development requires critical trade-offs in features to match latent customer requirements and competitive offers. Most product characteristics and key features are decided at early stages, which can pre‑fix their market scope. Changing these later is expensive, sometimes unviable, or infeasible. Early decisions have major strategic and operational impact on success.

Two major targets of NPD:

1. The product is suitable and viable to users.
2. Time to market is as short as possible.

Cost of Late Design Changes

Making a design change later in the process multiplies cost dramatically:

Exam tip: The same change costs 100× more if postponed to production. This is why understanding customer requirements early is critical – it reduces both cost and time to market.

Time to Market Improvements

Major reductions in development time occurred between the 1980s and 1990s. Examples:

Faster time to market allows companies to incorporate new technology into the latest products more quickly, giving a competitive advantage.

Key takeaways

• Early product definition locks in market scope; late changes are expensive.
• Cost of a design change increases ~10× per stage (design → process design → production).
• Reducing development time is a major competitive lever, as shown by Honda, AT&T, and HP.
• NPD must balance user suitability with speed to market.

---

Business Models and Why They Fail

A business model tells a story about:

• Who are the customers?
• What do they value?
• How does the company make money?
• How is value delivered at a reasonable cost?

A good business model requires articulation of how the product/service is made and delivered. Innovation can focus on either or both.

New products often require new business models. If the business model is inappropriate, the product can fail.

Two Tests for a New Business Model

1. Narrative test: Does the story about customers, their values, and why they will buy make sense?
2. Numbers test: Do the projected profits add up? Can value be delivered at a reasonable cost?

If either test fails, the business model is unsuitable.

When Existing Business Models Fail

Existing business models may fail because the assumptions they were built on (e.g., customer behavior) no longer hold. Specific limits (e.g., willingness to pay) may be stretched too far. If the model is robust to variations, corrective action may save it; if it is sensitive, even prompt action may not.

Assessing the Business Model for a New Product – Two Sets of Questions

Customer set:

• Who are (and are not) your customers?
• What do these customers value?
• What will you offer? What will you not offer (even if asked)?
• How much will customers pay? How much are they willing to pay? (These may differ.)
• How will customers behave in terms of opting out?

Cost set:

• What activities drive the cost of the offer?
• Is there high upfront investment? (Risk: must invest before launch)
• Is there a float (advance from customers) or high working capital?
• How much does it cost to deliver the promised value?
• Does cost depend on scale? (Scale does not always lower cost.)
• Will cost vary for different customer types? Will it grow over time?

Example: Uber Taxi Business Model

Uber connects customers to nearby drivers faster than call-taxi services. Benefits:

• Customers get early confirmation and shorter wait times.
• Drivers drive less empty (lower “dry run”) to reach the next customer.

Value creation: Increases efficiency and lowers driver costs, raising their income; provides fast car availability for users.

Stakeholder equity: Uber raises prices during shortages to attract more drivers, increasing supply. While customers pay more, they at least get a ride – unlike competitors where no cars are available. This improves service during peak demand.

Business Model vs. Business Strategy

• Business model: How the firm creates value for target customers. It is opportunity‑centric.
• Business strategy: How the firm captures the value created. It is competition‑centric (gaining advantage over rivals).

Even a good business model fails if the business strategy does not persuade customers to buy from you rather than competitors.

Key takeaways

• A business model must pass both the narrative test (story makes sense) and the numbers test (profitability).
• Existing models fail when assumptions about customers or limits break.
• Assess business models via customer questions (who, value, offer, pay) and cost questions (activities, upfront investment, scale, variation).
• Uber’s model creates value through efficiency and dynamic pricing, but value capture still requires competitive strategy.

---

Developing a Mission Statement

The NPD process starts with a mission statement for the product. Example: a kids’ calculator.

Key elements of a mission statement:

Stakeholders to consider:

• Users (children in target group)
• Buyers (parents, teachers)
• Retailers and sales force
• Production and quality control
• Packaging and environment (standards)
• Servicing (e.g., replacement for sealed products)
• Legal standards for children’s products

Key takeaways

• The mission statement defines the product, business goals, target markets, and key assumptions upfront.
• All stakeholders (users, buyers, retailers, production, legal, etc.) must be identified and their requirements addressed.

---

Portfolio Management – Balancing the Product Portfolio

Managing the NPD process aims at two targets:

1. Reduce time to market.
2. Align product to user and market needs.

Two aspects:

• Doing the right things: Balancing the product portfolio.
• Doing things right: Managing the project (product development funnel and stage‑gates).

The Balanced Portfolio – Two Dimensions

Projects are spread across two dimensions:

• Technology: from existing/basic to new/radical
• Customer need: from same need as current products to completely new need

The resulting portfolio contains:

• Minor innovations (e.g., new branding, batch size changes) – lower right
• Derivative products and new platform products – middle
• Breakthrough/radical innovations – top left

A balanced portfolio includes both:

• Products that milk existing markets (minor improvements)
• Products that capture new markets via breakthroughs

Risks of imbalance:

• Only breakthrough products → undervalues current product improvement.
• Only incremental products → jeopardises future when competition innovates.

Key takeaways

• Portfolio balances technology risk (existing → radical) and market risk (same need → new need).
• A balanced mix of incremental, derivative, platform, and breakthrough projects is essential.
• Lopsided portfolios miss either current revenue or future growth.

---

Portfolio Decisions

When adding a new product, decisions span multiple dimensions:

Exam tip: Component‑level competition can erode profits even if the overall product is unique. Always check whether any part of your offering can be unbundled by rivals.

Key takeaways

• Adding a product requires evaluating brand, market, pricing, cost, operations, distribution, and competition at multiple levels.
• Using the same brand and distribution can reduce costs, but only if quality and positioning align.
• Component and service competition limit pricing power.

The Product Development Funnel

The product development funnel visualizes how a firm transforms many raw ideas into a single launched product. Intuitively: start with a wide net of possibilities, then systematically filter out weaker concepts until only the strongest remains.

The funnel combines customer needs with technological possibilities to generate concepts. The process consists of sequential stages:

1. Concept generation – multiple concepts are developed.
2. Concept selection – concepts are assessed and ruled out based on feasibility, workability, or strategic fit.
3. Product design – the selected concept is developed into exact component specifications.
4. Development & prototyping – each component is built, a prototype is created and tested.
5. Product launch – after successful testing, the product enters the market.

The number of concepts is “whittled down” as the funnel narrows. Maximum flexibility exists at the beginning; as commitments are made to specific designs, the funnel constricts.

Exam tip: Starting with a broad funnel (many initial ideas) dramatically increases the chance of a successful outcome. A narrow funnel risks selecting inadequate ideas early.

Key Takeaways – Product Development Funnel

• The funnel combines customer needs and technology into concepts, then filters them.
• Stages: concept generation → selection → design → development/prototype → launch.
• Early stages have maximum flexibility; later commitments reduce options.
• A broad initial funnel yields better final products.

---

Stage-Gate Management

The funnel alone is insufficient – organizations need a formal stage-gate process to control it. A gate is a management review point where decisions to continue, stop, or redirect a project are made.

Real example: 6 ideas enter → 5 pass Gate 1 → 4 pass Gate 2 (feasibility) → 3 enter launch preparation → 1 product launches (others may launch later).

Managing Stage-Gates Effectively

The following practices ensure good ideas proceed and weak ones are stopped early to avoid wasting money:

• Communication – the entire process must be known by all employees.
• Transparency – assessment criteria and decisions are open at every gate.
• Top management commitment – senior leaders enforce the process.
• Periodic reviews – against agreed standards.
• Good documentation – allows post-hoc analysis (e.g., why a competitor succeeded with a project the firm stopped).
• Cross-functional teams with project champions to lead.
• Not all projects get fully funded – funding follows promising projects.

Key Takeaways – Stage-Gate Management

• Gates are decision points that control the funnel’s narrowing.
• Example: 6 ideas → 5 → 4 → 3 → 1 launched.
• Effective management requires communication, transparency, top management commitment, documentation, and cross-functional teams.
• Stopping failing projects early saves resources.

---

Flexibility in Product Development

Given high market and technology uncertainty, rigidly locking the design early is risky. Flexibility is an alternative to investing in better upfront research.

Ways to increase development flexibility:

• Adopt flexible technologies that allow fast, cheap design iterations.
• Structure tasks to allow progressive commitment (lock down requirements gradually, not all at once).
• Keep viable backup options and revisit trade-offs.
• Use modular architecture – uncoupled modules reduce design volatility and enable easy component replacement.

Exam tip: Flexibility is especially valuable when market uncertainty is high. The decision involves an economic trade‑off: weigh the benefits of late adaptation against overheads and possible product compromises.

Key Takeaways – Flexibility

• Flexibility enables efficient late design changes under uncertainty.
• Comes with costs: overheads and risk of inferior products.
• Achieved through flexible technologies, progressive commitment, modular design, and keeping backups.
• Choose the best trade‑off per project context.

Identifying New Product Opportunities

New product opportunities can be surfaced through multiple systematic approaches. Each method targets a different source of insight: external changes, competitor moves, user experiences, or emerging technologies. The key is to move beyond incremental improvements and uncover white spaces – areas of genuine unmet need.

Buyer Utility Map (36-Square Grid)

The buyer utility map is a strategic tool for visually scanning all possible points where a product could deliver value. It consists of two axes forming a 6×6 grid (36 squares):

• Horizontal axis – Stages of customer experience: Purchase → Delivery → Usage → Supplements → Maintenance → Disposal
• Vertical axis – Utility levers: Customer productivity, Simplicity, Convenience, Risk, Fun & Image, Environmental impact

How to use it:

1. For each of the 36 squares, note what your company already does.
2. Next, note what each major competitor does in the same squares.
3. Identify overloaded squares (both you and competitors are active) – these are red squares, where differentiation is hard.
4. Identify empty squares (neither you nor competitors are active) – these are blue squares, representing uncontested space for innovation.

The goal is to shift competition from red to blue squares – creating new utility at a stage or lever the market hasn't addressed.

Exam tip: The buyer utility map is a blue‑ocean strategy tool. The “blue squares” are the ultimate target; they represent genuine opportunities to leapfrog competitors rather than fight for share in saturated areas.

Key takeaways

• 36‑cell matrix crossing six experience stages with six utility types.
• Overloaded squares = red (head‑to‑head competition); empty squares = blue (innovation space).
• Use it to systematically discover unmet value propositions.

Product Frustrations – Idea Generation

Another rich source of new product ideas is user frustration with existing products. By categorising frustrations, designers can target specific pain points for elimination. The following list was compiled from a class exercise:

These frustrations fall into two groups: issues where the user (knowledge/skill/ability) is the bottleneck, and issues where the product design itself is flawed. Removing either type can yield a clearly superior product.

Key takeaways

• User frustrations are a direct source of improvement ideas.
• Two broad classes: user‑side obstacles and design‑side flaws.
• Not every frustration is actionable for all users; prioritise those that affect the target market most.

Lead Users – Tapping Advanced Experience

Lead users are individuals or organisations that experience needs well ahead of the general market and have a strong incentive to innovate on their own. They can provide insights that common users cannot.

Three types of lead users, with examples from the scissors case:

Limitations of lead‑user research:

• Their specifications may not suit the common user (over‑engineering).
• Identifying type‑2 and type‑3 lead users requires a broad, sometimes costly search.
• Lead users in the target area may become early adopters; those in analogous markets usually won't.
• Always complement lead‑user insights with traditional, large‑sample market research.

Exam tip: Lead users are not a replacement for mainstream market research. Use their radical ideas to inspire, then validate with the broader target audience.

Key takeaways

• Lead users face needs before the market and often experiment.
• Three types: same application, analogous market, specialised problem area.
• Provide breakthrough ideas but must be adapted for mass adoption.

Building Superior User Experience – Peter Morville’s Honeycomb

The Peter Morville Honeycomb model (often called the User Experience Honeycomb) identifies seven qualities that together create a valuable product. All qualities orbit around the central goal: value.

When all six are satisfied, the product delivers value – not only to the end user but to all stakeholders (company, partners, society).

Key takeaways

• Seven dimensions of UX: Useful, Usable, Desirable, Findable, Accessible, Credible → Valuable.
• Each dimension is a lever for improving the overall experience.
• Superior UX is not just about usability; it integrates trust, accessibility, and emotional appeal.

Market Research for New Product Development

Market research for new products differs fundamentally from research for existing products. The goal is to uncover what is missing in current products and what users truly desire, rather than measuring satisfaction with what works. Because customers are expensive to engage, the research must be focused and small-scale: carefully chosen users and non-users (as few as 30 can identify 90–95% of needs) reach saturation quickly. Questions cover only four areas:

• Typical uses of the product
• What the user likes
• What the user dislikes
• Suggestions for improvement

Prototypes can later be shown to a subset of interested users for feedback; focus groups may reveal insights that individual interviews miss.

Sources of User Information

Exam tip: Matching the method to user experience level is a classic test – observation for low articulation, lead users for rich expertise.

---

Kano’s Model of User Preferences

Not all user needs have the same impact on satisfaction. Kano classified attributes into five types based on how their presence/absence affects customer satisfaction.

Satisfaction dynamics (conceptual):

How to use the Kano model for product decisions:

1. Meet minimum requirements – include all must-have attributes.
2. Add value with one-dimensional attributes – offer tiered configurations (e.g., hard disk capacity).
3. Infuse attractive attributes – a few delights to justify a premium.
4. Ignore indifferent and reverse attributes – they waste resources or harm adoption.

---

Product Variety Matrix

Using Kano’s one-dimensional (satisfiers) and attractive (delighters) attributes, a product variety matrix can be built. Example with two satisfier levels and two delighter levels:

• Nine configurations result from just two dimensions.
• Purpose: Customers can select the combination that best fits their budget and preferences – a competitive advantage over firms offering fewer options.
• For example, a ₹50,000 laptop budget may have three configurations; the customer chooses which mix of satisfier and delighter to include.

---

The House of Quality

The House of Quality (HoQ) is a visual tool that collates customer needs, technical specifications, competitor benchmarks, and trade-offs into one diagram.

Key components:

1. Left wall (Customer needs & benefits) – from market research, listed in rows.
2. Ceiling / top (Technical responses) – engineering specifications, listed in columns.
3. Relationship matrix – cells showing how each technical spec satisfies each customer need (strong, moderate, weak).
4. Roof (Technical correlations) – triangle above the columns indicating positive/negative interactions between specs (e.g., faster chip vs. battery life).
5. Right side (Planning matrix) – benchmark of customer needs against competitors’ products (e.g., 1–5 scale). Identifies gaps.
6. Basement (Technical comparison) – benchmark of technical parameters against competitors.

How it helps: Product designers see all essential information in one place: what users want, how to deliver it technically, what trade-offs exist, and where competitors are better or worse.

---

Quality Function Deployment (QFD)

QFD is the structured process that uses the House of Quality (and possibly other matrices) to translate customer requirements into design specifications.

Effect on design changes over time:

• Without QFD: Many design changes occur late in the development cycle, when costs are high (rework, retooling).
• With QFD: Design changes happen early, when changes are cheap; later stages see few changes, often dropping to zero before production.

Result: Higher product quality, lower overall cost, and on-schedule delivery.

---

Benefits of QFD

• Increased customer satisfaction – needs identified and met early.
• Shorter development cycle – fewer late reworks.
• Earlier resolution of design trade-offs – clear visibility in the HoQ.
• Minimised startup difficulties – production issues caught early.
• Better inter‑functional knowledge transfer – HoQ becomes a shared language for marketing, design, and production teams.
• Visual thinking – entire team participates.
• Cross‑functional team building – common tool fosters collaboration.

Exam tip: QFD is powerful for complex products but can be over‑kill for simple products. Know when it is appropriate.

---

User Tool Kits

Toolkits allow users to design or customise their own product, bypassing the difficulty of accurately assessing heterogeneous needs.

How they work:

• Users experiment with features via a toolkit.
• They create a prototype or configuration that exactly matches their preferences.
• The firm then manufactures/delivers the user‑designed product.

Examples across industries:

Benefits: Saves costs, improves customer choice, and reveals configurations that the firm might not have considered.

---

Key Takeaways

• Market research for NPD focuses on missing/latent needs; small samples (~30) suffice; questions cover uses, likes, dislikes, suggestions.
• Kano model classifies attributes as must‑have, attractive, one‑dimensional, indifferent, reverse – guides what to include and where to invest.
• Product variety matrix uses one‑dimensional and attractive attributes to create multiple configurations, giving customers choice and competitive advantage.
• House of Quality integrates customer needs, technical specs, correlations, and competitor benchmarks into one diagram – essential for QFD.
• QFD reduces late, costly design changes by forcing early resolution of requirements; improves quality, cost, cycle time, and team collaboration.
• Toolkits let users design their own products, ideal for highly heterogeneous demand and when needs are hard to articulate.

Requirements of an Effective User Toolkit

A user toolkit enables customers to design their own product variants. An effective toolkit must be:

• Complete trial-and-error cycles – users can iterate within the toolkit without stepping outside it.
• Adequate solution space – covers all high-potential designs customers may want.
• User-friendly – users employ their own design language and simple skills.
• Library of common modules – e.g., a travel site includes a calendar feature to avoid date errors.
• Seamless translation to production – the company implements the user’s design exactly (no revisions), preventing dissonance.

Value of an Effective Toolkit

• Creates a distinctive competitive advantage (harder to copy; first-mover benefits).
• Shifts trial-and-error cycles to the user → cuts development time.
• Offers high variety at drastically reduced cost, potentially revolutionising the industry.
• Provides early learning about user trends in the market.

Methods for Evaluating Innovation Ideas

Several evaluation methods exist; the ATAR model is one of them.

The ATAR Model

The ATAR model forecasts demand for a new product by multiplying four components:

$Adoption = Awareness \times Trial \times Availability \times Repeat$

Each factor is a proportion (0 to 1):

The result is an estimate of total adopters. All inputs are assumptions; results must be cross‑checked with real data and revised each period.

Exam tip: The ATAR formula is a multiplicative funnel. If any component is zero, total adoption is zero. In practice, Awareness and Availability often constrain Trial and Repeat.

How the Components Relate

Key takeaways

• An effective user toolkit enables self‑design, cuts dev time, and yields competitive advantage.
• ATAR = Awareness × Trial × Availability × Repeat – a multiplicative demand forecast.
• Awareness comes from advertising; Trial from purchase; Availability from distribution; Repeat from repurchase or recommendation.
• All inputs are assumptions – validate with actual results and update the estimate.

Product Architecture

Product architecture is the internal structure of a product—how its components are arranged and interact. The choice between two fundamental styles directly shapes a product’s performance, flexibility, and cost.

Modular Architecture

In modular architecture, components (modules) are independent and interchangeable. Classic example: a desktop computer—every part (CPU, RAM, GPU, storage) can be removed and replaced with an identical or compatible unit.

Benefits:

• Standard components → easy upgrades, add‑ons, replacements
• Re‑use of existing parts across products
• High flexibility for post‑purchase customization
• Enables greater product variety and user‑specific tailoring
• Isolates wear‑and‑tear parts for simple replacement

Trade‑off: Optimises flexibility over raw technical performance.

Integral Architecture

In integral architecture, components are tightly coupled and not easily separable. Found in laptops and tablets where space is constrained—components are often soldered or embedded, forcing whole‑module replacement.

Benefits:

• Minimises form factor: size, volume, weight
• Single part can serve multiple functions
• High robustness and quality
• Limited post‑purchase change, repair, or upgrades
• Fewer standard components; little cross‑product compatibility

Trade‑off: Optimises performance (especially compactness) over flexibility.

Six Types of Modularity

Exam tip: The six types of modularity are often tested by matching each definition to the correct name. Focus on the precise verb—sharing (same part across products), swapping (same interface), cut to fit (length adjustment), mix (blending), bus (common base), sectional (connectivity).

Key takeaways

• Modular architecture maximises flexibility, variety, and upgradeability; integral architecture maximises compactness and robustness.
• Integral design limits post‑purchase change and standard component use.
• Six modularity types cover different ways components can be standardised or combined.

Design for Manufacturing (DFM)

Design for Manufacturing aims to make a product easy and cheap to produce. Key techniques:

• Minimise number of parts – fewer parts → less assembly, lower cost.
• Use common parts across many products.
• Eliminate fasteners (screws, bolts) → cut assembly time.
• Eliminate jigs and fixtures during assembly.
• Eliminate adjustments – pre‑align parts so they fit without tweaking.
• Prevent errors – use color coding and other mistake‑proofing designs.
• Consider customer assembly – let the user assemble (e.g., IKEA) → lower manufacturing and transport cost.
• Minimise system complexity to allow easy assembly.
• Isolate wear parts – place them so customer can replace without factory service.
• Choose modular architecture for parts needing repair/upgrade; choose integral architecture for parts where performance/cost matters most.

Worked Example: Swatch

Swatch combined integral internal architecture (compact, reliable, cheap to manufacture) with modular external face (high variety). This allowed them to compete against Japanese quartz watches while maintaining Swiss quality perception.

Worked Example: Shimano

The bicycle component industry was fragmented—users bought individual parts from different makers. Shimano introduced the click‑shift gear system, then integrated it into an optimised kit (shifters, rails, cranks, brakes). They realised user needs were more homogeneous than manufacturers assumed; customers preferred a single, high‑quality integrated set over mixing sub‑optimal components. Shimano’s branding on the handle also increased visibility. By 1997, they commanded 86–98% market share in gear systems across different markets.

Key takeaways

• DFM reduces manufacturing cost and opens larger markets.
• Techniques include part minimisation, fastener elimination, error‑proofing, customer assembly, and isolating wear parts.
• Firms can mix modular and integral architectures within the same product (e.g., Swatch) to get the best of both.

Prototyping

Prototypes are approximations of the final product used for testing, learning, communication, and integration. They reduce overall time, cost, and risk in development—even though making them has its own expense.

Purposes:

• Demonstrate feasibility (especially for breakthrough products)
• Detect problems (derivative products)
• Plan releases (platform products)
• Serve as funding milestones in development
• Allow target users to evaluate and identify blind spots

Types of Prototypes

Prototyping strategy – decisions such as:

• In‑house vs. vendor‑made: In‑house keeps secrecy and uses skilled workers, but transfer to production is harder. Vendors who make prototypes learn the manufacturing process early, enabling faster production ramp‑up.
• Spacing of prototypes: Leave enough time to incorporate learnings from each cycle into the next.
• Multiple prototypes – combine learnings from different types for complex projects.

Key takeaways

• Prototypes reduce risk and uncover hidden problems.
• Analytical prototypes are fast and flexible; physical prototypes reveal real‑world issues.
• Outsourcing prototypes can accelerate production readiness.

Organising for Product Development – Team Structures

Choosing the right team structure depends on the project’s complexity, degree of change, and need for cross‑departmental collaboration.

Functional NPD Structure

• Product moves sequentially from one department to the next (e.g., blueprint → casting → costing).
• Suitable for customised projects with minor changes and for projects requiring deep functional specialisation.
• Drawbacks: coordination issues, potential bottlenecks, no single owner of the project, long completion time.

Project NPD Structure

• Dedicated team works 100% on one product until launch.
• Common in startups and breakthrough projects.
• Advantages: short cycle time, excellent coordination.
• Disadvantages: experts are not shared across projects, functional expertise may be underutilised.

Matrix NPD Structure

• Dual reporting: team members report to a functional manager for routine tasks and to a project manager for new product activities.
• Suitable for complex, long‑gestation projects (e.g., automotive 2–3 years, aerospace nearly a decade).
• Two variants:

Matching Structures to Project Types

Also:

• The lead function should match the product’s dominant change area (e.g., R&D leads for technology‑dominant projects; design leads for ergonomics/aesthetics).
• Many companies stick to one dominant structure even when it mismatches the project type—this can hinder performance.

Key takeaways

• Functional structure works for simple, low‑change projects; project structure for breakthrough work; matrix for complex, long projects.
• Heavyweight matrix gives project managers strong authority; lightweight matrix keeps power with functional heads.
• Mismatch between structure and project type is common but costly.

Product Integrity

Product integrity is the total balance of product features that creates instant appeal for customers — the feeling that “it’s just right” or “they got it right.” It goes beyond functionality or performance; it is the harmony of the product or service with the user’s lifestyle. Organizations that create products with integrity reflect that integrity internally: a seamless pattern of organizing, coherent with strategy, and clarity across all levels on what to do (and what not to do) regarding new products and target customers.

Achieving Product Integrity

• Consistency across all aspects of the firm’s relationship with its target customers.
• Organizational coherence – efforts aligned with strategy, clear choices on products and customers.
• Leadership – effective leaders focus the team on meeting (and sometimes exceeding) user expectations, act as catalyzing forces, and help create powerful product concepts (the “soul” of the product) infused into every detail.
• Heavyweight project managers – on major long‑gestation projects, they drive integrity and know when a product is right (and do not tinker unnecessarily).

Two Dimensions of Product Integrity

Exam tip: Internal = “engineering harmony”; External = “user harmony.” Both are required for true product integrity.

Key takeaways

• Product integrity = consistency that creates an instant “just right” feeling.
• Requires organizational coherence and clear strategic choices.
• Two dimensions: internal (parts fit) and external (fits user).
• Effective leadership and heavyweight project managers are crucial.

---

Developing Services

Pure services are harder to develop and sell due to intangibility. Clients are often skeptical and unsure of results. Productizing a service – making it more like a tangible product – eases purchase, budgeting, and reduces perceived risk.

How to Productize a Pure Service

1. Give it a descriptive name, define its scope, fix time frame, and set a price tag.
2. Offer customized service packages tailored to different user groups.
3. Create interlinked service modules that can be purchased without prior commitment.

Productizing also allows the seller to reduce costs by templating the service.

Key takeaways

• Pure services are intangible → harder to sell; productizing makes them tangible.
• Steps: name, scope, time, price → packages → modular options.
• Benefits for buyer: easier budgeting, lower risk of cost overruns or poor results.

---

Product Service Systems (PSS)

A product service system (PSS) is a marketable combination of products and services that serves users better than either alone. It sits on the spectrum between pure product and pure service.

• Adding services to a product reduces commoditization and can yield higher profits.
• PSS can also reduce resource needs and wastage.

How PSS Creates Value

1. Cost reductions in utilization of assets.
2. Increased value of the product‑service combination.
3. Expansion of customer base by including more customers.
4. Changes in the competitive environment.

Three Types of PSS

Moving from product‑oriented → use‑oriented → result‑oriented can significantly change business models.

Key takeaways

• PSS combines product + service to reduce commoditization and increase profits.
• Four value drivers: cost reduction, value increase, customer expansion, competitive change.
• Three types: product‑oriented (own + maintain), use‑oriented (rent function), result‑oriented (pay for outcome).

---

Platform Thinking for Developing Services

Platform thinking leverages service subsystems that can be reused across multiple services, offering high variety at lower cost. A platform has a common architecture with shared subsystems and interfaces. Robust platforms can be extended to new business models and hold key capabilities and insights.

Example: Superseva (Bangalore)

Superseva offers 87+ concierge services at low prices. Its platform approach:

• Desk space at the entrance of major IT firms.
• Detailed data‑collection forms for each service, error‑proofed.
• Robust backend modules (e.g., proof of service) reused across many services.
• Common service‑tracking infrastructure → cost per new service drops.
• 11 free services (online bill payments, providing cash float) + 76 paid services at ~50 cents each.

Why it works as a monopoly:

• New competitors cannot offer 87+ services from the start.
• They cannot match the low rates (high setup costs).
• They cannot refine service quality quickly.

Superseva’s platform creates a virtual monopoly in its space.

Key takeaways

• Platform thinking: share modules and infrastructure across services → low cost per new service.
• Robust, failure‑proofed processes built over time.
• Example: Superseva uses free services for cash float, paid services at ultra‑low prices.
• Platform approach can create insurmountable competitive advantages.

Building Markets for Products & Services

Companies often struggle when a well-designed product fails to attract buyers. The core problem is usually not the product itself but a gap between the company's internal view (a great offer) and the customer's reality (no perceived need, hidden substitutes, cultural mismatches, or missing supporting infrastructure). Building a market means systematically identifying and fixing all reasons why potential buyers who can afford the product still will not purchase it.

Diagnosing the “No-Buy” Problem

Before any solution, a firm must ask a structured set of diagnostic questions to uncover hidden substitutes, cultural mismatches, and missing complements (spares, repairs, instruction-following ability). These go beyond surface-level objections.

Key diagnostic questions:

• Who specifically are your target customers? Who are not your target customers – and why?
• What are their unmet needs? How do they currently meet those needs?
• Does that current way hurt them in any way?
• What is your product as a solution? How will customers benefit? Can you quantify the benefit?
• How will the product earn? Who pays? What is the addressable market?
• Who are the most direct competitors? How does your product compare?
• Can you involve users to create better products?
• Can you leverage assets/competencies to gain advantage?
• Will the product generate sustainable high profits by expanding the user base over time?

Five Ways to Create New Demand for Existing Products

If the product already exists but demand is low, you can modify it along five dimensions:

Exam tip: These five levers (Utility, Efficiency, Safety, Aesthetics, Ergonomics) are a checklist for demand creation – not a theory. Memorise the list.

Key takeaways

• No-buy reasons are often hidden: substitutes, cultural mismatches, missing complements.
• Diagnostic questions must probe beyond stated objections into real customer behaviour.
• Five demand-creation dimensions: Utility, Efficiency, Safety, Aesthetics, Ergonomics.

---

Product Differentiation

Differentiation ensures a product stands out from rivals. Two fundamental strategies:

Horizontal Differentiation

Customers differ in tastes and needs. The firm identifies unserved tastes and serves them profitably. Example: The Indian saree – made in multiple colours and designs to appeal to diverse preferences.

Vertical Differentiation

Customers differ in willingness to pay (income). The firm identifies combinations of features and quality not served by competitors and targets them profitably. Example: Sarees in popular patterns are made with cheaper materials (lower price), while exclusive patterns are available only in silk (higher price).

Key takeaways

• Horizontal = different tastes (e.g., colours, styles).
• Vertical = different income (e.g., quality tiers).
• Both aim to profitably serve segments competitors ignore.

---

Creating Demand Without Latent Need – Case Studies

When customers see no need for a genuinely superior product, market creation is extremely difficult. Four real cases from N. Balasubramanian illustrate the approach:

Summary of Mr. Balasubramanian’s 12 Principles for Creating Demand Without Latent Need

1. Do not trust market research when no latent need exists – it will be unreliable.
2. Accept directional accuracy or grudging acceptance as progress.
3. De-risk failure: limit advertising initially; keep it low-key.
4. Educate channel partners and retail executives on product value.
5. Use own retail or unique channels if existing channels are averse.
6. Do not antagonise potential customers by telling them they are wrong.
7. Try unique promotions: trials, samples → build interest and word-of-mouth.
8. Experiment and demonstrate; directly address wrong perceptions.
9. Demonstrate value with cost comparisons in customer-oriented ways.
10. Respond with agility to complaints; extend customer trials over longer periods.
11. Communicate internally on the product plan and how negative results will be viewed.
12. Wait for the tipping point – advertise only when the market is ready to take off; premature advertising leads to rejection.

Exam tip: These 12 steps are a classic framework for launching truly novel products where no demand exists. The last step (wait for tipping point) is the most counter-intuitive and often tested.

Key takeaways

• No latent demand requires a long, patient process – not a quick launch.
• Tactics: educate influencers (vets, retailers), use trials, avoid antagonising, delay advertising.
• The tipping point is critical: advertise only when word-of-mouth is strong.

---

Choosing Between New Product Options

Four options ranked by cost and risk:

Key takeaways

• Always start with existing users and existing resources if possible.
• Option 4 (new resources + new users) is highest risk – avoid until exhausted lower options.

---

Intellectual Property (IP) Types

Five types of IP relevant to product development:

Patent Holder’s Rights

• Offensive right: exclude others from using, making, selling, or importing an infringing product.
• Defensive right: prevent any part of disclosed prior art from being patented by someone else.
• Barter: companies with many patents can cross-license rather than sue.

Patenting Process & Strategy

Process essentials:

• File within one year of first disclosure (use provisional patent).
• Delay final filing until product idea is refined.
• For multi-country, use a known patent attorney.
• Many firms file a provisional patent and never finalise – it’s cheaper.

Patent application components: scope of invention, prior art search, new claims, description, defence, refining claims, pursuit on challenge.

Patent strategies:

1. Prevent imitation of proprietary knowhow.
2. Defend patents via litigation.
3. Leverage patents to bargain with competitors and license for rents.
4. Buy out firms holding important related patents.

Patent fences: a wall of related patents to block easy imitation.

Key takeaways

• Five IP types: utility patent, design patent, copyright, trademark, trade secret.
• Patent = right to sue, not a guarantee of market monopoly.
• Strategy: fence, license, litigate, or buy the patent holder.

---

Dealing with Design & Digital Piracy

What to do if you invent: a raw idea has little value. File a provisional patent, then build and test to ensure the product is the best it can be. Patents can be sold or licensed.

Design piracy (physical products):

• Product enhancement: redesign locally to create significantly higher-value products aimed at upper-class/niche customers who buy originals.
• Service enhancement: add skilled services, bespoke flourishes, good product-service combos to lock in customers.

Digital piracy:

• Encryption prevents casual piracy.
• Allowing piracy can create a future market (e.g., Microsoft in China).
• Low-cost legal options make piracy unviable (e.g., Apple 99¢ songs; Moser Baar 3 movies for 50¢).

Key takeaways

• For design piracy: upscale redesign and service lock-in.
• For digital piracy: encryption, allow it as a loss leader, or undercut with low prices.

---

Nine Essential Components of an Effective Plan

1. Clear, fact-based executive summary.
2. New business model – justified.
3. How you will reach buyers and convert them.
4. Who implements the plan.
5. Risk coverage – all risks identified and addressed.
6. Fit with firm’s business goals.
7. Few critical numbers – only the most important.
8. Homework – answer obvious questions.
9. Credibility of product and team.

Common Mistakes

Key takeaways

• Plan must be concise, credible, and answer obvious questions.
• Most mistakes are customer-related (wrong segment, wrong pricing) or cost-related (overspending, wrong cost structure).

---

Why Hire a Consultant?

• Undiagnosed performance problem the firm cannot decipher internally.
• Known problem but inability to address it.
• Difficult strategic choice – firm cannot figure out how to choose.

What Clients Rely On Consultants For

1. Domain expertise in the strategy area.
2. Data synthesis across wide sources.
3. Creation of new, credible options.
4. Structuring choices and demonstrating the best option.
5. Implementation ability and showing early results.

Consulting Process

Proposal stage:

• Identify all issues underlying the observed problem.
• Interact with client to build hypothesis, quick diagnosis, redefine problem.
• Pre-consulting work to define scope and bid (skipping this leads to underbidding losses).

After contract sign-off:

1. Research to generate credible options.
2. Quantitatively model benefits and trade-offs.
3. Perform scenario/sensitivity analysis on each option.
4. Recommend solutions and show implementation path.

Quick win: a limited-scope demonstration (e.g., a prototype tested with customers) to prove the chosen solution works.

Key takeaways

• Consultants are used for problems the firm can’t solve alone.
• Their value: expertise, synthesis, option generation, structured choice, implementation.
• A “quick win” prototype after initial recommendation builds credibility.

Features of Appropriate Products

Appropriate products meet customer needs better than competition, with quality defined by the user, unique benefits, and real problem-solving ability. They reduce total in‑use cost over the product’s lifetime and have highly visible benefits. Novelty is a bonus, not a necessity.

Key attributes:

• Better quality (as users define it)
• Unique benefits and features
• Solves real problems better than alternatives
• Lower total cost of ownership
• Highly visible benefits to the user
• Novelty/innovativeness is desirable but secondary

Lessons from Product Examples

Failed product: Personal Internet Communicator (PIC) by AMD

• Launched 2004 at $250, aimed at emerging markets; divested in 2006.
• Reasons for failure: could not compete with cheap internet cafés; recurring high‑cost, slow internet subscriptions; a 3‑year‑old second‑hand PC cost <$200 locally and was easily serviceable. The PIC increased technology risk for users.
• Ironically won the 2006 Industrial Design Excellence Award.

Successful product: Nokia 3310/3315

• Sold 136 million units; priced low, robust, longest battery life, reliable, wide service support, good resale value.
• Non‑obvious success factors: no non‑call features, ideal for first‑time users, simple intuitive UI, largest font size available, natural for senior citizens and semi‑literates. Reduced risks, especially for first‑time users.

Successful product: Nokia 1100

• Sold >250 million units, followed the 3315.
• Developed after a field study in India (three weeks, rural and urban). User insights led to: torch light, removable cleanable surface (dust protection), better grip lines, clear red on‑off button.
• Design trade‑offs vs. 3315: smaller, harder for older eyes (smaller font), keypad seemed less robust, but cheaper to manufacture and easier to carry.
• Some customers still sought unsold 3315s.

Exam tip: The PIC failure vs. Nokia success illustrates that functional appropriateness (low risk, low total cost, ease of use, serviceability) matters more than industrial design awards.

Key takeaways

• Appropriate products reduce user risk (technology, cost, complexity).
• Simplicity, familiarity, and ease of use are critical for first‑time users.
• Field research reveals unarticulated needs (e.g., torch, dust‑proof surface).
• Design trade‑offs are inevitable; one product cannot satisfy all segments.

New Business Options in Emerging Markets

Building a base‑of‑pyramid market requires:

• Minimal feature products – no distracting extras.
• Intuitive design – no training needed at point of sale.
• Easily demonstrable utility.
• Robustness for harsh conditions, abuse, and misuse.
• Easy to try at low user risk.
• Modular, interlinked product series that customers buy over time.
• Innovative financing to match cash flows.
• Long warranty and support over product life.
• Smooth transition from previous products.
• Tight control of price‑performance equation – customers are value‑sensitive, not just price‑sensitive.

Six strategic options for new products in emerging markets:

Key takeaways

• Emerging‑market users are value‑sensitive, not merely price‑sensitive.
• Removing non‑essential features reduces risk and increases adoption.
• Different market segments require different entry strategies (access, price, perception).

Design Thinking for New Products

Why design thinking? School education develops routine left‑brain abilities (calculation, memorization). Work demands right‑brain abilities: asking good questions, interpreting unfamiliar texts, creative solutions, judgment. Design thinking combines left‑brain (linear, logical, analytical) with right‑brain (design, synthesis, context, pattern, artistic). Dan Pink: right‑brain abilities are more valued because they are rarer.

Right‑brain abilities listed:

• Design – craft novel unique solutions
• Storytelling – weave context and emotion
• Symphony – big‑picture strategic thinking
• Empathy – see from another’s viewpoint
• Playfulness – improvise with available resources
• Meaning – create significance and purpose

Design thinking cycle vs. typical engineering approach:

Engineer approach works well for simple users; fails with complex users.

Design thinking mindset

• Designers do not know enough initially; must start with users.
• User‑based, solution‑focused (not problem‑solving focused).
• Draws equally on logical reasoning and user‑context imagination.

The design thinking cycle:

1. Deep understanding of what users are trying to do.
2. Create easier, more enjoyable ways to achieve their goal.
3. Build broad perspectives to appreciate challenges.
4. Generate a range of potential solutions.
5. Rapid experimentation with quick cycles of user feedback.
6. Flexibility and openness to all ideas from users and stakeholders.
7. Multiple prototype cycles → novel solution that neither users nor designers could have thought up alone.

Exam tip: The core principle: “Thou shall not make any design sketches till thou meets the real users.” Empathy and iteration are non‑negotiable.

Key takeaways

• Design thinking is user‑focused, iterative, and builds on empathy.
• Engineer approach works for simple contexts; design thinking handles complex users.
• Rapid prototyping and user feedback are essential.
• Right‑brain abilities (storytelling, empathy, playfulness) are critical.

Soft Innovation and Hyper‑Competition

Soft innovation (Stoneman) is the creation of variants that affect aesthetic or intellectual appeal, not just functional performance. Examples: new book titles, packaging, marketing innovations, recorded music, food creations, delivery methods. Also includes smell, touch, color, intangibles. Price variations (e.g., mobile tariff deals, combo offers) are a form of soft innovation. Protected by design registrations, not patents. Standard commodity economics does not apply.

Hyper‑competition occurs when all players launch new products so frequently that no player can be profitable on average. Launching is costly and risky; not launching risks losing market share.

If few players → hyper‑competition may die out. If many players → may persist. Overall industry profitability declines because most new products are unprofitable at launch. Necessitates re‑examining the basis of competition.

Key takeaways

• Soft innovation differentiates through non‑functional appeal; protected by design registration.
• Hyper‑competition erodes industry profitability; firms must launch or lose share.
• Transformational hyper‑competition reshapes the competitive landscape permanently.
• In hyper‑competition, rethink the basis of competition.