Why software development requires servant leaders
Engineering Impact is a weekly newsletter that highlights trends in engineering leadership, productivity, culture, and scaling development teams.
This week features posts on: Leadership, Documentation, Career Transitions, User Research, and Hyper Growth.
Aaron Longwell, CTO at Culture Foundry, explores what “servant leadership” means for leaders of software projects and breaks down what it looks in practice: giving developers control over estimation, driving uncertainty out of requirements, and embodying a “Chief Unblocker.”
Sweta Ackerman, Senior Engineering Manager at PagerDuty, recalls an on-call horror story (her words: “an engineer’s worst nightmare”) — and clearly articulates the three major elements of a post-mortem process.
“In this post, I’ll share how I prepared for eight manager handoffs over a short timespan.” Here’s Steve Wozniak (no, not that one), Engineering Manager at Meetup, with a 4-step process for a seamless transition.
Cindy Alvarez, Principal Design Researcher at Microsoft, illustrates how cognitive bias impacts both the questions we ask and what people tell us in response. Here’s how to rephrase the questions you ask customers, so you can get to the heart of what the problems really are and how they ought to be prioritized.
Matt Klein, Engineer at Lyft, shares an insightful take on how and when pure DevOps begins to break down — and explains what high growth companies can do to mitigate many of the potential scaling issues that Klein describes.
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.