Skip to main content

Team Impact

Overview

Beyond individual investigation metrics, OpsWorker changes how your team operates day-to-day. This page explains how to read that impact through the time saved metric and the feedback your team gives in Slack.

Impact Areas

Time Saved

The most direct impact is time that engineers no longer spend on manual investigation. The Dashboard reports this as time saved in minutes, computed as count multiplied by (average user time minus average agent time), and broken down by month and alert type.

  • Per investigation: Each automated investigation removes manual work that typically took 30 to 80 minutes
  • Over a period: Use the date range filter to see total minutes saved across the window
  • Reinvested time: Reclaimed engineering time can be redirected to feature work, reliability improvements, or technical debt

On-Call Burden Reduction

Automated investigation changes the on-call experience:

  • Before: Alert fires, engineer wakes up, spends time on manual investigation, finally understands the issue
  • After: Alert fires, the investigation completes automatically, engineer reviews a summary with root cause and fix commands
  • Engineers respond to understanding, not to uncertainty

Consistency

Manual investigation quality varies by who is on call:

  • Senior engineers investigate thoroughly but burn out over time
  • Junior engineers may miss root causes or take significantly longer
  • OpsWorker applies the same investigation process every time, regardless of who is on call

Knowledge Democratization

Investigation results are shared, documented, and searchable:

  • New team members can learn from past investigations
  • Investigation patterns are visible to the whole team, not locked in one person's memory
  • The chat interface lets anyone ask questions about the cluster without deep kubectl expertise

Feedback in Slack

When OpsWorker posts an investigation to Slack, team members can react to individual sections with thumbs up or thumbs down. This per-section feedback stays in Slack and helps you gauge whether a given investigation was useful.

This feedback is not aggregated into a portal accuracy score or rating. The Dashboard reports activity (alerts, finished investigations) and time saved in minutes, not feedback ratings.

Measuring Impact

Use the Dashboard to track:

  • How many investigations finished, per cluster, over the selected date range
  • How many minutes OpsWorker saved (actual and potential), broken down by month and alert type
  • How alert volume is distributed across your clusters

Next Steps