I like to do the counter factual. This is something actually that's worked with folks on my team to day, which is, if you could go back in time and at different junctures, do something different. Instead of spending your time coating, hire somebody who could have helped accelerate that over the long run. Would you have? I think that's one thing that most people, when they look back, they're able to be objective and to look forward. For some other reason, it's very hard for us. We're in the heat of battle, in the moment, war time, whech need get shit done, and it's harder to be objective. But this exercise
Today’s episode is with Snir Kodesh, Head of Engineering at Retool, which is a development platform for building custom business tools. Before joining Retool, Snir spent six years as a Senior Director of Engineering at Lyft.
In our conversation, we cover some of the biggest differences between leading engineering teams for a consumer product versus an enterprise platform — and the things that are consistent across both orgs.
First, Snir pulls back the curtain on the software development cycle, starting with setting the product roadmap while balancing a diverse set of customer needs. He outlines who’s in the room to represent product, engineering and design, and what those meetings actually look and sound like.
Next, he dives into how engineering actually starts taking that product roadmap and making a plan of action using the “try, do, consider” framework. He makes the case for leaning on QBRs instead of OKRs, why scope creep gets a bad rap, and his advice for getting better at estimating how long a feature will actually take to complete.
Finally, we zoom out and cover his essential advice for engineering leaders — especially folks who are scaling quickly from leading a small team to a much bigger one.
You can follow Snir on Twitter at @snirkodesh
You can email us questions directly at review@firstround.com or follow us on Twitter @ twitter.com/firstround and twitter.com/brettberson