Share the Wisdom | ||||||||||||
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
||||||||||||
 |
[ Login/Subscribe ] | |||||||||||
 |
||||||||||||
 |
 |
 |
 |
 |
 |
 |
|
 |
||||
 |
||||||||||||
Features
Departments
Opinion
Executive
Resources
|
Home > Opinion > The Kickoff
Whether a project is a rousing success or a disastrous failure, there are always lessons to be learned. But many project managers are hesitant to document their difficulties, and even when they do, many of their peers don't take full advantage of the information. How might the process of sharing project wisdom be improved? We'd like to be part of the answer.
Whether a project is a rousing success or a disastrous failure, there are always lessons to be learned. What unplanned issues arose? What were the corrective actions? What mistakes could have been avoided, and how? The answers pave the way for better-run projects in the future.
But many project managers are hesitant to document their difficulties, and even when they do, many of their peers don't take full advantage of the information. Why? And how might the process of documenting and distributing project wisdom be improved? We've explored these questions in the past at Projects@Work, and we will continue to explore them in the future.
After all, the prevailing editorial goal here is to provide an open, engaging and active forum for sharing information that can help you and your peers in the project management community do your jobs better.
Please login/register to read the entire article.
| |||||||||||||||||
|
Privacy Policy Contact Us User Agreement