When "Yes" is the Wrong Answer

Systems Engineering's value comes from doing effective pre-work to avoid later, expensive rework. There are many barriers to uptake of Systems Engineering, including the difficulty of abstract and holistic thinking and project time pressures. This paper focuses on the time pressures, and the usual desire to show positive progress in any form of review of a project. This leads to a behavior where there is a tendency to say "yes" in answer to a question because we know it is the desired answer. Inappropriate "yes" statements to questions like "Are the requirements complete?" result in a tendency to stop the pre-work, and start the solution stage pre-maturely or with false confidence. The paper proposes as a heuristic that the Systems Engineer recognizes that there are implicit dangers in answering "yes" to many review type questions.

[1]  Kelly C. Strong,et al.  THE* Rules of Stakeholder Satisfaction (* Timeliness, Honesty, Empathy) , 2001 .

[2]  Eric C. Honour,et al.  Systems engineering return on investment , 2013 .

[3]  J. Conklin Wicked problems and social complexity , 2003 .

[4]  Laurent Gasser 6.2.1 Function Durability over System's Life Span , 2008 .

[5]  Ricardo Valerdi,et al.  Heuristics for Systems Engineering Cost Estimation , 2011, IEEE Systems Journal.

[6]  Joseph P Elm,et al.  The Business Case for Systems Engineering Study: Results of the Systems Engineering Effectiveness Survey , 2012 .

[7]  Tom Gilb 7.6.4 Some Powerful Systems Engineering Heuristics , 2007 .

[8]  Dieter Scheithauer,et al.  4.5.3 V‐Model Views , 2013 .

[9]  Silvia Mara Abrahão,et al.  Requirements Uncertainty in a Software Product Line , 2011, 2011 15th International Software Product Line Conference.

[10]  Eberhardt Rechtin,et al.  The Art of Systems Architecting, Second Edition , 2000 .

[11]  David I Blockley,et al.  Doing it Differently , 2000 .

[12]  Thomas Maak,et al.  Relational Intelligence for Leading Responsibly in a Connected World. , 2005 .

[13]  David D. Walden,et al.  Systems engineering handbook : a guide for system life cycle processes and activities , 2015 .

[14]  Richard Beasley,et al.  4.3.1 The Barriers to Systems Thinking , 2012 .

[15]  Richard Beasley,et al.  8.3.1 Certainty, Risk and Gambling in the Development of Complex Systems , 2010 .

[16]  Peter Checkland,et al.  Learning For Action: A Short Definitive Account of Soft Systems Methodology, and its use for Practitioners, Teachers and Students , 2007 .

[17]  David Blockley,et al.  Doing it Differently: Systems for Rethinking Construction , 2000 .