Principles, Operational Procedures, & Permissions on a Wiki

French Caldwell of Gartner offers his take on the Army’s pilot project to gather experience and revise field manuals using a wiki:

The Army saw the failures of doctrine in Iraq, and how the gaps were filled by social networking. To the Army’s great credit, they learned the lesson and then brought the social networking in-house and have supported it.

So — what we may be looking at in the Army is the end of doctrine as training manuals, procedures and instructions — expeditionary warfare requires that those be changed more often than the Cold War system can support — so doctrine exists, but it is stripped of the operational procedures which must change rapidly.

Splitting doctrine and operational procedure makes sense. Instead of spending tremendous resources to write operational procedures based on knowledge from the last conflict, it’s much better to capture it from the field of the current one. That gives the Army staff responsible for maintaining the field manuals a much more up-to-date, relevant set of information to work with.

But what about the core principles, or doctrine. Caldwell asks the question, “Should Your Organization’s Principles Be on a Wiki?” The major focus of the Army’s wiki is operational procedure, but there’s nothing wrong with putting the principles on the wiki as well.

This is where the distinction between view and edit permissions in the wiki is important. Pages containing the operational procedures are open to editing by anyone with appropriate login credentials, but the principles don’t need to be made editable by everyone. Only the people responsible for maintaining the content of the core principles should be given the appropriate permissions to edit them.

For the wiki to be successful, as much information as possible should be available there so it becomes the destination people think of first when looking for information. Setting view and edit permissions on certain information is the tool an organization can use to focus activity where it is needed and appropriate.

(Via VMaryAbraham)

No Comments

Leave a Comment

Books
  • "Highly recommended."
  • "Important and insightful."
  • "Impressive. Read it."
  • Order from Amazon.com
  • Wikipatterns book: a practical guide to improving productivity and collaboration in your organization Using Wiki in Education wiki book

    random image

    Photos
    Click the photo above, or choose a photo essay
    Airbus FactoryBarcelona & MadridBritish Museum
    IstanbulPortoSydneyVancouverYosemite




    Work
    Future Changes is the online home of Stewart Mader, an experienced content strategist and project manager, dynamic speaker to corporate audiences and conferences, and author of two books. He has helped organizations around the world, including Booz Allen Hamilton, Brown University, ICANN, MARS, SAP, and The World Bank develop content strategies and build products that increase information value, collaboration, and employee & customer engagement.

    Future Changes, founded in October 2005, has been cited by CIO Magazine, Fast Company, InformationWeek, InfoWorld, The Guardian, The New York Times, and The New Yorker.

    View Work Samples and Work with Stewart