You Can Polish a Car That’s Driving Into a Hedge.

Activity is the easiest thing in the world to mistake for progress, especially in a product team, because product teams generate so much evidence of themselves. Story points burned. Releases shipped. A backlog that’s never, ever empty. All of it real, all of it visible on a dashboard that goes green every single sprint. None of it tells you whether the product does its job better than it did a year ago.

This is what happens when a team gets very good at answering “what shall we build next” and nobody’s answering “why”. Features get built because a customer asked, or a competitor shipped one, or someone senior mentioned it twice in a meeting. The backlog grows. The product grows with it, in every direction at once, which from a distance looks a great deal like sprawl.

The engineers aren’t the problem. The standups are fine. What’s missing is somebody in the room whose job is to say no, out loud, to a thing that everyone else is too polite, too junior, or too tired to argue with.

Most product management at scale is coordination, and coordination done well looks impressive: tidy tickets, slick update decks, a roadmap slide nobody’s embarrassed by. All of it useful. None of it is leadership, and treating the two as the same thing is exactly how a product team ends up well-run and going nowhere in particular.

Senior product leadership is the set of judgement calls nobody else in the organisation is positioned to make: understanding the customer well enough to disagree with them when they’re wrong, understanding the business well enough to know which technical bets compound and which are just expensive, and having enough standing in the room to tell a senior person no and have it actually stick.

None of that comes from a certification programme. It comes from having made the expensive calls before, been wrong about a few of them, and built the pattern recognition to tell a hard call worth making from a bad one wearing a confident suit.