Decision Style Matrix

Work through eight short questions about one decision, pick a style between deciding alone and deciding together, adjust it for time, stakes and development, and tell people in advance how much say they have.

The contrast between autocratic and democratic leadership is strong research (Lewin, Lippitt & White, 1939; DeRue, Nahrgang, Wellman & Humphrey, 2011). The Vroom-Yetton decision model has mixed evidence, with most of its validation from its own authors (Vroom & Yetton, 1973; Vroom, 2000; Vroom & Jago, 2007). Use its recommendation as a structured starting point to argue with.

Use it when:

• A decision is coming that affects other people's work, and you are unsure whether to decide, consult or decide together.
• Past decisions have stalled in implementation, or people said they were "consulted" on something already settled.
• You lead a team, a project or your own business and want your decision habits to be a choice rather than a temperament.

Skip it when:

• You need to test the decision itself for bias and risk: use 3.6 Decision-Making Checklist.
• You need standing rules for which kinds of decisions the team makes: use 4.4 Ways of Working Agreement.

How much you involve others in a decision should itself be a decision, made case by case, not by temperament. The underlying contrast between autocratic and democratic leadership is old and well studied, going back to experiments with group climates (Lewin, Lippitt & White, 1939). Vroom and Yetton (1973) turned it into a procedure: a few diagnostic questions about how much quality matters, what you know, whether people must accept the result and whether they share the goal, which point to a style somewhere between deciding alone and deciding together (Vroom, 2000).

The evidence is mixed, and most of the validation comes from the model's authors, so treat the output as a recommendation to argue with, not an algorithm. The mechanism is still sound: the questions make you name what this decision requires before habit picks the style. Most of the value lies in answering them honestly, since wishful answers lead to comfortable styles. The page then adds what the questions underweight (time, stakes, developing people) and asks you to announce the style in advance.

Write the decision as a question with a deadline. Note whether it could be undone cheaply.

Strong answer: "How do we lay out the picking zones before peak season? Decide by 1 October. Stakes high: a bad layout costs us every shift through December. Hard to undo once the racks are moved."

What you are deciding:

Deadline:

Stakes: ☐ Low ☐ Medium ☐ High ☐ Critical

Easy to undo? ☐ Yes ☐ No

Illustrative example: the company, the roles and the details are made up.

An operations manager at a logistics warehouse near Gothenburg must decide the picking-zone layout before peak season.

Step 1: decide by 1 October; stakes high; hard to undo once the racks move.

Step 2: quality high; leader information no (the pickers know where time is lost); problem structure partly; acceptance needed; acceptance probability no, because the last layout he decided alone was ignored on night shift; goals shared; disagreement likely between shifts; team information yes.

Step 3: the rules point toward GII, but he chooses CII: he keeps the final call because of the deadline and the safety rules on rack placement, and says so openly.

Step 4: three weeks is enough for one session per shift; he also wants the shift leads to own layout questions next year.

Step 5: one session per shift with the volume data, decision by 1 October, and a note on the board showing which suggestions were used. Before he announces the sessions, he asks HR whether the change calls for MBL negotiation with the union.