You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 66
Next »
Unknown macro: {stickynotes}
Unknown macro: {snipedit}
- members - Sue, Ned, Benoit, Christine, Casper
- problem assigned (problem ID 4)
Sub-Group Pages
Table of ID #s of Identify Top Problems
Top Problems when Conducting Lessons Learned
ID# |
Problem |
# Votes |
1 |
Keep team focused on identifying LLs instead of just complaining about issues |
12 |
|
Difficult getting people to identify top 3 problems |
|
|
Avoiding personal attacks, poor attitudes &/or taking comments personally |
|
2 |
Difficult to translate LL's into concrete actions to improve processes and projects (Best practices) |
7 |
3 |
Facilitating the LL session without imparting PM biases |
|
4 |
No mechanism to share LLs more broadly than the project team, so LL's are not reusable, researchable or accessible to others |
16 |
|
How to communicate LL info to stakeholders for the next project/incorporate LLs into future projects |
|
5 |
No follow-through on LLs |
3 |
6 |
Distilling anonymous survey input & team discussion into a usable LL report |
1 |
7 |
Different PM for the next project |
|
8 |
Finding time to do LLs (especially when the project is "finished") |
3 |
9 |
How to pull info out of LL session participants, esp. those hesitant to bring up negative info/comments |
3 |
