Links

I’m primarily linking this because the first piece of advice – know your audience and your goals – is the best piece of writing advice I can think of, and the post has a great list of questions to ask yourself. I’m also a huge fan of using tl;dr bullets at the top of documents to start with the conclusion or ask (another piece of advice).

However, I’d be lying if didn’t mention how much this piece of advice made me smile:

Stop overusing formatting! Look at the formatting bar, and ignore almost all of the buttons.

This set of rules, pitched as “rules you can safely follow every time” are a great starting point for understanding modern visual design. If a great design breaks one of these rules, it’s for a well thought through reason.

Defining PM competencies is always challenging, but this breakdown by Ravi Mehta is the best I’ve seen. He splits the required skills into four buckets:

1. Customer insight — data fluency, voice of the customer, and UX design
2. Product strategy — outcome ownership, product vision & roadmaping, and strategic impact
3. Product execution — feature specification, product delivery and product quality
4. Influence — stakeholder management, team leadership and managing up

I’ve been reading a lot to improve my writing skills recently, and I really liked this blog post by doist (makers of the Todoist app). The questions to help you edit your work are particularly helpful (e.g. How can I make this message simple? What can I delete? Am I making assumptions?).

In his newsletter, Lenny Rachitsky shared some great tips on how to build your influence and how to get a yes on your asks.

To build influence:

• Build trust over time (listen to others, help them out, take feedback, be reliable)
• Consistently show success; others will trust you know what you’re doing
• Gain the support of influential leaders
• Be likeable

To get a yes on your asks:

• Connect your asks to others’ goals
• Take the time to help others see what you see
• Bring evidence to discussions

Critiquing existing products is a great way to build product intuition. In this essay, Julie Zhuo explains how to explore why some products work, and others don’t.

Great managers have a “strong and principled practice” of 1-1 meetings. To do 1-1s right: prioritise the time, create the right environment, have a structure, and respond to individual needs.

This (older) HBR article suggests it’s more important to make it easy for customers to access the value of your product (by removing barriers), than ‘delighting’ them by exceeding service expectations.

Matthew Butterick’s guide typography is an easy reference to improve the readability and professionalism of docs.

Julius Walter’s four suggestions to develop better product sense:

1. Observe people interacting with products
2. Deconstruct everyday products
3. Learn from great product thinkers
4. Be curious about changes in technology and your domain

SVPG guide on how to successfully take a product to market in a crowded environment (like app stores). In these cases, the role of the Product Lead is to (1) connect the market and customer insights, (2) direct the product’s go-to-market, (3) shape how the world thinks about the product, and (4) enable others to tell the story.

Interesting note on the evolution of Netflix’s rating scale. Bad / good / great is a simple scale that aligns well with how people actually think about their experiences. No need to debate what 5 stars actually means.

This article from 2001 on new architectures vs. new products outlines the same problems blockchain/web3 is currently facing.

Julie Zhuo defines four stages of development for 0 to 1 product development:

1. Define the user needs or wants your product will meet
2. Get product-market fit
3. Reconcile the product with constraints (e.g. positive unit economics)
4. Grow the product

A great collection of collection of writing on technology strategy put together by Sriram Krishnan.

Ben Thompson’s good (though imperfect) definition of what a tech company is. Getting this right seems important as the push to regulate ’tech’ grows.

I always loves articles like these about people who develop a deep passion for something despite the obvious inconveniences.