There you are running your project. When one of your team members alerts you to a problem, it has not been identified as a risk. You and your team did an amazing job identifying and analyzing risks.
Still, something will happen, perhaps an unknown unknown, something that you could not foresee. Even with thorough risk identification, unexpected problems will arise. Technology shifts, key team members depart or sponsor changes can introduce new challenges. Regulations may change or company priorities pivot, impacting scope or budget.
These are issues, not identified risks. Where should this be documented? If you and your team experience something that blocks your ability to move forward or will potentially cause a delay, and you do not have a resolution prepared, then you need to document this as an issue.
Keep an issue log that includes challenges team members face, who or what is needed to resolve them, and when that resolution is needed. Be sure to proactively manage project issues, advising your sponsor and other leaders when they are needed. Give them as much advance notice as possible and let them know how delays in issue resolution will impact project objectives.
Assign issues to the appropriate team member and discuss open issues during your regular team meetings. Be sure to include pending issues on status.
Unexpected challenges will come your way. Do your best to prevent them from becoming bigger than necessary.
Don't wait for issues to resolve themselves,be proactive!
Wishing you every success,
Margaret Meloni - pmStudent
