Product development lifecycle
Why This Matters
# Product Development Lifecycle Summary The product development lifecycle encompasses the systematic stages from initial concept through to market launch and beyond, including research, design, prototyping, testing, manufacturing, and disposal. Students must understand how designers employ iterative processes, user-centred design principles, and feedback loops to refine products whilst considering constraints such as time, cost, sustainability, and market viability. This topic is central to IB Design Technology examinations, frequently appearing in both Paper 1 (multiple choice and short answer) and Paper 2 (extended response), where candidates must analyse real-world case studies and justify design decisions using lifecycle terminology and appropriate evaluation criteria.
Key Words to Know
Core Concepts & Theory
The Product Development Lifecycle (PDL) is a systematic framework that guides a product from initial concept through to market launch and beyond. This iterative process ensures products meet user needs, remain commercially viable, and comply with regulatory standards.
Key Stages of the PDL:
-
Research & Analysis - Investigating market needs, user requirements, and existing solutions. Includes primary research (surveys, interviews) and secondary research (market reports, competitor analysis).
-
Design Brief & Specification - Defining the problem and establishing measurable criteria. The design specification lists quantifiable requirements (dimensions, materials, cost constraints).
-
Concept Generation & Development - Creating multiple solutions through sketching, modeling, and prototyping. Employs techniques like morphological analysis and SCAMPER.
-
Testing & Evaluation - Assessing prototypes against specifications using both qualitative (user feedback) and quantitative (performance data) methods.
-
Manufacturing & Production - Scaling from prototype to mass production, considering economies of scale and quality control systems.
-
Launch & Distribution - Market introduction, including marketing strategies and supply chain management.
-
Post-Launch Review - Monitoring performance, gathering feedback, and planning improvements or obsolescence strategies.
Key Terminology: Iteration refers to cyclical refinement based on feedback. Validation confirms the product meets user needs, while verification checks it meets specifications.
The PDL is non-linear; designers frequently return to earlier stages based on testing outcomes, making it fundamentally iterative and responsive to emerging insights.
Detailed Explanation with Real-World Examples
Understanding the PDL through real products illuminates its practical application. Consider Apple's iPhone development as an exemplar:
Research Phase: Apple identified smartphone market fragmentation—devices were either business-focused (BlackBerry) or had poor user interfaces. Market research revealed consumers wanted simplified, intuitive technology.
Specification Development: Key criteria included: touchscreen responsiveness <100ms, battery life >8 hours, thickness <12mm, and seamless iOS integration. These quantifiable specifications guided all subsequent decisions.
Concept Generation: Multiple prototypes explored different form factors. Early concepts included devices with physical keyboards (later abandoned) and various screen sizes. Iterative prototyping refined the glass-metal-glass sandwich design.
Testing: Extensive user testing in controlled environments revealed issues with antenna placement (later causing "Antennagate"). This demonstrates how testing identifies problems before mass production.
Manufacturing Decisions: Foxconn was selected for assembly, with component suppliers vetted for quality. Production scaled from thousands to millions, requiring sophisticated supply chain coordination.
Post-Launch Evolution: User feedback drives annual iterations—Face ID replaced Touch ID, camera systems evolved, and form factors adapted.
Analogy: Think of PDL as baking a new recipe. You research existing cakes (market analysis), write your recipe with precise measurements (specification), test different ingredient combinations (prototyping), have taste-testers provide feedback (user testing), perfect your method for scaling up (manufacturing), sell at markets (launch), then refine based on customer reactions (post-launch review).
Worked Examples & Step-by-Step Solutions
Example 1: Design Specification Development
Question: "A company wants to develop a sustainable water bottle for university students. Outline FIVE design specification points with measurable criteria. [5 marks]"
Model Answer:
- Capacity: Must hold 750ml ±50ml to meet daily hydration needs
- Material: Constructed from 100% recycled stainless steel for sustainability
- Thermal performance: Maintain liquid temperature ±5°C for minimum 6 hours
- Dimensions: Height ≤28cm, diameter ≤8cm to fit standard backpack pockets
- Cost: Retail price £18-£25 to remain competitive in student market
Examiner Note: Each point earns 1 mark. Ensure specifications are measurable (numbers, percentages) not vague ("good quality").
Example 2: PDL Stage Justification
Question: "Explain why prototyping is essential in the product development lifecycle, using a specific product example. [6 marks]"
Model Answer: Prototyping is critical for identifying design flaws before expensive mass production. Using ergonomic hand tools as an example:
Physical testing (2 marks): 3D-printed prototypes allow designers to assess grip comfort, weight distribution, and handle diameter with actual users, revealing issues computer models miss.
Cost reduction (2 marks): Discovering that a handle design causes hand fatigue during prototyping costs £500 in materials; discovering post-launch could mean £50,000+ in recalls and reputation damage.
Iterative refinement (2 marks): Multiple prototype iterations enable designers to test materials (rubber vs. silicone grips), refining based on quantitative data (grip strength measurements) and qualitative feedback (user comfort ratings).
Examiner Note: High-scoring answers justify with consequences and use specific examples.
Common Exam Mistakes & How to Avoid Them
Mistake 1: Treating PDL as Strictly Linear
Why it happens: Diagrams show PDL as sequential steps, creating miscon...
Cambridge Exam Technique & Mark Scheme Tips
Command Word Mastery:
"Outline" (2-3 marks): Brief points without deep explanation. Bullet points acceptable. ...
2 more sections locked
Upgrade to Starter to unlock all study notes, audio listening, and more.
Exam Tips
- 1.When asked about the lifecycle, always list the stages in order and briefly explain what happens in each. Think of it as telling a story from beginning to end.
- 2.Use a real-world example (like a phone or a new type of shoe) to explain each stage. This shows you understand how it applies in practice.
- 3.Be ready to compare and contrast the Linear (Waterfall) and Iterative (Agile) models. Explain when each might be more suitable.
- 4.Remember that the lifecycle isn't always a perfect straight line; sometimes stages loop back or overlap, especially in iterative models.
- 5.Focus on *why* each stage is important – what problem does it solve, or what benefit does it bring to the product development process?