Strategic Procrastination
The deliberate practice of delaying action on tasks that may become unnecessary, resolve themselves, or benefit from additional information gained through waiting.
Also known as: Intentional Delay, Deliberate Procrastination, Productive Waiting
Category: Techniques
Tags: productivity, techniques, decision-making, time-management, mindsets
Explanation
## What Is Strategic Procrastination?
Strategic procrastination is the intentional decision to delay action on certain tasks, not out of avoidance or fear, but from the recognition that many tasks will resolve themselves, become irrelevant, or benefit from the additional context that time provides. It is a form of productive laziness that conserves energy for work that truly matters.
## The Insight
Not all tasks that appear on your plate require immediate action. Some common patterns:
- **Self-resolving tasks**: issues that fix themselves or get handled by someone else if you wait
- **Disappearing tasks**: requests that the requester forgets about or deprioritizes
- **Clarifying tasks**: problems that become better defined with time, making the eventual solution more efficient
- **Premature tasks**: work that would need to be redone if started too early due to changing requirements
## How It Differs from Regular Procrastination
| Regular Procrastination | Strategic Procrastination |
|---|---|
| Driven by avoidance or anxiety | Driven by deliberate assessment |
| Unconscious and reactive | Conscious and intentional |
| Increases stress over time | Reduces total workload |
| Delays everything indiscriminately | Selectively delays specific tasks |
| Eventually requires rushed completion | Often eliminates the task entirely |
## How It Differs from Structured Procrastination
Structured procrastination (John Perry) is about doing useful task B while avoiding task A. Strategic procrastination is about deliberately not doing task A at all, betting that it won't need to be done.
## When to Apply
Strategic procrastination works best for:
- Requests from others that may not persist
- Tasks with unclear or shifting requirements
- Low-stakes decisions that don't compound with delay
- Feature requests that may be superseded by other changes
It should NOT be applied to:
- Time-sensitive deadlines with real consequences
- Tasks where delay increases cost or difficulty
- Commitments made to others
- Health, safety, or legal obligations
## Practical Implementation
- **Wait 48 hours** before acting on non-urgent requests
- **Use a parking lot**: collect tasks you're strategically delaying and review periodically
- **Track your hit rate**: monitor how many delayed tasks actually needed doing
- **Set review dates**: don't forget indefinitely -- schedule check-ins on delayed items
Related Concepts
← Back to all concepts