Product Development & Design Thinking Flashcards
7 cards from real CPI practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Product Development & Design Thinking flashcards as text
What is the Kano Model used for in product development?
Answer: Categorizing features by how they impact customer satisfaction to guide prioritization
The Kano Model classifies features as Basic, Performance, or Delighter to reveal which investments drive the most satisfaction.
In a Stage-Gate process, what is the function of a 'gate'?
Answer: A structured decision point where projects are evaluated and either advanced, redirected, or killed
Gates serve as Go/Kill decision checkpoints that ensure only viable projects consume further resources.
What distinguishes a 'feature' from a 'benefit' when communicating product value?
Answer: Features describe what a product does; benefits describe the value or outcome users experience
Features are product attributes (what it has or does), while benefits articulate the positive outcome users gain from those features.
When should a product team conduct 'usability testing' versus 'concept testing'?
Answer: Concept testing validates early ideas for desirability; usability testing evaluates whether users can navigate and complete tasks in a working interface
Concept testing occurs early to test an idea's appeal, while usability testing occurs with a prototype or live product to assess ease of use.
What is 'co-creation' in the context of user-centered design?
Answer: Actively involving users or customers as creative partners in the design process
Co-creation engages users as active collaborators in generating and refining solutions, not merely as research subjects.
In the context of product roadmaps, what is the key difference between an 'outcome-based roadmap' and a 'feature-based roadmap'?
Answer: Outcome-based roadmaps organize work around goals and user/business outcomes; feature-based roadmaps list specific features to be built
Outcome-based roadmaps keep teams focused on the 'why' and remain flexible on solutions, while feature-based roadmaps can lock teams into predetermined solutions.
What is 'technical debt' and how does it affect product development velocity?
Answer: Shortcuts or suboptimal code decisions made for speed that accumulate and slow down future development
Technical debt is the future cost of rework created by choosing expedient solutions now over proper ones, which compounds and degrades development speed over time.