Chapter 10 Flashcards

(40 cards)

1
Q

Q: What is a product protocol?

A

A: A signed cross-functional agreement specifying the benefits, performance, and marketing changes the final product must deliver

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q
  1. Q: Why does a protocol help reduce cycle time?
A

A: Clear targets let functions work concurrently without waiting for late clarifications.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q
  1. Q: Name two main purposes of a product protocol.
A

A: (1) Tell each department what to deliver, (2) synchronize all players toward common, measurable targets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q
  1. Q: List four typical items found in a product protocol.
A

A: Target market, product positioning statement, key attributes/benefits, competitive benchmarks.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q
  1. Q: Which attribute form is preferred in protocols—features, functions, or benefits?
A

A: Benefits, because they speak the language of customer value.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q
  1. Q: Define concurrent system in NPD.
A

A: All functions work in parallel, doing as much as possible at any time.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q
  1. Q: What are augmentation dimensions?
A

A: Extras beyond the core and formal product (e.g., warranty, service) that enhance value.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q
  1. Q: What is the biggest risk if coordination is poor in a concurrent system?
A

A: Major rework and project delays when late conflicts surface.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q
  1. Q: VOC definition in one sentence.
A

A: A prioritized, customer-language list of wants and needs organized the way customers think and use the product.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q
  1. Q: How many raw customer need statements does a good VOC process typically capture?
A

A: About 70–140.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q
  1. Q: What are affinity groupings?
A

A: Clusters of similar VOC statements (usually 15–25 groups) used to simplify and prioritize needs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q
  1. Q: First tool used in QFD?
A

A: The House of Quality (HOQ) matrix.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q
  1. Q: Main goal of QFD in one line.
A

A: Drive every downstream technical decision from genuine customer needs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q
  1. Q: Name two benefits of applying QFD.
A

A: Keeps teams customer-focused and forces cross-functional dialogue early.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q
  1. Product positioning –
A

“Product X is better because …” reasoning for the target user.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q
  1. Q: How does the product protocol “translate” VOC?
A

A: Converts grouped needs into measurable product specs and targets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q
  1. Q: List two ways to streamline a large QFD project.
A

A: Focus on key engineering characteristics or group them and assign each cluster to a specific team.

14
Q

Competitive comparison –

A

Benchmarking against reference products or policies.

15
Q

Potholes

A

Anticipated major risks listed in the protocol.

16
Q

Target market

A

The specific customer segment the product is built for.

17
Q

Concurrent engineering

A

Same as concurrent system in development.

18
Q

Core benefit

A

Fundamental value delivered.

19
Q

Formal product

A

Tangible features/functions.

19
Q

Augmented product

A

Extra services & experiences beyond the core.

19
Extra services & experiences beyond the core.
Measurable tech spec linked to customer need in HOQ.
20
Cycle time
Total calendar time from idea to launch.
20
HOQ roof
Shows trade-offs/correlations among engineering characteristics.
20
Delta team
Cross-functional group managing concurrent tasks
21
Importance rating
Customer weight for each need in HOQ.
22
Relationship matrix
Links customer needs to engineering “Hows.”
22
Signed agreement
Formal approval of protocol by all functions.
23
Cost-benefit analysis (QFD)
Evaluates bang-for-buck of each engineering improvement.
24
Pothole list
Early warning items inside the protocol.
25
Service protocol
Adapted version for service innovations (often lighter).
26
Protocol metric
Quantifiable target (e.g., weight < 1 kg, setup under 5 min).
27
Cross-functional communication
Cross-functional communication
28
Voice of engineer
Technical realities that meet VOC demands in QFD.
28
Voice of customer table
Raw, verbatim customer quotes with importance scores.
29
Customer driver
Need cluster guiding a set of specs.
30
K-J affinity diagram
Method for grouping VOC statements into affinity sets.