
Electra-Department of Theatre and Dance SUNY-Fredonia. Scenic and Lighting Design by Colin Chauche Costume Design by Ashley Arnone
This month in Stage Directions Magazine Justin Lang author of the popular lighting blog isquint.net wrote an article on the new service Google Wave and how it can be used for collaboration for Theatre. He used as an example the work of Colin Chauche and the lighting crew on SUNY-Fredonia’s production of Electra. The article can be found here and if you don’t know about wave start with his article. When the article was written the production was sill in progress almost ready to open. After the production I sat down with Colin and we discussed the pro’s and con’s of using Google and here are our thoughts.
How Wave Was Used
Pre Production
Colin and his design assistant Gerald used the Wave to create the plot and subsequent revisions. Gerald created the plot then uploaded it to the wave. Colin would add comments and Gerald would make updates and Colin’s design mentors would also make comments. Once the final plot was done it was uploaded was well as the Lightwright paperwork files. It was quickly found it was a good idea to post a pdf of the final plot and pdf of the paperwork for those who did not have those Vectorworks or Lightwright. The Master Electricians took the files to prepare for the load-in.
Production
Once the hang started the Master Electricians were required to report their progress each night. This allowed Colin, the mentors and the buildings Operation Manager to leave comments and answer questions posed in the report. It took a while to get the format for the report. First it was a new report each night which cluttered the wave and then it was one report that was edited each night striking through what had been done and adding new items to the list. This practiced was continued through the close of the show.
Post Production
After the production everyone was invited to comment on the process of using Google Wave in the wave but no one responded. Most people did not check it after the show closed.
Pros
Having all the comments and files in one place is a big advantage. Often in emails its hard to follow a conversation when you have multiple people responding. Wave puts the conversation in one place and makes it easy to follow.
Being able to upload multiple files was useful. Colin and his design assistant were able to work on early versions of the plot. This was really handy over break, Colin was traveling out of the country and work on the plot did not stop.
The basic program was easy to use and learn. Adding files and responding to a wave was easy to figure out and no one on the team seemed to have a problem learning it.
Each reply has the picture of who posted it. If you have uploaded a picture to your Google account it shows up in the wave next to your reply.
Cons
Remembering to check the wave was the biggest problem. At the time you had to check the site to see if the Wave had been updated. The good news is email notifications have now been turned on in wave. To learn how, check out the Google Wave blog.
Wave needs a better way to do a to-do list. Once the production started and the wave got long it was hard to check off things and add new with out a manual reorder. An extension that let you check things off and move them to a done list is needed. I did find a wave extension for a to-do list but that leads to the next con.
The basic service is easy, some of the more advanced features that make wave very useful are hard to find and figure out. You can add a gadget or extensions to Wave that allow you to have a conference call add a map or poll. If it’s a featured extension it easy to find. There are hundreds of third party extension but finding them and installing them are not easy. Once you put a gadget in a wave you have to store the link or code somewhere so you can use it again. I created a wave that just has the extensions I have used. For help with wave and extension I recommend The Complete Guide to Google Wave by Gina Trapani with Adam Pash. It cost $6 but can be accessed free online.
Colin suggested, ability to tag or star a reply would be helpful. As the wave got longer it was harder to find things in the long lists. A tag would make it easier to find the important things.
There is no way to track changes in a single reply. It would be nice to have a document that could be edited by everyone in the wave and those changes could be tracked and approved by an administrator of the wave. If you posted a props list in a wave and need to change the changes would be highlighted telling you who made the changes.
There needs to be more integration with other Google products. The ability to add a Google Doc or picture from Picassa Web Albums would only add the the experience. For productions Google Calendar would could be used to post the schedule. That being said, a document, calendar or picture can be attached to a reply in wave.
Any member of the wave can add a member for a production that deals with sensitive materials an administrator should have control of who reads the wave.
Next Production
Looking forward I intend to build a base wave that has building policies and inventories uploaded so that all I need to do is to add new recipients.
A calendar with deadlines should be the first thing uploaded.
Conclusion
I have listed more cons than pros but this is still a service I recommend to use for collaboration. The ability to have a conversation with multiple people over a long period of time is something that I have not found in any other service. Over all it worked well for the production and the electrics department will continue to use it in the future.

