Write it Down
Posted on March 1, 2007 Comments (3)
Right on. In meetings writing down decisions (what is the issue, who is going to do what…) is very helpful. It is very easy for people to think people agree to some somewhat clear statements made in the meeting. Only later it becomes obvious several people have different understandings (sometimes this is even really basically know in the meeting but it is easier to let things slide instead of confronting the disagreement – but this is not helpful, it just means the issue is not properly address, it might make the meeting easier but that should not be the goal). Writing it down greatly reduces the chance of miscommunication.
Russell Ackoff also has some great stuff on the importance of documenting decisions – both to serve as guide posts to future action and to serve as documentation that can be examined over time to find historic weaknesses and strengths with decision making in the organization. The Team Handbook is a very good book for improving team meetings and team performance.
Ackoff on decision making (pdf):
• The justification for the decision including its expected effects and the time by which they are expected…
• The assumptions on which the expectations are based…
• The information, knowledge, and understanding that went into the decision.
• Who made the decision, how it was made, and when…
The decision should be monitored to determine whether the expectations are being met and the assumptions on which they are based remain valid.
When a deviation is found in either the assumptions or expectations, it should be diagnosed, the cause determined and corrective action prescribed and taken.
The corrective action is itself the result of a decision. A record of this decision should be made and treated as the original decision. In this way the process can not only yield learning but also learning how to learn.
A record of the entire process (all four steps) should be made and stored for easy access by those who may later be confronted by the need to make a similar type of decision.
Related: Peter Scholtes’ web site (Team Handbook author) – How to Improve – Deming Cycle
Categories: Management, Process improvement, Quality tools, quote, Systems thinking
Tags: Ackoff, curiouscat, Process improvement, tips
3 Responses to “Write it Down”
Leave a Reply
RSS Feed
May 10th, 2007 @ 8:12 pm
Personally I have found the act of actually making predictions and examining the results incredibly helpful in improving the speed and depth of my learning.
November 24th, 2009 @ 9:25 am
The best strategy to learn from decisions is to:
* predict the results of your decisions
* write down those predictions
* Then analyze the results
* Then adjust future predictions and decisions based on what you learn
December 20th, 2009 @ 12:00 pm
[...] I have said many times the keys to success are to turn the PDSA cycle rapidly, predict the results in advance, and analyze the results to continually improve. the Improvement Handbook is an excellent [...]