Recipient Question Log¶
Feedback channel — instantiates Recipient Knowledge-State Calibration
A running record of the real questions and confusions recipients raise in use, tagged for recurring misconceptions and fed back to revise the material rather than blame the reader.
Recipient Question Log is the standing feedback channel that keeps calibration alive after the material ships. It captures the actual questions and confusions recipients raise in real use, tags the recurring ones as misconceptions, and applies a rule that turns a repeated confusion into a required revision of the source. Its defining move is that it is longitudinal and in-production — it does not stage a test or recruit a panel, it passively accumulates evidence from live use over time, and each recurring question is treated as data about the material rather than a defect in the reader. It exists because a knowledge-state model built once goes stale: audiences shift, vocabulary drifts, and new confusions surface only when real people meet the material at scale.
Example¶
A mid-size company's IT helpdesk fields the same new-hire onboarding questions week after week. Someone starts a recipient question log: every ticket and Slack question during laptop setup is captured and tagged. Within a month the pattern is unmissable — "where do I get the VPN password?" has come in forty times, always at the same step. The onboarding guide, it turns out, says "connect to the VPN" but never says the password is generated in the identity portal, a step the author performed so often they forgot it existed. The log's revision rule — any confusion that recurs past a threshold triggers a fix at the source — promotes this from "another ticket to answer" to "revise step 6." The guide is edited, and the forty-per-month question drops to near zero. The log then keeps watching, because the next silent gap will surface the same way.
How it works¶
The distinctive discipline is capturing real-use confusion, clustering it, and converting recurrence into a mandated source fix — with the failure attributed to the material, never the recipient:
- Capture where recipients actually ask. Support tickets, forum posts, office-hours questions, chat threads — the channel meets recipients where confusion already surfaces rather than manufacturing a test.
- Tag and cluster into misconceptions. Individual questions are grouped so a recurring confusion becomes visible as a pattern, not a scatter of one-offs.
- Apply the revision rule. A recurrence threshold converts a repeated confusion into a required edit of the source material, closing the loop; answering the ticket without fixing the source is explicitly not enough.
Tuning parameters¶
- Capture breadth — logging every channel versus a sampled subset. Full capture catches more but costs attention to maintain; sampling is lighter but can miss a low-frequency, high-stakes confusion.
- Tagging granularity — coarse buckets versus fine-grained misconception categories. Fine tags reveal subtle recurring gaps but demand more triage discipline; coarse tags are cheap but blur distinct problems together.
- Revision threshold — how many recurrences trigger a mandated fix. A low threshold reacts fast but chases noise; a high one waits for a clear signal but leaves a confusion live longer.
- Attribution stance — whether a logged failure is read as a material defect or a recipient shortcoming. This is the load-bearing dial: only the material-defect stance turns the log into calibration rather than a blame ledger.
When it helps, and when it misleads¶
Its strength is catching what no pre-release test can: drift over time, new audience segments, and the confusions that only appear once real people use the material at volume. It is the mechanism that keeps the knowledge-state model honest after launch, treating each recurring question as evidence to revise against rather than a nuisance to deflect.[n1]
Its failure mode is survivorship bias — the log only records the recipients who asked. The ones who silently misunderstood and gave up, or acted on a wrong reading and never came back, leave no trace, so a quiet log can mean either clear material or a confused, silent majority. The classic misuse is closing tickets without ever fixing the source, so the same question is answered forever and the material never improves — support absorbing the cost of a defect indefinitely. And blaming recipients for "not reading" converts the log from a calibration instrument into an alibi. The discipline that keeps it honest is to treat every recurrence as a signal about the material and to watch for the silent failures the log structurally cannot see.
How it implements the components¶
Recipient Question Log fills the ongoing-feedback side of the archetype — the loop that keeps calibration current after release:
misconception_capture_loop— the capture-and-cluster channel is the loop that surfaces recurring recipient misconceptions from live use as they emerge.calibration_revision_rule— the recurrence threshold is the explicit rule that converts a repeated confusion into a mandated revision of the source material.
It does not stage a task with recruited users or score them against a defined target action (representative_recipient_panel, target_understanding_or_action) — that is Comprehension Usability Test; the log passively harvests real questions after release rather than testing before it.
Related¶
- Instantiates: Recipient Knowledge-State Calibration — the log is the standing feedback channel that keeps the recipient model and material calibrated over time.
- Sibling mechanisms: Comprehension Usability Test · Expert Compression Red Team · Jargon Inventory and Glossary · Novice Walkthrough · Plain-Language with Precision Review · Prerequisite Mapping Workshop · Teach-Back Protocol · Worked Example Ladder
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Recipient Question Log operates as a persistent ledger, log, register, or case record that preserves history and traceability because it a running record of the real questions and confusions recipients raise in use, tagged for recurring misconceptions and fed back to revise the material rather than blame the reader.
Independent corroboration: The frozen evidence defines Recipient Question Log as 'A running record of the real questions and confusions recipients raise in use, tagged for recurring misconceptions and fed back to revise the material rather than blame the reader', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Human-Computer Interaction
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Collecting real recipient questions and iterating an information artifact from observed use is user-research and usability practice; formative instruction and audience testing are companion traditions.
Related originating lineages:
- Communication & Media Studies — Audience feedback research contributes coding recurrent misunderstandings.
- Education & Pedagogy — Formative assessment independently uses learner misconceptions to revise instruction.
Review resolution: The blind reviewers disagreed on primary lineage. Light authoritative research resolves the defining form in favor of human_computer_interaction: Collecting real recipient questions and iterating an information artifact from observed use is user-research and usability practice; formative instruction and audience testing are companion traditions. The rejected primary is retained only when it materially shaped the mechanism, and present-day breadth is recorded separately as domain_reach=multi_domain.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] Double-loop learning — Argyris and Schön's distinction between fixing an error within existing assumptions (single loop) and revising the underlying assumptions that produced it (double loop). A question log does double-loop work only when a recurring confusion revises the material's model of the recipient, rather than just being answered again. ↩