Confucius spent years advising rulers who ignored him, and he kept meticulous records of which arguments landed and which didn't — not to protect his ego, but because he believed the gap between intention and reception was itself the data. Product managers live in that gap constantly. You ship something carefully reasoned, and users respond to something you barely noticed. The 16th-century Confucian scholar Wang Yangming pushed this further: he argued that knowing and doing are not sequential steps but a single act — if you truly understand something, you are already changing your behavior. Which means that when a team 'knows' users don't want a feature but ships it anyway, they don't actually know it yet. The knowing is incomplete. Use that reframe today: wherever you're treating a user insight as information rather than action, that's not knowledge — it's a placeholder for it.

In the last week, what user or stakeholder signal did you log, discuss, and then override — and what would it mean if overriding it proved you never fully believed it?

Drawing from Neo-Confucian Philosophy (Yangming School) — Wang Yangming (Instructions for Practical Living / Chuanxilu, c. 1518 CE)