2016年8月30日 星期二

事前防範勝於事後檢討

總是會有失敗的項目,而多數的專家會告訴你要避免未來的失敗,最好檢討一下之前發生過什麼錯誤。
與其做事後的檢討,不如做事前的防範。你可以在實際啟動項目前,考慮到任何可能發生的錯誤。
當你宣佈要啟動新項目后,立即召集你的團隊成員。告訴他們,假設項目已經失敗了,然後要他們寫下來任何可能導致失敗的原因。然後,根據他們的回饋,修改你的原始計劃。
這樣的練習,能夠讓你避免脫節,並且讓團隊在執行項目是,有機會發現可能發生錯誤的信號。
Prevention is better than post-review
There will always be failed projects, and most experts will tell you that to avoid future failures, it's best to review what went wrong before. 
It is better to take precautions before doing things than to make a review afterwards. You can consider any possible errors before actually starting the project. 
When you announce the start of a new project, bring together your team immediately. Tell them to assume that the project has failed and ask them to write down any possible cause of failure. Then, based on their feedback, modify your original plan. 
This practice allows you to avoid disjointing and gives the team the opportunity to detect signs of error in the execution of the project.

沒有留言:

張貼留言