Problem Statements for Engineers

• Writing a clear and effective problem statement is an important skill for engineers.
• Good problem statements need to be defined and have described qualities.
• "Classic" problem statements can be used as a tool.
• The Fine Whys root cause analysis tool can be applied to focus a problem.
• The problem can be structured as a "How Might We?" statement to facilitate a strong starting point for Ideation and an appropriate context for a wide range of solutions.
• Specific and actionable problem statements can be structured from broad, less-defined, problem-solving ambitions.
• ENGGEN 303 focuses on B2C Problems in order to facilitate learning of the Innovation process.
• Innovation does not yield an exact answer, it is practice based and grounded in theory.
• Structured Creativity is key
• Find creative confidence

Problem Finding

• Start with passion and interest, then understand the problem and ask questions.
• Problems should be refined using mind mapping, Fishbone diagrams, 5 whys, and root cause analysis.
• The final step is to create a "How might we" statement
• Root cause analysis is a tool to help in problem finding
• In problem space finding there are many problem spaces
• In the problem state there is problem space
• Value is found by understanding: the customer/user, and root cause

Double Diamonds Maps to DT Steps

• Design Thinking steps include: Empathise, Define, Ideate, and Deliver.

Considering Your User

• You have to consider your User's needs
• Consider your User's values

Point of View (POV)

• A Point Of View (POV) is a meaningful and actionable problem statement that allows to ideate in a goal-oriented manner.
• A POV involves reframing a design challenge into an actionable problem statement.
• Combine all knowledge about the users/stakeholders and their needs in the POV statement.
• Your POV should be an actionable problem statement that drives the rest of your design work.

Divergent and Convergent

• Problem space includes Discover and Define
• Solution space includes Develop and Deliver

The Innovation Process

• Tutorial 2 relates to Early Week 2
• Exploration, Identification, and Solutions are key

Root Cause Analysis

• One can do a Root Cause Analysis by asking the 5 Whys
• Then define the problem, Why is it happening? Why is that? and determine the result as the root cause

Exemplary Problem Statement

• Need should be justified to solve the problem
• To know what is being tried to be accomplished
• To well define scope of the issues
• To maximize creativity and innovation, do not prescribed within problem statement
• Know how solutions will be evaluated, or how success is measured
• Write clearly so that the audience and the objective can understand
• Analyse what action, what to change and the customer or user for the issue

Summary

• Narrow down to a specific problem
• Think critically while digging into the problem space and asking questions
• Never jump to conclusions, understand the real problem
• The 'Five Why's' are important to address root causes
• The HMW syntax must be broad enough while narrow enough that the solution can assist the overall goal
• Come back to the HMW statement a number of times and finetune it