Nothing Special   »   [go: up one dir, main page]

Lessons Learned Overview

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 10
At a glance
Powered by AI
The key takeaways are that knowledge transfer through the Lessons Learned process is important for maintaining industry competitiveness, avoiding repeat mistakes, and continuously improving operations. The Lessons Learned process involves identifying, reviewing, approving and sharing lessons to apply to future projects.

The purpose of the Lessons Learned process is to capture knowledge gained from past experiences, both positive and negative, and share those lessons widely so others can learn from them. This helps avoid repeat mistakes and improve processes and operations over time.

The Lessons Learned process involves project teams identifying potential lessons, reviewing and vetting lessons for accuracy and applicability, approving and storing valid lessons, and then sharing and applying approved lessons to future projects and planning. A role-based workflow and the Lessons Learned eApplication support this process.

malombard

EMDC Assimilation
Lessons Learned Process and eApplication

March 2010

This material is not to be reproduced without the permission of ExxonMobil Development Co Project Execution Project Best Practices
Table of Contents

Todays Objectives:
Why knowledge transfer is important
The Lessons Learned Process
Lessons Learned Quality
Lessons Learned eApplication Features
Where to find the Lessons Learned Computer
Based Training (CBT) Modules and Access
Request eForm

ExxonMobil Use Only MALombard


malombar
Page 2
malombard
d
Upstream Demographics

Knowledge transfer is a need to maintain


industry competitive advantage
Avoid repeat instances / re-learning
Ensure that applicable Lessons are effectively
integrated into new activities
Continue to improve processes and
operations

ExxonMobil Use Only MALombard


malombar
Page 3
malombard
d
What are Lessons Learned?

The fundamental principle of any Lessons Learned (LL) effort is the concept of learning
by collective experience. Knowledge gained by one individual can be widely distributed
and shared to others.
In its simplest form a Lesson Learned can be thought of as answering the questions:
What went well, and why? or What went wrong, and why?

Consistently applying Lessons Learned can provide great benefits in cost, efficiency and
effectiveness to a Company.

A Lesson Learned that is found to be widely applicable to a variety of projects may


evolve over time to become a Best Practice.
Best Practices are based on a set of repeatable procedures that have proven
themselves over time for large numbers of people, demonstrating their reliability to
consistently deliver a desired outcome. Best Practices may also set new standards or
introduce innovative practices.

ExxonMobil Use Only MALombard


malombar
Page 4
malombard
d
EMCAPS 14.1 - Lessons Learned Process

The lessons learned process is a continuous process that is applied throughout the life
of a project.
As project work is conducted, teams identify
lessons learned for potential capture and
sharing
Lessons are reviewed/vetted for:
Apply Project Factual, relevant and technically correct
Work information
Root cause identification
Potential impact (positive or negative)
Apply Lessons for Compliance with MPI policy and other
Store &
Share
Continuous Capture guidelines
Improvement Actions needed to correct deficiencies or
enhance procedures are assigned
Once vetted and approved, lessons are stored
Update and shared for application to future projects
(Processes, Procedures, Vet and Project plans.
Guidelines)
A role-based workflow within the new LL
eApplication is the primary support for the LL
process

ExxonMobil Use Only MALombard


malombar
Page 5
malombard
d
Lessons Learned Quality Check

Guidelines the Lessons Learned Coordinator (LLC) should use to check the quality of a lesson.
Is the lesson factual and technically correct and did the author describe the event (what
happened) in sufficient detail? The Lesson Learned Description should:
o Include a summary of actual past situations, events, or results
o Focus on visible and indisputable facts, not causal theories or implications
Has the root cause (how and why it happened) been identified accurately? The Root Cause
should:
o Focus on the relationship between causes and the results given in the Lesson Learned
Description.
Was the impact well defined and were all impacts included? The Description of Impact(s) should
be:
o Testable or verifiable
o Stated with three parts - if this happened (the situation), then this will occur (rule),
resulting in this (metric)
Did the author provide a recommendation for improvement? The Recommended Action should:
o Suggest a process or decision that needs to be considered
o Suggest a manager who might champion the recommended action
Is the lesson written clearly and can it be understood by people outside of the Project Team? The
author should:
o Provide background information to clarify understanding
o Use common language, avoiding jargon and region or contractor/vendor specific terms
o Spell out uncommon acronyms or abbreviations

ExxonMobil Use Only MALombard


malombar
Page 6
malombard
d
Sample Lesson Scenario

Its been a busy work week and you are trying to balance all your deadlines.
You have an offsite meeting scheduled for Friday afternoon.

Friday morning your manager comes to you with a last minute task. You are
now in rush mode, because you really need to leave the office by 11:30 to
get across town for your meeting.

Youre on your way to the meeting and now stuck in lunch time traffic. You
decide to call ahead to the meeting facilitator to inform him that you are
running late due to bad traffic. As you scroll your blackberry phone list, you
are unaware that the cars in front of you have stopped. The next thing you
hear is crashyou are now part of a traffic accident and will never make it
to your meeting.

What is the root cause of this lesson?

What is impact of this lesson?

What is the recommended action of the lesson?

ExxonMobil Use Only MALombard


malombar
Page 7
malombard
d
The Lessons Learned eApplication

The Lessons Learned eApplication is a tool to capture, store, and browse lessons in real-
time complying with EMCAPS 14.1.
Benefits of LL eApplication include:
Access from any computer, anywhere in the world.
User-friendly interface that allows for real-time capture of lessons.
Template-based data entry that ensures consistent lesson format.
Role-based workflow for streamlined lesson capture, vetting, and action tracking.
Capability to attach supporting material (map, diagrams, images, etc).
Search and reporting capabilities that allow users to:
Search approved lessons using multiple parameters.
Compile potentially significant lessons for application on a new project
through a Register feature.
Export capability to Excel.
Ability to forward a Lesson via Internet email.
Automatic email notifications to support workflow activity.
Copy & Paste capabilities from Office programs.
Metadata alternative to enter consecutive lessons in the same project.
Access security and other information management considerations.

ExxonMobil Use Only MALombard


malombar
Page 8
malombard
d
Additional Information

http://intrattacc.na.xom.com/EMUP/prjmgt/Lessons_Learned/lessons_learned.htm

ExxonMobil Use Only MALombard


malombar
Page 9
malombard
d
Any Questions?

ExxonMobil Use Only MALombard


malombar
Page 10
malombard
d

You might also like