Kicking off Season 2 of Lead Time Chats, Jean Hsu, VP of Engineering at Range, talks to Camille Fournier, Managing Director at Two Sigma and author of The Manager's Path, about making boring plans.
Camille and Jean discuss:
A boring plan recognizes more than the technical implementation
“First of all, it looks like a plan at all. It looks like a plan that recognizes the migration part of this work that isn't just the technical implementation.
So I think that's table stakes, right? A lot of people don't have a plan at all. Let's be honest, engineers are not great at planning. I'm not great at planning, but we all have to do it at some point. A lot of times you get a plan for a system and it's like, here's all the cool technical stuff that we need to do to build this. Great. That's a good baseline, but you have not addressed what we do once we have something that we think is working, right. A boring plan is going to have a lot of that technical stuff. It's going to recognize the systems that you need to integrate with. It's going to recognize how do we get assurance that this thing can scale.
It's going to recognize security and stuff like that. Right? Well, then it's also going to recognize that even once we get to something we think is working, we now need to talk to people. We need to have target alpha users, people that are going to use this thing.”
Reward people on your team that do the tedious drawn-out work
“You just have to make sure that you can reward people who do the long drawn-out work. This stuff often falls down when you have a culture that only rewards, "I just I did the alpha launch of this. And then I did the alpha launch of that." The alpha, you know, it takes 20% of the time as opposed to getting all the way to GA.
And so you do have to be thoughtful culturally about not over-rewarding the people who only do the new stuff and forgetting about the people who actually do the tedious work to finish it, because then you just end up with like a graveyard of alpha beta products that have never quite gone to GA.”
Find high-profile alpha use cases to build credibility
“You've also got to figure out how to deliver value incrementally during the process if you can. You're doing something that needs to be long running. You're doing it for a reason. It's going to provide some value. What is a high-profile use case, high-profile new product feature, high-profile system that needs to scale, high-profile data processing, that is really struggling, but you're like, we're going to do the alpha version of this with that team or for this thing. And then we're gonna launch that, and we're going to show how awesome this is. And that is going to be part of the way we get the credibility and coverage to do this long running project, because we are not just saying we're going to deliver value in two years.”
Please leave us a rating or review on iTunes! It'll help these chats get in front of more engineers and leaders like yourself.
Listen in on unscripted conversations between Jean Hsu, VP of Engineering at Range and engineering leadership coach, and engineering leaders and other influential folks in tech.
Lead Time Chats is brought to you by Range. Range helps hybrid teams check-in asynchronously about what matters most. Know what's happening through status updates that pull from tools like Github and JIRA without scheduling yet another meeting.
Checking-in with Range creates more focus time for heads-down work, all while feeling a deeper sense of connection and belonging with your team. To learn more about Range, you can check it out here.
Season 1 Episodes
» Episode 1: Will Larson on the path of the senior engineer
» Episode 3: Cate Huston on working with an external coach
» Episode 4: Juan Pablo Buriticá on common eng manager mistakes
» Episode 5: Gergely Orosz on the decision to go into management
» Episode 6: Lara Hogan on leading effectively in a pandemic
» Episode 7: Kaya Thomas on common early career engineer challenges
» Episode 8: Uma Chingunde on starting a VPE role in a pandemic
» Episode 9: Katie Wilde on supporting your team's mental health
» Episode 10: Akhil Gupta on navigating uncertainty in new roles
» Episode 11: Harper Reed on giving everyone a voice in team meetings
» Episode 12: Marc Hedlund on sponsorship