Engineering Design Process Steps

---

Why This Matters

The engineering design process is the fundamental framework that separates random tinkering from systematic problem-solving. In your intro course, you'll be tested on your ability to recognize which phase of the process addresses specific challenges, why iteration matters, and how constraints shape every decision from start to finish.

Each step builds on the previous one, but here's what you really need to internalize: the process is cyclical, not linear. Real engineering projects loop back through steps constantly as new information emerges. Don't just memorize the order. Know what each step accomplishes and when you'd need to return to an earlier phase.

---

Problem Framing: Where Every Design Begins

Before you can solve anything, you need to understand exactly what you're solving. These initial steps establish the boundaries and possibilities for your entire project. Poor problem definition is the leading cause of failed engineering projects.

Define the Problem

A good problem statement is specific and measurable. "Make it better" gives you nothing to design toward or test against. Something like "reduce the device's weight by 20% while maintaining its load capacity" gives you a clear target.

• Constraints are non-negotiable limits (budget caps, size restrictions, safety regulations). Criteria are goals you optimize for (lighter weight, lower cost, easier to use). You need to know the difference.
• Stakeholder needs drive the entire process. Engineering exists to solve human problems, so understanding who will actually use your design is foundational.

Research and Gather Information

• Background research prevents reinventing the wheel. Existing solutions, patents, and technical literature show what's been tried and what works.
• Data collection includes technical specifications, material properties, cost factors, and environmental conditions relevant to your problem.
• Stakeholder engagement at this stage reveals requirements that aren't obvious from the problem statement alone. Interviews and surveys capture real-world needs that pure technical research won't uncover.

---

Ideation: Generating and Selecting Solutions

This is where creativity meets critical thinking. You need to generate many possibilities before narrowing to one: divergent thinking (expanding options) followed by convergent thinking (narrowing them down). Jumping straight to a single solution is one of the most common engineering mistakes.

Brainstorm Potential Solutions

• Quantity over quality initially. The goal is generating as many ideas as possible without filtering. Judging ideas too early kills creativity in this phase.
• Structured techniques like mind mapping, SCAMPER, or brainwriting help teams move beyond obvious solutions. For example, SCAMPER prompts you to Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, or Reverse elements of existing ideas.
• Diverse perspectives strengthen brainstorming. Team members with different backgrounds and expertise produce more varied and robust solution sets.

Select the Best Solution

Once you have a pool of ideas, you need a systematic way to choose. This is where you switch from open-minded to analytical.

• Decision matrices (also called weighted scoring) let you rate each solution against your criteria and constraints. You assign weights to each criterion based on importance, score each solution, and multiply. The highest total score points to your strongest option.
• Feasibility analysis asks whether a solution can actually be built given your resources, timeline, and technical capabilities.
• Trade-off decisions are inevitable. No solution is perfect, so selection means choosing which criteria matter most and accepting compromises elsewhere.

---

Prototyping and Testing: Making Ideas Real

Ideas on paper mean nothing until they're built and tested. This phase transforms concepts into physical (or digital) reality and reveals whether your solution actually works. The prototype's purpose is to learn, not to impress.

Create a Prototype

• Prototypes are learning tools, not final products. They should be quick and cheap enough that you're willing to change or discard them.
• Fidelity levels range from low (cardboard mockups, rough sketches) to high (functional models with real materials). Match fidelity to what you need to test. If you're checking whether a shape fits in someone's hand, cardboard works fine. If you're testing structural strength, you need something closer to the real thing.
• Focus on key features that address your core problem. Don't waste resources on cosmetic details that won't affect your testing outcomes.

Test and Evaluate the Prototype

• Controlled testing isolates variables so you know why something works or fails, not just that it does. Change one variable at a time.
• User testing reveals usability issues that engineers often miss. Real users interact with designs in unexpected ways, and their feedback is data you can't get any other way.
• Document all results, including failures. This creates the evidence base for your next iteration and your final communication. If you didn't write it down, it didn't happen.

---

Iteration and Communication: Completing the Cycle

Engineering is never "one and done." The best designs emerge from multiple cycles of refinement, and even the best solution is worthless if you can't communicate it effectively to others.

Refine and Optimize the Design

• Iteration is not failure. Returning to earlier steps based on test results is exactly how the process is supposed to work. A test might send you back to prototyping, back to brainstorming, or even back to redefining the problem.
• Optimization balances competing factors like performance, cost, manufacturability, and sustainability. Improving one often affects others. Making something stronger might make it heavier and more expensive.
• Multiple cycles typically produce better results. Plan for at least 2-3 iterations in any serious design project.

Communicate the Final Solution

Your design only has impact if others can understand, evaluate, and reproduce it.

• Technical documentation includes specifications, engineering drawings, assembly instructions, and testing data.
• Visual communication through diagrams, CAD renderings, and physical models makes complex ideas accessible to non-technical stakeholders like clients or managers.
• Persuasive presentation connects your solution back to the original problem and demonstrates how it meets your criteria and constraints. This is where you close the loop.

---

Quick Reference Table

---

Self-Check Questions

1. A team builds a prototype and discovers it doesn't meet one of their key constraints. Which earlier step should they return to, and why might they need to go back even further than prototyping?

2. Compare and contrast the mindset required for brainstorming versus solution selection. Why is it problematic to combine these steps?

3. Which two steps both involve stakeholder engagement, and how does the purpose of that engagement differ between them?

4. An engineering team presents a final solution but can't explain how it addresses the original problem statement. Which steps in the process did they likely rush or skip?

5. If an FRQ describes a product that works perfectly in lab testing but fails when real users try it, which phase of the process was inadequate, and what should the team have done differently?