The medieval Japanese concept of *ma* — the productive emptiness between things — was treated by architect Arata Isozaki as the most load-bearing element in any structure. Not the beams. The gaps. Product managers almost universally treat the spaces between features as waste: dead time, backlog debt, something to fill. But the philosopher Kitaro Nishida, writing in his 1911 work *An Inquiry into the Good*, argued that consciousness itself operates through intervals — that what we attend to is always shaped by what we allow to remain empty. These two traditions converge on something PMs rarely hear: the space between releases is not a failure of throughput. It's where users actually form their relationship to your product. When you compress every sprint into the next one, you eliminate the cognitive breathing room in which adoption deepens, feedback crystallizes, and your team's tacit knowledge of what's actually working can surface. The practical implication is simple but resisted: the next time you feel pressure to fill a roadmap gap with something, sit with the question of whether the gap is doing work that a feature cannot.

What is currently sitting in a roadmap gap that you scheduled not because it was ready, but because the emptiness felt professionally uncomfortable?

Drawing from Kyoto School Philosophy / Japanese Aesthetics (Ma) — Kitaro Nishida (An Inquiry into the Good, 1911)