PM BOKs and the knowledge challenge…

At a recent event in the PM UK APM Knowledge SIG November 2012 an interesting conversation took place.   To watch the outcome click on http://www.apm.org.uk/news/courageous-conversation#.UXE_pLXfCSp.

http://www.youtube.com/watch?v=7OuvgICPGC8&feature=player_embedded#!

Great words by Judy Payne and Jon Whitty, pictures by Vanessa Randle and Tech by Ian Sabell.

I currently struggle with the BOK approach and this clip says it all…
We are not learning our PM lessons…
We need to find another way…

Stephen
http://www.pmlessonslearned.info/

Update 25/4/2013: Check out also the related discussion in Linkedin – fascinating!

 

 


Share in top social networks!

Lessons Learned from a Nuclear Accident (A new addition to the lessons learned available to the general public)

Lessons Learned from a Nuclear Accident (A new addition to the lessons learned available to the general public)

As most of you know, I am always on the look out for public domain lessons learned. While researching for a new journal paper I came across the
Institute of Nuclear Power Operations (INPO). The INPO was created as a result of the Three Mile Island event. The INPO help to identify precursors, disseminate lessons learned and best practices, and generally ensure that every plant operates with the best knowledge available (and also to forestall further regulation). The World Association of Nuclear Operators performs these tasks globally. Although knowledge development and dissemination have been successful overall, problems continue in this industry, which is under continuous scrutiny by regulators and a wary public (Carroll 2004).

Nuclear Energy Institute
INPO Updates Report on Lessons Learned From Fukushima Daiichi Accident
Lessons Learned from the Nuclear Accident at the Fukushima Daiichi Nuclear Power Station

The lessons learned make an interesting read…..

Looks like to me the SLLCK Model could help?


Share in top social networks!

Doesn’t a new NASA knowledge policy just mean another layer of bureaucracy?

Doesn’t a new knowledge policy just mean another layer of bureaucracy? Looking forward to the new policy http://go.nasa.gov/15QrjzO

“…Where knowledge is concerned, the primary concern is ensuring that we manage the knowledge resources that enable us to execute the agency’s programs, projects, and missions. Up to now, the focus of NASA’s knowledge policy has been on capturing lessons learned in the Lessons Learned Information Systems (LLIS) database. As I’ve written in the past, there is a rich diversity of knowledge work going on across the agency, from the Shuttle Knowledge Console at JSC to the case studies developed at Goddard Space Flight Center. Our policy needs to reflect the breadth of knowledge management efforts already in place across NASA.

In January, the CKOs and points of contact from the centers, mission directorates, and cross-agency support organizations (such as the NASA Engineering and Safety Center and the NASA Safety Center) got together at the Academy Center for Excellence at Kennedy Space Center to forge a new knowledge policy for NASA. We left the meeting with a working draft that is being internally reviewed and revised. Two weeks after that meeting, the NASA Program Management Council granted us authority to proceed with developing this new knowledge policy. In the months ahead, I will be writing more about what the knowledge policy covers and how it should ultimately help NASA practitioners be able to find the knowledge they need when they need it. Stay tuned”

Sure will be….

 

 


Share in top social networks!

Lessons Learned from failures (A new addition to the lessons learned available to the general public)

Lessons Learned from failures (A new addition to the lessons learned available to the general public).

success_failure

Government and business need to successfully manage programs and projects, to learn from success and failure, and to capture, disseminate and apply lessons learned (Duffield & Whitty 2012). Lessons from failures are a special class of Lessons Learned.

The term failure is defined as ‘a lack of success in doing or achieving something, especially in relation to a particular activity (Collins 2001); or ‘omission of occurrence or performance, or a failing to perform a duty or expected action’ (Merriam-Webster Online Dictionary 2010).

Often individuals and organisations prefer success over failure due to the rewards brought by success. Even discussions of success are more welcome, and we are motivated by success more than by failures. We keep away from discussing failures because blame is usually accompanied with such a discussion. From the collective point of view, project teams often know they are in trouble, however they take no or minimal effort to resolve errors as owning up to failure may cause shame. So not unexpectedly, we tend to hold close to successful experiences and avoid stories of failure. This favouritism leads to a disparity between success and failure as sources of learning’s. Failures are necessary in the sense that they are essential prerequisites for learning, especially for learning lessons to prevent the mistakes of the past.

As you would know from this blog I keep a list of lessons learned available to the general public. I recently came across a Failure Knowledge Database (FKD) hosted by the Japan Hatamura Institute for the Advancement of Technology (Japan Science and Technology).  The work of Dr Yotarou Hatamura makes interesting reading.

Enjoy the lessons :-)

Stephen

Image courtesy of Stuart Miles at FreeDigitalPhotos.net


Share in top social networks!

Lessons learned debate turns to competitive advantage. Have your say… (from a Linkedin post) Part 1

Lessons learned debate has provided an interesting set of views, all focused in the right direction.

My latest comments are:  …Agree with Andrew, great to see the thread alive and thanks to Chris, Judfor their feedback. Chris, I am all for innovation, just that we need to be careful with the change process approach in learning lessons, as I have seen a couple of times that the leaning of a process may come back and bite you in the future, if you’re not careful. (A lesson learned for me). Judy, culture looks to be the key cause of failure in the lessons learned process, which is why I am looking for alignment to other culture experiences that may be able to add value to the project management lessons learned process. The just culture work of Sidney Dekker may also be of interest. On the question ‘lessons Learned’ (I really don’t like this label – can we call it something else? ) sends me down the path to why in am researching about lessons learned. For some reason, Project Management methodologies and PM knowledge books seem to only use the term ‘lessons learned’? Perhaps the Project Management community needs to shift the focus to more knowledge management, which will open up the language we use?  I like the work of Milton and Krammer in the KM space for projects. On the PMO front, having managed a functional PMO with 130 project managers, the trouble I see is you can lead a PM to best practice (…that has incorporated lessons learned) but you cannot make them follow it…hmm culture…people?  We as a PM community need to learn lessons and not repeat mistakes of the past.

Thanks for sharing, Stephen


Share in top social networks!

What are the impediments to sharing project knowledge?

I need your help. What are the impediments to sharing project knowledge?

don’t have time / takes too much time
not invented here
divisional stove pipe
geographical scatter
people afraid that sharing will make them less valuable
unwillingness to share
leadership
lack of trust
legal constraints
culture
systems
memories fade
people don’t want to appear vulnerable and stupid by admitting to mistakes
difficult to find what went wrong
we look at others as inferior to us
internal politics
lack of an actual organizational process to identify knowledge learned
lack of an actual organizational process to communicate knowledge learned
post-implementation audits are not done
takes too much time to document lessons learned
no way to classify lesson for easy retrieval
No one is assigned the responsibility
the lessons won’t apply to my projects
lessons Learned are not seen as useful
to use lessons learned would reflect badly on my reputation
unbiased information is not forthcoming
teams wont share mistakes and dirty laundry
Time / Schedule pressures – “Fire Fighting Mode” “Leave it until  later”‘
Costs involved
Don’t want to draw the crabs/seagulls
“Dangerous Attractiveness” of immediate fix
not trained in the use of software tools

What am I missing?

Regards, Stephen


Share in top social networks!

PMLLblog summary of Knowledge Conversion

A key element of KM is the knowledge conversion process. Nonaka and Takeuchi (1995) developed four modes of knowledge conversion based on cognitive psychology known as the SECI model (socialization – tacit to tacit / externalization – tacit to explicit / combination – explicit to explicit / internalization – explicit to tacit). They also state that the knowledge transformation is interactive and spiral based. They further note that an organisations knowledge is produced in a active and continuous interaction between explicit and tacit knowledge. When consideration is given to the enabling conditions of the four modes of knowledge, Nonaka and Takeuchi (1995) derived an integrated five phase model of an organisational knowledge conversion process. The difficulty of transferring tacit to explicit knowledge on projects is frequently discussed and most authors refer to the importance of externalisation mode of the SECI model (Bresnen et al. 2003; Fernie et al. 2003; Holste & Fields 2010; Keen & Tan 2007; Nonaka 2007; Nousala, Hall & John 2007; Reich & Wee 2006).

Firestone and McElroy (2003) indicate that the SECI model (Nonaka & Takeuchi 1995) may be incomplete. The oversight is that the SECI model neglects to consider ‘implicit’ knowledge. Firestone and McElroy (2003) maintain that tacit knowledge is inexpressible and there can be no conversion from tacit to explicit, whereas implicit knowledge can be converted to explicit. Keen and Tan (2007, p. 4) refer to implicit knowledge as ‘…what we take for granted, rarely think about and are surprised to find that others do not share’. Srikantaiah et al. (2010, p. ix) refers to implicit knowledge as ‘…knowledge that is not captured in documentary form but in practice could be’. Polanyi (1958) makes reference to implicit knowledge so it is interesting to note that Nonaka and Takeuchi (1995) made no provision for implicit knowledge. Wilson (2002), Keen and Tan (2007) and Srikantaiah et al. (2010) propose to include implicit knowledge as the link between explicit and tacit knowledge. Additionally, Day (2005) states that implicit and tacit knowledge are often synonymous terms and he attempts to clear up the implications for KM. The challenge with knowledge conversion and the lessons learned process is the ability to capture and transfer/disseminate the tacit/implicit knowledge subject as the KM project management process is primarily explicit in nature.

What are your thoughts on Knowledge Conversion? Have I missed something?

The next post will focus on Learning and Organisational Learning.

Stephen


Share in top social networks!

PMLLblog summary of Knowledge Management (KM)

During the 1980s individuals and organisations began to value the role of knowledge in competitive business and industrial environments. A number of reports emerged during the late 1980s in the public domain focussed on how to manage knowledge explicitly (Wiig 1997). During the 1990s various KM journals and conferences started to appear with an exponential growth and the knowledge focus started to drive the development of KM frameworks and literature (Hasan & Handzic 2003; Hislop 2005; Wiig 1997). Some of the major approaches to KM frameworks were identified by Nonaka and Takeuchi (1995) (knowledge processes), Nonaka and Kono (1998) (enablers framework), and Alavi and Leidner (2001) (six knowledge perspectives and ten knowledge area’s). O’Dell and Grayson (1998, p. 6) from the American Productivity and Quality Center (APQC) describes KM as ‘…a conscious strategy of getting the right knowledge to the right people at the right time and helping people share and put information into action in ways that strive to improve organizational performance.’

Edwards et al. (2003) conducted a survey of KM academics and practitioners which highlighted the following most influential authors in the domain of knowledge management: Nonaka; Nonaka and Takeuchi; Davernport and Prusak; and Snowden. Edwards et al. (2003, p. 60) further concludes that the single most important challenge to KM is ‘…to produce a coherent and cohesive body of theory, based on empirical evidence’.

Here in Australia, KM became very active early in 2001 when Standards Australia formed a technical writing committee to develop the Australian Knowledge Management Standard. The first edition of the Standard was released in 2003 (Standards Australia 2005) and provided clear KM definitions. There is a general feeling that a KM definition is difficult to achieve and that many avoid defining it (Firestone & McElroy 2003). Firestone and McElroy have identified a KM definition ‘specification gap’ and they prefer the term Knowledge Life cycle (KLC) as the new KM and are critical of many KM definitions by influential authors. Firestone and McElroy also conclude that publishing standards for KM are seriously premature as most of the KM literature fails to make the distinction between KM and knowledge processing. Burford and Ferguson (2011) researched Australian government organisations and found that most participants had not heard of the Australian KM Standard and identified a significant gap between KM practice and the Standard. An observation of the Australian KM Standard with respect to the lessons learned is that the Standard does not reference the lessons learned process. This does provide a problem and limitation in a project perspective when using the standard with other current PM knowledge sources.

Across the globe many organisations in the public and private sectors are now recognising KM as being of central importance to advanced economies and organisational performance (Hislop 2005; National Audit Office 2009). Nousala et al. (2009) reports that it is hard to implement the KM process in organisations that are project based, as setting up activities across stove-pipe organisations and profit cost centres is challenging. However it is clear that KM in project based organisations is critical to keep up the competitive advantage (Ajmal, Kekäle & Takala 2009; Love, Edum-Fotwe & Irani 2003; Nousala et al. 2009).

Prusak (2011) suggests that the knowledge management principles developed in the mid-1990s and early-2000s were developed with information in mind and not knowledge and that is one of the key reasons that knowledge management efforts have run into problems. Prusak (2011, p. xii) further states that we now know different things about working with knowledge:

  • Knowledge is better understood as a flow. It is highly dynamic, non-linear, and difficult to measure or even manage. Working with it entails new techniques that we are still learning about.
  • Although technology surely has its place, working with knowledge is primarily a human activity needing human organization and understanding.
  • Knowledge in organizations is profoundly social and best managed in groups, networks, communities, and practices.

O’Dell and Hubert (2011, p. 2) describe the new edge in KM based on APQC research and benchmarking activities and define KM as ‘…a systematic effort to enable information and knowledge to grow, flow, and create value’. The new forces affecting KM are: digital immersion (multitasking); social computing; evolving demographics and dynamics; mobile devices and video (O’Dell & Hubert 2011). O’Dell and Hubert state that a KM program needs to include the teachable moment (when a person is most open to learning) and the management of knowledge above and in the flow of work (which is focused on making KM part of the work process).

Snowden (2002) suggests that we are getting to the end of the second generation of KM (SECI model of Nonaka and Takeuchi). Snowden (2002, p. 2) proposes that the third generation of KM ‘…requires the clear separation of context, narrative and content management and challenges the orthodoxy of scientific management’.

Wiig et al. (1997) identified the lessons learned process as a key KM practice. The KM life cycle when applied describes the lessons learned cycle and it is therefore proposed that by understanding the KM theories we further develop our understanding of the lessons learned process around the areas of knowledge flow, people, organisation structure and technology.

What are your thoughts on Knowledge Management? Have I missed something?

The next post will focus on Knowledge Conversion.

Stephen


Share in top social networks!

PMLLblog summary of Knowledge

‘What is knowledge?’ represents a question that humankind has grappled with for centuries at least back to Plato and Aristotle (Hislop 2005; O’Dell, Grayson & Essaides 1998). The current day knowledge exploration is attributed to Drucker (1993) (knowledge as management resource and power), Wiig (1997) (knowledge as a form of belief), Polanyi (1958, 2009) (distinction between tacit and explicit knowledge) and Davenport and Prusak (2000, p. 5):  Knowledge is a fluid mix of framed experience, values, contextual information, and expert insight that provides a framework for evaluating and incorporating new experiences and information. It originates in and is applied in the minds of knowers. In organizations, it often becomes embedded not only in documents or repositories but also in organizational routines, processes, practices, and norms.’

The Australian Knowledge Management Standard, Standards Australia (2005, p. 2) defines knowledge as ‘A body of understanding and skills that is constructed by people and increased through interaction with other people and with information’.

Polanyi’s work formed the foundation for the highly respected KM theory authors Nonaka and Takeuchi (Nonaka 2007; Nonaka & Takeuchi 1995). Tacit knowledge is subjective, environment-specific and personal. Tacit knowledge is difficult to communicate whereas explicit or codified knowledge is objective, easily communicated and transferred without in depth experience (Nonaka & Takeuchi 1995). Polanyi (2009, p. 4) stated ‘…we can know more than we can tell’ and contends that human beings create knowledge by involving themselves with objects through a process Polanyi calls ‘indwelling’. Nonaka and Takeuchi propose that tacit knowledge consists of cognitive and technical elements. The cognitive element is based on Johnson-Laird (1983) ‘mental models’ (schemata, paradigms, perspectives, beliefs and viewpoints) where humans create working models of the world in their minds. The technical element is the existing know how and skills. The cognitive elements are important as they form the mobilisation process in creating new knowledge. An understanding of people elements in the lessons learned knowledge process requires further work as Duhon and Elias (2008) reports that failure of learning valuable lessons from projects can be connected to a number of cultural, social and cognitive factors (Bresnen et al. 2003; Fernie et al. 2003; Holste & Fields 2010).

What are your thoughts on Knowledge? Have I missed something?

The next post will focus on Knowledge Management.

Stephen


Share in top social networks!

Is an Organisation’s knowledge system like a washing machine?

As I search the literature for Project Management Lessons Learned, I often find some interesting reading material. I came across the following transformational learning discussion (cited by Schieg (2009)) noting that although we desire for divergent and new organisation knowledge, in reality it is not likely to happen. Blackman and Henderson (2001) describes the analogy of a washing machine:

   ‘If the clothes are to be really clean (attainment of new knowledge) and not reflect previous dirt (experiences) then all the water must be drained out of the system before new water is put in. Even if only a little dirty water remains it will taint the entire rinse. The learning organisation routines discussed in this paper define residual dirt as clean, or at least acceptably so. However, if the system is closed it will never be possible to get really clean water and so real new knowledge will be unattainable. Some incremental development may occur but transformation seems very unlikely.’

Interesting material, let us know what you think.

Regards, Stephen


Share in top social networks!