Design
Review: When the Best Time to Catch a Fatal Flaw Is Before You Build
Anything — Not After You’ve Built Everything
The Million-Dollar
Question Nobody Asked
Picture this. A team of engineers has spent fourteen months designing
a new automotive assembly — a structural component that will sit inside
every unit rolling off the production line. The CAD files are pristine.
The simulations passed with flying colors. The prototype met every spec
on the test bench. The customer signed off. Production tooling is
ordered. And then, three weeks before launch, someone on the shop floor
asks a question that no one in the design review ever asked:
“How are we supposed to hold this in the fixture when the
clamping arm is in the way?”
Silence. Then panic. The component is physically impossible to
manufacture as designed — not because it violates physics, but because
it violates the reality of the production cell. The fixture can’t grip
it. The operator can’t reach it. The robot can’t weld it from the
required angle without colliding with the part itself.
The redesign takes four months. The tooling is scrapped. The customer
receives a polite letter about “adjusted timelines.” And somewhere in
the wreckage of the project budget, a quiet lesson hides: this
was entirely preventable — if anyone had asked the right people the
right questions at the right time.
That is what a Design Review is for. And if you think you’re already
doing them, there’s a good chance you’re doing them wrong.
What Design
Review Actually Is — And What It Isn’t
Let’s clear something up right away. A Design Review is not a
presentation. It is not a status update meeting. It is not a checkbox on
your APQP timeline that you tick by gathering twelve people in a room
and watching a PowerPoint while they check their phones.
A Design Review is a structured, multi-disciplinary,
decision-gated evaluation of a design at defined stages of its
development. Its purpose is brutally simple: to identify and
resolve design deficiencies before they become manufacturing disasters,
customer complaints, or warranty claims.
The keyword is structured. Not casual. Not ad hoc. Not
“let’s look at this quickly.” A proper Design Review follows a defined
agenda, uses prepared checklists, involves the right stakeholders,
produces documented action items, and results in a formal decision:
proceed, proceed with conditions, or go back and fix it.
If your Design Reviews don’t produce at least a few uncomfortable
moments, at least a few action items that require real engineering work,
and at least one person saying “I hadn’t thought of that” —
you’re not doing Design Reviews. You’re doing theater.
The Anatomy of a Real
Design Review
A mature Design Review system operates at multiple gates throughout
the product development cycle. Each gate has a different focus, a
different set of questions, and a different panel of reviewers. Here’s
how it works in practice.
Gate 1: Concept Review
This happens when the design is still an idea taking shape. The
question isn’t “Is this design correct?” — it’s “Is this the right
design to pursue?”
The concept review examines: – Customer requirements
alignment — Does this concept actually solve the customer’s
problem, or are we designing something elegant but irrelevant? –
Technical feasibility — Can this concept be realized
with available technology, materials, and processes? –
Manufacturability direction — Is there a clear path to
producing this at volume, or are we committing to a design that requires
magical manufacturing? – Risk identification — What are
the obvious risks? What are the assumptions we’re making that could be
wrong?
The reviewers at this stage should include the lead designer, the
product manager, manufacturing engineering representation, and —
critically — someone who will actually have to build it. Not a manager.
A person who works on the line.
Gate 2: Detailed Design
Review
This is the heavy lift. By now, the design is fully specified —
drawings, tolerances, materials, surface treatments, the works. The
question now is: “Will this design work as intended, and can we
actually produce it consistently?”
This review goes deep: – Tolerance stack-up analysis
— Have we verified that the parts will assemble correctly when
everything is at the worst-case end of its tolerance? – FMEA
alignment — Do the design FMEA findings match what the design
actually specifies? Have the recommended actions been implemented, or
just documented? – Material selection validation — Are
the chosen materials appropriate for the operating environment? Have we
considered corrosion, fatigue, thermal cycling, UV exposure? –
Process capability match — Can our manufacturing
processes actually hold the tolerances we’ve specified? Do we have Cpk
data to prove it, or are we assuming? – Assembly sequence
verification — Can this product be assembled in the order we’re
planning? Are there access issues? Tool clearance problems?
Opportunities for mis-assembly? – Inspection
feasibility — Can we actually measure what we’ve specified? Do
we have gauges, fixtures, and instruments capable of verifying these
requirements?
The reviewer panel expands here. Add quality engineering, supplier
quality (if outsourced components are involved), metrology, and
potentially the customer’s technical representative.
Gate 3: Pre-Production Review
The design is locked. Prototype testing is complete. Now the question
shifts to: “Is our production system ready to produce this
design at quality and volume?”
This review examines: – Production process validation
results — Did our trial runs produce conforming product? What
was the yield? What were the failure modes? – Control plan
completeness — Does the control plan address all the critical
characteristics identified during design? Are the inspection frequencies
appropriate? – Operator instruction quality — Can a
trained operator follow the work instructions without ambiguity? Have we
verified this, or just assumed it? – Supply chain
readiness — Are all suppliers qualified? Have incoming parts
been measured and verified against specifications? – Packaging
and logistics — Will the product survive shipping? Have we
tested the packaging with actual product, not just empty boxes?
At this gate, production supervisors, logistics, and sometimes even
the customer’s quality representative join the panel.
The People Problem:
Why Design Reviews Fail
You can have the best checklist in the world, the most structured
agenda, and the most rigorous gate criteria — and still have terrible
Design Reviews. The reason is always the same:
people.
The Echo Chamber
In many organizations, Design Reviews are conducted exclusively by
the design team reviewing their own work. This is the engineering
equivalent of proofreading your own writing. You see what you intended,
not what’s actually there. The design team has lived with this design
for months. They’ve internalized its logic. They can no longer see its
flaws because those flaws have become invisible through familiarity.
The fix: mandatory outside reviewers. Bring in
people who have never seen the design before. Bring in the maintenance
technician. Bring in the supplier’s process engineer. Bring in the
person who runs the competitor’s teardown analysis. Fresh eyes find
familiar problems.
The Hierarchy Trap
In too many Design Reviews, the most senior person in the room sets
the tone — and everyone else follows. If the engineering director says
“this looks good,” junior engineers won’t raise their concerns. If the
project manager is under pressure to hit a deadline, the Design Review
becomes a rubber stamp.
The fix: anonymous pre-review input. Before the
meeting, collect written feedback from all reviewers independently.
Compile it. Present it. This prevents anchoring bias and gives quiet
voices equal weight.
The Confirmation Bias
Engineers are human. Once they’ve invested months in a design, they
want it to succeed. This creates a powerful unconscious bias toward
confirming that the design is good rather than aggressively searching
for reasons it might fail. Questions become soft. Challenges become
polite. “It should be fine” replaces “prove it works.”
The fix: assign a designated devil’s advocate.
Rotate this role. Give someone explicit permission — and the expectation
— to challenge every assumption, question every decision, and look for
the weakest link. This isn’t adversarial. This is how professionals
prevent disasters.
The Firehose
Some Design Reviews attempt to review an entire product in one
sitting. Four hours of dense technical content, hundreds of dimensions,
dozens of specifications, and by hour two, everyone has stopped
listening. Critical details get missed because human attention is
finite.
The fix: break reviews into focused sessions. Review
the structural design separately from the electrical integration. Review
the materials separately from the assembly process. Shorter, focused
reviews produce better outcomes than marathon sessions.
The Checklist:
What a Mature Design Review Covers
If you’re building or improving your Design Review process, here’s a
practical checklist that goes beyond the obvious:
Functional Requirements – [ ] All customer
requirements traced to specific design features – [ ] Performance
requirements validated through calculation or simulation – [ ] Interface
requirements with adjacent systems documented and verified – [ ]
Regulatory and compliance requirements identified and addressed
Design Robustness – [ ] Tolerance analysis completed
for critical assemblies – [ ] Design FMEA conducted with
cross-functional input – [ ] Worst-case scenarios identified and
mitigated – [ ] Safety margins verified for critical parameters
Manufacturability – [ ] Design for Manufacturing
review completed with production engineering – [ ] Process capability
assessed against specified tolerances – [ ] Assembly sequence verified
for accessibility and ergonomics – [ ] Error-proofing opportunities
identified and implemented
Verification and Validation – [ ] Test plan covers
all critical characteristics – [ ] Test methods validated (Gage R&R
completed where applicable) – [ ] Acceptance criteria clearly defined
and justified – [ ] Test sample size and frequency statistically
determined
Supply Chain – [ ] Critical suppliers identified and
assessed – [ ] Incoming inspection requirements defined – [ ] Supplier
PPAP requirements communicated – [ ] Material certification requirements
specified
Documentation – [ ] Drawings complete and correctly
dimensioned – [ ] Bill of materials accurate and complete – [ ] Change
management process defined – [ ] Revision control system in place
The Output: What a
Design Review Must Produce
A Design Review without documented output is a conversation, not a
review. Every Design Review must produce three things:
1. A Decision. The design either passes the gate,
passes with conditions, or fails. There is no “we’ll see.” Ambiguity is
the enemy of quality. The decision and its rationale are documented.
2. Action Items. Every open issue identified during
the review gets an action item with an owner, a due date, and an
acceptance criterion. Not “someone should look into this.” A specific
person will do a specific thing by a specific date and demonstrate that
it’s been resolved.
3. Updated Risk Register. Risks identified during
the review are logged, assessed, and tracked. If a risk was identified
and not mitigated, it doesn’t disappear — it follows the project until
it’s either resolved or consciously accepted with documented
justification.
The
Metrics: How Do You Know Your Design Reviews Are Working?
If you want to measure the effectiveness of your Design Review
process, track these:
- Design changes after gate freeze — If you’re making
significant design changes after the design is supposed to be locked,
your reviews aren’t catching issues early enough. - First-pass yield at production launch — This is the
ultimate test. If your first production runs have low yield, your Design
Reviews missed something. - Customer complaints traceable to design — Every
customer complaint that can be traced back to a design deficiency is
evidence of a Design Review gap. - Action item closure rate — If action items from
Design Reviews remain open at launch, the review process is functioning
as a suggestion box, not a quality gate. - Review attendance diversity — Count the number of
different functions represented at each review. More perspectives equal
better reviews.
The Cultural Foundation
Here’s the uncomfortable truth that most quality frameworks won’t
tell you: Design Reviews only work in organizations where people
feel safe raising concerns.
If an engineer identifies a potential design flaw and worries that
raising it will make them look incompetent or will anger the project
manager who’s already promised delivery to the customer — that flaw will
not be raised. The Design Review will sail through. And the flaw will
surface six months later as a production problem, a customer return, or
a field failure.
Building a culture where raising concerns is rewarded rather than
punished is not a soft skill. It is a hard engineering requirement. The
best Design Review checklist in the world is worthless if the people in
the room don’t feel safe using it.
This means leadership must model the behavior. When someone raises a
concern in a Design Review, the response should be “thank you — tell me
more,” not “we don’t have time for that.” When a Design Review delays a
project because legitimate issues were found, that delay should be
framed as a success, not a failure.
A Personal Reflection
In twenty-five years of quality work, I’ve seen Design Reviews that
saved companies millions and Design Reviews that were pure performance
art. The difference was never the checklist. It was never the conference
room. It was never even the quality of the engineering.
The difference was always honesty. Teams that were
honest about what they didn’t know, honest about what worried them, and
honest about what assumptions they were making — those teams caught the
fatal flaw before it was forged in steel. Teams that went through the
motions, nodded along, and prioritized schedule over substance — those
teams learned their lessons the expensive way, in production, in the
field, in front of the customer.
Design Review is not a meeting. It’s a discipline.
And like all disciplines, it only protects you if you practice it with
rigor and integrity — not when it’s convenient, but especially when it
isn’t.
Peter Stasko is a Quality Architect with over 25 years of
hands-on experience in automotive and manufacturing quality systems. He
specializes in building practical, no-nonsense quality processes that
actually prevent problems instead of just documenting them. His approach
combines deep technical knowledge with a relentless focus on the human
dynamics that determine whether quality systems succeed or become
shelfware.
