ONE THING on Proxy Metrics

In a famous example, Facebook found that users who add at least 7 friends in their first 10 days on the app tended to be more engaged and stay with the product longer. This led them to set an Objective of getting more new users to add more friends right away. The product team then went about testing various changes to the onboarding experience to encourage adding friends early.

Read more

ONE THING on a Dirty Word

MVP (Minimum Viable Product) has become a dirty word. In The Lean Startup, Eric Ries defines MVP as “that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.” Somehow, this has come to mean “let's ship something, anything, no matter how crappy.”

Read more

ONE THING on the Narrative

A narrative is a well-thought-out argument that uses precise communication to sell a specific idea. To create one that sticks, treat it like a product: it needs to be designed, built, tested, and iterated. If you get good at creating narratives, you will bring people together.

Read more

ONE THING on Hidden Power

I once reported to a charismatic CEO, following his lead on most things. Over time, however, I realized that to gain the necessary support and funding for anything significant, I needed the buy-in of the CFO. Decisions became quicker, easier, and more durable with that realization.

Read more

ONE THING on Enrolling your Team

Many engineering teams think of their product person as separate. Most know they are supposed to take input and insight from you, but they still think of you as a guest in their meetings. Some tech leads will redirect resources or even overrule you if they think you're wrong.

Read more

ONE THING on Getting to No

Sometimes you need to get creative when saying “no” — on the roadmap or in life. Counterintuitively, saying “yes” to a few small requests makes it easier to say “no” when you really need to. A clever product person will leave some roadmap capacity flexible for “small wins.”

Read more

ONE THING on Too Many OKRs

OKRs are not your backlog. They don’t include everything you plan to do, only the most important things you want to focus on right now. Teams cannot concentrate on more than a handful of things at once. I have seen teams with dozens of OKRs. Invariably, they fail all of them for lack of focus.

Read more