Welcome to the WIP
Yamashita's post argues for a simple cultural shift: share work-in-progress earlier, more visibly, more comfortably.
Most product organisations accidentally reward polished artefacts — documents ready to present, designs ready to ship — and punish the messy middle where most of the thinking actually happens.
The post is a manifesto for the opposite practice, and a useful companion to Manrubia's "Radiating Programmer" from the same tradition.
For product direction it is a small but portable argument: every team you work with has a signal-to-noise ratio on visibility, and making WIP safer to share usually improves both the work and the coordination.
Short, illustrated, easy to pass around internally.
Central argument
Yamashita argues that most organisations have developed an implicit norm of sharing work only when it is polished, which structurally hides the messy, generative middle of the creative process where real thinking happens. His central thesis is that this norm is both culturally constructed and culturally reversible: teams can deliberately make work-in-progress more visible, more comfortable to share, and less subject to premature judgment. The piece is less a tactical guide and more a normative argument — that the default should be sharing early, and that the burden of justification should fall on those who wait.
Critique
The argument treats psychological safety around WIP primarily as a cultural choice, which risks underweighting the structural and incentive-based reasons teams resist early sharing — performance reviews tied to deliverables, cross-functional stakeholders who use incomplete work as evidence of incompetence, or organisational climates where visibility invites interference rather than collaboration. A CPO operating in a politically complex or risk-averse environment may find the manifesto aspirational but underspecified: it does not offer a theory of when WIP sharing backfires or how to calibrate visibility across different stakeholder audiences. The Figma context also means the advice is implicitly optimised for design artefacts, leaving open how the principle translates to strategy documents, roadmaps, or technical spikes.
Why it matters for product
For a product leader, the practical leverage point is not in their own behaviour but in what they signal as acceptable across the teams they direct: if roadmap reviews, design critiques, or discovery readouts only feature finished thinking, WIP will stay hidden and coordination will happen too late to matter. The argument connects directly to discovery and delivery handoffs — the moments where misalignment is most expensive are precisely the moments that polished-artefact norms push visibility away from. Making WIP safer to share also compresses feedback loops, which is structurally valuable when directing multiple product areas simultaneously and needing early signals rather than late surprises.