Defining the problem is the first step in the engineering design process. One of the most popular inspirations for this strategy is the Albert Einstein quote “If I had an hour to solve a problem, I’d spend 55 minutes thinking about the problem and 5 minutes thinking about solutions.” What it implies is that defining the problem is the most important and yet difficult part of the engineering design process.
You may have seen engineers that tend to ignore this part. The allure of being focused on the potential solutions and disregarding the problem can be strong for some inexperienced engineers. A design process that fails in this step can be costly and time-consuming eventually.
Problem definition is necessary because the engineer and the client must agree on what the solution is seeking to address. If there is no agreement on design requirements, the chances of creating a solution to a strange problem are high. The client will most likely be dissatisfied with the design.
What is an engineering problem? We can view it as consisting of a need, a desired result, and a problem context. The need motivates the design engineer to search for answers. It should be as clear and concise as possible. On outcome, the design engineer needs to identify the qualitative requirements of the project. Using the required outcome, the engineer should be able to derive a quantitative representation of the customer’s needs.
It is also important for the engineer to understand the context of the problem. This is where the engineer and the team consider if they can tackle the engineering design.
In summary, defining an engineering design problem is a thorough exercise that needs the engineer to understand the context of the problem. Defining the constraints of the project and writing a problem statement are part of this step. When well executed, problem definition should help craft reliable ideas. This would pave the way for a satisfying design solution.