Boxes and Arrows: An introduction to user journeys

Boxes and Arrows: An introduction to user journeys


Consider implementing a wiki if:
You want to establish a company intranet quickly and cheaply without sacrificing functionality, security, or durability.
You want to publish a range of corporate documents in one universally accessible location and let employees manage those documents with a minimum of effort, lag, and risk of redundancy.
You want to manage and organize meeting notes, team agendas, and company calendars.
You need a project management tool that is cheap (if not free), extensible, and accessible through any Web browser.
You need a central location where shared documents can be viewed and revised by a large and/or dispersed team.

A wiki might not be right for your organization if:
You need to use complex file formats. Some wiki platforms can support only text or HTML files. Consider using a PHP/SQL-based wiki platform that can handle robust file types. Avoid wikis based on PERL.
You don't have a staff member who can take responsibility for its use. A wiki is only as good as its ontology (or the search engine it uses). You will need somebody who can establish conventions for naming pages and maintaining links.
The collaborative format isn't appropriate for your group or workplace. Peer review is not always the best solution for content management.
You're looking for an exchange of views. Wikis are not the best tool for airing opinions or carrying on conversations. If that's your primary goal, use a blog instead.