V1.03.5Partner-specific common grounddesignresearch

Explanations established collaborators can omit do not work for newcomers

Aliases: shared interaction history · conceptual pact · audience design

What it is

Partner-specific common ground consists of labels, assumptions, work routines, and tacit criteria accumulated through interaction with particular collaborators. “Do it like last time” can retrieve a shared history for established partners but leaves a newcomer without the episode that gave the phrase its content. The gap does not demonstrate low ability; the expression depends on a dialogue history in which the newcomer did not participate.

Why it happens

Repeated interaction compresses long initial descriptions into mutually accepted shorthand and turns boundaries and exceptions into routines. This lowers joint effort while binding interpretation to participants in the prior exchange. When membership changes, a record that preserves outcomes without rationale can still be completed from veterans' memory but not reconstructed by newcomers. Reading the message archive does not necessarily reproduce the mutual acceptance that made an assumption usable.

Studying it

Referential tasks can compare stable dyads with pairs whose partners are switched after shared labels emerge. Measures include description length, clarification, selection error, and rounds required to regain stable performance. In organizations, ask newcomers to perform an authentic handoff task and record questions, search paths, and points blocked by tacit premises, then compare established members. Partner switching also changes familiarity and social relations, so not every difference is attributable to vocabulary knowledge.

Where it stops holding

Not every local convention belongs in permanent documentation. Low-risk, short-lived agreements may cost more to maintain than to rediscover, and newcomers bring domain knowledge and experience from other teams. Explaining everything for a hypothetical newcomer overloads authors and readers. Priority belongs to high-consequence, cross-role, infrequent judgments whose rationale cannot be inferred from the outcome.

Applying it

  • Preserve rationale, applicability conditions, and key rejected alternatives beside a decision, not only its final state.
  • Link local shorthand to maintainable terms or objects instead of leaving meaning solely in chat history.
  • Layer explanation so established members can skim while newcomers can expand background, examples, and decision history.
  • Validate with an unassisted newcomer task, measuring time to first independent completion, consequential questions, and rework caused by tacit premises.

Related

  • Same group: V1.03.1 Common ground is mutually available knowledge · V1.03.2 Grounding requires reciprocal evidence · V1.03.3 Feedback cost shapes confirmation · V1.03.4 Insufficient common ground produces divergent interpretations
  • Adjacent: V4.05 Handoffs and context transfer · V8.02 Newcomer onboarding
  • Search terms: partner-specific common ground · conceptual pact · audience design

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/V1.03.5