Army Uses Wiki to Gather Experience, Revise Field Manuals

ako_logoNoam Cohen writes in the New York Times about a three-month pilot underway to collectively rewrite seven of the U.S. Army’s field manuals:

Under the three-month pilot program, the current version of each guide can be edited by anyone around the world who has been issued the ID card that allows access to the Army Internet system. About 200 other highly practical field manuals that will be renamed Army Tactics, Techniques and Procedures, or A.T.T.P., will be candidates for wikification.

Cohen writes that with 140,000 members of the Army’s online forums, there’s a large pool of potential contributors who can offer a wide range of experiences and examples to illustrate the procedures and techniques outlined in field manuals:

“For a couple hundred years, the Army has been writing doctrine in a particular way, and for a couple months, we have been doing it online in this wiki,” said Col. Charles J. Burnett, the director of the Army’s Battle Command Knowledge System. “The only ones who could write doctrine were the select few. Now, imagine the challenge in accepting that anybody can go on the wiki and make a change — that is a big challenge, culturally.”

That cultural challenge is reflected in the slow rate of contributions to the manuals so far:

Still, the reaction of the rank and file thus far has been tepid. A visit to the site hosting the seven wikified guides shows that there has been little editing over the first six weeks. In part, this slow acceptance reflects the different priorities between Army theorists and the working Army, according to Mr. Paparone, a retired colonel with a Ph.D. in public administration.

Here are three techniques the Army can use to help people get past their initial reluctance to contribute:

  1. Assemble small groups of people with knowledge on specific techniques and procedures, and ask them to make the first few contributions. Once others see activity, they’ll be more likely to join in.
  2. Reward those who contribute by giving perhaps an extra day or two of leave to the person who makes the most valuable contributions to each field manual during the pilot. (Don’t base rewards on the number of edits; this just encourages people to focus on numbers instead of quality).
  3. De-emphasize the cultural shift of using the wiki. When people hear that something is different and requires a major shift in thinking, they’re more likely to focus on the perceived differences and dangers. Instead, present the concept of contributing to the field manuals as part of daily routine, just like answering emails. The pilot will be successful when people focus on what to do with it and how they’ll benefit (see #2).
Share Army Uses Wiki to Gather Experience, Revise Field Manuals

2 Comments

  1. Part 3 is awesome – the psychology of change hey…Lee Bryant talks about steering away from terms like blog, wiki in slide 37 http://www.headshift.com/blog/2009/08/behavioural-transition-strateg.php
    I also notice some vendors use the term online document rather than wiki, and messages rather than blog…this way it feels like nothing THAT new

    I really like this use case for a wiki…I mentioned something similar in my post
    http://libraryclips.blogsome.com/2008/10/13/wikis-for-exceptions-and-process-failures/

    I mentioned that Wikis reach what procedures cannot forsee, here’s an excerpt:

    “Every plant site has procedures, but like everything else these procedures cannot be aware of every situation that can occur, or meet every need, so a site wiki for these heuristics, anomalies, band-aids, exceptions can be communally created by the people who actually work at the site.

    A wiki would be doing a site manager a favour in the ways of safety, and possible new inclusion into the procedures…when exceptions become the rule. Now that I think of it, it’s kind of a distant cousin to an online suggestion box.

    What I like about this is no-one is in charge or responsible to write such a document, it’s just stuff everyone knows or doesn’t know, so by everyone pitching in we help each other out, there is no effort on just one person, therefore it’s more prone to exist…plus none of us are smarter than the sum of us.”

Leave a Comment

WIKIPATTERNS
A Practical Guide to Improving Productivity and Collaboration in Your Organization
  • Amazon.com
  • Enterprise Wiki Software Guide
  • Design Pattern Library
  • Wikipatterns book: a practical guide to improving productivity and collaboration in your organization

    USING WIKI IN EDUCATION
    Case Studies from the Classroom
  • Amazon.com
  • Teaching Students to Share Knowledge
  • Examples & Resources
  • Using Wiki in Education wiki book


    Email Twitter RSS
    Loading
  • Monthly Archive and 'Best of' since October 2005
  • 21 Days of Wiki Adoption Video Series English | Hebrew
  • 8 Things You Can Do With an Enterprise Wiki
  • Failure to Launch: Factors Behind Stalled Wiki Adoption
  • How do Successful Institutions Respond to Change?
  • Your Website as a Museum; Your Content as Exhibitions
  • Lock-Step Equity: Knowledge Sharing & the Bottom-Line
  • Info Wants to be Free. It Also Wants to be Expensive
  • How to do a Better Job of Project Collaboration
  • Starting Your Company's Wiki? Don’t Forget Design
  • Research Report: Why Businesses Don't Collaborate



  • random image

    PHOTO ESSAYS
    Click the photo above, or choose a photo essay from the list
  • Airbus Factory - Toulouse, France
  • Istanbul, Turkey
  • Porto, Portugal
  • Sydney, Australia