Learning Targets
- Identify stakeholders connected to a design problem.
- Collect user needs through research, observation, or interview-style prompts.
- Translate stakeholder information into design insights and possible requirements.
Focus question: How can understanding the user help engineers design a better solution?
Use this page with the lesson presentation, your engineering notebook, and the tools or evidence assigned for Investigate Stakeholders and User Needs.
You can identify stakeholders, collect user needs, and translate research into design insights.
Connect your response to the decision, evidence, or quality standard required for Investigate Stakeholders and User Needs.
This lesson is ready to move forward when the evidence meets this standard: Each proposed user need is supported by research evidence rather than team assumptions.
Stakeholders are people affected by the design, not just people who use it directly.
User needs describe what people must accomplish, avoid, understand, or experience.
Better research leads to better criteria and more meaningful design decisions.
Gather and organize information about the people affected by the design before defining the final problem.
Quality check: Each proposed user need is supported by research evidence rather than team assumptions.
Classify each interview statement so the team can separate user pain points, context, goals, and preferences.
| Stakeholder statement | Evidence type |
|---|---|
| “My fingers hurt after opening the latch several times.” | |
| “I usually operate it outside while wearing thick gloves.” | |
| “I need to finish the inspection in under two minutes.” | |
| “I would rather feel a click than rely only on a light.” |
Submission standard: Each proposed user need is supported by research evidence rather than team assumptions.
Use the lesson slides for guided practice, interactive checks, and the exit ticket.
Return to the IED course hub for units, resources, certifications, and current course information.