I contend thusly:
"General Orders for Sentries" is one of the finest written processes of all-time.
You can read the orders here, if you like, for the various branches of the U.S. Armed Forces --
On the surface, it's a pretty simple thing, being a sentry. "Watch this area. Tell us if anything odd happens."
In practice, there's thousands of permeations of things that can go wrong when you're guarding an area, and a sentry failing in his duty could lead to -- literally -- thousands of people getting killed.
(Millions, even, if you consider the cascading effects of losing a war to a side like the Nazis, North Koreans, or Khmer Rouge.)
Here are the orders at a high level for the U.S. Navy and U.S. Marine Corps --
1. To take charge of this post and all government property in view.
2. To walk my post in a military manner, keeping always on the alert and observing everything that takes place within sight or hearing.
3. To report all violations of orders I am instructed to enforce.
4. To repeat all calls from posts more distant from the guardhouse (or the Quarterdeck) than my own.
5. To quit my post only when properly relieved.
6. To receive, obey, and pass on to the sentry who relieves me, all orders from the Commanding Officer, Command Duty Officer, Officer of the Day, Officer of the Deck, and all Officers and Petty Officers of the watch only.
7. To talk to no one except in the line of duty.
8. To give the alarm in case of fire or disorder.
9. To call the Corporal of the Guard or Officer of the Deck in any case not covered by instructions.
10. To salute all officers and all colors and standards not cased.
11. To be especially watchful at night and during the time for challenging, to challenge all persons on or near my post, and to allow no one to pass without proper authority.
As you can see right away, this is short enough to memorize and know by heart. In fact, the Navy and Marines drill on these. "It is very common for a drill instructor or (after boot camp) an inspecting officer to ask a question such as, "What is your sixth general order?" and expect an immediate (and correct) reply."
Where these orders really shine is in that there is a very true and elegant set of human nature. Consider the expanded version of Order #8, "To give the alarm in case of fire or disorder":
"While this is rather straightforward and obvious, keep in mind that a fire or disorder of some kind might be a deliberate distraction to keep you from observing some other disorderly or subversive activity. If you are certain that a fire is not meant to be a distraction, you should fight the fire if you have the means to do so. Remember, however, that your first responsibility is to report whatever is amiss."
Consider the sheer pragmatic brilliance of that paragraph.
Fires have been set as diversions since the dawn of history: Scipio Africanus famously destroyed the Numidian and Carthaginian forces by setting a night fire to King Syphax's camp, and the Carthaginians rushed to assist without checking if it was set by the enemy -- the Romans cut down 40,000 Carthaginian and Numidian forces that night. Such is the danger of a sentry turning to firefighting and not raising the alarm.
But, can you imagine what a senior officer would typically say to a sentry who doesn't fight a genuinely bad fire if it wasn't explicitly in the orders? "Sir, my duty is to the General Orders, I cannot fight the fire" -- this would bring hell down upon a soldier in any time, unless the duties are explicitly clear.
As such, the Orders acknowledge that you might fight a fire but only once you confirm it's not a deliberate distraction and only after it has been reported.
This seems like a good compromise between the ideal order which wouldn't be followed ("never abandon sentry duties; it's more important to be alert than have one more set of hands to fight a fire") and human nature (immediately start fighting the fire and allow your side to be ambushed).
The elaboration on Order #1 is good, too:
"When you are a sentry, you are "in charge." This means that no one—no matter what their rank or position—may overrule your authority in carrying out your orders. The only way that you may be exempted from carrying out your orders is if your orders are changed by your superior. For example, if your orders are to allow no one to enter a fenced-in compound, you must prevent everyone from entering, even if an admiral tells you it is all right for him or her to enter. The petty officer of the watch (or whoever is your immediate superior) may modify your orders to allow the admiral to enter, but without that authorization you must keep the admiral out. Situations such as this will not often, if ever, occur, but it is important that you understand the principles involved. It is also your responsibility to know the limits of your post. This information will be conveyed to you among your special orders. You must also treat all government property that you can see as though it were your own, even if it is not technically part of your assigned post."
The Orders aren't based in some sort of Platonic ideal of good sentry duties, but rather the most common conflicts and errors. What do you do if you're a sentry and a high-ranking officer demands to be admitted to somewhere? You report it to the petty officer, who can modify orders.
Because these orders are universally known, a high-ranking officer demanding an exception is the one who is doing something out of line -- this means that rogue forces with fake uniforms or single bad actors can't undermine critical areas, and also sets a clear precedent for what should happen, and how requests for exceptions to the rules are to be managed.
My friend Kai Zau (coauthor Gateless; we've done a number of commercial, scientific, educational, nonprofit projects together) -- he and I obsess over operations, communications, details, and how to get things done.
"General Orders for Sentries" seems to come up very often between us in conversation: it's a set of rules that collapses so small that it can be memorized and said on command, it covers all the general situations, it covers the most dangerous exceptions and where things go wrong, it squares with human nature and is actually achievable, and then it goes in greater detail that can be studied and trained in.
If you're interested in operations, I highly recommend you go read and study the whole Wikipedia page on it. While on the topic, the Code of the United States Fighting Force is a very worthwhile read, too. When your procedures and processes start to approach this level, you know you're doing something right.
Other odds and ends:
We're doing the GiveGetWin Tour 2015 again this year. Details to be released relatively shortly, starting 15 March in San Francisco. If you'd like to be involved, email me.
For early readers of my next book, I finished the complete rough draft towards the start of the last month. I'll send it along reasonably shortly after cleaning up two last large pieces that I know need a quick re-write and have scoped... I knew I had something big coming up, so I marched it hard to get it done before starting.
On that note, my apologies for delayed email replies lately -- I took one of the largest projects in my life, both in scope and in stakes... I've been all-in on that, but I'm getting some breathing room to catch up. Thanks.