knowledge management and lessons learnt Flashcards
what does knowledge allow us to do
- improved planning and delivery of projects with all key issues taken into consideration
- development of project schedules and cost estimates that are more likely to be achievable
- improved understanding and management of risks and uncertainties that might impact on projects
- improved quality and supply chain management
- greater project control and understanding of EVM data
- improved engagement with project stakeholders
define knowledge management
an effective means of learning from experience from projects, that combines explicit knowledge with tacit knowledge in a way that encourages people to learn and embed that learning into continuous improvement
what is knowledge management based on?
an organisation’s most valuable resource is the knowledge of its people
describe the effectiveness of knowledge management
depends on industry sector
* highly competitive, mass production: likely to be well done
* non-competitive, low volume, high-complex projects: less likely to be well done
what drives knowledge management?
competition
what are the two different types of knowledge?
explicit and tacit
what is explicit knowledge?
- easily shared
- can be captured and written down in documents/databases (instruction manuals, written procedures and processes, performance/benchmarking data)
how can we categorise explicit knowledge?
- structured = referenced for future retrieval (documents, databases etc.)
- unstructured = not referenced for retrieval (e-mails etc.)
what is tacit knowledge?
- carried in people’s heads
- more of an ‘unspoken understanding’ about something, knowledge that is more difficult to write down, e.g. Lessons learned reviews, anecdotal information, experience
- difficult to access as it is often not known to others: most people are not aware of the knowledge they possess or of its value to others
- considered more valuable than explicit because it provides context for people, ideas, and experiences
- has been described as ‘know-how’ rather than ‘know-what’, ‘know-why’, or ‘know-who’
- involves learning and skill but is difficult to articulate
why is it good to convert from tacit to explicit?
- help reduce risk and uncertainty
- better understanding (through experience gained) of issues
- better understanding of how to manage these issues
- helps us see the signs of approaching problems, allowing for effective management
- difficult to achieve this
what problems can we encounter converting from tacit to explicit?
- people are a scarce resource and so are required on other projects; as a result, there is little time or appetite to conduct lessons learned exercises
- organisations are under pressure to keep delivering projects as they are typically in the business of making money
- people fail to see its value or lack motivation to do it
- it is not company policy/practice
- it takes time and discipline
- people get tired and just want to move on to the next project or decide to leave the organization
- lack of necessary organisational KM facilitation skills
- people see projects as being standard day job and so there is nothing original to learn from them
- management lacks debriefing/communication skills required to capture people’s experience and know-how
- people only see the downside of projects they have been involved in
- even where lesson gathering takes place, results are poorly documented or archived, are described too generically or are not accepted by the supposed beneficiaries
- company size: small companies might not be able to spare the resources while people can ‘become lost’ in large companies
what is the importance of conducting lessons learned?
- lessons learned: project evaluation
- force organisations to state explicitly what they are trying to achieve on their projects, i.e. identify core project objectives
- provide information on project performance, enabling project members to take corrective action if project is not on track (EVM)
- enable organisations to learn what does and does not work so that processes can be altered if required (‘good’ and ‘bad’ practice)
- sessions should be run throughout a project rather than just at the end (parallels with ‘continuous
- improvement’)
describe the project evaluation process
pre-project evaluation, mid-project evaluation(s), post-project evaluation
what happens in pre-project evaluation?
- identifies criteria against which potential projects should be assessed
- selects projects that should be carried out
what happens during the mid-project evaluation?
- identifies extent to which project performance criteria are being met
- determines actions that might be taken: bring projects in line with objectives; kill projects; do nothing