Upgrade & Secure Your Future with DevOps, SRE, DevSecOps, MLOps!
We spend hours scrolling social media and waste money on things we forget, but won’t spend 30 minutes a day earning certifications that can change our lives.
Master in DevOps, SRE, DevSecOps & MLOps by DevOps School!
Learn from Guru Rajesh Kumar and double your salary in just one year.
Here is a familiar scene on an operations team. An incident ends on Tuesday, everyone agrees the write-up matters, and by the following Friday there is still a blank page titled “postmortem” sitting in a shared folder. Nobody is lazy. The problem is structural, and it usually has a boring cause: the write-up needs a long unbroken stretch of thinking, and the calendar never contains one. If you want deep work to happen on incident reviews and design notes, you have to block time for it deliberately. This post diagnoses why the pages stay blank and walks through a fix you can start this week.
The symptom: work that is always “next up” and never done
Teams that run AI-assisted monitoring or any other modern operations stack tend to report the same pattern. Short tasks get done because they fit between meetings. Long, thoughtful tasks slide, because they do not. A timeline reconstruction, a design proposal for a new alert routing scheme, or a careful review of last quarter’s recurring faults all need an hour or two of continuous attention before they start to produce anything useful.
The giveaway is how people describe their day. “I was busy all day but I did not get to the real work.” That sentence is the symptom. The day was full of valid activity, yet the demanding piece never found a home.
The diagnosis: leftover minutes cannot carry heavy thinking
Every time you switch from a chat thread to a document, part of your attention stays behind. Researchers who study interruptions describe this as attention residue, and most people recognise it without needing a study: you reread the same paragraph three times after a ping. When a day is chopped into twenty-minute pieces, the first ten minutes of each piece go to rebuilding context. What remains is enough for tidying and replying, not for reasoning about why a queue backed up.
There are three common contributing causes worth checking against your own week.
- No reserved window exists. Look at the calendar for the coming fortnight. If every free hour is simply unclaimed, it will be claimed by someone else’s request.
- Notifications stay on during the work. A block that is nominally protected but still lets every chat badge through is only a block in name.
- The task is too vague to start. “Write the postmortem” is a mountain. Without a first small step written on the block itself, the opening minutes drain away.
The fix: treat a focus window like an appointment
The remedy is not heroic willpower. It is a calendar entry that behaves like a meeting with an important person who will not reschedule casually. For teams with on-call duties, the same rule applies, with one extra step: agree in advance who covers the pager during the block, so that the person writing can truly step away.
Follow these steps in order.
- Pick the work. Choose one task that needs sustained thought: a postmortem draft, a design note, or a first pass at a runbook revision.
- Choose the length. Ninety minutes is a workable default. Two hours suits bigger documents. Anything under an hour rarely gets past warm-up.
- Book it as busy. Mark the time so colleagues see an actual commitment, not a pale tentative slot.
- Write the first action in the invite. For example, “List the ten key events with timestamps.” It removes the awkward blank-page start.
- Silence the channels. Quit the chat client, close the dashboard tab you do not need, put the phone face down. If someone must reach you, give one named backup.
- End with a handoff note. The last five minutes are for writing down where you stopped, so the next block begins at speed.
Where the block belongs in the week
Placement matters as much as length. Your thinking is probably sharpest at a particular hour, and for plenty of engineers that is early morning, before the day’s requests accumulate. Put the protected window there and let routine work flow into the afternoon. If your team spans time zones, anchor the block to the hours with the fewest overlapping meetings, which tend to be the early part of the local day.
Resist the urge to schedule the block “whenever things calm down”. Operations work almost never calms down on its own, and a block with no fixed time is a wish rather than a plan. Two or three recurring windows per week, at the same hours, build a rhythm that colleagues learn to respect. After a month, people stop asking “can you jump on a quick call?” during those hours, because the pattern is familiar.
Where the plan tends to wobble
Good plans still stumble now and then. These are the wobbles that show up most, each with a repair.
The block gets eaten by an urgent request. Sometimes that is justified, and a genuine production fault outranks a document. The repair is to move the block rather than delete it. Drop it into the next free slot the same day, so the commitment survives. A block that is cancelled outright tends to vanish for good.
You sit down and cannot start. Open the invite, read the first action, and do only that. Momentum usually arrives within a few minutes. If it does not, switch to the easiest part of the document, such as the timeline, and build upward.
Teammates resent the unavailability. Explain the arrangement once, in plain words, and publish the hours. People accept boundaries that are predictable. They resent boundaries that appear without warning.
The output is thin even though the time was protected. Check the preparation. Gather logs, ticket links and chat excerpts before the block starts, so the window is spent thinking rather than hunting for material. Gathering is shallow work and belongs in the gaps between meetings.
One scenario, end to end
Picture a small platform group of five that handles its own on-call rota. After a weekend incident, the manager asks for a written review by midweek. In the past, that request would have drifted. This time, one engineer books a ninety-minute Monday-morning block, writes “assemble the event timeline” in the invite, and hands the pager to a teammate who is already reading tickets that morning. By the end of the window the timeline exists and a rough list of contributing factors is sketched. A second block on Wednesday turns the sketch into a finished document, and the follow-up actions get entered into the tracker straight afterwards. Two protected windows replaced ten days of guilty procrastination.
Nothing about the engineer’s skill changed. The calendar did.
Using your time away from the desk well
Focus blocks work better when the rest of your week includes some contact with the wider technical community, since fresh ideas feed the thinking you will do inside the block. Meetups, workshops and conferences are a natural source. Hackathons and meetups can spark the ideas you later develop in a quiet window. Readers in India can look through the MyEventsNow website, where a discussion forum and a blog sit beside the event listings and the venue pages, and then sign up for something nearby. Once a seat is confirmed, block that date as firmly as any writing window.
Related reading on this site
If your fragmented days are partly caused by noisy tooling, the article about taming IT event floods using smart tooling addresses the monitoring side. For a gentler starting point, there is a beginner-level introduction to solving IT problems as they unfold, and teams considering a wider rollout may find the straightforward advice on adopting AIOps within an IT group a handy companion.
A short checklist to close the diagnosis
- Is there at least one protected block on the calendar this week for demanding written work?
- Does the invite name the first action?
- Is someone else covering the pager and the chat during that window?
- Are logs and links gathered before the block begins?
- Do you end each block with a handoff note?
Any “no” above marks your next repair. Pick the cheapest one, book tomorrow morning’s window, and watch whether that empty document finally starts to fill.