Those of you who attended Techpalooza, or any summer staff development course this summer, may have heard me mention the book Gamestorming by Dave Gray, James Manifuco, and Sunni Brown. This book contains a variety of activities to add creativity to our meetings. They not only make meetings fun but they serve to spark creative collaboration in the collaborative spaces where we work. I highly recommend it!
A blogger for Harvard Business Review named Gary Klein wrote about an activity he performed as a type of Gamestorm called the Project Premortem.
The concept is to increase the probability of the project's success by assuming that the project has failed and then listing the reasons why it failed. You then spend the time eliminating as many of those reasons as possible for the rest of the gamestorm.
So here is the activity for our group and anyone who reads is welcome to add their thoughts and comments below.
We rolled out Google Apps for Education to all staff across the district. We migrated mail services to Google Mail and uploaded Z:drives to Google Docs. All staff were given access to the system but it failed. Miserably. Explosively.
People aren't using the system and they are harboring resentment toward all technology, especially the technology staff. They are distrustful of our department and there is even resentment within the department among our team.
Now, you now tell me why this failed. List reasons or narrate why it failed. Don't tell how to fix. Just list the reasons why this project imploded.