Brian over at Designing Better Libraries has an interesting post on the recent process he took introducing a reference desk wiki at his library.
This is the second time they've tried the wiki, and this time, he notes:
We’re going to demo “homegrown” software created by campus IT, provide a flowchart illustrating the concept, and offer examples of content that are linked to actual needs.
He goes on to say that prototyping helps others in your organization see the technology first-hand, learn how it works, and see how it can be adapted to fit local needs.
I especially like how his prototype image helps explain who would use / view the wiki, what kind of infornation would reside on there, etc... It helps to graphically lay out for people how a tool will be used, and how it will benefit them (and their users). I think sometimes, we let the glitz of the technology overwhelm communicating the utility of it, and we forget to incorporate in this important step.
Leave a comment