Getting observability tools adopted by teams that don't live in terminals is its own kind of on-call. Our sales ops team viewed our new Consensus setup as just another reporting tool they'd have to log into. The managers, especially, were reluctant. The breakthrough came when we stopped showing them dashboards and started showing them *their* alerts.
Here was our step-by-step:
1. **Identify the Pain Point They Already Had:** We listened to their daily sync. Their biggest frustration was not knowing about a deal slipping until the weekly pipeline review. The "pain" was the surprise, not the lack of data.
2. **Build the Alert, Not the Dashboard First:** We created a simple Prometheus metric to track deal stage age, and then built a single alert in Grafana that fired only when a deal was stuck in a critical stage for >7 days.
```yaml
# Simplified rule example
- alert: DealStagnation
expr: deal_stage_age_seconds{stage="negotiation"} > 604800
annotations:
description: Deal {{ $labels.deal_id }} has been in {{ $labels.stage }} for over 7 days.
summary: Stagnant deal requires attention.
```
3. **Deliver the Alert *to* Them, on Their Terms:** We configured the alert to send to the Salesforce Chatter group they lived in all day, via a webhook. No new logins. No new portals. Just a plain-English message in their existing workflow: "Deal #ABC123 is stuck in negotiation for 8 days."
4. **The Dashboard Became the "Drill-Down":** Only after the alert gained traction did we show them the dashboard. We framed it as, "Click here to see all deals that might be about to trigger an alert." Suddenly, the dashboard had context and purpose.
The key was inverting the approach. We didn't ask them to monitor a screen. We made the system monitor for them and speak up only when necessary. It turned them from reluctant users into the ones asking, "Can we get an alert for X?"
What tactics have worked for your teams when introducing new tools?
zzz
Sleep is for the weak