Professional Documents
Culture Documents
Overview
Costly rework due to avoidable mistakes is often a key factor leading to product launch
delays. Quality leaders want to help catch these errors earlier in the process by getting
involved further upstream. However, resourcing constraints and resistance from new
product development (NPD) project teams often prevent them from having end-to-end
involvement. Instead of pushing for early involvement on all projects, quality leaders
should decide when and how to be involved in NPD projects based on the risks associated
with regulations, how new the product or process change is and the product or process
change’s potential business impact.
Key Findings
■ Fifty-one percent of quality errors are caught after new products move past the
design phase, creating costly rework and delaying launch times.
■ Quality’s early involvement is crucial for highly regulated products and those with
many new elements because it ensures NPD teams understand how to meet the
necessary requirements to successfully bring the product to market.
■ Products with the potential to most significantly impact the bottom line require more
integrated involvement from tenured quality professionals in early NPD stages.
Recommendations
■ Decide what stages to get involved in based on regulatory and novelty risks.
■ Work with business partners to determine the appropriate level of quality team
involvement based on the product or process’s potential impact on the business’s
bottom line.
Some companies believe the best way to launch products on time is involving only critical
personal during early NPD stages, so they resist quality’s involvement. This approach is
grounded on the idea that involving too many people slows things down. Conversely, other
companies recognize the value of quality’s involvement in the early stages. However,
quality struggles to meet the demand for early involvement — a problem that’s only
exacerbated with the increasing number of new product launches each year.
In either case, quality struggles to effectively provide the right level of support during the
early stages of every new project. Instead, the best quality leaders determine and
articulate when and how they should, and shouldn’t, be involved based on when they can
add more value. This approach works because:
■ Once quality clearly defines and articulates when and how it should, and should not,
be involved in early NPD stages, business partners that were initially resistant will
see the benefit of quality’s involvement.
■ It ensures quality most effectively allocates its limited resources.
1. When the quality function should get involved (that is, the stages in NPD that require
quality’s participation)
2. How much involvement quality personnel should have during those stages of NPD
(that is, how embedded quality should be in each step of the process and which
quality staff members should be involved).
Quality decides when to get involved and the amount of involvement based on regulations,
novelty and business impact.
To determine when and how much quality should be involved in early development for
each new product or process change, quality leaders should consider three risk factors —
regulations, novelty and business impact.
Interviews with over 80 quality leaders show that virtually all quality functions are
involved in NPD during the final three stages — development and testing, manufacturing
and production, and commercialization. However, quality’s involvement during the first
three stages is less common. While a majority of quality organizations are involved during
the design phase, only about half play a role in concept and creation and very few are
involved in ideation.
Rather than following this benchmark or overcorrecting and getting overly involved too
early, quality needs to assess if it is involved at the right time on the right projects.
Consideration 1: Regulations
The more heavily regulated the product, the earlier the quality function should be involved.
Early involvement ensures NPD teams know the relevant regulations before the design
work begins and the potential downstream implications of changes. This prevents
commercialization delays and additional costs from rework when making required,
significant compliance changes in later stages.
Quality can help NPD teams prevent regulation issues during early stages in the following
three distinct ways:
1. Identify regulatory implications. During concept and creation, quality can identify
existing and forthcoming regulatory requirements applicable to the concept
proposal. These considerations ensure NPD teams accurately understand and
design for compliance and select certified suppliers.
Consideration 2: Novelty
The second determining factor for when quality should be involved is novelty — how new
is the change, the environment or the team for a given new product or process design?
Design problems are more likely to occur when a design project is trying something
significantly new. Therefore, the earlier quality can help NPD teams think through and
identify potential implications of the new elements of the product or process, the more
likely the projects are to succeed.
Specifically, novelty in four different areas increases the risk of failure for a new product
or process:
■ Level of innovation of the design: Is the product or its components new, unique,
different, difficult (NUDD), next generation or incremental?
■ Product’s complexity: How intertwined are the elements of the product (e.g., creating
software versus embedding software into a legacy, physical product)? And, how
much experience do product teams have with individual and combined elements?
■ Impact of the product on processes or other products: How much does each new
design element impact preexisting products or processes?
■ Level of design team experience: How much experience does the NPD team (either
internal or external) have with the company’s design process and the product it is
creating?
Products with many new elements based on this assessment require quality’s early
involvement. Table 1 highlights the activities quality should conduct in predevelopment
and testing phases for products with many new elements or processes.
Failure Modes ■ Identify potential failure modes (areas where a failure
Process/ Identifier could occur).
Evaluating novelty is best completed during concept and creation, allowing quality the
time to assess the proposed product and identify related requirements and processes to
ensure they are met.
Rather than assuming its level of involvement should be the same for all projects, quality
should adjust how much it is involved based on the impact the project will have on the
bottom line. This approach ensures:
To determine the relative implications of failure, quality should consider two things:
■ Expected cost savings from scaling new processes created for the product
Based on this assessment, quality should place the most attention and resources on the
products that matter most. It can do that by adjusting how many staff members are
involved, which staff members and what role they take (see Figure 2).
Quality can use three factors to adjust its level of involvement to best match the business
impact.
For new products or processes that have a higher potential to impact the bottom line,
quality should deploy more of its most experienced staff. These staff members should act
as an integrated facilitator — embedded in the project team to ask probing questions,
validate tests and facilitate quality process execution. Often, quality also acts as the final
decision maker before the product moves to the next phase. This ensures costly flaws are
caught early on in the process and allows time for changes when business partners are
more receptive to iteration.
For projects with a lower potential impact on the bottom line than other projects in the
portfolio, quality should still be involved, but fewer team members with less experience
can be involved. Given the lower risk, they also do not need to be embedded in the project
and can instead act as advisors as issues arrive. This not only creates a lower-stakes
opportunity for newer team members to learn but also frees up resources for greater
involvement for other, more financially critical projects.
Endnotes
[1] “CEOs’ Curbed Confidence Spells Caution: 22nd Annual Global CEO Survey,” PwC.
[2] “J&J Still Has Much to Explore With Continuous Manufacturing,” BioPharma Dive.
Specification Translator ■ Translate customer and company expectations of product quality into critical-to-quality
aspects (CTQs).
■ Ensure design specifications are realistic given current manufacturing capabilities.
Failure Modes Identifier ■ Identify potential failure modes (areas where a failure could occur).
Quality Test Definer ■ Set product approval standards and development test components that ensure products
meet quality specifications.
■ Assist in identifying ways to improve quality in design when errors occur.
Process Educator Help NPD teams understand the quality processes and standards relevant to the product to
ensure they are met.
End-to-End Advisor Set short, targeted and frequently occurring design consultations to identify potential issues
People
early, and often, before they build up.