underclarification

Underclarification is a term used to describe a state or process in which the amount of clarification provided is insufficient to ensure mutual understanding. It occurs when statements, instructions, or data are not explicit enough, lacking definitions, criteria, examples, or boundary conditions. In practice, underclarification can leave recipients with multiple plausible interpretations, potentially leading to errors, inconsistent implementations, or delays.

Common settings include requirements engineering, policy drafting, technical documentation, education, and customer support. For example, a project brief that says "implement the feature with appropriate steps" without specifying success criteria or constraints risks underclarification.

Causes include complexity, assumptions about shared knowledge, time pressure, differing stakeholder perspectives, and language or domain barriers.

Consequences include ambiguity, misaligned expectations, rework, reduced safety, and decision delays.

Mitigation involves clarifying terms and criteria, providing explicit definitions, edge cases, test cases, acceptance criteria, and measurable outcomes; using structured formats such as glossaries, checklists, or flowcharts; asking targeted clarifying questions; and conducting iterative reviews with stakeholders.

Related concepts include ambiguity and vagueness; underclarification differs from miscommunication caused by intent. It is a risk factor in information design, knowledge management, and collaborative work, where explicit guidance and shared understanding are essential for accurate execution.