#Product
-
The Feature Nobody Asked to Remove
Read more: The Feature Nobody Asked to RemoveA bank’s quiet decision to remove a feature sent me back to a general question: how do you decide when to cut something you’ve already built? The usual checklist, sunk cost, adoption, maintenance, misses the one cost that’s hard to undo. The signal.
-
The Product Decision Nobody Wants to Make
Read more: The Product Decision Nobody Wants to MakeThe email arrives on a Tuesday morning. A competitor has just announced a new feature. Someone forwards it to the group chat. Within the hour, someone asks: “are we building this?” And just like that, someone else’s product decision becomes yours.
-
Good Enough to Move
Read more: Good Enough to MoveSome of the information you’re looking for doesn’t exist yet. Customers can describe their current frustrations accurately. They struggle to evaluate something they’ve never seen. The last stretch of market understanding is always on the other side of shipping something.
-
Great Artists Ship
Read more: Great Artists ShipBuilding the product is only part of the job. What really matters is how it enters the world: who sees it first, how it’s explained, and what you learn once people start using it.
-
Deciding What Not to Build
Read more: Deciding What Not to BuildFeature requests are easy to accept and hard to undo. Real product discipline shows up in deciding what not to build, and keeping the roadmap aligned with what the product is actually for.
