Listening for What Is Left Unsaid
Launch library · evergreen read
An answer is defined as much by its gaps as by its content. A subject who describes an entire project in detail but skips over one particular week has usually skipped it on purpose, whether consciously or not, and that gap is often more informative than anything spoken aloud around it. A subject rarely announces what they are choosing to skip, which is exactly why it is easy to miss.
Noticing an absence requires a different kind of attention than noticing content: it means holding a mental map of what a full answer would cover, and registering when a piece of that map goes quiet. This is harder in real time than it sounds, and it improves mainly with practice. Building that mental map takes real practice, since it means tracking absence as closely as content.
Once noticed, the gap does not need to be confronted immediately. Simply marking it, and returning to it later with a gentle question, respects the fact that the omission may be significant without assuming the worst about why it happened. Approaching the gap with curiosity rather than suspicion tends to keep the subject open rather than guarded.