logoalt Hacker News

glenngillen • today at 4:24 PM • 1 reply • view on HN

yep, did the same for my team at one place "[IMPORTANT] CUSTOMER OUTAGE" (or something similar).

We had a publicly viewable calendar policy. And I couldn't believe the audacity of people in other areas to take it upon themselves to just book over the top of existing meetings because they had decided their meeting was more important. And I'm not talking a group meeting where it's hard to find a gap that works for everyone, these were essentially 1:1 meetings where the organizer was someone with a little more seniority. No polite ask/DM first if it's ok, or a note in the invite to explain. Just see "focus time - no meetings" or something else _they_ deemed not important and they'd schedule it in that block and assume the IC wouldn't challenge their authority.

So had to play them at their own game to give my team their time back. The meeting was as much as an invite to them to challenge my authority as their previous attempts were. Conveniently it worked and nobody would book over my meeting. I do not miss working for larger companies.


Replies

roryirvine • today at 5:30 PM

It depends. In the situation where an Ops team has become stuck in firefighting mode, that's something which is often painfully obvious to the rest of the org. And, in that case, it's possible to make a good case for deliberately reorienting towards strategic rather tactical work.

Blocking out, say, 2x2 hours each day for "problem management" (fixing root causes of recurrent issues) becomes easy in that situation, with no subterfuge needed. Alternatively, you can nominate part of the team to be either on-call or entirely dedicated to incidents, shielding everyone else who can be dedicated to strategic work full-time (obviously, you need to do regular rotations).

The team themselves often need help in adjusting to that (firefighting can make you feel like a hero so, although stressful, it can be addictive). Blocking out specific timeslots can be helpful from this point of view, too - incidents often seem a lot more manageable if they're not crashing in on top of you at unpredictable intervals.

➕ show 2 replies