Design Review

Study Guide

Prepare to communicate engineering progress clearly, defend design choices with evidence, and turn feedback into useful next steps.

Go to Practice Check Certification Home

1. Purpose of a design review

A design review is a structured checkpoint used to improve a design before more time, material, or fabrication is committed.
The goal is not to “sell” a perfect idea; the goal is to expose reasoning, evidence, risks, and next steps.
Good reviews help teams catch problems early and make stronger engineering decisions.
Reviews should be based on project requirements, not personal preference alone.
Professional review behavior includes listening, clarifying, and documenting feedback.

2. Problem, criteria, and constraints

Start by restating the design problem and intended user or mission.
Criteria describe what success looks like.
Constraints are limits such as materials, time, size, tools, cost, safety, or performance requirements.
A strong review explains how the current design responds to the highest-priority criteria and constraints.
Do not present a solution without connecting it to the problem it is supposed to solve.

3. Evidence and design rationale

Use evidence such as sketches, CAD screenshots, prototypes, calculations, measurements, test data, or research.
Design rationale explains why a choice was made.
Strong rationale connects design decisions to constraints, criteria, data, or observed performance.
A decision matrix can support tradeoff discussions when multiple options are compared.
Claims should be backed by evidence, not only confidence or preference.

4. Visual communication

Use visuals that make the design easier to understand quickly.
Label important features on sketches, CAD images, test photos, or prototype pictures.
Show multiple views when one image does not communicate enough information.
Keep slides or review boards readable; avoid tiny screenshots and cluttered text.
Show failures and revisions when they explain how the design improved.

5. Risks, tradeoffs, and unknowns

A risk is something that could cause the design to fail, become unsafe, or miss a requirement.
A tradeoff occurs when improving one criterion may weaken another.
Unresolved questions should be named clearly instead of hidden.
Good teams identify what must be tested next.
Honest risk discussion builds trust and helps reviewers give useful feedback.

6. Feedback and professional response

Listen fully before defending a decision.
Ask clarifying questions when feedback is unclear.
Separate the design from personal identity; critique is aimed at improving the solution.
Record feedback even when the team does not immediately agree with it.
Thank reviewers and explain which feedback will be acted on first.

7. Action items and revision plan

A design review should end with clear next steps.
Action items should include the task, owner, due date, and reason it matters.
Prioritize action items based on safety, feasibility, major risks, and project deadlines.
Revision plans should describe what will change and what evidence will confirm improvement.
A review without action items is only a conversation, not an engineering checkpoint.

8. Documentation after the review

Update the engineering notebook or project documentation after the review.
Record decisions, feedback, action items, and planned revisions.
Attach or reference review slides, photos, sketches, or test data used in the review.
Mark design changes with revision notes so the design path is traceable.
Documentation should show how feedback changed the design or confirmed the next step.

Hands-on performance checklist

To earn the badge, students must complete a design review artifact or presentation that explains the problem, current solution, evidence, risks, feedback, action items, and documentation updates.

Take Practice Check Go to Final Test