33 Wikis: #22 -- Lucky Number Slevin Wiki -- Managing the Administrative Beast

This is the twenty-second installment in "33 Wikis," a close look at best practices in wiki-based collaboration.  Each day -- for 33 days   -- we look at one wiki and briefly describe what the wiki is for, why we like it, and what we all can learn from it.  If you want to nominate a wiki, please let us know.  On day 34 we will post a public wiki featuring info on all nominees

What this wiki is for:  As Heather Green at BusinessWeek recently noted, the producers for the film "Lucky Number Slevin" used a wiki to track production and financing.  I wish we could show you the wiki, but this one is private.

Why we like it:   Well, as a former independent theater producer, I can tell you: managing production and budget can be an awful burden because there are so many players, so many moving pieces, and so many potential crises.  I haven't seen the Slevin wiki, but if it made life easier for the producers I am impressed.

What we all can learn from it:  There are many collaborative tasks in the business world that can be better managed on a wiki.  If you have a project that generally requires updates and signoffs from multiple people, at multiple locations, we strongly recommend you go the wiki way.

This is the twenty-second installment in "33 Wikis," a close look at best practices in wiki-based collaboration.  Each day -- for 33 days   -- we look at one wiki and briefly describe what the wiki is for, why we like it, and what we all can learn from it.  If you want to nominate a wiki, please let us know.  On day 34 we will post a public wiki featuring info on all nominees

What this wiki is for:  As Heather Green at BusinessWeek recently noted, the producers for the film "Lucky Number Slevin" used a wiki to track production and financing.  I wish we could show you the wiki, but this one is private.

Why we like it:   Well, as a former independent theater producer, I can tell you: managing production and budget can be an awful burden because there are so many players, so many moving pieces, and so many potential crises.  I haven't seen the Slevin wiki, but if it made life easier for the producers I am impressed.

What we all can learn from it:  There are many collaborative tasks in the business world that can be better managed on a wiki.  If you have a project that generally requires updates and signoffs from multiple people, at multiple locations, we strongly recommend you go the wiki way.