Planning is so critical for a project and what makes a project successful is in the way you approach the first few weeks.  I have conducted these strategy and implementation workshops in a week but the work of the team goes well beyond that.  The first few weeks, however, are what can determine success or failure for a project.  So far we have discussed how important it is to get a project right the first time, the importance of scope, and organizational impact or change.  Another important factor that needs to be addressed in the first week is how you will handle issues that arise during the project and what the process will be for resolving those issues.

If you are working with a standard implementation methodology there is probably a process for issue resolution.  If not, develop a database, excel spreadsheet or similar method for tracking issues.  It is important that you establish what an acceptable time frame is for resolution and what will be done if the issues are not resolved in a timely manner.  What are the roles involved in the resolution process, who identifies, who assigns, who tracks, how high up in the organization will you have to go to find a solution, and finally who determines if an issue is closed.

Issues should be addressed on a weekly basis at meetings.  If critical you might have a process in place to identify them on your project website, or even use twitter to get information out to your team in a timely fashion.

Of course, there is a deliverable that would be associated with this part of the workshop which would be a template for tracking issues.

So we have now addressed one more small part of what would happen in Day 2 of your implementation/upgrade workshop.

Looking forward to any additions you might provide via comments.


Leave a Reply