Your Internal Wiki as a Project War Room
What about using a wiki as a war room, a single location for strategic action-packed activity surrounding a specific set of goals? Wikis have lots of great features that make it an ideal collaborative web space. We’re not the first to think of this either - this article from a wiki about using wikis for Project Management discusses Building a Virtual War Room. But Duo has an excellent example of using an internal wiki page as a command center, a war room of sorts.
Duo uses its internal wiki to document and collaborate on mission-critical projects, like Chicago Park District registration. When the throughput gets intense, the Duo Consulting team uses an internal wiki as a war room for troubleshooting a web application that contains underlying SQL queries to help Chicagoans register for park department offerings. The wiki becomes a strategic command center, a virtual room from which information is gathered and decisions are made. With a slogan for Chicago Parks like “Come out and play” a war room metaphor seems opposite to the end game, but the team must attempt fully concentrated efforts and strategic decision making from one location. There are a couple of reasons why the wiki is so useful:
- there are so many people involved, with so many time-critical tasks and dependencies, that one central location that shows the progress prior to registration helps keep the team on track as a team
- during registration itself, there are so many people monitoring so many different aspects of the application all at once that they need one central location to store that information, as well as knowing who is responsible for following up on any immediate issues
- the wiki engine itself does an awesome job of syntax highlighting and storing SQL queries
- the team can use the wiki as a task list, crossing off items as they’re done.
A specific scenario as an example: one team member might log an issue where a patron can’t register for a particular class. The site is giving the user conflicting information about whether the class is sold out already or not. Another team member might throw up the raw database SQL for that class display on the wiki, and a third team mate might closely analyze that SQL for clues as to what the underlying issue really is – all within minutes, because it’s so important for people to be able to register for these programs as quickly as possible. It’s like the wiki page is the heads-up display in the war room.
Kelly Tetterton, director of development at Duo says, “In some ways, I would imagine working on Chicago Parks Department registration is not entirely dissimilar from working at the air traffic control tower at O’Hare – it feels like that kind of high-pressure, high-intensity experience.”
I’d say that wiki updates give more immediate answers to questions than emailing and waiting for a reply. Wikis make all decisions known to all who monitor the pages. Wikis let you display mission-critical information in a heads-up display or you can print if you happen to like your clipboard or three-ring binder. Wiki’s history pages give you the path to the decision made, and wiki discussion pages can contain lively back and forth while the main page maintains the “truth” decision for the time being.
Let’s hear some war stories - how are you using internal wikis as your strategic project war room?

