I'm incident commander this week. Didn't realize until the rotation hit me (oops), so my schedule was a mess.
I wanted to know two things: how often I'd get paged, and when. Then I'd figure out what I ACTUALLY had to move around.
The stack
@Zapier SDK x @Databricks inside @Cursor_ai
If you haven't used the Zapier SDK before, you absolutely should. Here's a one-liner to install:
The query
“How many sev0-2 incidents per hour of the day, ET, over the last year?”
What came back
About 1.7 incidents a week land in my 6am - 1pm window. We rotate between 3 people, so my share is ~0.6 pages.
0.6 pages/week
That number was relieving. 60% of weeks I won't get paged at all during my shift. And 0.6 pages between 10am and 1pm is plannable.
To be fair, any given week could still hand me 2+ pages by chance. But that 10am-1pm hot block holds regardless.
So I drew a fence around 10am - 1pm. If I rescheduled us, sorry not sorry.
It's a lot easier to guard one window than worry my way through a whole week.
(I'll find out soon whether this was brilliant, lazy, or both)