The On-Call Context-Loading Pattern
When on-call inherits an issue mid-shift, they need context fast. The pattern that loads it in 60 seconds.
The context dashboard
The on-call context loading pattern is the discipline of producing fast situational awareness when the on-call comes on shift. Without the pattern, the on-call spends 15-30 minutes piecing together Slack scrollback, recent deploys, and dashboard checks. With the pattern, the on-call is situationally aware in under a minute.
What the context dashboard provides:
- Active incidents.: The incident tool's view of currently-active incidents. The on-call sees what is in progress; the handoff context is captured.
- Recent deploys.: The deploy tool's view of changes deployed recently. The on-call sees what changed; correlation between deploys and incidents is immediate.
- Open alerts.: The alerting platform's view of currently-firing alerts. The on-call sees what is firing; the picture is complete.
- One screen; auto-refreshing.: All three views consolidate into a single dashboard. The dashboard refreshes automatically; the on-call's information stays current without manual refresh.
- The on-call sees it on shift start.: The first thing on shift is reviewing the dashboard. Within a minute, the on-call knows the current state; they can begin their shift effectively.
- And during incidents.: The same dashboard is referenced during incidents. The active state, the recent changes, the firing alerts all available; the investigation flow is supported.
The dashboard consolidates the data the on-call needs. Without it, each data source is a separate place to check.
The flow
The flow for using the dashboard is structured. Two 30-second checks produce situational awareness; the discipline is faster than the unstructured alternative.
- 30 seconds: what is on fire.: The on-call's first 30 seconds are spent on active incidents and open alerts. The view shows what is currently broken; the on-call knows the immediate situation.
- 30 seconds: what changed recently.: The next 30 seconds are spent on recent deploys. The view shows what changed; the on-call has the context for any incidents that started recently.
- Total: 60 seconds to be situationally aware.: One minute of dashboard time produces complete context. The on-call is ready to engage with whatever the shift brings.
- Beats reading Slack scrollback.: Without the dashboard, the on-call reads Slack scrollback to piece together context. The reading is much slower; the conclusions are less reliable; the cognitive load is higher.
- Discipline pays off.: The team that adopts the pattern saves time on every shift change and every incident. Across many shifts, the savings compound; the on-call experience improves.
The flow is fast and effective. The pattern produces situational awareness in less time than alternative approaches.
Share with team
The same dashboard the on-call uses is shared with stakeholders during incidents. The shared source of truth eliminates the "which dashboard?" confusion that wastes time during high-stakes moments.
- The dashboard is the same one stakeholders see during incidents.: Stakeholders (other engineers, product owners, leadership) reference the same dashboard during incidents. Everyone sees the same data; the conversation is grounded in shared facts.
- Single source of truth.: One dashboard, one view, one source of truth. The team does not maintain multiple dashboards that show different aspects; the consolidated view serves all audiences.
- Eliminates "wait, which dashboard?": During incidents, time spent finding the right dashboard is wasted time. The shared dashboard eliminates this; everyone goes to the same place.
- Trust through shared visibility.: Stakeholders see the same data the on-call sees. The visibility builds trust; the conversations during incidents are more productive because everyone has the same information.
- Maintained as a team artifact.: The dashboard is maintained collaboratively. Improvements suggested by stakeholders are evaluated; updates benefit everyone. The discipline is sustainable.
On-call context loading pattern is one of those operational disciplines that pays off across every shift and every incident. Nova AI Ops integrates with incident, deploy, and alerting tools, produces the consolidated context dashboard, and saves the team's time on every shift change.