Product management

After 10 years of building consumer social apps, I've decided to start exploring new areas. Building these products is an unforgiving grind—but I learned a lot along the way. For those embarking on this path, here's everything you need to know: TIME FOR A THREAD 👇

Every PM should save these 2 screenshots to their desktop. @bhorowitz's Good Product Manager / Bad Product Manager: (15 years old and still ridiculously relevant.) https://t.co/8EFB1476Wu... See more

Google is standardizing interview questions (finally?) so I am forced to retire my bootleg interview questions. In honor of the great service they've done over 200+ PM interviews, I'm going to do a thread that I expect no one to read but I have no other way to memorialize them.

One pagers are great way to drive decisions. Here’s an effective one pager format: 1. Objective of document 2. Background of Problem Statement 3. Recommendation / Way Forward 4. Reasoning behind recommendation 5. Next Steps Stick to 2 to 4 lines per section.

I'm consistently surprised by how the single act of doing this as an eng manager or product manager makes incredible waves: Send an email explaining what your team did the past 1-2 weeks, what your plans are for the next period, blockers & lessons learned. Every. Single. Time.

It’s time to say it out loud: BUILD LESS SOFTWARE Centering too much on adding new functionality will break your product, your users, and your team. Maybe your business. 1/10