Final Design Review Presentation: Project Summary

1. The Purpose and Narrative of a Design Review

A final design review, often called a Critical Design Review (CDR) in industry, serves a specific purpose. It's not about brainstorming new ideas; it's about demonstrating that your final design is complete, meets all requirements, and is ready for the next stage (in the real world, this would be manufacturing and procurement).

The most effective presentations tell a compelling story. A powerful and widely used framework for this is the Situation-Complication-Resolution (SCR) model.

We will use this SCR framework as the narrative backbone for your technical design review. Here's how it maps to an engineering project:

• Situation: The problem you set out to solve and the design requirements you established.
• Complication: The engineering challenges you faced—the process of designing, analyzing, and iterating to meet the requirements.
• Resolution: Your final, validated design, supported by calculations, FEA results, drawings, and a BOM.

2. Structuring Your Final Design Review Presentation

Now, let's build the detailed slide-by-slide structure of your presentation, using a standard CDR format as our guide. As you build your presentation, think about how each section contributes to the SCR narrative.

Here is a recommended structure for your project's final presentation, blending the CDR outline with our SCR narrative framework.

Part 1: The Situation (Setting the Stage)

1. Title Slide
   • Project Title (e.g., "Design of a 3-Axis Camera Slider")
   • Your Name and Title (e.g., "Design Engineer")
   • Event (e.g., "Final Design Review")
   • Date

*This is an example of a professional title slide for a Critical Design Review, clearly stating the project, team, and purpose of the presentation.*

2. Executive Summary (1-2 slides)
* Project Objective: Clearly state the problem you solved. What was the goal? (This is your "Situation").
* The Design: Show a high-level visual of your solution, like an annotated rendering or exploded view from Onshape. Briefly explain what it is and how it works.
* Key Features: Highlight 1-3 key features or results. (e.g., "Achieved 0.1mm positioning accuracy," "Reduced weight by 30% through FEA-driven topology optimization," "Modular design for easy assembly"). This gives your audience the key takeaways upfront.

3. Design Requirements Recap (1 slide)
   • Briefly list the 3-5 most critical design requirements from the start of your project. This reminds the audience what you were trying to achieve and sets the criteria for success.

Part 2: The Complication & Resolution (The Engineering Journey)

This is the core of your presentation. You'll walk the audience through how you arrived at your final design, showing your work and justifying your decisions.

4. Concept to Final Design (1-2 slides)

   • Briefly show the 2-3 concepts you brainstormed.
   • Explain why you selected the final concept (referencing your decision matrix from Module 11 is a great way to show a systematic approach).
   • Introduce the final design in more detail, perhaps with a short animation or a few key views.

5. Mechanical Design & Validation (3-5 slides)

   • CAD Walkthrough: Use visuals (renderings, section views) to explain key sub-systems and components. Highlight clever design features.
   • Analysis: Present the results of your most important hand calculation and FEA. Don't just show a colorful plot; explain what it means. For example: "The FEA showed a maximum stress of 150 MPa under a 10kg load, resulting in a factor of safety of 2.5, which meets our requirement of >2.0."
   • Risk & Manufacturing: Briefly mention one key finding from your FMEA and one key DFMA consideration you made. This demonstrates your awareness of the full product lifecycle.

*An excellent example of a detailed CAD visual used in a presentation. Annotations and clear layout help explain a complex assembly to the audience.*

Part 3: The Resolution (The Final Package)

This section proves the project is complete and ready.

6. Final Documentation (1-2 slides)

   • Showcase a key page from your drawing package, perhaps the top-level assembly drawing with callouts.
   • Display a screenshot of your finalized Bill of Materials. Explain that all components are specified for procurement.

7. Conclusion & Next Steps (1 slide)

   • Summary: Confidently state that the design is complete and meets all key requirements. Briefly restate your key achievements from the executive summary.
   • Next Steps: If this were a real project, what happens next? (e.g., "Procure all BOM items," "Assemble first prototype," "Develop test plan for prototype").

3. Crafting the Story Before Opening PowerPoint

A common mistake is to open PowerPoint or Google Slides and start making slides immediately. A more professional approach is to draft the storyline first in a text document. This helps you focus on the logic and flow of your argument without being distracted by formatting.

The video you watched earlier mentioned the "dot-dash" method.

• Dot (.): The main point or "action title" of a slide.
• Dash (-): The supporting evidence for that point (a chart, a CAD image, a key number).

When you string all the "dots" together, they should form a complete, logical story.

For your homework, I encourage you to try this. Open a text editor and write out the "dot-dash" outline for your presentation following the structure we've discussed today. This will make the process of creating the actual slides much faster and more effective.

Conclusion

Today, you've learned how to structure a professional engineering design review presentation. This is the culmination of your project, bringing all your design, analysis, and documentation work into a single, persuasive story.

Key Takeaways:

• A final design review aims to prove your design is complete and meets all requirements.
• The Situation-Complication-Resolution (SCR) framework provides a powerful narrative structure for your presentation.
• A standard CDR includes an Executive Summary, Requirements, a detailed Design and Analysis walk-through, and a summary of the final deliverables.
• Drafting your presentation's story using the dot-dash method in a text editor first ensures a logical and compelling flow before you begin creating slides.

Preview of the Next Lesson:
In our next session, we will focus on "Present design work using storytelling techniques to explain the problem, solution, and impact." We will build directly on the structure and SCR framework from today, and dive deeper into how to deliver your message effectively, create compelling visuals, and tailor your story for different audiences (like managers versus technical peers).