Yoshida Kenkō, a 14th-century Japanese Buddhist monk and court aesthetic, wrote that the most beautiful things are those left slightly incomplete — a garden with one corner unraked, a story that ends just before resolution. He called this sensibility *mono no aware*, the poignancy of impermanence, but the practical edge of his observation cuts deeper than aesthetics: incompleteness keeps you in conversation with something. Finished things go silent. This has a direct bearing on how product managers relate to their roadmaps and frameworks. The instinct to resolve ambiguity — to fully specify the feature, to lock the mental model, to close the loop on every open question before shipping — feels like rigor. It often isn't. It's the discomfort of incompleteness wearing the costume of discipline. What Kenkō noticed, and what Don Norman later formalized in design as 'feedforward' — the anticipation a user feels toward an unresolved system — is that a deliberately unfinished thing generates continued engagement, both from users and from the person who built it. The product that still has one unanswered question in its core mechanic keeps its team curious. The framework with one acknowledged gap forces the PM to keep observing rather than applying. Closure is a cognitive sedative. The discipline isn't finishing well. It's knowing which things to leave deliberately open.

What is one open question in your current product work that you've been treating as a problem to eliminate rather than a signal to stay curious about?

Drawing from Japanese Buddhist Aesthetics / Medieval Japanese Philosophy — Yoshida Kenkō (Essays in Idleness / Tsurezuregusa, c. 1330–1332 CE)