focus-timeboxing-8020

What this skill does

# Focus, Timeboxing, and 80/20

## Table of Contents
- [Workflow](#workflow)
- [Common Patterns](#common-patterns)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)

## Example

**Scenario**: Engineer overwhelmed with tickets, meetings, code reviews, and a complex feature.

**80/20**: Ship payment feature (biggest customer request, revenue impact) = vital 20%.

**Weekly Plan**:
- Mon-Wed mornings (9-12): Deep work on payment feature (no meetings, Slack off)
- Mon-Wed afternoons: Code reviews, standups, pair programming
- Thu-Fri: Batch meetings, planning, admin, lower-priority tickets

**Outcome**: Feature shipped in 3 days (18 hours deep work) vs. estimated 2+ weeks with constant interruptions.

## Workflow

Copy this checklist and track your progress:

```
Focus & Timeboxing Progress:
- [ ] Step 1: Identify your 80/20
- [ ] Step 2: Design focus blocks
- [ ] Step 3: Timebox your week
- [ ] Step 4: Timebox your day
- [ ] Step 5: Execute with discipline
- [ ] Step 6: Review and adjust
```

**Step 1: Identify your 80/20**

What 20% of tasks drive 80% of your results? Separate vital few from trivial many. See [resources/template.md](resources/template.md#8020-analysis-template).

**Step 2: Design focus blocks**

Block time for deep work on high-impact tasks. Match duration to task type (Pomodoro 25min, Deep Work 90-120min). See [resources/template.md](resources/template.md#focus-block-design-template) and [resources/methodology.md](resources/methodology.md#1-deep-work-and-focus-blocks).

**Step 3: Timebox your week**

Allocate weekly calendar: deep work blocks, meeting blocks, batched admin, buffer time. See [resources/template.md](resources/template.md#weekly-timeboxing-template) and [resources/methodology.md](resources/methodology.md#2-timeboxing-techniques).

**Step 4: Timebox your day**

Break day into time-constrained blocks with start/end times. Schedule breaks. Plan evening hard stop. See [resources/template.md](resources/template.md#daily-timeboxing-template).

**Step 5: Execute with discipline**

Honor timeboxes. Use timers. Eliminate distractions (Slack off, phone away, close tabs). Take breaks. See [resources/methodology.md](resources/methodology.md#3-execution-discipline).

**Step 6: Review and adjust**

Weekly review: Did you protect deep work? What interrupted focus? Adjust schedule. See [resources/template.md](resources/template.md#weekly-review-template) and [resources/methodology.md](resources/methodology.md#4-energy-management-and-optimization).

Validate using [resources/evaluators/rubric_focus_timeboxing_8020.json](resources/evaluators/rubric_focus_timeboxing_8020.json). **Minimum standard**: Average score ≥ 3.5.

## Common Patterns

**Pattern 1: Pomodoro Technique (25 min focus)**
- **Format**: 25 min focused work + 5 min break, repeat 4×, then 15-30 min break
- **Best for**: Tasks with high resistance (procrastination), need for frequent breaks, building focus habit
- **Tools**: Timer, task list, distraction blockers
- **When**: Short tasks, starting new habits, high-distraction environments
- **Guardrails**: Don't interrupt Pomodoro mid-session, actually take breaks (don't skip)

**Pattern 2: Deep Work Blocks (90-120 min)**
- **Format**: 90-120 min uninterrupted focus on single cognitively demanding task
- **Best for**: Complex thinking (writing, coding, design, strategy), high-value creative work
- **Preparation**: Clear goal for session, all resources ready, distractions eliminated
- **When**: Peak energy hours (usually morning), maximum 2-3 blocks per day
- **Guardrails**: No meetings during deep work, Slack/email off, phone in another room

**Pattern 3: Weekly 80/20 Planning**
- **Format**: Sunday/Monday - identify top 3 high-impact goals for week, schedule deep work blocks
- **Best for**: Strategic prioritization, ensuring vital few get attention
- **Output**: 3-5 focus blocks (90-120 min each) on calendar for week's top priorities
- **When**: Start of week, quarterly planning, project kickoffs
- **Guardrails**: Protect these blocks ruthlessly, treat like unmovable meetings

**Pattern 4: Task Batching (30-60 min blocks)**
- **Format**: Group similar low-cognitive-load tasks (emails, calls, admin) into single session
- **Best for**: Reducing context-switching, clearing small tasks efficiently
- **Examples**: Email batches (11am, 4pm), meeting blocks (Tue/Thu afternoons), admin Fridays
- **When**: Low-energy periods, after deep work, end of day
- **Guardrails**: Set timer, don't let batches expand, resist checking email outside batches

**Pattern 5: Maker's Schedule (Half-day or Full-day blocks)**
- **Format**: Uninterrupted half-days (4+ hours) or full days for creative/technical work
- **Best for**: Large projects (research paper, product launch, complex feature), flow-state work
- **Preparation**: Clear all meetings for that period, OOO on Slack, backup plan if interrupted
- **When**: Critical deadlines, breakthrough work needed, once/week minimum for makers
- **Guardrails**: Communicate boundaries, delegate urgent issues, plan breaks within block

**Pattern 6: Energy-Based Scheduling**
- **Format**: Match task type to energy level (peak → deep work, trough → admin, recovery → meetings)
- **Best for**: Maximizing output while preventing burnout
- **Typical cycle**: Peak (9am-12pm) → Trough (2-3pm) → Recovery (4-5pm)
- **When**: Designing weekly/daily schedules, recovering from overwork
- **Guardrails**: Track your actual energy patterns (not generic), honor low-energy periods with rest

## Guardrails

1. **Protect deep work time**: No meetings, no Slack, no email during focus blocks. One interruption destroys 20+ minutes of flow. Schedule deep work during peak energy (usually mornings).

2. **Use Parkinson's Law**: Work expands to fill available time. Shorter timeboxes force prioritization and prevent perfectionism. A 90-minute timebox with a clear outcome beats open-ended "work on this."

3. **Identify the 80/20**: Force rank tasks by impact. The top 20% should get 80% of focus time. Cut, delegate, or batch the rest.

4. **Energy matters more than time**: 8 hours tired produces less than 4 hours energized. Match intensity to energy level. Troughs are for admin and meetings, not complex thinking.

5. **Build in buffer**: Leave ~20% unscheduled for unexpected issues, overflow, and breaks. Over-scheduling is fragile; one delay cascades.

6. **Set hard stops**: Define an end-of-day time. Constrained time forces prioritization; endless time enables procrastination.

7. **Take breaks**: After 90 minutes of deep work, take 10-15 minutes. Walk, stretch, look outside. Focus degrades after 90-120 minutes without a break.

8. **Measure focus quality, not hours**: 3 hours of deep work outperforms 8 hours of distracted work. Track completed focus blocks per week, not total hours.

**Common pitfalls:**

- ❌ **No real deep work blocks**: Calendar full of meetings, "focus time" constantly interrupted. Protect minimum 2-3× 90-min blocks per week.
- ❌ **Ignoring 80/20**: Everything feels important. Force rank. If you can't identify top 20%, ask: "If I could only work 10 hours this week, what would I do?"
- ❌ **Timeboxing trivia**: Scheduling every email, every Slack message. Batch low-value tasks, don't timebox them individually.
- ❌ **Skipping breaks**: "I'll break after I finish this." Then work 4 hours straight, output quality tanks. Use timer, force breaks.
- ❌ **Peak hours on admin**: Checking email at 9am (peak energy). Save admin for afternoon trough. Peak hours = deep work only.
- ❌ **Overcommitting**: Timeboxing 10 hours of work into 8-hour day. Be realistic. Under-schedule, over-deliver.

## Quick Reference

**Timeboxing durations:**

| Duration | Best For | Rest After |
|----------|----------|------------|
| **25 min** | Pomodoro, high-resistance tasks, building habit | 5 min |
| **50 min** | Focused work, moderate complexity | 10 min |
| **90 min** | Deep work, complex thinking, creative tasks | 15 min |
| **120