Great Products Attract the Wrong People. Here's How to Protect Yours.

Three things crossed my desk this month that seem unrelated at first. A book review about corporate governance. A workshop for building product vision. A career interview with Kent Beck. But they all point at the same problem you already feel: building a great product is only half the job. Keeping it great, and keeping your team pointed at the right thing, is the other half. Let me catch you up.

Winning is exactly when you become a target

Marty Cagan has spent years arguing that great products power great companies. He now says that is true but not enough. A company that proves it can ship great work turns into a magnet for the wrong people. Cagan puts it plainly: boards and leadership teams get infiltrated, founders get replaced, cultures get wrecked, all for a quick financial win.

He has watched it happen and admits he has a bad track record talking boards out of it. He begged members not to fire good leaders over a missed quarter. It rarely worked. His point for you: your product success does not protect your company. It paints a target on it.

Governance is a product decision, not a lawyer decision

Cagan reviews Eric Ries' new book, Incorruptible, which is about corporate governance. He admits governance is a topic he used to hand off to lawyers and business experts, and calls that a possible big mistake. The book pushes what Ries calls "mission-locked" companies, ownership structures built to fend off the predators that strong products attract.

Why should you care as a product leader? Because governance shapes your daily life more than you think. It decides who sits on the board, what they optimize for, and whether your leaders survive a rough quarter. Cagan hopes product people will read this and vote with their feet toward companies where they can actually do good work. That is a real hiring and career filter, not a legal footnote.

A vision your team helped build, not one handed down

Protecting a team from the inside starts with knowing what you are all pointed at. Tim Herbig walks through how Victoria Ponomareva, a PM at EcoVadis, rebuilt her platform team's product vision after a reorg. Her team was newly formed, internal-facing, and drifting toward stakeholder requests. Vision work became the most direct path to becoming a team at all.

Her method is worth stealing. Name the actual user first, a procurement manager at a desk, not the API that calls your service. Pull real customer quotes into the room from what she calls the "feedback river." Run a half-day workshop with 18 people in four groups to generate raw material, then let a small core group of two or three synthesize it. You get collaboration without decision by committee.

Test the vision against a real decision

The part worth copying: before writing any statement, Ponomareva wrote a one-page story about a procurement manager's day, before and after her product. Herbig's line lands hard. A story you cannot tell compellingly is a sign the vision is not sharp yet. If you cannot tell it, you do not have it.

Then she drafted four short statements, each stressing a different value, and ran them against two or three real decisions the team could face. Each group asked which statement actually helped them choose. A clear frontrunner emerged. That is the test that matters. A vision that cannot guide a decision is decoration.

What still can't be automated

With agents now writing real code, it is easy to think the human part is shrinking. Kent Beck, who created Extreme Programming and TDD, pushes back hard. Coding is a small part of the job. The rest is building confidence, making connections with people, and understanding the domain. Those stay.

His own story backs it up. At 50 he joined Facebook, found a company that barely tested anything yet ran a huge stable site, and threw out everything he knew to relearn the craft on their terms. His hard-won lesson: "Your ability to affect change in the world is gated by your ability to communicate with, to soothe, to understand other human beings." The skills he thought he did not need turned out to be the whole job.

The deep cut

All three pieces circle the same thing you can control: whether your team stays pointed at users and protected from the forces that pull it off course. Beck warns that in the AI era we are piling up new code far faster than we are accumulating trust. That gap is where products quietly rot and where predators, in Cagan's sense, find room to operate.

So do the unglamorous thing. Write the one-page story of your user's before-and-after, and test your current roadmap against it. If a project does not move that story forward, you have found either a bad bet or a vision that is too fuzzy to defend. Bring that story to your next review, not a slide of metrics. Metrics tell you if you are on track. The story tells you if the track goes anywhere worth going.

Three questions for your team

• Can you name the actual person your product serves, and pull three real quotes from them, before you name a single feature on the roadmap?
• If your company hit a rough quarter, do you know how your board would react, and does your governance protect the leaders who are doing right by customers?
• Which of your current bets would survive being run through a one-page before-and-after story of your user's day, and which would fall apart?