1 / 16

Resilience as a goal for quality management systems design

Resilience as a goal for quality management systems design. Petter Øgland, Department of Informatics, University of Oslo UKSS Conference, Sep 1.-3. 2008. Background and motivation.

otto-faulkner
Télécharger la présentation

Resilience as a goal for quality management systems design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Resilience as a goal for quality management systems design Petter Øgland, Department of Informatics, University of Oslo UKSS Conference, Sep 1.-3. 2008

  2. Background and motivation • Complex Adaptive Systems (CAS) seems to be an interesting framework for thinking about design of quality management systems (QMS) in turbulent organizations

  3. Observation/question • CAS has been used efficiently for creating distributed control systems to be used in artificial intelligence and robotics (Brooks, 1989, 2002; Kelly, 1994) • In organization theory, CAS appears to be dominantly used for criticising “command and control” (Stacey et al, 2000) or motivating BPR (Beckford, 2002), not for prescribing distributed control designs (QMS design) • How to use CAS for designing a QMS in a politically turbulent organization?

  4. Hypothesis • Rather than trying to explicitly design a QMS, perhaps it would be better to “grow” a QMS by “seeding” frameworks for self-control among various teams in the organization and then nurture and cultivate the frameworks

  5. Arguing CAS as not unreasonable strategy for QMS design • Some researchers argue that CAS and the mathematics of chaos and complexity breaks with earlier concepts of command and control (Stacey et al, 2000; Beckford, 2002; Dooley, 1995) • Simon (1996, chapter 7) argues against this in saying that CAS is a ”conservative extension” of earlier modes systems thinking • As ISO 9000 was originally developed for conventional systems thinking (Hoyle, 2006), Simon leads us to believe that CAS might be an equally suitable systems approach as any

  6. Design for empirical research(action research) • An “artificial intelligence” approach towards a CAS based QMS design was developed in one organization 1992-1999 (quality control of meteorological data) • A QMS is designed in another organization (NTAX), applying the same CAS approach now on a socio-technical system rather than just a technical system

  7. CAS design principle for QMS You & I System Environment Environment System Complex adaptive systems thinking (CAS) General systems thinking (GST)

  8. Airport weather data SYNOP System monitoring AWS Weekly and monthly climate statistics Quality Manager / Computer Programmer HIRLAM (weather forecast data) SONDE (weather balloon data) AANDERAA DNMI QMS topology email email email email email email email email

  9. Documentation control CobiT audits COBOL software control EFQM assessments Development life cycle quality assurance Quality Manager / Action Researcher ISO 9001/9004 assessments Controlling the revision of standards and methods Control of ITIL implementations NTAX QMS topology audit audit audit audit audit audit audit audit

  10. A personal assessment of the organization (system) • Management: A QMS is needed to satisfy external stakeholders, to manage and to improve, BUT it is often strategically better to hide faults than admit and improve • Workers: All others should follow standards, but personally I would like be flexibility and improvise • => People in quality management may easily end up as scapegoats

  11. NTAX QMS performance Rapid improvements Sudden collapse (political mistake) Beginning from scratch Redefined as action research

  12. What went wrong? • Audits and measurements generated tension and conflict (as expected and as needed) • In order to test methods before implementing and improving the quality unit, it seemed reasonable to apply “own medicine” (second-order cybernetics) • Surprise (to me): quality personnel and auditors at NTAX revolted against being subject to own methods

  13. Should the revolt have been anticipated? • Survey investigation and interview with 30 ISO 9000 experts at national quality conference: Would you, as an ISO 9000 consultant, apply ISO 9000 on your own organization?

  14. Why did the internal conflict within the quality department matter? • The quality department was organized under the projects department • The head of the projects department world view: Deliver projects on time within cost (quality = “good enough”) • In 2005 a new quality manager was appointed, but in 2008 he gave up quality management to rather devote his time to projects management (to feel appreciated)

  15. Insights for improved CAS design • The CAS approach might be very efficient (as the first years 2000-2004 indicated) doing assessments of the organization against ISO 9000, EFQM, CMM, ITIL, BSC, CobiT etc • As the CAS design places the quality manager (action researcher) in the role of ”environment” for making the ”system” grow quality awareness, it is necessary to have full protection • Protection comes from myopic attention to the people above (”your boss is your most important customer”)

  16. Conclusion: Top-down engineering + bottom-up evolution B. Work as “environment” for the “system” to develop strategies A. Focus on (1) goals of organization and (2) goals of immediate superior ISO 9001

More Related