feedback loops
why
product truth comes from contact with visitors. the invariant: every loop is a closed circuit — words or behavior in, triage by a named owner, visible written answer out. a channel that collects without answering trains visitors that speaking is useless; the signal dies and the product problem it named surfaces later as churn. the written answer — even a decline with a reason — keeps the channel alive and the evidence attributable.
rule
a feedback loop is a durable channel through which a visitor's words or behavior reach a decision, with a named triage owner and a visible answer. after three messages vanish without reply, people stop using the channel — worse than no loop. the problems then emerge later as churn or support chaos, expensive to fix and unattributed to their root cause.
loop inventory
| loop | signal | triage |
|---|---|---|
| support/inbox | words: problems, requests, confusion. | every message answered or triaged within the declared window. |
| in-product feedback | words at the moment of friction. | same channel, tagged by surface. |
| behavior (analytics) | actions: abandonment, retry storms, feature silence. | reviewed on the declared cadence. |
| errors (error tracking) | failures people actually hit. | feeds incident response thresholds. |
| churn/return | the ultimate answer. | reviewed with the question set. |
triage discipline
- every piece of human feedback gets a written answer — even "not doing this, because X". the answer is part of the loop, not a courtesy.
- tag feedback with the glossary domain word (
workflow,onboarding) so it joins behavior and errors under the same vocabulary. - a repeated theme becomes a candidate in prioritization, not an automatic roadmap item.
do not
- open a feedback channel with no owner or cadence.
- answer feedback with a roadmap promise you will not schedule.
- treat silence as approval — silence is measurable abandonment, per analytics.
- let feedback bypass the question set: it informs questions; it does not replace them.
verification
send one test message through each open loop; confirm it reaches its triage owner and gets an answer within the window. review the last month: every received human message has a visible outcome (answered, linked, declined with reason). confirm at least one shipped change traces to a feedback theme, or the loop is decoration.
good and bad
bad
feedback form submitted (2026-08-01)feedback form submitted (2026-08-03)feedback form submitted (2026-08-05)feedback form submitted (2026-08-10)no replies to any messageonboarding completion rate drops from 62% to 44% (same period)support inbox: 3 emails mentioning "setup unclear"
four messages, no replies — the visitor stops using the form. the team sees churn and support load rising, but the root problem (setup is unclear) was reported and ignored; reconstructing it later costs six weeks of user interviews.
good
feedback: workflow setup is unclearowner: onboardingoutcome: declined; current setup requires a connection first
a visible, accountable response even when no feature ships. a decline with a reason keeps the visitor in the circuit and the evidence attributable — the next person reporting the same friction joins an existing record instead of starting a dead thread.