Tony Karrer suggests going for the small wins, specifically by taking the following steps:
- “implement a small Wiki that has performance support materials that goes along with your eLearning on that new software application
- at first have it only editable by the authors
- then open it up to edit the FAQ and Common Issue pages by your help desk
- and then open up editing to end-users
- and to more pages”
hmmm
Small wins is the way to go. In a previous life, I spent some time in the Agile/Scrum world of organizing projects. Small wins show immediate progress, build a sense of accomplishment, and address the 1st and most immediate needs. Waiting until things are “fully cooked” means that by the time you’ve figured out where it’s all going, it’s going somewhere else.