<aside> <img src="/icons/info-alternate_yellow.svg" alt="/icons/info-alternate_yellow.svg" width="40px" /> This page is part of The Toolbox by Danny Smith.
</aside>
The military has long made use of Warning Orders to give advance notice of operations to troops. Once a unit commander receives orders they’ll issue a quick Warning Order to their troops outlining the situation, their mission, the scope of operations and the time and place of the O Group where they’ll brief the team on the detailed plans. They’ll usually include a No Move Before time and basic details of required personnel & equipment, as far as it’s known. This gives the troops a chance to start preparing for the mission while the commander works out a detailed plan and prepares his orders for them.
A warning order (WARNO) gives subordinates advance notice of an upcoming operation. This gives them time to prepare. A warning order is brief but complete – US Ranger Handbook
This concept can be useful in a business setting, too. It’s a way for leaders to tell people that there's a change that they will have to action, but we don't have a fully-formed plan yet. It gives people a chance to prepare, but is explicit about the fact that details will probably change once the full plan is worked out.
While I’ve seen one company use WarnOs quite formally (they even called them that), I often see the concept applied more informally as a kind of expanded version of a “heads up”. In remote companies, it’s very normal to use this concept to prepare for meetings (see ‣).
It’s also possible to use WarnOs to give advance notice about other stuff though, in which case they should probably include…
Here’s a made-up example…