Signal ops board

Are the signals being acted on, and how fast Illustrative data
High signal → first touch
9h median
Target under 24h. Last week 14h.
Queue depth per rep
Founder11
AE4
Unassigned6
Signal mentioned on call
6of 9
From Otter transcripts. Three calls never raised it.
Reply rate by signal
Migration doc + card4 / 12
Migration doc, no card2 / 12
Ceiling hit1 / 7
Events untagged
7%
Above 3% and the board can't be trusted.
Highfired · acted · outcome5
Northwind Migration
Migration doc ×2, VP Eng title present
touched 3howner Founderstatus replied
Acme Cloud Ceiling
Credit at 85%, three engineers active
touched 19howner AEstatus sent
Fabrikam Renewal
Datadog renewal in 41 days
touched –owner unassignedlate
Contoso SSO ask
Requested SAML in support thread
touched 1howner Founderstatus meeting
Tailspin Cross-org
Dashboard shared into a new domain
touched 26howner AElate
Mediumstacking toward a trigger4
Litware 1 of 2
AWS integration connected
needs one more Medium + a decision-maker
Wingtip 2 of 2
Kubernetes connected · RBAC config copied
needs a decision-maker
Proseware 1 of 2
Former power user joined as Staff SRE
needs one more Medium
Adatum 2 of 2
Retention config copied · GCP connected
needs a decision-maker
Unknownwatched, not routed3
Unresolved Deanon
Four visits from one company ASN, no identity yet
pages pricing → compare → gone
Pattern Backtrack
Docs → migration page → 404 on old URL
action fix redirect, keep watching
Community Slack
"Can we do this?" on the GCP metrics post
action candidate for the lab
Fast actionSlack queue3 queues
Newest first frustration · stale in 7d
Acme Cloud · ceiling hit waiting 40m
Contoso · migration error waiting 2h
Nearest deadline renewal · migration
Fabrikam · renewal 41d out
Northwind · migration in progress
Oldest first everything else · floor 5/wk
Tailspin · cross-org share waiting 26h
Wingtip · two Mediums waiting 3d
Litware · integration waiting 5d

What the lanes mean

HighOne signal that's enough on its own to act. Someone reads the migration doc. An account hits its credit ceiling. A renewal date is inside 60 days. Someone asks for SSO. A dashboard gets shared into a new company.
MediumReal, but not enough alone. An integration connected. A config snippet copied. A former user at a new job. Needs a second Medium and a decision-maker at the account before it fires.
UnknownSomething happened and we can't yet say what it means. A visit we can't tie to a person. A path through the site that stopped. A reaction in the community. Watched, not routed. Nobody gets an email from this lane.
Fast actionWhat's already been sent to Slack, sorted by how fast it goes cold. Frustration newest first. Deadlines nearest first. Everything else oldest first, with a floor of five a week so it never starves.
What becomes a High. A Medium turns High when a second Medium lands at the same account and a decision-maker is active there. An Unknown turns Medium when we can name the person or the company behind it. Nothing in Unknown goes straight to High. Weak signals (a star, a saved post, a docs skim) never enter any lane.
Tiebreak inside High. Two accounts, one rep: the one with an engineer and a budget-holder both active goes first.