/Product Management

An Inside Look At How Figma Ships Product

- Yuhki Yamashita tl;dr: Yuhki guides us through a new product roadmap doc and process. Meetings start with a silent review of the doc. Then the team (1) vote for certain topics to be discussed, (2) reflect on recent launches, (3) team leads complete weekly updates, (4) wins are celebrated.

featured in #221

Assign Problems (Not Work) To Your Teams To Build Extraordinary Products

- Raphaela Wrede tl;dr: A top down approach when a product manager mandates, with little buy in from the team, yields low engagement. A collaborative sprint with members of product, design, engineering, research, support, and analytics creates much higher engagement.

featured in #216


- Itamar Turner-Trauring tl;dr: The goal of YAGNI - You You Ain’t Gonna Need It principle - and YDNIY - You Don’t Need It Yet - is to get something useful into users’ hands as quickly as possible.

featured in #208

Ask the EM: How Can I Work Better With My Product Manager, As An Engineering Lead?

- Gergely Orosz tl;dr: A healthy relationship between engineering and product lead has (1) two people, one voice inside and outside the team. (2) Frequent communication. (3) Empathy towards the other. (4) Clear understanding of where roles start and end. Gergely discusses how to forge such a relationship.

featured in #200

Why Standups Are Useless And How To Run Great Product Team Meetings

- Andy John tl;dr: In the bulk of a product development process, standups aren't useful. Instead, hold 1-2 meetings a week with the following agenda - (1) action items: who is handling what key action item and by what date? (2) what decisions need to be made?

featured in #160

Performance Metrics For Blazingly Fast Web Apps

- Conrad Irwin tl;dr: Conrad discusses Superhuman's approach to performance metrics (1) Use event.timeStamp for start of events (2) end of events, use use performance.now() in a requestAnimationFrame() 3) ignore when the tab is not focused 4) aggregate data using “% of events that are under target” 5) visualize multiple thresholds. 📈 Click on the link in this tweet to bypass the paywall.

featured in #155

How Product Managers Lose Trust

- John Cutler tl;dr: Trust is essential between team members and is a result of previous decisions made between team members. Second, language used by PMs is essential - John uses various scenarios to illustrate this.

featured in #154

Guide to Product Planning: Three Feature Buckets

- Adam Nash tl;dr: Features can be bucketed into one of three. Metric movers, designed to make business goals happen. Customer requests and customer delight, making sure customer needs are focussed on.

featured in #152

Do, Try, Consider - How We Give Product Feedback At Asana

- Jackie Bavaro tl;dr: Framework for giving feedback on product related matters. "Do" is rarely used and mandatory, asking the team to perform a next step. "Try" asks the team to explore a next step. "Consider" shares an optional idea.

featured in #151

Creating Flow and Value in Product Development

- John Cutler tl;dr: The time developers spend coding in a 40 hour work week is relatively small. Hence, limiting work in progress, the scope of work, and handoffs between teams can increase flow and value in product development. The key is to focus on cadence and flow.

featured in #137