Product Development

Introduction to the Module

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

Prerequisites: The product must satisfy three requirements

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

Three core topics in development

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

How development fits into the overall product process

This module does not specify the detailed practices behind “design and architecture” or “team management.”

Key takeaways

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

Product Design

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

Signs of Poor vs. Good Design

Definition of Design

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

Design‑Driven Innovation

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

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

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

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

Key takeaways

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

---

Product Architecture

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

Modular Architecture

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

Integral Architecture

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

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

Six Types of Modularity

Key takeaways

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

Design for Manufacturing (DFM)

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

Core DFM principles

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

Modular vs. Integral Architecture

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

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

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

Key takeaways

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

---

Swatch – From modular to integral (and back)

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

Shimano – From modular to integral

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

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

Key takeaways

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

---

Design for New Product Process (Other DFx Approaches)

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

Design for Speed to Market

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

Design for Differentiation

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

User‑Centric Design

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

Universal Design

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

Design for Corporate Identity

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

Design for the Environment (Green Design)

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

Key takeaways

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

Prototyping

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

Why prototype?

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

Form of prototypes

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

Role across product types

Multiple prototypes: learning cycles

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

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

Prototype strategies: build vs. buy

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

Participants in product design

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

Key takeaways

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

Innovation Strategy

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

Mach 3: Breakthrough from Twin-Blade

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

Design challenges of adding a third blade

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

Incremental vs. breakthrough debate

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

Development timeline and cost

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

Consumer Testing & Pricing

Product‑use tests with consumers gave decisive results:

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

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

Launch and Success

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

Competition and the Next Generation: Fusion

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

Key features of Fusion:

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

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

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

Key takeaways

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

Developing New Services

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

Productizing a Service

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

Key steps to productize a service:

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

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

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

Customised Service Packages

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

Key takeaways

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

---

Product Service Systems (PSS)

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

Why Use PSS?

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

Four Ways PSS Creates Value

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

Types of Product Service Systems

Three distinct models are based on ownership and usage:

Intuition:

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

Subscription models such as Netflix are closer to use-oriented PSS because the user rents access over a period, whereas pay-per-view is result-oriented.

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

Key takeaways

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

Platform Thinking for Services

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

Old Approach vs. Platform Thinking

Connection to Lead Users

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

Example: SuperSeva (Bangalore Concierge)

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

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

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

Key takeaways

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

Identifying the Product Development Team

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

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

Key organisational challenges for NPD teams include:

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

Types of Team Structures

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

Functional NPD Structure

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

Project‑Based NPD Structure

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

Matrix NPD Structure

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

Two sub‑types:

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

Choosing the Right Structure: Product Type → Structure Fit

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

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

Key takeaways

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

Structuring the Team

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

Two starting dimensions from earlier discussion:

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

Why structure matters

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

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

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

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

Managerial takeaways

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

Key takeaways

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

---

Product Integrity

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

Two dimensions:

Sources of product integrity

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

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

Key takeaways

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

Ownership and Empowerment

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

Where ownership comes from:

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

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

Key takeaways

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

Leadership Selection and Style

Selecting the leader (product manager):

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

Leadership characteristics vary by stage:

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

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

Key takeaways

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

Team Composition: Core, Ad Hoc, Extended

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

Three concentric team layers:

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

Key takeaways

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

Roles in NPD Teams

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

Key takeaways

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

Network Teams (No Dedicated Team)

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

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

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

Key takeaways

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

Training and Mindset

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

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

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

Key takeaways

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

Managing Globally Dispersed Teams (GDT)

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

Challenges:

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

Advantages (when managed well):

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

Success factors for GDT:

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

Key takeaways

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

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