Overview:
In complex systems engineering projects, technical problems are interdependent and often masked by inter-related issues, making identification of the right problem highly challenging. Without resolving the right problem, technical issues are likely to accumulate which can lead to project cost and schedule overruns and may force acceptance of low-quality products/systems. The paper shows how application of Systems Thinking over the Systems Engineering processes can assist with the identification of the problem cause and thus resolution can assist to maximise the likelihood of good project outcomes.
Context
Symptoms of an underlying problem are often more visible leading to possible perception that they themselves are the problems. By spending time and effort addressing the incorrect problem, technical debt is accumulated which worsens the situation and further hindering project progress.
Purpose
The paper highlights typical symptoms indicating that there are possible technical issues that need to be resolved. The paper explores how the right problem can be identified for a specific project phase and scenario by asking the right questions. In addition, the paper emphases the benefits of utilising event-driven approach in the validation of engineering progress by gathering and analysing relevant data to minimise the risk of technical debt.
Approach
Typical Engineering project phases are tabled with a list of common pitfalls in each phase of the systems engineering lifecycle are discussed. Suggested questions to ask that are likely to lead to the identification of right problem, which is of most value, in that specific phase of the project.
Insights
The benefits of Systems Thinking application to assist with identification of the right problem within the project Systems Engineering framework, which is not explicitly discussed and is generally assumed in many project phases.