BDSM

Basic Doctrine, Staff, and Mission

What you thought I was talking about something else?  This is MUCH dirtier.

Doctrine, Staff, and Mission are some of the most critical elements of getting anything done in combat operations.  These three items form a tripod that supports everything any organization (military or otherwise) tries to do.

Let’s start with an exciting story.  On December 19th the Allied commanders met at Verdun to discuss how they would respond to the German Offensive that would come to be called the Battle of the Bulge.  Eisenhower asked Patton how long it would take him to turn his army north to attack the southern flank of the German offensive.  Patton responded that he could launch and attack within 48 hours.  Everyone at the table was flabbergasted.  They thought there was no way an army could stop its forward movement, pivot, reorganize its logistics and attack in a new direction that quickly.  And they were right.

Patton however cheated.  Before travelling to Verdun, he gave his Staff a Mission and using Doctrine developed over the bloody years of WWII his staff was able to issue orders, reorganize the troops, and launch the attack on Patton’s timetable.

See those italicized words?  They didn’t get there by accident.  Now let’s talk games.  I’m going to go an example from EvE.

Your corporation is planning on occupying a Wormhole.  You have 30-40 people and can rely on 20 logging in for a planned operation.  Does the CEO just send an EvE mail telling people to log in on such and such a date to get into a wormhole?  Well… probably yes.  But it’s not what he should do.  First they decide the overall goal and what steps it will require.  This will likely involve discussion with key corporation members who know about wormhole mechanics, scouting, probing, ship fitting, POS operations, capital ship construction, etc.  This discussion will lead to a series of steps preparing to enter and exploit the wormhole, THEN the CEO sends an EvE Mail.

Now I’m about to butcher the 12-step process that is MDMP (Don’t ask.  If you don’t know you are MUCH better off).  The CEO sets a vague mission outline.  Usually known as the Commander’s Intent.  He then brings his staff together.  This is the subject matter experts, they are his staff.  They meet and talk about what steps need to be done, what materials need to be gathered, what ships, people etc.  They establish a doctrine that the corporation will follow.  This doctrine can be adapted later for moves into future wormholes, or even into other areas.

Now, assuming that nothing interrupts the process (drunken aussies tackling a carrier in the target wormhole *ahem*) your group will have a Mission to accomplish, a Doctrine to accomplish it with, and a Staff to blame when it doesn’t work.

This model can be adapted to other games, but it’s a time intensive process.  It’s often overkill to go through the whole thing for every little operation.  However when you are working on a project you will do repeatedly, for example Raid Progression, or Clan Wars, it can be useful to do the whole process out the first time because it’s MUCH easier to adapt (steal) pages from earlier doctrine than to reinvent the wheel, and you end up with fewer square wheels at the end.

Advertisements

About Corelin

An Eve playing Fool who occasionally writes about the shenanigans he and his minions get up to.

Posted on January 9, 2016, in Uncategorized. Bookmark the permalink. 1 Comment.

  1. In my defence, I wasn’t that drunk.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: