Skip to content

afeezadebayo/planning-task-management-skills / focus-deep-work

focus-deep-work

Verified

Protect and use focused time: choosing work that deserves deep focus, focus patterns from daily blocks to focus days and sprints, booking and defending calendar blocks, team norms and urgent routes, interruption reduction, a start ritual, handling attention residue, message batching and weekly focus-hour reviews. Use whenever someone cannot focus, has a fragmented day, keeps getting interrupted, needs deep work time for writing, analysis or coding, wants fewer notifications or wants team focus hours.

Focus and Deep Work

Knowledge work rewards long stretches of concentration, yet most workdays are cut into fragments by meetings, messages and notifications. Cal Newport's book Deep Work argues that the ability to focus without distraction on hard tasks is increasingly rare and valuable. [Reference, Deep Work] Research by Gloria Mark and colleagues found people interrupted during tasks compensated by working faster, but reported more stress and frustration. [Research, Mark et al. 2008] Sophie Leroy described "attention residue": after switching tasks, part of the mind stays on the previous one, lowering performance on the next. [Research, Leroy 2009]

This skill helps people protect and use focused time: choosing the work that deserves it, scheduling focus blocks, reducing interruptions, preparing a focus routine, handling messages without losing the thread, and reviewing what worked. It balances focus with real job demands such as support, management and collaboration.

Operating principles

  1. Focus is scheduled, not found. Book it like a meeting before the week fills.
  2. One task per block. Decide the task before the block starts.
  3. Remove triggers, not just resist them. Notifications off, phone away, tabs closed.
  4. Batch the shallow work. Email and chat in set windows, not all day.
  5. Fit the role. A support lead and a writer need different focus patterns.

Focus patterns

PatternHow it worksFits
Daily focus block90 to 120 minutes at the same time each dayMost knowledge workers
Focus daysOne or two meeting-free days a weekMakers, writers, engineers
Sprints25 to 50 minutes of focus, 5 to 10 minutes break, repeatedInterruptible roles, getting started
SeasonalWeeks of intense focus between busy periodsResearchers, founders, writers
Team focus hoursWhole team pauses meetings and chat for set hoursTeams sharing calendars

When to use, and when not to

Use it when important work keeps getting pushed aside, the day is fragmented, notifications dominate, a big piece of thinking work is due, or a team wants protected focus time.

Don't use it to treat attention difficulties that may need assessment; suggest a qualified professional while still offering practical strategies. Don't use it to ignore real responsibilities such as on-call duties or customer commitments.

Inputs

  • The important work that needs focus.
  • Calendar and typical meeting pattern.
  • Main sources of interruption (chat, email, phone, colleagues, home).
  • Energy pattern: when the person thinks best.
  • Role demands: response expectations, on-call, management.

Workflow

Step 1. Choose deep-work tasks

List work that needs sustained thinking: writing, analysis, strategy, design, coding, learning. Link each to a goal.

Step 2. Pick the pattern and times

Match the pattern to the role; place blocks in high-energy hours.

Step 3. Book and protect the blocks

Recurring calendar events with a clear title, such as "Focus: Q4 report". Decline or move meetings that collide, with alternatives offered.

Step 4. Set expectations

Tell the team when focus blocks happen and how to reach the person for real emergencies. A status message such as "Focusing until 11, call for urgent issues" works well.

Step 5. Prepare the environment

Notifications off, phone in another room, one window open, materials ready, water nearby, a notepad to park stray thoughts.

Step 6. Start with a ritual

The same short start each time: open the task, write the goal for the block, set a timer.

Step 7. Handle interruptions

Park thoughts on the notepad; check messages only at the end of the block; for unavoidable interruptions, write one line about where you were before switching to reduce attention residue.

Step 8. Close and review

At the end, note what was done and the next step. Weekly, count focus hours and adjust.

Interruption reduction checklist

  • Turn off non-essential notifications on desktop and phone.
  • Close email and chat during focus blocks.
  • Use do-not-disturb and focus modes, with exceptions for key people.
  • Batch email and chat into two to four windows a day.
  • Agree response-time norms with the team (for example, chat replies within two hours, urgent issues by phone).
  • Move recurring meetings to one part of the day.
  • Use website or app blockers if needed.

Output format

1. Deep-work tasks linked to goals
2. Focus pattern and weekly schedule
3. Calendar blocks and meeting changes
4. Team message on focus times and urgent contact
5. Environment and start ritual
6. Message batching windows and response norms
7. Weekly focus hours target and review question

Using AI agents during focus time

Agents can protect focus as well as break it. Useful patterns: ask the agent to prepare materials and summaries before the block starts, hand it research questions to answer while you work on something else, and review its output after the block rather than checking in constantly. Turn off agent notifications during focus time, just like chat.

Breaks and energy

Focus depends on energy. Short breaks between blocks, a walk, water and daylight help people return sharper. Two to four hours of real deep work a day is a strong result for most people; trying to force eight usually backfires. When concentration fades early every day, check sleep, workload and stress before adding more techniques.

Team focus hours

Teams can agree shared focus hours, for example 9 to 11 on Tuesdays and Thursdays, with no meetings and chat on pause except for incidents. Write the norm down, add it to calendars, review it monthly and adjust for time zones in distributed teams.

Working from home

At home, agree focus hours with the people you live with, use a consistent spot that signals work, and keep household tasks out of focus blocks by listing them for a set time later in the day.

Edge cases and judgement calls

SituationWhat to do
Manager or support roleShorter blocks, early morning or late afternoon; protect two longer blocks weekly
Open-plan office or busy homeHeadphones, booked rooms, or focus at quieter times
Team culture of instant repliesAgree norms openly; start with one protected block a day
Focus blocks keep getting booked overMark them busy; move them, never delete them
Hard to startBegin with a 25-minute sprint on the smallest part
Energy crashesShorter blocks, breaks, movement; check sleep and workload

Handoffs to related skills

  • Scheduling the blocks: time-blocking
  • What deserves focus: prioritisation, goal-setting-okrs
  • Getting started: procrastination-unblocking
  • Focus routines: habits-routines
  • Fewer emails during focus time: the Email and Inbox skills

Worked example

An analyst had back-to-back meetings and never finished a quarterly model. The plan moved recurring meetings to afternoons, booked 9 to 11 focus blocks on four days, set chat to do-not-disturb with a status message, batched email at 11:30, 2 and 4:30, and kept a notepad for stray thoughts. The team agreed urgent issues come by phone. Focus hours rose from about three to ten a week, and the model was finished two weeks early.

Common mistakes

  • Waiting for free time instead of booking it.
  • Starting a block without choosing the task.
  • Leaving notifications on and relying on willpower.
  • Checking messages "quickly" mid-block.
  • Copying someone else's focus pattern that does not fit the role.

Measuring focus

Count focus hours each week and the important outputs finished. Aim to grow focus hours steadily rather than jump to an ideal. If hours drop, look for the cause in the weekly review: meetings, interruptions, unclear tasks or fatigue.

Self-check before you answer

  • Are focus blocks booked in high-energy hours?
  • Does each block have a chosen task?
  • Are interruptions reduced at the source?
  • Do the team know the norms and urgent route?

Created by Afeez Adebayo, Marketing, SEO & Growth Expert Website: https://afeezadebayo.com LinkedIn: https://www.linkedin.com/in/afeez-adebayo/ X: https://x.com/za_icon Source: https://afeezadebayo.com/skills-md/productivity/planning-tasks/focus-deep-work/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall