The end of the status update
Status updates are an artifact of broken plans. Fix the plan and they vanish.
All articles
Long-form writing on how to build product.
Product
Why we stopped doing standups
Daily standups are a workaround for a broken plan. Here's what to do instead.
The correct shape of a PR
Most code reviews fail because the PR is the wrong shape — too big, too unfocused, or scoped to the author's git history rather than the reader's attention.
The shape of good roadmaps
Roadmaps fail because they pretend the future is more knowable than it is. Treat them like burn-ups, not deadlines.
Design reviews without design reviews
Our design team killed the design review meeting and shipped more design than ever. Here's the system that replaced it.
The anatomy of a good bug report
Five fields. That's all a bug report needs. If your form has more, you're building a wishlist generator.
The hidden cost of context switching
We instrumented a year of engineer focus time. The numbers are worse than you think.
On writing things down
The single highest-leverage habit in product work, no contest.
Agents and the shape of teams
Teams used to grow by hiring. Now they grow by adding agents. The org chart hasn't caught up.
Killing the quarterly planning cycle
Quarters are an accounting convenience. They're terrible for product work.
The onboarding doc that changed our company
It started as a 4-page Notion. It's now a 60-page handbook. And it's the most important thing we own.
Three words that saved us an engineer
In a code review last quarter, three words changed how we think about scope.