featured in #558
A/B Testing Mistakes I Learned The Hard Way
- Lior Neu-ner tl;dr: “Running experiments is equal parts powerful and terrifying. Powerful because you can validate changes that will transform your product for the better; terrifying because there are so many ways to mess them up. I’ve run hundreds of A/B tests, both in my previous life as a growth engineer at Meta, and on my personal side project. These are some classic mistakes I’ve learned the hard way and how to avoid them.”featured in #545
Where More Effective Product Teams Spend More (and Less) Time
- John Cutler tl;dr: “When trying to understand where a team or company is at, one of the first things I do is talk to people about how they spend their time and energy. Words like empowered, feature factory, and outcome-oriented are squishy and can mean a million things. Behaviors don't lie. There are only so many hours in a week, and we have finite energy to do thoughtful work.” John shares where teams that are further along their product journey spend time.featured in #534
How We Use Friction Logs To Improve Products At Stripe
- Mike Bifulco tl;dr: “Friction logging is a practice that can be used by engineering teams building products to track and improve upon issues that users experience while using a product. The goal of friction logging is to make a given product better for everyone involved. End users and developers get a product that delivers value more directly, the team building the product gets a more attached, happier user base, and salespeople have an easier time showing value to potential customers.”featured in #531
An Engineer’s Guide To Talking To Users
- Ian Vanagas tl;dr: (1) How to prepare for a user interview. (2) How to find the right users to talk to. (3) What to ask during user interviews. (4) Mistakes to avoid. (5) What to do after an interview.featured in #511
featured in #369
When Users Never Use The Features They Asked For
- Austin Henley tl;dr: Austin concludes his story with what he learnt as a product minded engineer, including: (1) Always keep your users in the loop. Do not go build in isolation. (2) Don't underestimate engineering challenges that you have an external view of. (3) Voice your concerns to your team regularly and often. They might be to solve them far more quickly or identify a future roadblock. And more.featured in #256
featured in #254
Google’s Heart Framework For Product Metrics
- Rohit Verma tl;dr: This framework uses 5 metrics to help make product decisions: "Happiness, Engagement, Adoption, Retention, and Task Success." In this post, Rohit presents the goals, signals and metrics for each.featured in #243
A Conversation With Shreyas Doshi & John Cutler
- John Cutler Shreyas Doshi tl;dr: "We cover topics like leadership, becoming a better listener, the role of middle management, career and self identity, stubbornness, calendar theater, and treating your dashboards as products."featured in #240