Define the Problem
Clearly specifying a knowledge gap, defining your end-users, narrowing to a focused and feasible question, explaining what you're measuring, and using experience to develop a plan that allows systematic investigation.
Tips to Define the Problem
Why is this component important?
Team consensus and understanding are most important when starting a project
Different ideas of what problem is being solved will cause delays
Defining roles on the team enhances efficiency
What are the goals of this step?
Achieve a collective team understanding of the project and the roles of team members
Imagine “the thing” you are developing being used in actual practice
| Common Pitfalls | Actions to Avoid Them |
| Assuming that everyone is on the same page at the beginning. | Use a formal process to achieve team consensus. |
| Rushing this step – it may seem like obvious work but can save time later. | Be detail oriented and methodical – focus on overall project goals. |
| Not taking into account the resources available and the scope possible. | Include all team members when scoping – define burden individually. |
| Trying to solve every problem and cover all the bases in the first version. | Be simple to start. |