The team and company below do not exist; they are a composite of scenes that crop up across consulting work, though the arc will feel familiar to anyone who has sat in a DevOps engagement. A mid-sized company asked for help because its platform group, six engineers and a team head, was permanently busy and rarely finished anything significant. The visible problem was a stalled migration plan. The underlying one turned out to be that no one on the team had two quiet hours in a row, and the fix was a handful of protected focus blocks.
The first visit: busy, and getting nowhere
On the first morning the consultant simply watched. Messages arrived in three chat channels at once. A build failure drew half the team into a thread. The team head was pulled into a budget call, then a hiring screen, then an impromptu review. Nobody was idle, and by lunch nobody could point to a piece of finished thinking.
When asked which task mattered most, the answer came quickly: a written design for moving the company’s scheduled jobs to a new orchestration setup. It had been on the board for nine weeks. Asked who had worked on it, three engineers named three different small contributions, each squeezed into a gap between other things. There was no author in any real sense, and no single picture of the whole.
The conversation about calendars
The consultant did not begin with tooling. They began by exporting the team’s calendars for a typical week and laying them out in a grid. The result was a patchwork of short meetings, with the longest unbroken free stretch measuring about forty minutes, and that stretch fell at the end of the day when attention was thin.
One engineer said, with a half-laugh, that the design doc was done in “twenty-minute bites, usually while something else was on fire”. The consultant wrote that sentence on a whiteboard and left it there for the rest of the engagement. It described the problem better than any chart.
Proposing a small experiment
The proposal was modest. For three weeks, each engineer would hold two blocks of ninety minutes a week, scheduled by themselves and labelled with a single task. The team head would hold one, devoted to the planning document that never got written. Notifications would be switched off during blocks, and one rotating person would handle incoming requests and be the contact for genuine emergencies.
The sceptics had fair objections. Wouldn’t production suffer? Wouldn’t requesters complain? The consultant answered that the rotating contact existed for exactly these concerns, and that the experiment could be abandoned after three weeks if it caused harm. That honest escape hatch lowered resistance more than any argument did.
The bumpy start
Those opening days were awkward. Two blocks were raided in the first two days, once by a manager who did not know about the arrangement and once by an engineer who reached for chat out of habit. The rotating contact absorbed most requests, grumbling a little about the load. The consultant gathered everyone for ten minutes on Friday and asked a single question: what got in the way?
- People had not named their tasks tightly enough, so a few blocks started with twenty minutes of deciding what to do.
- A neighbouring team had no idea the blocks existed and kept sending direct messages.
- Phones were within arm’s reach and kept lighting up.
Each had a cheap fix. Tasks were named the evening before. A short note went to the neighbouring group explaining the windows and the emergency route. Phones went into a drawer. None of it required budget approval.
Week two: the document appears
By the second week something shifted. The engineer who took on the scheduled-jobs design used both blocks on the same document and found that the structure came together almost on its own. In the first block they listed every job, its schedule, its dependencies and its owner. In the second they worked out the order of migration, which jobs could move together and which needed a rehearsal first. Neither task had been possible in the old twenty-minute bites, because each step leaned on the one before it.
The team head used their block to write the plan’s risk section. Reading it afterwards, the others noticed it contained concerns nobody had voiced in any meeting, such as an old job that wrote to a shared directory in a way that would break under the new scheduler. That one paragraph saved the team an outage later.
What the consultant measured
At the end of the three weeks the consultant resisted the urge to produce a glossy report. They compared a few plain facts. The nine-week-old design document was finished and reviewed. Two other stalled items had moved to done. The count of repeat build failures from the same root cause had slipped, though the consultant cautioned that one good month does not prove a trend. Most telling were the engineers’ own words in a short survey: several said that the week finally felt like it had a shape.
What the engineers said afterwards
In the retrospective, the comments were revealing in their ordinariness. One engineer said the blocks felt like being allowed to finish a sentence. Another admitted to dreading the first one, then discovering that ninety minutes passed faster than a single stand-up. A third pointed out that the rotating contact role, which they had expected to resent, gave them a legitimate reason to say no to drive-by questions on the days they held it, since the answer was simply that the requester should go to the person on duty.
The team head raised one concern: whether the arrangement would hold when deadlines tightened. The consultant’s honest answer was that it would bend, and that bending was acceptable provided the team noticed it happening. A raid that is logged and discussed is information. A raid that nobody mentions becomes the old habit returning by stealth.
Where the engagement went next
With the migration design settled, the work became more typical consulting territory: sequencing, rehearsal environments and training. This is where the broader material on this site becomes relevant. Teams planning a move can read the full guide on consulting support during cloud migrations, and those wondering how an engagement is structured from the first assessment onwards can look at the blueprint that follows an engagement from its opening assessment through to enablement. The focus blocks were not a substitute for that structure. They were what let the team do the thinking the structure called for.
Lessons worth borrowing
- Look at the calendar before the tooling. A grid of the real week revealed more than interviews did.
- Keep the experiment small and reversible. Three weeks and an exit clause made agreement easy.
- Name the task in the block. The vague blocks were the ones that got raided or wasted.
- Separate the shield from the shielded. A rotating contact let everyone else concentrate without leaving production uncovered.
- Tell the neighbours. Blocks only hold when the people around you know the rules.
A note on keeping life outside the sprint visible
Teams also have people who want to attend meetups, workshops and conferences. If that sounds like your group, a site for finding and registering for events across India, such as this one, where event pages sit alongside venue pages, a forum for visitors and a blog, lets you spot those dates while you are still arranging the quiet windows, which keeps the two commitments from colliding.
The ending, honestly told
The team did not become a model of serenity. Blocks still got raided during incidents, and a few weeks later a reorganisation shuffled everyone’s calendars again. What remained was a shared understanding that deep thinking is real work and deserves a reserved place on the schedule. When the next large design item arrived, the team head did not ask who had time. They asked which two blocks it should take, and the answer was on the calendar by the end of the day.
Best Cardiac Hospitals Near You
Discover top heart hospitals, cardiology centers & cardiac care services by city.
Advanced Heart Care • Trusted Hospitals • Expert Teams
View Best Hospitals