Skip to content

Migrate from OpsGenie to Spike and never miss a critical alert.Get 20% off your first year 

← All emails

No. 21 · Oct 1, 2026 · On-call

One rotation for every system might slow you down.

Here's how you can fix the delay.

You get paged at 2am for a service you're not familiar with. You spend the first five minutes just finding the right dashboard.

That's what a single shared on-call rotation does on a team running multiple systems. Whoever's on-call gets every incident, whether or not they're familiar with that service.

A system-specific on-call rotation splits this up. One rotation covers the database, another covers infrastructure, each responder only gets paged for what they actually know.

That changes what 2am looks like. You're not learning the system while it's on fire; you're already familiar with it.

The tradeoff is more rotations to manage and more people needed across your team. Worth it if your systems are different enough that expertise doesn't transfer between them.

Get the next one in your inbox

A weekly email for engineers who carry the pager.

Enter to open, arrows to move, Esc to close

Browse everything on spike.sh