Routing evidence to product & docs
A pattern in the Insights hub is only useful once it reaches the person who can act on it. This is how a card becomes a spec, a doc plan, or a training note — with its evidence riding along so nothing is lost in translation.
The Insights hub is where company-wide patterns surface. This article is the next step: what to do with one once you've read it. The move is almost always the same — hand it to whoever owns the fix, and hand them the evidence at the same time.
What routes where
The card type tells you the destination. Each pattern in the hub maps cleanly to an owner and an artifact — most of the routing decision is already made for you.
Attach the evidence
When you route a card, you're not copying a headline into a ticket — you're carrying its receipts. Each pattern card opens into the exact conversations behind it, with excerpts, timestamps, and the accounts they came from. Pull those into the spec or doc so the reader can check the claim themselves.
Weight it before you route it
Two numbers decide how hard to push. The account count is reach — how many customers this pattern touches. The confidence is how sure the read is. A card at nine accounts and high confidence is a straightforward prioritization case; a two-account, low-confidence card is worth watching before you spend a sprint on it.
Neither number replaces reading the evidence. They tell you which cards deserve your attention first — the conversations tell you what to actually build or write.
Closing the loop
Routing isn't a one-way street. Once you ship the feature or publish the doc, the pattern should fade — customers stop asking, the conversations that fed the card age out, and the card clears itself. That disappearance is your confirmation the fix landed, visible right back in the hub.
If a card doesn't fade after you've addressed it, that's a signal too — the fix may not have reached the customers who needed it, which is usually an enablement or docs-placement problem rather than a product one.