Tips For Turning "20:20 Hindsight" Into "20:20 Foresight"
- Date: 2007-10-23 - Word Count: 712
Share This!
If you've ever heard the expression, "Looking back, knowing what we know now, we'd surely have done things differently" -- that's usually a sign that there were unanticipated events or circumstances that came back to bite, haunt, or baffle the participants of a particular project or undertaking.
Even if the circumstances were difficult at the time, the good news is that astute observers can later extract valuable gems of wisdom from the experience, which they can then apply to their greatest advantage going forward.
20:20 Hindsight = "Lessons Learned"
"Lessons learned" are the perfect 20:20 hindsight that we frequently have after completing a project or endeavor. This hindsight is worth its weight in gold if we mine its special value, but it's absolutely worthless if we don't make use of what it has to offer.
When identifying lessons learned, our goal should be to identify what went well, what didn't go well, and why. At this point, you might be thinking, "What kind of reason can I give to my team that we should be doing this? It sounds like a bunch of bureaucratic overhead and more things to do. When the project's over, we're anxious to move on!"
The value lies in paving the way for future projects, so they will experience fewer headaches and setbacks. You don't, however, need to wait until the entire project finishes. You could capture 20:20 hindsight incrementally throughout the project, or very soon after it's over, while the issues are still fresh.
What Lessons Should You Capture?
For any problems that went largely unresolved, for instance, consider preventative measures that could help people work through or avoid the problems in the future.
Those measures could involve checklists to make sure people perform critical steps, tools that streamline the work, and solutions for difficult problems. Examples:
-- If people were stymied by complex document formats, try preparing and pre-testing some document templates that will be much easier to use next time.
-- If quality was a issue because people didn't do thorough testing, try creating step-by-step checklists to guide people through the process next time.
-- If you found components that were supposed to work together but didn't, and someone found a solution or a workaround, record that information to help people prevent or solve similar dilemmas in the future.
Lessons learned can have many possible uses. You can use your repository of lessons learned to help your customer service or technical support personnel solve problems in a just-in-time fashion, for example. If your staff or colleagues need to address complex issues on the fly, or troubleshoot technical issues quickly over the telephone, they would need fast access to solutions for similar situations that were addressed in the past.
20:20 Foresight = "Best Practices"
After capturing a series of lessons learned, the next step is to derive what's called "best practices." What is a best practice? It's a procedure or method that over time has proven itself to be better than any other procedures or methods that you were using to do the same thing. You could say that it's the very best way that you, your group, or your organization has found of doing something.
Why do they matter? Best practices are invaluable because they're the intellectual assets -- the "secret sauce" -- that can help organizations remain highly competitive. The ideal approach is to standardize best practices so the entire organization follows them. You could incorporate them into policies, procedures, and/or online task support systems.
One idea is to design a best practice repository that other people can access easily. You don't want that valuable information to be buried in a file cabinet that no one knows anything about. The storage area could be in a database, on a Web site, or another highly visible electronic or physical location.
Best practice repositories can substantially reduce the negative effects of attrition on the company's intellectual assets, which can be devastating. When people leave because they quit, retire, are laid off, or were simply temporary contractors to begin with, the company's "brain trust" completely vanishes out the door with them unless their knowledge is being captured and made available to others.
In conclusion, by capturing 20:20 hindsight incrementally and turning it into 20:20 foresight, you will achieve far greater long-term success than by blissfully ignoring or forgetting problems, or by simply moving on when a project or endeavor ends.
Even if the circumstances were difficult at the time, the good news is that astute observers can later extract valuable gems of wisdom from the experience, which they can then apply to their greatest advantage going forward.
20:20 Hindsight = "Lessons Learned"
"Lessons learned" are the perfect 20:20 hindsight that we frequently have after completing a project or endeavor. This hindsight is worth its weight in gold if we mine its special value, but it's absolutely worthless if we don't make use of what it has to offer.
When identifying lessons learned, our goal should be to identify what went well, what didn't go well, and why. At this point, you might be thinking, "What kind of reason can I give to my team that we should be doing this? It sounds like a bunch of bureaucratic overhead and more things to do. When the project's over, we're anxious to move on!"
The value lies in paving the way for future projects, so they will experience fewer headaches and setbacks. You don't, however, need to wait until the entire project finishes. You could capture 20:20 hindsight incrementally throughout the project, or very soon after it's over, while the issues are still fresh.
What Lessons Should You Capture?
For any problems that went largely unresolved, for instance, consider preventative measures that could help people work through or avoid the problems in the future.
Those measures could involve checklists to make sure people perform critical steps, tools that streamline the work, and solutions for difficult problems. Examples:
-- If people were stymied by complex document formats, try preparing and pre-testing some document templates that will be much easier to use next time.
-- If quality was a issue because people didn't do thorough testing, try creating step-by-step checklists to guide people through the process next time.
-- If you found components that were supposed to work together but didn't, and someone found a solution or a workaround, record that information to help people prevent or solve similar dilemmas in the future.
Lessons learned can have many possible uses. You can use your repository of lessons learned to help your customer service or technical support personnel solve problems in a just-in-time fashion, for example. If your staff or colleagues need to address complex issues on the fly, or troubleshoot technical issues quickly over the telephone, they would need fast access to solutions for similar situations that were addressed in the past.
20:20 Foresight = "Best Practices"
After capturing a series of lessons learned, the next step is to derive what's called "best practices." What is a best practice? It's a procedure or method that over time has proven itself to be better than any other procedures or methods that you were using to do the same thing. You could say that it's the very best way that you, your group, or your organization has found of doing something.
Why do they matter? Best practices are invaluable because they're the intellectual assets -- the "secret sauce" -- that can help organizations remain highly competitive. The ideal approach is to standardize best practices so the entire organization follows them. You could incorporate them into policies, procedures, and/or online task support systems.
One idea is to design a best practice repository that other people can access easily. You don't want that valuable information to be buried in a file cabinet that no one knows anything about. The storage area could be in a database, on a Web site, or another highly visible electronic or physical location.
Best practice repositories can substantially reduce the negative effects of attrition on the company's intellectual assets, which can be devastating. When people leave because they quit, retire, are laid off, or were simply temporary contractors to begin with, the company's "brain trust" completely vanishes out the door with them unless their knowledge is being captured and made available to others.
In conclusion, by capturing 20:20 hindsight incrementally and turning it into 20:20 foresight, you will achieve far greater long-term success than by blissfully ignoring or forgetting problems, or by simply moving on when a project or endeavor ends.
Related Tags: project management, project, organization, process, practice, downsizing, best practices, redesign, lessons learned, project planning, attrition, layoff
Adele Sommers, Ph.D. is the creator of the "Straight Talk on Boosting Business Performance" success program. To learn more about her tools and resources and sign up for other free tips like these, visit her site at LearnShareProsper.com Your Article Search Directory : Find in Articles
Recent articles in this category:
- The No. 1 Rule For Projecting Confidence - Speak With Authority
One of the most important characteristics a person can project in a business setting - or any situat - After the Autumn Checkout European Debt Crisis and U.S. Brewing Rebound
In the commotion caused by the Fed on interest rates come to an end, the "disastrous" for the euro a - Advantages Of Arcade Game Rentals
There are many different advantages to arcade game rentals. Most people need something to release th - A General Primer on Truck Cargo Nets
In modern highways it is quite rare to see truck cargo nets in action, this is because they are usua - The United States Will Burst More Severe Financial Crisis
Not long ago, suddenly announced that the central bank to raise interest rates, the interest rate hi - Niche Marketing Profits - 3 Easy Steps to Finding a Profitable Niche Market Income in 10 Minutes
Like most beginners I was having a very difficult time trying to find a niche market to earn extra m - The Importance of Hospitality Management Consulting Firms Toronto
Businesses and the managers that help guide any business are in a constant state of improvement and - New Keynesian Theory Label
2010 winner of the Nobel Prize in Economics three theories have been labeled as "New Keynesian" labe - Federal Reserve Pouring Money QE2 Unpredictable Fortune
U.S. economist Milton Friedman proposed a "throw the cash from a helicopter" view, while the practic - Fiscal Consolidation Should no Longer Delay
British Chancellor of the Exchequer George Osborne today announced fiscal consolidation policy, shoc
Most viewed articles in this category:
- Common Financial Problems to Avoid
One must first change their habits and not procrastinate. American Consultants Inc at offers key fi - How a Bad Hire Can Hurt Your Business
What's worse - hiring the wrong person or not hiring anyone at all? Companies can become almost des - Joel Comm Is Dr. Adsense
What is Adsense? If you are new to making money online and net marketing, you may not know what Ads - 5 Steps For A Dynamic Wealth System Online
Recipe: Opportunity + knowledge + Dynamic Wealth System + Your Action = Massive Success!!! Step 1 - How To Stop Foreclosure
Losing your house to a foreclosure can be very scary. There are times when circumstances are ou - How to Always Pitch A Strike
As business owners, we are always working on new ways to convince people to become customers, client - Membrane Diffuser Solutions for Wastewater Treatment Systems
In the aeration basin of a typical wastewater treatment plant there are both organic and inorganic m - Another Year Hating Your Job or Loving Life?
Copyright © 2007 Mary Foley I've come to the conclusion that to be successful - really successf - Dyestuff Industry In India And China
World demand for dyes and organic pigments to touch $10.6 billion in 2008According to a study on dye - Cma-cgm Case : the Series of Lawsuits Continues in Syria, Lebanon, Egypt, France, England and the United States
Damietta company case : The series of lawsuits continues in Syria, Lebanon, Egypt, France, England a