Skip to content

implementation-intentions.md

Latest commit

 

History

History
94 lines (70 loc) · 2.82 KB

implementation-intentions.md

File metadata and controls

94 lines (70 loc) · 2.82 KB

Overview

Implementation Intentions are specific plans that spell out when, where, and how you will act on a goal using an if-then format: "If situation X arises, then I will perform response Y."

The Science

Research shows implementation intentions:

  • Increase goal achievement by 2-3x
  • Automate desired behaviors
  • Reduce decision fatigue
  • Overcome procrastination
  • Bridge intention-action gap

Format

Standard Goal: "I will work on my report."

Implementation Intention: "If it's 9am on Tuesday, then I will work on my report at my desk for 2 hours."

Components

  • Trigger (If): Specific situation/time
  • Action (Then): Concrete behavior
  • Context: Where/how specified

Examples

Time Management

  • "If it's 8:30am, then I will start my most important task."
  • "If someone requests a meeting during my focus block, then I will suggest alternative times."
  • "If I finish a task early, then I will start the next planned item."

Overcoming Obstacles

  • "If I feel like checking email, then I will wait until my designated email time at 11am."
  • "If an urgent request comes in, then I will ask if it can wait until after my focus session."
  • "If I'm tempted to multitask, then I will close all other tabs and focus on one thing."

Building Habits

  • "If it's Friday at 4pm, then I will review my week and plan next week."
  • "If I complete a pomodoro, then I will take a 5-minute break."
  • "If I log off for the day, then I will note my stopping point for tomorrow."

Creating Effective IIs

Be Specific

  • ❌ "When I have time, I'll exercise"
  • ✅ "If it's 7am on Monday/Wednesday/Friday, then I'll do a 30-minute workout"

Link to Cues

  • Time-based: "At 2pm..."
  • Event-based: "After lunch..."
  • Situation-based: "When email notification appears..."

Make It Actionable

  • Clear, concrete action
  • Within your control
  • Measurable completion
  • Realistically achievable

Integration with Time Tracking

Track Adherence

  • Log when IIs are followed
  • Measure completion rate
  • Identify effective triggers
  • Refine based on data

Create Time-Based IIs

  • "If my time log shows <20 hours on Project X, then I will block 4 hours next week."
  • "If I've had 3 low-productivity days, then I will adjust my schedule."

Benefits

  • Reduces need for willpower
  • Automates good behaviors
  • Overcomes decision paralysis
  • Increases consistency
  • Bridges planning-action gap
  • Handles obstacles proactively

Common Mistakes

  1. Too vague: "If I can, then I will..."
  2. Unrealistic: "If it's Monday, then I'll complete my entire project."
  3. No trigger: "Then I will work out" (missing the if)
  4. Multiple actions: Trying to change too much at once

Best Practices

  1. Start with 2-3 IIs maximum
  2. Focus on biggest challenges
  3. Write them down
  4. Review weekly
  5. Adjust based on experience
  6. Celebrate successes