Holders of unique information usually speak only when explicitly invited

What it is

When someone holding unique information stays quiet, it is rarely concealment — they are stuck on two invisible thresholds: unsure whether the information is relevant, and unsure whether bringing it up now is appropriate. An explicit invitation ("You ran that project — what do you know that we don't?") clears both at once: it confirms relevance (the organization genuinely needs this) and grants standing (speaking now is neither showing off nor drifting off-topic). A group's information output depends heavily on whether its facilitator keeps a "who knows what" map and asks from it.

Why it happens

The first threshold is cognitive: people systematically overestimate how much of their own knowledge others share — what I know feels self-evident, hence not worth mentioning. This is the mutual knowledge bias, and it devalues unique information in the holder's own appraisal before anyone else can. The second is social: inserting possibly-irrelevant material into a converging discussion risks breaking rhythm and appearing boastful for uncertain gain; silence is the rational default. An explicit invitation dismantles both: being named shifts the relevance judgment from the holder to the asker, and the naming itself is a complete license to speak. This is also why the generic "anything to add?" almost never works — it designates no person and no information category, leaving both thresholds intact, while a question specific to person and topic works immediately.

Studying it

• Paradigm: questioning manipulations inside the hidden-profile paradigm — comparing unique-information entry rates between a no-prompt condition and one where the facilitator is instructed to ask information holders directly; team-cognition research using the transactive memory system framework measures the group's meta-knowledge accuracy about "who is responsible for knowing what" and its predictive power for information use and task performance.
• Variables: specificity of the prompt (none / generic / person-specific), accuracy of knowledge-distribution meta-knowledge, and status differences as independent variables; unique-information mention rate, time of first mention, and decision quality as dependent variables.
• Use in interface research: designing knowledge-reach mechanisms in collaboration tools — @-mentions, topic-routed questions, member expertise profiles — and testing whether they function as the digital equivalent of the explicit invitation.
• Methodological caveat: the prompting effect is tightly coupled to the facilitator's meta-knowledge; lab paradigms that randomly assign "the informed member" measure the mechanism's ceiling. Real teams have faulty expertise maps (assuming someone knows who does not), so shipped features must treat "map error" as its own failure mode to measure.

Where it stops holding

Invitation-by-name depends on the asker's sense of the knowledge distribution; beyond a dozen or so members, nobody maintains an accurate expertise map, and the mechanism needs archival substitutes (skill tags, project histories) in place of personal memory. Status differences invert the effect: publicly calling on a junior member for "your take" can produce performance pressure rather than information flow — a written, private channel works better there. In written collaboration the invitation can be asynchronous: @-mentioning someone on a question gives them time to compose, gentler than being put on the spot, but also easier to shelve — hence response deadlines.

Applying it

• Before the meeting, map topic-relevant knowledge: which members plausibly hold which information, as a list, and call on people by map rather than by seniority.
• Use question templates specific to an information category: "In the last comparable case you handled, what were the judgment calls?" rather than "What do you think?"
• In tools, bind @-mentions to topics (@-someone answers a specific question) with response deadlines and an escalation path, so asynchronous invitations cannot be shelved indefinitely.
• Offer junior members a written submission channel that bypasses the spotlight pressure of being named in the room.
• Verification: compare unique-information output after being named against spontaneous output; then sample decisions for information "discovered too late that someone knew all along" — the blind spot invitations never reached. Together the two measures form a full audit of knowledge reach.

Related

• Same group: V9.02.1 Group discussion rehashes shared information and ignores what only individuals know · V9.02.3 The first speaker's frame bounds the whole discussion · V9.02.4 Structured round-robin beats free discussion at pooling unique information · V9.02.5 Records capture only what was said; omissions stay invisible
• Nearby: V9.03 Groupthink · V5.05 Hand-Raising, Queues, and Moderation Tools
• Search terms: transactive memory · mutual knowledge bias · expertise location