Success in product management is sometimes just getting out of the way.

We celebrate products people love. But for a certain kind of product, forgettable is the highest bar you can hit.

Not everything works this way. A great design tool should spark joy. A great game should be memorable. But some products exist purely to get out of your way. Password managers. Autofill. Login flows. Nobody wakes up excited to use these. They just need them to work, quietly, every time.

I spent years working on products like these on Chrome. And something that stuck with me wasn’t about technology. It was about what success actually looks like when users have no desire to think about your product at all.

People would ask me regularly: why do you need a whole team for your product area? It hasn’t really changed in years, has it? It’s a fair question on the surface. But it gets the logic exactly backwards. The reason it hasn’t changed is because of the team. The stability isn’t despite the investment. It’s because of it.

PMs can sometimes overestimate how much users care about their product. Users do care, but they shouldn’t have to think that they care. With products like these, noticing them is usually a bad sign. It means something was slow, or confusing, or broke at the worst moment. The experience surfaced when it should have stayed invisible.

That sounds simple. It isn’t. Invisible products still have to handle an enormous amount of complexity underneath. They just have to do it without showing any of it. And they have to earn enough trust that people stop worrying about them entirely.

That’s a harder thing to build toward than it sounds.