Scoping Product Plans Just Right (Without Compromising Vision)
Engineering Impact is a weekly newsletter that highlights trends in engineering leadership, productivity, culture, and scaling development teams.
This week features posts on: Product Development, Career, Managing Yourself, Code Review, and Culture.
The first step in building a product plan is to scope the product — Steven Sinofsky, Partner at a16z, calls this process “rightsizing”. Here, he says “it is common to fall into extremes of this step — being extremely minimal or being too broad,” and offers a detailed approach to getting this practice right.
Swaroop H., Engineering Manager at Helpshift, unpacks his first year in management and shares the resources that helped accelerate his learning along the way (referencing some of the best work from Jennifer Dary, John Cutler, and Julia Evans, to name a few.)
Claire Lew, CEO of Know Your Company, shares 12 common pitfalls that managers can easily slide into (especially during times of high stress). Check-in with these ‘signs’ occasionally to get back to a more balanced approach.
This two-part series covers 7 common patterns to look for in code review — exploring both the “process dynamics” (Part 1) and the “people dynamics” (Part 2) involved in the process. Here’s how to leverage the review process to reinforce cultural values, debug the onboarding process, and more.
Will Larson, Head of Foundation Engineering at Stripe, takes a deep-dive into how “talent distributions” — meaning how productive and happy people are — are impacted by various company policies and cultural values.
Ben Thompson is a co-founder at GitPrime where he leads design and customer experience. He is a Y Combinator alumni, with a background in product design, branding, and UX design. Follow @thebent on Twitter.
Get Engineering Impact: the weekly newsletter for managers of software teams
Keep current with trends in engineering leadership, productivity, culture, and scaling development teams.