A practical guide for managers to make faster, better decisions. Covers delegation frameworks, stakeholder management, strategic vs tactical decisions, and building a decision-making culture within your team.
- The Manager's Decision Burden
- Decision Classification
- Delegation Framework
- Strategic Decision Making
- Speed vs Quality Trade-offs
- Stakeholder Alignment
- Data-Informed Decisions
- Building Team Decision Skills
- Decision Documentation
- Common Manager Pitfalls
- Templates
- Resources
Managers make an estimated 35,000 decisions per day. Most are trivial, but a handful have outsized impact. The key to effective management is not making every decision well -- it's identifying which decisions matter and investing appropriately.
- 80% of decisions should be delegated or decided in under 2 minutes
- 15% need structured analysis (30 minutes to 1 day)
- 5% are strategic and deserve deep deliberation (days to weeks)
Most managers spend too much time on the 80% and too little on the 5%.
| Type | Characteristics | Approach | Example |
|---|---|---|---|
| Type 1 | Irreversible, high-stakes | Deliberate, data-driven, consult widely | Org restructuring, major hire |
| Type 2 | Reversible, lower-stakes | Decide quickly, delegate freely | Process changes, tool selection |
Before making a decision, ask:
1. Is this reversible? (If yes → decide faster)
2. What's the cost of being wrong? (Low → delegate)
3. What's the cost of delay? (High → decide now)
4. Who has better context? (Not you → delegate)
5. Does this set a precedent? (Yes → invest more time)
| Delegate | Keep |
|---|---|
| Decisions where team has better context | Decisions that set team direction |
| Reversible operational choices | Hiring and firing decisions |
| Technical implementation details | Budget allocation over $X threshold |
| Process improvements | Cross-team commitments |
| Day-to-day prioritization | Organizational restructuring |
| Level | Description | Manager Action |
|---|---|---|
| 1 | Tell | "Do exactly this" |
| 2 | Sell | "I've decided this, here's why" |
| 3 | Consult | "I want your input before I decide" |
| 4 | Agree | "Let's decide together" |
| 5 | Advise | "I'll share my thoughts, you decide" |
| 6 | Inquire | "Tell me what you decided" |
| 7 | Delegate | "You decide, I trust your judgment" |
Match the level to the decision's importance and the team member's experience.
- Delegating authority but not information
- Delegating and then micromanaging
- Not delegating enough (bottlenecking yourself)
- Delegating without clear success criteria
Observe → Orient → Decide → Act → (repeat)
- Observe: Gather data from multiple sources (metrics, team, customers, market)
- Orient: Analyze through your mental models and experience
- Decide: Commit to a course of action with clear criteria
- Act: Execute quickly and measure results
## Decision: [Title]
### Context
- What business problem are we solving?
- What has changed that makes this decision necessary now?
### Options
1. [Option A]: Pros, cons, risks, effort
2. [Option B]: Pros, cons, risks, effort
3. [Do nothing]: What happens if we delay?
### Criteria (weighted)
- Business impact (40%)
- Feasibility (25%)
- Team capability (20%)
- Risk level (15%)
### Recommendation
[Your recommendation with reasoning]
### Success metrics
[How we'll know if this was the right call in 3/6/12 months]- The cost of delay exceeds the cost of being wrong
- You have 70%+ of the information you need (Jeff Bezos's rule)
- The decision is easily reversible
- Your team is blocked waiting for a decision
- The decision is irreversible or very expensive to reverse
- Key stakeholders haven't been consulted
- You're making the decision emotionally (angry, excited, pressured)
- New information is expected within a defined timeframe
"If you wait for 90% of the information, you're too slow. Most decisions should be made with about 70% of the information you wish you had." -- Jeff Bezos
But this only applies to Type 2 (reversible) decisions. Type 1 decisions deserve more patience.
| Influence Level | Supportive | Neutral | Opposed |
|---|---|---|---|
| High | Champion (leverage them) | Inform early (bring on board) | Manage actively (address concerns) |
| Medium | Keep informed | Low priority | Monitor sentiment |
| Low | Thank and update | Ignore (nicely) | Note but don't overreact |
For important decisions, never surprise stakeholders in a meeting:
- Share the proposal in writing 48 hours before the meeting
- Have 1:1 conversations with key stakeholders
- Understand and address objections before the group discussion
- Use the meeting to confirm, not to debate
| Extreme | Problem | Better Approach |
|---|---|---|
| Data-driven (only data) | Ignores context, judgment, and qualitative factors | Use data as input, not the sole arbiter |
| Gut-driven (no data) | Susceptible to bias and blind spots | Always look at data, even imperfect data |
For Type 2 decisions: Quick metrics check, team input → decide
For Type 1 decisions: Deep analysis, A/B test if possible, expert consultation → decide
- What does the data actually say? (Not what we want it to say)
- What's the sample size and confidence level?
- Are there confounding factors?
- What data are we missing?
- What would change our mind?
For managers building a track record of decisions over time, KeepRule provides a structured way to log decision context, rationale, and outcomes. Reviewing this log quarterly helps you identify patterns in your decision-making strengths and blind spots.
The best managers develop their team's decision-making ability:
- Share your reasoning: When you make decisions, explain your thought process
- Ask coaching questions: "What would you recommend?" before sharing your opinion
- Allow mistakes: Let people learn from reversible bad decisions
- Debrief decisions: Review outcomes together (good and bad)
- Increase delegation gradually: Raise the stakes as judgment improves
| Healthy Culture | Unhealthy Culture |
|---|---|
| Decisions are documented | Decisions happen in hallways |
| Disagreement is expected and welcome | Everyone agrees to avoid conflict |
| Decisions have clear owners | "We" decided (no accountability) |
| Speed is valued | Perfect analysis is valued |
| Failures are learning opportunities | Failures are punished |
- Your team needs to understand and execute decisions
- You need to remember your own reasoning 6 months later
- New team members need context for existing decisions
- Leadership needs visibility into your reasoning
For every significant decision, capture:
**Date**: [date]
**Decision**: [one sentence]
**Context**: [why now]
**Alternatives considered**: [brief list]
**Rationale**: [why this option]
**Owner**: [who executes]
**Review date**: [when to revisit]Maintaining this discipline becomes much easier with a dedicated tool. KeepRule makes it simple to create, search, and review management decisions, turning your experience into a searchable knowledge base that compounds over time.
| Pitfall | Description | Fix |
|---|---|---|
| Analysis paralysis | Overthinking reversible decisions | Set decision deadlines |
| Consensus addiction | Needing everyone to agree | Use RAPID -- one decider |
| Recency bias | Overweighting recent events | Look at 12-month trends |
| Sunk cost fallacy | Continuing failing initiatives | Ask "Would I start this today?" |
| Authority bias | Deferring to the highest-ranking person | Seek input before revealing your opinion |
| Bottlenecking | Being the single decision-maker | Delegate more Type 2 decisions |
| Decision fatigue | Poor decisions late in the day | Schedule important decisions for mornings |
## Week of [Date]
| Decision | Type | Options | Chosen | Rationale | Review Date |
|---|---|---|---|---|---|
| | 1/2 | | | | |## Decision Coaching: [Team Member]
**Decision**: [What they need to decide]
**Their recommendation**: [What they suggest]
**My questions**:
1. What's the biggest risk?
2. What data supports this?
3. What would change your mind?
**Outcome**: [Did I agree, coach, or redirect?]- High Output Management by Andy Grove
- The Manager's Path by Camille Fournier
- An Elegant Puzzle by Will Larson
- Thinking in Bets by Annie Duke
- Decisive by Chip and Dan Heath
Share your management decision frameworks and real-world examples. Battle-tested approaches from experienced managers are especially welcome.
MIT License - see LICENSE for details.