|
Wikis: When the cart goes before the horse.
|
How do you develop plans and ideas?
• You put your ideas down in a draft document.
• You mail this out to the colleagues.
• They send you feedback.
• You update the document and mail it out again.
You are doing it all wrong!
What is so bad about the way you are working?
- You waste time trying to understand the
feedback and integrate it into the document.
- You cannot send out new copies every hour, so your team aren't
aware of each others' feedback.
- one suggests 'a lighter blue' when another has already decided
to change 'blue' to 'black'.
- Or if your colleagues start 'reply-to-all', the discussion
dissolves
into multiple threads, and no-one remembers what the decision were.
- The old drafts hang around in people's inbox... and often get
used instead of the correct version.
- It's tedious to see the changes between
drafts... and even more tedious to see who initiated what changes.
With a Wiki, you can put the cart before the horse!
- You send out a link, which always gives the latest version of the document.
- All your colleagues can edit the document online.
- and when they make changes, that becomes the new 'latest version'.
- It's easy to compare any versions of the document, and see who made the changes.
- because there are no side-discussions in e-mail, how decision were formed becomes clear.
- But you keep control. You get notified whenever the document changes.
I've been using Jot Wikis for 6 months now... try one here:
|
Copyright © 2006 Daniel Greenspan.
|
|