Hampton, Va. (April 3, 2006) - Mark Drajeske explains to Herman Hill the Common Ground Truth Server which displays a consistent representation of the ground, to aid in tactical decision making in the battlefield, during the 2006 U.S. Joint Forces Command (USJFCOM) Industry Symposium, held at the Ham. Decision skills guide: five roles, and why reversibility sets the process
Photo by U.S. Navy photo by Photographer's Mate Airman Apprentice Patrick Gearhiser on Wikimedia Commons, Public domain

Rules

Part of Decision skills fields compared: statement, constraints, criteria and reversibility

Decision skills guide: five roles, and why reversibility sets the process

A decision skills guide to roles and sizing: decider, recommender, consulted, informed and veto, and why reversibility rather than cost sets the process.

Most stuck decisions are not stuck on evidence. They are stuck because nobody has said who decides, and the group is trying to reach a state of agreement that was never required.

This guide is about the second half of decision skill: the roles, and how to size the process to the decision so that small choices do not consume the process built for large ones.

What to take away

  • Deciding, being consulted, and being informed are three different jobs. Most friction comes from people holding one and believing they hold another.
  • Reversibility is the main dial for how much process a decision deserves.
  • Say the roles out loud before the discussion, not after it has gone wrong.

The role words, defined

Decider. The person who says yes or no and lives with it. Exactly one, or

Five decision roles compared

Decider

Core job
Says yes or no
Authority
Final call
Obligation
Own outcome
Failure mode
Two deciders

Recommender

Core job
Proposes an answer
Authority
None
Obligation
Work problem
Failure mode
Announced twice

Consulted

Core job
View must be heard
Authority
None
Obligation
Listen, not agree
Failure mode
Feels overruled

Informed

Core job
Must know after
Authority
None
Obligation
No input owed
Failure mode
Told too late

Recommender. The person who works the problem and proposes an answer. Its nearest neighbor is the decider, and the difference is authority: a recommendation can be rejected without anything having gone wrong.

Consulted. Someone whose view must be heard before the decision. The obligation is to listen, not to agree. Being consulted and then overruled is a normal outcome, and treating it as a failure is what makes people stop offering views.

Informed. Someone who must know afterward. No input is owed, which is why telling people they are informed rather than consulted is a kindness rather than a slight.

Veto. A right to block, usually held for a narrow reason such as legal or safety exposure. A veto that can be used on general grounds is a second decider, and two deciders is the same as none.

Where the roles get confused

The reality

I am consulted
I am informed
I am the decider
I am the recommender
We all decide
Nobody decides
I hold a veto
I hold a strong view

What happens

I am consulted
Views arrive after the decision
I am the decider
The decision is announced twice
We all decide
Discussion continues until someone tires
I hold a veto
Escalation, then resentment

The third row is the most common and the most expensive. Consensus is a

desirable feeling, not a decision procedure, and a group that requires it hands the decision to whoever is most willing to keep talking.

Sizing the process to the decision

Two questions do almost all of the work. First, how hard is this decision to reverse? Second, how many people does it bind?

Sizing the process to reversibility

Can it be undone, and at what cost?

Yes

fast process and a review date

No

slow process, written record, named owner

An easily reversed decision deserves a fast process and a review date. A hard to reverse decision deserves a slow one, a written record, and a named person who would be wrong. The mistake is applying the same weight to both, which produces either paralysis on small things or carelessness on large ones.

There is a third question worth adding where the answer to the first is uncertain: what would it cost to find out how reversible this is? Sometimes that is a cheap experiment, and running it converts a hard decision into two easy ones.

Note what these questions do not ask. They do not ask what has already been spent. Money and effort already committed are gone whichever way you choose, and the nine acumen confusions cover the version of this that shows up in operating decisions.

The order that works

  1. Write the decision as a choice, not a topic. "Whether to accept the standing order at the offered price" is a decision. "Pricing" is a subject heading.
  2. Name the decider, the recommender, and who is consulted, before any discussion.

The order that works

  1. Write the decision as a choice
  2. Name decider, recommender, consulted
  3. Say when the decision will be made
  4. Record reasoning and what would change it
  5. Set a review trigger, not a date
  1. Write the decision record while the reasoning is still fresh.
  2. Set a review trigger rather than a review date wherever a trigger can be defined.

Step four is where the value accumulates. A record of reasoning is the only thing that lets you tell a bad decision from bad luck later, and the decision record fields set out what it has to contain.

The fields are short: the decision, the decider, the date, the reasoning, and the trigger. A worked entry for the standing order above reads: accept the order, owner decides, dated Friday, reasoning is margin per unit, trigger is the buyer asking for longer terms.

What the roles do not fix

Naming roles does not create authority that does not exist, and it does not make a genuinely hard trade-off easy. It removes a specific class of waste: the argument about whose argument counts.

It also does not settle whether the reasoning is good. Two people can agree on who decides and both be reasoning from the same confirmation bias. The protection against that is asking, in advance, what evidence would change your mind, and then noticing whether it ever arrives.

Common questions

What if the real decider is not the nominal one?

Then say so privately and work with the real one. Running a process that ignores where the authority sits produces a decision that gets reopened, which is worse than a slower honest process.

Does naming roles work in a small business with three people?

It works better there, because the roles are usually held informally and sincerely believed to be shared. Writing down who decides what takes ten minutes and prevents the argument that otherwise arrives during the first hard month. The business acumen walkthrough shows one such decision end to end.

Is consensus ever the right procedure?

Where the decision requires voluntary effort from everyone afterward, agreement is worth buying and the extra time is well spent. Where it does not, consensus is a cost with no return.

How do I disagree and still support the decision?

Say your objection once, in full, on the record, and then act as though the decision were yours. That is a defensible position and a common one. It stops being defensible if you keep relitigating it in private.

Where does the group's information come from?

From whoever has it, which is usually not the most senior person in the room. The Small Business Administration's guidance on market research is a reasonable model for the outside-facing half: decide what you need to know before you decide where to look.

How do I keep this from becoming bureaucracy?

Apply it only where the decision is hard to reverse or where more than two people are involved. Everything else can be decided by the person closest to it, told to the people who need to know, and revisited if it turns out badly. The communication skills guide covers the telling.

More in Rules

Latest from Reporting Desk