Time Management#

Engineers face a unique time management challenge: their highest-value work requires deep focus, but their environment is full of interruptions — Slack messages, code reviews, meetings, incidents, and “quick questions.” Managing time is not about doing more — it’s about protecting the space for work that matters.

Prioritisation Frameworks#

The Eisenhower Matrix#

Categorise tasks by urgency and importance to decide what to do, schedule, delegate, or drop.

quadrantChart
    title Eisenhower Matrix
    x-axis "Not Urgent" --> "Urgent"
    y-axis "Not Important" --> "Important"
    quadrant-1 "DO: Schedule focused time"
    quadrant-2 "DO FIRST: Handle now"
    quadrant-3 "ELIMINATE: Stop doing"
    quadrant-4 "DELEGATE: Hand off"

The trap: spending all time in Quadrant 1 (urgent) while Quadrant 2 (important but not urgent) atrophies. Invest in Q2 to reduce future Q1 emergencies.

MoSCoW for Sprint/Task Prioritisation#

RICE Scoring#

For backlog prioritisation at the feature level:

Score = (Reach × Impact × Confidence) / Effort

Deep Work#

Cal Newport’s concept: cognitively demanding work performed in a state of distraction-free concentration. This is where engineers produce their best output — design, complex debugging, architectural thinking.

Protecting Deep Work#

The Maker’s Schedule vs Manager’s Schedule#

Communicate your needs: “I need mornings for deep work. I’m available for meetings after 1pm.”

Managing Interruptions#

Not all interruptions are equal. Use a triage approach:

flowchart TD
    A[Interruption arrives] --> B{Is it urgent AND important?}
    B -->|Yes| C[Handle now - production down, security issue]
    B -->|No| D{Is it blocking someone?}
    D -->|Yes, actively| E[Respond within 30 min]
    D -->|No| F{Is it time-sensitive?}
    F -->|Today| G[Batch - handle at next break]
    F -->|This week| H[Add to task list]
    F -->|No deadline| I[Handle in next review session]

The “Let Me Finish” Technique#

When interrupted during deep work:

1. Note where you are (write a TODO comment, jot down your thought)
2. Assess the interruption’s urgency
3. If not urgent: “I’ll get back to you at [specific time]”
4. Return to work. The note helps you reload context.

Estimation#

Engineers chronically underestimate. Understanding why helps you estimate better.

Why Estimates Are Wrong#

Better Estimation Practices#

• Break it down — estimate small pieces (< 1 day each), then sum
• Use ranges — “2-5 days” is more honest than “3 days”
• Reference past work — “Last similar task took X” beats gut feeling
• Separate work from calendar — 2 days of work ≠ 2 calendar days (meetings, reviews, context switches)
• Track actuals — compare estimates to reality. Your calibration improves over time.

Saying No#

Saying yes to everything means saying no to your priorities. Engineers who can’t say no accumulate obligations, miss deadlines, and burn out.

How to Say No Constructively#

Making Trade-offs Visible#

When asked to add work, surface the trade-off instead of silently absorbing it:

“I can take this on. If I do, [other task] will slip by [X days]. Is that acceptable, or should we reprioritise?”

This puts the decision back on the requestor without you being the bottleneck or the villain.

Avoiding Burnout#

Burnout is not just “being tired.” It’s chronic exhaustion combined with cynicism and reduced effectiveness. Engineering’s culture of overwork makes it especially common.

Warning Signs#

Prevention Strategies#

• Set boundaries — define work hours and honour them. Log off at a consistent time.
• Take breaks — Pomodoro (25 min work, 5 min break) or similar rhythm
• Single-task — multitasking drains energy faster than focused work
• Say no early — overcommitment is the #1 path to burnout
• Invest in recovery — exercise, sleep, and hobbies are not luxuries
• Ask for help — struggling silently accelerates burnout

The Sustainable Pace Principle#

Sprinting is for emergencies. Marathons require a sustainable pace. If you’re consistently working overtime, you’re not a hero — you’re a future liability. The code you write exhausted today creates the bugs you’ll debug next month.

Key Takeaways#

• Use the Eisenhower Matrix to focus on important work before it becomes urgent
• Protect deep work blocks — context switching is the enemy of engineering productivity
• Estimate in ranges, break work into small pieces, and track actuals to calibrate
• Saying no is a skill — make trade-offs visible instead of silently absorbing work
• Burnout is preventable with boundaries, realistic commitments, and intentional rest
• Sustainable pace produces better results than chronic overtime