Army Asks Its Personnel to Wikify Field Manuals
Hugh Pickens writes "The NY Times reports that the Army began encouraging its personnel — from the privates to the generals — to go online and collaboratively rewrite seven of the field manuals that give instructions on all aspects of Army life, using the same software behind Wikipedia. The goal, say the officers behind the effort, is to tap more experience and advice from battle-tested soldiers rather than relying on the specialists within the Army's array of colleges and research centers, who have traditionally written the 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.' Under the three-month pilot program, the current version of each guide can be edited by anyone around the world who has been issued an ID card that allows access to the Army Internet system. Reaction so far from the rank and file has been tepid, but the brass is optimistic; even in an open-source world, soldiers still know how to take an order."
This is a good idea. Even though I haven't read any field manuals I have read numerous instruction booklets, documentation and books about programs and often times what the official documentation says and what you need to do are totally different. Many times even though the "official" way to do something is doable, it might be awkward or slow, and you can do an "unofficial" way and save time and get 95% or more of the same results. I expect that army field manuals are no different.
Taxation is legalized theft, no more, no less.
Wiki entry:
In case you come under attack, shoot back. [clarification needed]
Take Nobody's Word For It.
That is absolutely one of the most intelligent things I have ever heard
of the US armed forces doing.
Well, that and letting Haynes design T-shirts, and letting go of the 20+
page specifications for fruitcakes.
The problem with american military doctrine is that the American military does not read it's field manuals, and even when it does it doesn't follow them.
between this and Wikipedia is that each edit will be linked to an ID which in turn is linked to a known service(wo)man.
Combine this with the way that the final manual will be the product of review teams rather than the wiki-style entries themselves, and this seems as much a very efficient public feedback/comment system (using wiki software and formatting) as a true wiki.
tap more experience and advice from battle-tested soldiers rather than relying on the specialists within the Army's array of colleges and research centers
Forgive my ignorance, but by definition a field manual should be exactly that - a tool relevant to experience in the field of combat.
I fail to see how some "researcher" no doubt with a worthless degree in "Ancient Medievil History" or the like is more qualified that some who's, gasp, actually been in the field?
By open-sourcing information, they have basically allowed for a large influx of new, refreshing and indeed relevant ideas and ideology.
The Common Access Card (CAC Card. yes, it's redundant) is not unique to the Army, the entirety of the U.S. Armed Forces uses them to varying degrees because it's integrated into the Military ID (which is a Smart Card)
This just in: the military command structure has decided to put ARPANET to use as originally intended a scant 40 years after development!
On a (slightly) more serious note, the rank and file and upper brass have differing views on how their opinions are going to be received by the other side. Of course they do! The higher level officers have always expected their suggestions to be taken seriously and responded to with a prompt, "Yes, sir!" They see no problem here. The grunts have a long history of learning exactly how much their input is both required and appreciated by those men, especially when it comes unsolicited. This is one of those rare situations in the military where both sides' reactions are perfectly understandable and even... rational.
there's a book called Infotopia (http://www.amazon.com/Infotopia-Many-Minds-Produce-Knowledge/dp/0195189280), about how information is generated and shared in an increasingly tech advanced society, and this is one of the things it mentions in its "vision for the future" in the intro. interesting book. quite optimistic.
weinersmith
Standard SOP for solid waste burning is SERGEANT MAJOR IS A COCK SUCKER!
In other news, Stephen Colbert is now commander-in-chief of US forces in the middle east, and the number of elephant attacks has tripled in the last 6 months.
This would seem to pose a problem when there are conflicting viewpoints - esspecially among higher ups. Wikipedia has this problem too, but wikipedia articles on controversial topics aren't really actionable (and you can't plead your case that oh, you read this on wikipedia it must have been true! when something is wrong that you did act on wikipedia from). Army doctrine is.
If you take a look at the current US army and marine corps counterinsurgency field manual Chapter 2is titled "Unity of Effort: Integrating Civilian and Military Activities". I bet with 200k troops or so active at any given time on recolonization (I term I would prefer to counter insurgency), there are going to be at least a dozen different high level officers with different ideas on how to get things done, and some with contradictory ideas both seeing success (or failure). Figuring out which goes in the manual, which doesn't, and why is the sort of thing that requires people at the top to act as editors, pick sides and end up essentially censoring one group of people is likely to build dissent - and public dissent. It's different when they're silenced in a research lab, the only people who've know they've been shut up are immediate colleagues, but when you make opinions widely public (or in the case of an army wide wiki, mostly public), even wildly wrong ones, you're giving the people who dissent a voice to end up on faux news touting how their solution to 'counter insurgency' would have been to gas the lot of them! It even made it into the field manual before it was pulled! The government isn't supporting our commanders who want to use more/less/different whatever.
Certainly a military wiki has its place, but I'm betting there are going to be some kinks to be worked out yet. One of the virtues of the military structure is deffering responsibility for being wrong. If I'm colonel A and General B tells me to do something I know to be wildly misguided (but not illegal), I go and do it, and when questioned about it, can say with honesty, and possibly with written orders to squarely place the blame on General B. On the other hand with the wiki system if Generals C, D, E and F all say things on a topic, not all of which is consistent, and the one I happened to see was General E's opinion which happens to be wrong who's fault is it now? Colonel A for not researching enough Gen. E for being wrong, or the Lt who was moderating the discussion for not blocking the wrongness of E that was agreed upon by C, D and F.
1) define legal rules for prisoner treatment as "use only techniques listed in the Field Manual"
2) wikify the Field Manual
3) ...
4) oppress it!
[
... prepare for edit wars unlike any you've ever seen before.
Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
as a consultant that has such CAC card (no, it's not repetitive)
I believe the access too broad for this to be effective.. Although there does exist STRONG accountability within the credentialed system, no anonymous access or anything allowed on the network. This will probably work ok, but there will be much more overhead in the moderation and administration than exists even in wikipedia out publicly.
No, it's actually Obama posting these things to try to make racists look bad.
You are welcome on my lawn.
In the past, Training and Doctrine Command (TRADOC) looked at the threat, defined and acquired the means of dealing with the threat and then trained the people at the sharp end how to use what TRADOC or the other commands had acquired to dispatch the threat. Since everything but the threat was theoretical, the only way to do things was to have the FM written by TRADOC. No one had any real experience on which to base a FM. This made a lot of sense when the overall threat was assumed to be the Warsaw Pact armies rolling through the Fulda Gap with their latest collection of toys.
Fast forward to the 21st century and both the overall threat and the specific means of implementing the threat aren't as clearly defined. On the other hand, we have people in the field getting real experience dealing with the current threat. It just makes sense to get the people with the experience to data dump into a FM that represents how things really work. Conversely, no one but the analysts and people at TRADOC had any idea of how to deal with the cold war threats. Asking the people at the sharp end back then to write the FM wouldn't have made any sense either.
Cheers,
Dave
They that can give up essential liberty to obtain a little temporary safety deserve neither safety nor liberty.
Ben
A while back I was reading a survival page from a practicing guide and Park Ranger working in the Texas desert. He had made a point about the standard "suck out the poison" from a snakebite advice still being in the army field manual long after anyone in the medical community, or desert survival park ranger community had given up the practice.
http://ridgerunnersurvival.tripod.com/da1.htm
Now the page is from 2000 and he's quoting the various field manuals up to 1992. There's also advice on why water rationing as described in the manuals is a bad idea. Digging a condensation trap will cost you more sweat than it will gather in drinking water, etc.
So I wonder what other areas it might be better to enlist some subject matter experts in, the idea of opening it up to more voices outside the war colleges is good, maybe they should open it up even more.
And like a good wiki-citizen he cites the books he references and his credentials.
This isn't really new, per se, but it is a reassertion of one of the best values of American soldiery - the guy on the ground should have some room to make some decisions for himself or herself. Good commanders have always encouraged their subordinates to lead, and given them tools to do so. Bad commanders don't.
This is my sig.
...but in practice, this could have potential for serious disaster.
There are just some things that should NEVER be subject to change without extensive and careful review.
Case in point: MRCs or Maintenance Requirement Cards.
Basically, they're mini manuals on how to perform preventative maintenance on your gear, some of which can be outrageously deadly if you don't follow the instructions to the exact letter. You really wouldn't believe how much stuff on a ship gets the label "MANKILLER", and I've no doubt the Army is little different, quite probably much worse. MRC cards have, quite literally in many cases, been written with the blood of those who discovered the "wrong way" to perform maintenance or took a "shortcut".
Army field manuals are much like MRC cards; they've been written either by those who've shed the blood, or by those who had to mop up the mess from those who didn't survive. They might look nice and boring in the way they read, but that dry tone of the manuals carries many, many lives behind it.
I hope these edits are subject to extensive review, and won't just pop up for everyone to follow with a click of a mouse? Otherwise, someone might try to get their lulz, and we might see subjects like...
Maintenance Requirement for the M33A1/M59 High Explosive Fragmentation Grenade
[End Of Line]
Taking into account what happens on Wikipedia sometimes - vandalism - I gotta say it occured to me that the percent of vandals re-writing and thus spoiling good articles goes down in proportion to the size of the public for the amount of pages said Wiki would contain. Simpler put, Wikipedia being a Wiki for the broadest possible public - the general public, no restrictions - is substantially more suspectible to vandalism than say a Wiki shared, written and accessed by 10 individuals (an intranet Wiki, for example). Add to that a relatively simple fact that probably any soldier with his sanity in behold will refrain from mal-editing Wiki entries on semi-automatic rifles because he knows he may be shot in the head by one held by his comrade - this makes the Army somewhat more of a unity than the general public, which generally does not care much for one another - everyone being anonymous and all. In the army, they would think twice before resorting to Wiki vandalism, because they know they may have to fight side by side, in which case you need all experience you can get from your buddies. The two factors should make for a very useful implementation indeed.