nucleation

LIT-756: Formality Considered Harmful: Experiences, Emerging Themes, and Directions on the Use of Formal Representations in Interactive Systems

2 min read

Properties4
StatusActive — read 2026-10-30 (NOTE-1446) in full, in the authors' web version from Xerox PARC on Frank Shipman's Texas A&M pages (https://people.engr.tamu.edu/shipman/formality-paper/harmful.html), a text of about 1993–94, not the 1999 journal article; worth reading as the standard statement of the premature-formalization failure: across hypermedia, design-rationale, knowledge-based and groupware systems, users would not or could not make structure explicit, for reasons of cognitive overhead, tacit knowledge, premature commitment and structure that differs by person and task, and they were often right. Read it knowing that its evidence is the authors' experience and others' reports, and that what the 1999 text adds was not checked.
Version4
Tagsdesign-rationale
Cited as “paper” byNOTE-1446 — Shipman & Marshall — Formality considered harmful

Graph View

Frank M. Shipman III and Catherine C. Marshall (1999), Computer Supported Cooperative Work 8(4):333–352 — DOI-10.1023/A:1008716330212

Read in full on 2026-10-30 (NOTE-1446), in the authors’ web version on Shipman’s pages, an earlier text than the journal’s.

Key takeaways

Read in the authors’ web version of about 1993–94 (NOTE-1446), not the 1999 journal text.

  • Across five kinds of system for intellectual work, users would not, or could not, chunk, label and link as the formalism required, and “there is always information that falls between the cracks, no matter how well thought out the formal representation is” (§2.2).
  • They are often right to resist: formalizing costs cognitive overhead, asks for tacit knowledge to be stated, commits people to structure before they understand the task, and gives a structure that suits one person, group or task and not the next (§3).
  • Designers should formalize what the task essentially needs, infer structure from informal material, and support incremental formalization and restructuring “as tasks are reconceptualized” (§§4–5).

Standing in the record

Filed on 2026-10-06 at the owner’s request, with the rest of the design-rationale batch under ADR-030. See the curation entry of that day for why the batch is here. It is the source of the objection CLAIM-181 turns on the record; the reading’s bearing on that claim is in NOTE-1446.

Backlinks