STRATEGYOngoing practice

Grove's Decision-Making Process

Free discussion, clear decision, full support

Problem it solves

unclear strategic direction

Best for

Knowledge-work organizations where decision-making authority must balance position power and expertise

Not ideal for

Simple, routine decisions that do not require group input

Overview

Why this framework exists

In knowledge businesses, power based on position and power based on knowledge rapidly diverge. The ideal decision-making process has three stages: free discussion where all viewpoints are openly welcomed and debated; a clear decision framed with utter clarity; and full support from all participants, whether they agree or not. Decisions should be made at the lowest competent level by people closest to the situation. The key insight is that commitment to support a decision is different from agreement with it, and organizations survive on commitment, not unanimity.

Core principles

6 total
  1. Free discussion must be genuinely free—withholding opinions produces bad decisions
  2. The greater the disagreement, the more important the word 'clear' becomes in the decision
  3. Full support does not require agreement—only honest commitment to back the decision
  4. Decisions should be made at the lowest competent level, closest to the situation
  5. Knowledge power and position power must be balanced through the middle manager
  6. Obscuring a controversial decision only postpones the argument

Steps

4 steps
  1. Stage Free Discussion
    Create space where all points of view and all aspects of an issue are openly welcomed and debated. The greater the controversy, the more important it is that discussion be genuinely free. Resist the tendency to wait and see which view will prevail before speaking.
    Pro tipIf knowledgeable people withhold opinions, the decision will be based on incomplete information. The manager must actively encourage dissent.
    WarningSome organizations reward people for waiting to echo their superiors' views. This is a terrible way to manage and produces consistently bad decisions.
  2. Reach a Clear Decision
    Frame the decision with utter clarity. The more controversial the issue, the more precisely the decision must be stated. Resist the urge to be vague in order to avoid conflict—that only postpones the argument.
  3. Secure Full Support
    All participants must commit to back the decision. This does not mean agreement. People may disagree but must honestly commit to support and execute. An organization lives by commitment, not by consensus on every issue.
    Pro tipA useful test from Grove: 'Andy, you will never convince me, but why do you insist? I've already said I will do what you say.' Commitment is sufficient; agreement is nice but not necessary.
    WarningDon't confuse your emotional comfort with operational need. You need commitment, not agreement.
  4. Keep Decision Meetings Small
    Decision-making meetings should have no more than six to eight attendees. Decision-making is not a spectator sport. Send minutes quickly afterward documenting what was decided, who is responsible, and by when.

Checklist

Saved in your browser

Examples

1 cases
Intel's Six-Question Decision Framework

For important decisions, Grove advocated structuring the process around six questions: What decision is needed? By when? Who should be consulted? Who decides? Who ratifies or vetoes? Who needs to be informed?

OutcomeThis framework ensures decisions happen at the right level, with the right input, and clear accountability for follow-through.

Common mistakes

3 traps
Waiting to hear the boss's view before speaking
Grove quotes an automobile executive who was told to wait for superiors to express their views before contributing. This produces decisions based on incomplete information and kills innovation.
Being mealy-mouthed about controversial decisions
When we know a decision is controversial, the instinct is to obscure it. But people affected will be far angrier if they don't get a prompt, straight story.
Insisting on agreement rather than commitment
Grove himself fell into this trap, insisting on convincing a subordinate rather than accepting his commitment to act. The insistence served Grove's emotional comfort, not the business.

Origin story

How this framework came to be

Grove observed that at Intel, technical knowledge became obsolete quickly. Veteran managers with position power were often less current on technology than junior engineers with knowledge power. Traditional top-down decision-making would mean decisions made by people unfamiliar with current realities. He developed this three-stage process to let knowledge and experience mesh properly, with middle managers serving as the crucial link.

Source

Traced to primary
Source · BOOK
High Output Management
Andrew S. Grove · 1983
Open source →

Related frameworks

Browse all Strategy →