Dec 27, 2024
Removing a feature signals a mistake. Few people feel comfortable admitting that.
This hesitation keeps bad features alive. Teams cling to them, fearing the optics of walking back a decision. But doubling down on something that doesn't work costs more in the long run - time, energy and user trust. Recognising when something doesn't fit and cutting it isn't failure. It's progress.
Users notice when products improve. Removing what's broken clears space for what works.
Keep reading
When you have a decent structure and process, it does feel like you are making progress, so PMs grab (R)ICE, HEART or whatever the latest prioritisation framewo...
There are tech teams that act like their job starts when the requirements arrive. Still! This is a tech leadership gap created by a tech leader who prefers an a...
The most obvious upcoming change in product, design and engineering is in team structure. Teams will get smaller. One person covers what used to take three or f...
I'm a father of 3 from Sydney, a product and technology leader. I write about leadership, product management, technology and the messy reality of making work work.
I'm currently building and experimenting with a mildly alarming number of things. I also work as a fractional product leader, stepping in where the founder or CEO is still carrying product decisions on their own, and offer 1:1 product leadership coaching for senior PMs and emerging product leaders. I founded SoundingBoard, practical peer exchange for product people. Connect via LinkedIn, or follow me on X.
Subscribe to the best posts on product, strategy, and AI. Just one email a month.
