When declaring an incident becomes everyone's favorite workaround (greatcircle.com)

I was stuck in the middle of one of these at a megacorp. It was a Code Mauve, which meant it was technically enough to pre-empt my existing project. I grabbed a meeting with my manager, and carefully asked if I should find a way to avoid being pulled off my project. My manager just said to shelve my current project and work on the Code Mauve, as the rules designate.

When my manager got heat for the shelved project, he threw me under the bus and got me onto a PIP for not being able to complete tasks.

I don't usually comment about LLM-written articles, but it feels like an especially bad idea to do so in an article where you promote a book you're writing. Will that be LLM output, too?

https://www.pangram.com/history/9c8f8da8-0b4d-48d6-be23-9e8a...

Which is why the only people authorised to declare an incident are your incident managers. They follow the published guidelines which dictate what's a Sev 2 and what isn't.

A manager of a service may not declare their own service a Sev 2. If they can, your incident management process is broken.

Reporting incidents as sev-2 that obviously aren't, across state lines, electronically, to secure employment is wire fraud.

Once your corporation normalizes serial felon behavior, stability goes down the drain.

Maybe there's the option of hiring better people as well so you don't have to babysit them at this level. If you can't trust teams to open incidents maybe the problem lies somewhere else.