The use of trade studies to evaluate alternative solutions is well understood within Systems Engineering. Using a similar approach to make sure that we are solving the right problem is less common. This presentation will describe why problem understanding can be so difficult and how to work with clients and internal stakeholders to better understand the real problems that need to be solved.
The double diamond model is a useful way to explain this (See figure in the attached document). The first diamond is about problem understanding, the second about solution selection. As the problem is explored, the situation becomes more complex, before being simplified. Conventional solution development is undertaken in the second diamond.
Systems engineers are often engaged to solve a precisely defined problem. Assuming that this is actually the problem that the client, or senior management actually wants is, however, risky. The initial problem analysis may: never have been done, been done poorly or be out of date.
This presentation will provide an overview of a key skill systems engineers should develop and employ. The presentation will cover:
• The financial, programmatic and safety implications of solving the wrong problems.
• Why as systems engineers we need to stay focussed on uncovering, confirming, and focussing on what the real problems are.
• How to identify the quality of problem analysis and how to convince different stakeholders to review their problem scoping.
• How to undertake problem analysis – what are the key activities to do, how to bring people with you and how to know when you have done enough
• Why problem analysis is hard for people to do and what you can do to make it easier for you and your stakeholders
The presentation will include specific real world examples from history and from the presenters’ recent projects. This will include the historical Death Ray example, as well as recent projects.