Jump to content

Situational Incompetence

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Magic links bot (talk | contribs) at 04:13, 18 July 2018 (Replace magic links with templates per local RfC and MediaWiki RfC). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Situational Incompetence applies when an otherwise experienced executive is placed in a position of authority or accountability for which they lack experience, training or specific skills. In this new role they are effectively incompetent and incapable of providing reasoned advice, guidance or management.

Situational Incompetence has implication for how leaders are selected for complex tasks requiring specialist domain knowledge and/or technical competence. This theory was developed with specific reference to the field of information systems, but may also apply to other disciplines requiring specific knowledge of unique technology in those domains (eg: science, technology, engineering, medicine, maths and etcetera).

The Research

Information Technology projects fail, and the cost of these failures is staggering. This concern has been highlighted and repeated for more than forty years. Yet, recent publications by the Standish Group (2017) have found that where ‘development projects exceed $100 million in labor costs, only 2% are successful, meaning on-time and within budget. Another 51% are considered challenged or over budget, behind schedule or didn't meet user expectations. The rest, 47%, are seen as outright failures'[1].

Two questions arise regarding IT project failure research. First, why is the success rate of IT projects so poor? And secondly, why, despite the efforts of many, the situation fails to improve? This problem is known as ‘Cobb’s Paradox’[2]. Cobb’s Paradox states: ‘We know why projects fail; we know how to prevent their failure — so why do they still fail?’. Cobb made the observation in 1995 while attend-ing a presentation by the Standish Group (authors of the Chaos series of reports) while working at the Secretariat of the Treasury Board of Canada. Cobb’s observation that “we know why projects fail” should not be taken in a literal, completely black and white sense, rather it should be considered to be a reference to the collective body of expert commentary, opinion, research and project practitioners that have offered solutions.

Cobb was not alone in observing that there is a great deal studied and written about project failure, and that consulting firms propose methodologies and remedies but little actual progress appears to have been made. The International Federation for Information Processing (IFIP) Working Party 8.6 ran a conference to address this specific issue asking ‘why our scholarship has not been more effective. Is the fault one of theory and inadequate understanding? Or is the problem one of knowledge transfer, the failure to embed research knowledge in the working practices of managers and policy-makers’[3].

The Case Study

The theory of "Situational Incompetence"[4] [5]was developed following an examination of the failed information systems project at Queensland Health to implement an HR and Payroll Solution between 2007 and 2010. The project was deemed by the Queensland Government to be such a significant failure that a Commission of Inquiry was formed to investigate the project and its failings.

The findings of the Commission of Inquiry state that ‘Its (Queensland Health payroll) failure, attended by enormous cost, damage to government and impact on workforce, may be the most spectacular example of all the unsuccessful attempts to impose a uniform solution on a highly complicated and individualised agency’[6].

The Commissionors' findings were that there exist two primary causes for the failure of the payroll project:

  1. unwarranted urgency, and
  2. a lack of diligence on behalf of state officials

The Commissions Report elaborated further on lack of diligence, describing it as ‘poor decisions made in scoping the Interim Solution, in their Governance of the project, and in failing to hold IBM to account’.

The Findings

The theme that was the most consistent throughout the project was that senior management was repeatably made aware of project risks and failings. Reports had been written about the whole-of-government project prior to the creation of the Queensland Health project that specifically enumerated the challenges and risks that needed to be kept front of mind to the QH project team. The prior research literature provided no plausible explanation to describe the fact that senior executives responsible for the direct execution of the project, and departmental executives with governance and oversight accountability apparently ignored all of the advice that they were presented with.

What emerged from the data was that the executives in charge of the project, those executives that operated above the hands-on technical level, were manifestly incompetent when it came to issues of information systems project management. The executives simply did not understand the information that was being presented to them, and interpreted professional concerns raised by Queensland Health team members as “personality conflicts”. These executives were presented with several formal reports outlining risks and issues, and acted in a manner that, under conventional wisdom, would defy rational explanation - the witness statements and project documents provide no evidence of any action being taken to address the issues raised. On more than one occasion IBM complained that employees of Queensland Health were trying to hold IBM to its contract and make IBM meet its obligations. IBM convinced senior departmental management that these staff were interfering in the project and senior management subsequently ordered their removal from the project.

Engelbrecht et al (2017)[7] suggest that inexperienced managers will seek advice and guidance from inappropriate sources.

Kruger and Dunning (2009)[8] offer the observation that the unskilled and unaware[9] are incapable of identifying their own failings, incapable of independently observing and learning from the competence of others, and incapable of identifying competence in others.

These findings have led this researcher to postulate a new theory: Situational Incompetence. Situational Incompetence applies when an otherwise experienced executive is placed in a position of authority or accountability for which they lack experience, training or specific skills. In this new role they are effectively incompetent and incapable of providing reasoned advice, guidance or management.

Situational Incompetence has implication for how leaders are selected for complex tasks requiring specialist IT domain knowledge and technical competence, it may also apply to other disciplines requiring specific knowledge of unique technology in those domains (eg: science, technology, engineering, medicine, and maths)

References

  1. ^ Thibodeau P 2017 “Pennsylvania sues IBM over troubled $110M IT upgrade”, http://www.computerworld.com/article/3180325/it-industry/pennsylvania-sues-ibm-over-troubled-110m-it-upgrade.html
  2. ^ Bourne. L., 2011, http://www.mosaicprojects.wordpress.com, "Cobb's Paradox is alive and well"
  3. ^ Dwivedi YK, Wastell D, Laumer S, Henriksen HZ, Myers MD, Bunker D, Elbanna A, Ravis- hankar MN, Srivastava SC, 2015b, “Research on information systems failures and successes: Status update and future directions”, Information Systems Frontiers, 17:143-157
  4. ^ CARLTON, D.. Competence versus Confidence in IT Project Leadership and its Impact on Project Outcomes. The Journal of Modern Project Management, North America, 5, may. 2017. Available at: <http://www.journalmodernpm.com/index.php/jmpm/article/view/240>.
  5. ^ CARLTON, D. Situational Incompetence: an investigation into the causes of failure of a large scale IT project publication description"Dark Sides of Organizational Behavior and Leadership," ISBN 978-953-51-6156-1.
  6. ^ http://www.healthpayrollinquiry.qld.gov.au
  7. ^ Engelbrecht J, Johnston KA, Hooper V., 2017 “The influence of business managers' IT compe- tence on IT project success”, International Journal of Project Management 35: p994-1005
  8. ^ Kruger J, & Dunning D., 2009 "Unskilled and Unaware of It: how difficulties in recognising one's own incompetence lead to inflated self-assessments"., Journal of Personality and Social Psychology, Vol 77 No 6. pp 1121-1134.
  9. ^ Ryvkin D, Krajc M and Ortmann A, 2012 “Are the unskilled doomed to remain unaware?”, Journal of Economic Psychology Vol.33.pp:1012-1031