optional-skills/creative/creative-ideation/references/methods/defamiliarization.md
Two traditions naming the same operation: make the familiar strange.
Long predates either: Borges, Wittgenstein, nouveau roman (Robbe-Grillet), Calvino, much philosophical writing.
Watch users do something everyone in your domain treats as obvious. Describe without domain vocabulary. Often reveals friction you'd long since rationalized.
Subject: writing about software engineering as a profession.
Familiar version: "Software engineers write code, debug, and deploy systems. The work is mostly typing, with occasional meetings."
Defamiliarized: "Software engineers spend the largest part of their day moving small marks of light across glass surfaces by twitching their fingers. The marks form chains that, when read by certain machines elsewhere, cause the machines to perform actions the engineer has imagined. The engineer cannot directly observe most of the actions; they receive reports about what happened. A significant portion of their time is spent identifying differences between what they imagined and what was reported, and adjusting the marks to bring the reports closer to the imagination. Many of these adjustments are minute — single missing or extra marks. Engineers describe the activity using metaphors of building, despite producing no physical object."
The labeled version had hidden the mediation (engineers can't observe the thing they're making), the imagination-vs-report gap (most of debugging), the abstract-physical mismatch (they say "build" but make nothing material). All three are critically important features that disappear under labels.
Sources: Shklovsky, "Art as Device" (1917); Brecht, "A Short Organum for the Theatre" (1948).