Using Organisational Experience to Solve Current Problems
Investigators of current problems can search the Lessons Learned database for problems similar to his or for factors similar to those contributing to his problem.
Pro-active Resources for New Task Planning
Workers beginning a job or task that they are not familiar with can do a quick search of Lessons Learned to acquaint themselves with potential problems involving the tools, equipment, materials and processes they will be using in the new task.
Identifying Chronic problems
When evaluating various corrective opportunities uncovered in REASON investigation, Managers can run key terms from root cause statements through Lessons Learned to see if similar breakdowns in control have been causing problems more widespread than the one which contributed to the current investigation.
Automatic Delivery of Relevant Operational Information
Managers, supervisors and workers can set up a profile and receive an e-mail when any case worldwide is submitted to Lessons Learned involving tools, equipment, materials and process that affect their operations and jobs.
An Executive’s Perspective
A Lessons Learned system can be measured for value only on the basis of the unique prevention benefits it provides to the organisation.
When a problem on the job occurs, employees, supervisors and managers need information on how to deal with the situation now if their chances for mistake and injury are to be reduced.
Conventional Lessons Learned systems failed to provide this immediately accessible data.
If we can overcome the shortcomings of the conventional approaches, rapid and cost-effective implementation of a successful Lessons Learned system is possible.
What the REASON Lessons Learned System Will Do for Your Organisation
Knowledge Broadcasting
Unencumbered Knowledge Sharing
A successful RCA Lessons Learned system must use the organisation’s investment of time on investigation and analysis, which then feeds an automatic system that targets and broadcasts the lessons to the organisation.
A Lessons Learned system that will meet the demands and needs of a large organisation must automatically broadcast lessons learned knowledge out to the people who need it in all facilities without bureaucratic obstacles.
With REASON, managers, supervisors and workers can set up a search profile for Lessons Learned, which will specify tools, equipment, materials, process, or any other factors that affect their operations and jobs.
Then, when a problem is released to Lessons Learned anywhere in the organisation containing any of the factors specified in the profiles, the users will receive an e-mail with an abstract of the case.
REASON will expedite problem resolution.Problem solvers can tap into knowledge acquired in the past in order to expedite problem resolution in the present and into the future
REASON Lessons Learned deployed organisation wide is an incredible oversight tool for tracking and trending new industry patterns, trends and changes.
The ability to see emerging patterns and issues within the problems experienced by your organisation allows you to take proactive, preventative steps before those issues make you pay a bigger price later as a consequence of not remembering past lessons.
Provide metrics to measure the effectiveness of policies
In many industries, the organisation-wide lessons learned system should provide a standard for metrics that can be used reliably to represent, calculate, anticipate and compare.
REASON Lessons Learned gives the organisation a solid base of reference beyond assessments and opinions.
How the REASON System Supercedes Conventional Lessons Learned Systems
Traditional word searches set their sights upon the whole document as the target. If the words appear anywhere in the document, it is listed as a "hit."When searching conventional Lessons Learned systems, you get an unmanageable number of "hits."
The user has to read through all of the reports located by the search in the hope that one of them will relate to his interests. Often, only a small number of these "hits" are even loosely associated with the information you were seeking.The screening effort required of the user is a disincentive to use the system.
REASON Lessons Learned solves the user's dilemma by providing
(1) a data-targeting method that allows users to better target their searches;
(2) a means to significantly simplify the data screening process for the user.
Traditional key word searches set their sights upon the whole document as the target.
If the words appear anywhere in the document, it is listed as a "hit."
“Situational,” Causal-Interaction Search
Instead of using the entire report document as a target for the word search, REASON narrows the search to only the factors which interacted causally.
Because the REASON search engine seeks out an interaction of causes instead of just looking for key words in a document, irrelevant cases that would have been included in conventional key word searches are weeded out.
When a REASON user explores the cases found in his causal data search, the REASON Lessons Learned system displays a brief abstract of the case report. With the click of a button, the user can expand the abstract to display more details, all the way up to displaying the entire narrative, and ultimately the complete case report.
This feature significantly reduces the time required for data screening of cases.
Now with REASON, quality professionals, with a new ability to see how causes interact within the environment, will devise new ways to improve operations.
Human factor engineers can know exactly how and why personnel act or fail to act in specific and similar situations.
Maintenance Directors will examine where and why equipment failures contribute to counter-quality problems.
Supervisors and safety professionals will have critical information about operations at their fingertips.
This is the future for operations and safety improvement, and REASON has opened it up.
“A friend once told me that he could look out across any land in Texas and tell how alkaline the soil was just by looking at the grasses growing in it. The grasses that indicated strongly alkaline soil – which in turn indicated poor production – he called “indicator grasses.”
In business and industry, some of the most common indicator grasses are the things that we call quality problems: recurring scrap, rework, missed schedules, accidents, angry customers, downtime, lost sales, and missed goals. It is no secret to any management team that they too should be looking intently at their industry’s “indicator grasses” and be ready to take action to protect their business.
But in large organisations, it is sometimes difficult to see the grasses for the forest.REASON’s Trending and Tracking Lesson Learned system is a state of the art system that gives management the ability to monitor the trends and health of their organisation.
With REASON, your organisation will be able to anticipate the development of serious problems so that you can take pre-emptive action to minimise or even prevent loss.
Notice:The contents of this website are protected by Australian (C) 2002 - 2006 Copyright REASON4 Consulting (Systemic-Resilient-Precision Pty Ltd) and/or U.S Copyright (C) 1979 - 2006 Decision Systems, Inc. All Rights Reserved, including excerpts from papers and presentations depicting the REASON® and RAID™ process from other sources.
