In this episode of Leadership Launchpad, Jeff Guido, Senior Director of New Missions at Planet Labs, shares his insights on effective leadership in technical organizations. Jeff discusses his experience transitioning from a technical individual contributor to a leader, highlighting the challenges and strategies involved in delegation and empowering teams. He emphasizes the importance of building strong relationships and trust within teams, both internally and across organizations, to enable effective collaboration and problem-solving. The conversation also covers practical techniques for onboarding new team members, balancing early engagement with support, and fostering a culture where decision-making is delegated appropriately. Whether you're a new manager or working to develop leaders in your organization, this episode offers valuable advice on cultivating trust and empowering technical teams.
Jeff Guido [00:00:00]:
Basically like if the team is able to have at the one to one level, like single direct relationships with each other, if those are good and they're good across, then the team just kind of just works.
Matt Gjertsen [00:00:32]:
When you work inside a highly technical organization like aerospace, software or energy storage, so many of the discussions around both problems and solutions end up talking about the technical side. It's almost as if we gloss over the very thing that often prevents you from meeting those challenges or allows you to find the solution, which is people and the relationships between people. Today on the Leadership Launchpad, my guest is Jeff Guido, senior Director of New Missions at Planet. He is not only responsible for leading some of the most cutting edge missions the company is currently embarking on, he's also responsible for coaching and leading many others who are leading their own missions. In this conversation we talk a lot about delegation and empowering your team, but most importantly the power of focusing on relationships and building trust if you want to be an effective leader. Before we get into the discussion, I do want to remind you that if this is your first time listening to the show, make sure you subscribe so you never miss a future episode. And if you happen to be someone responsible for developing leaders in your organization, I would love to talk to you. Please reach out to me at Matt atbettereverydaystudios.com so we can figure out how to make the leaders in your organization better.
Matt Gjertsen [00:01:55]:
With that, let's get into the discussion with Jeff Guido. Jeff, welcome to the Leadership launchpad. How are you doing today?
Jeff Guido [00:02:02]:
Great. Matt, how are you doing today?
Matt Gjertsen [00:02:05]:
I'm doing great because we've been trying to have this sit down for a while. Most of the time it's been my fault. I kept forgetting to follow up on getting the schedule because you're such a busy person right now. You've been particularly busy these last few months. I'd love for you to briefly describe what your kind of. What you do.
Jeff Guido [00:02:26]:
Yeah, sure thing. Yeah. Have you talk about that and you know, all of us are busy all the time. I think one of the ways in which, I mean I get criticized on a regular basis by friends and family, I'm always in motion trying to always be moving and so part of that is just like feeling like I'm always scheduled to the hilt on everything and I don't know, it's just a way to feel useful and way to feel like you're doing something worthwhile. So but as far as what I'm doing now, happy to talk about that. So I, I work at a company called Planet Labs. We currently have the the largest Earth imaging constellation that's ever existed. We have over 200 satellites currently in operation in low earth orbit and we have launched over 600 satellites in our decade long history.
Jeff Guido [00:03:10]:
Now those numbers that I'm throwing around right now used to be superlative in how large they were, but we've been recently passed up by another company or two that you're familiar with and that is okay. We're still doing great things and really excited about the work there. Currently what I work on is I'm what's called a mission director. It's basically someone that is more involved or more has their arms around an entire commercial space mission. And I lead a team of program managers, systems engineers, commercial folks that transition a brand new mission from incubation all the way to actual delivery of data to customers. In addition to that, my other hat is to actually lead the team of mission directors. So in addition to having my own program, I also help coach and lead mission directors in their own programs as well. And these are the some of the main missions that we have at Planet.
Jeff Guido [00:04:09]:
This is Pelican Tanager. New missions that are still in incubation as well as other things that we have on the horizon. Yeah, I know you want to talk about some of those things. So that's part of what we're here to discuss in terms of how to manage teams of leaders as well as like coaching them so they can execute effectively within their environment.
Matt Gjertsen [00:04:29]:
Yeah, yeah, exactly. And I think it's been, you know, we've known each other for several years now and it's been neat to kind of watch your trajectory through planet. Just on a personal note, just knowing you. And so, you know, when I talk with engineers, when people make that transition from, you know, being like a technical person or you're an individual contributor in any capacity into a leadership role. The most common difficulty that I hear is how to make that switch from kind of like the doer, the person actually getting things done, to the person helping people get things done. And so from your level, you made that transition, but now I'm sure you see a lot of others make that transition. I guess to ask in both of those situations, how did you make that transition and what kind of techniques do you, when you're coaching people, how do you coach people to make that transition?
Jeff Guido [00:05:21]:
Yeah, no, it's a good call. We often think about, I'll just say up front that we often look at people with a lot of technical skill that are effective in their roles. And I think it's a very common thing, at least in our professional cultures that we exist in. To be like, that person should lead, that person should be a manager. I think first, before you even cross that divide, is make sure that's part of that person's career, desires, what they want, their objectives. I think we often just peg people as like, they're doing great as an engineer, they should be a manager. But that logic doesn't always make sense. It makes sense a lot of the time.
Jeff Guido [00:05:58]:
And like, most people want to have that type of prestige associated with their role, but some people also just want to continue making cool stuff. I think that discussing that with the individual, making sure you have a clear career plan with them, is absolutely one of the ways to unlock success early on or to avoid setting them up for failure. But once that decision has been made and you're starting to go through that transition, the ways to transition from doing your own thing to having others do them out, there's a couple of frameworks you could use, but basically when it's your own work that you've been working on for a while, it's a project that you've invested a ton of time and energy into, it can be pretty hard to start to hand that away. We as professionals have a lot of pride in the things that we have done. And this is something that a lot of people need to know. They need to evolve within their careers. So the culture should be that we are continuously establishing a path to gradually transfer responsibility and work to junior folks. And if you can make that a part of like, we should always be developing and evolving our people that can build a virtuous cycle that makes the organization much stronger in the long run.
Jeff Guido [00:07:12]:
In general, if you want to take this from. From almost like start to finish, though, I could walk through a couple of things that I do. Like, first of all, hire deliberately for a role that normally has a little bit more narrow scope than what I hope that person will grow into in the long run. And the reason why is we can't look around every corner and anticipate every way in which that role will evolve. So having something where they can have like their core thing that they're delivering on, but then as opportunities present themselves, they're able to take them or not take them, depending on what the needs that they have in the program are themselves after someone is selected, I'd like to use things like 30, 60, 90 plans to onboard them. I don't know if that's a term you're familiar with, but Basically, in the first 30 days you're supposed to learn, the next 30 days you're supposed to contribute. And by the final 30 days, you're basically doing the job. And we will write down these plans together.
Jeff Guido [00:08:05]:
And we do this at Planet. And even if we write them down together and talk about them at the 30 day point, I honestly don't really remember to do it after that. And neither do they. And that's because really what it's about is setting those expectations up front and showing them the path to being a fully contributing member of the team. And you know, I think the temptation is strong once you get a new person in to like dump a whole bunch of work on them. But I don't. Even though the question or the prompt that you had was how do you get others to do the work that you've been doing? Like, even though the temptation can be strong and you're a manager, you find yourself as a new manager and you're like, oh, I could finally get rid of some of these things. You don't.
Jeff Guido [00:08:47]:
You want to make sure to have some restraint here because you don't want to set the tone for the new person or the junior folks that are starting to join your team of like a feeling of franticness or that emotional safety into their early days so that they understand and see how you're measured as a leader and will give them work as, as they grow into it, as the team grows into it together. Building that actually. Oh yeah, go ahead.
Matt Gjertsen [00:09:12]:
I'd actually love to pause you on that point because I do think the point you bring up is a great one and there's kind of that delicate balance because I think I've seen some research that talks about how kind of like the faster you can get a new employee to feel like they're having an impact on the team, the stronger the bond is going to be with them. Like the more engaged they're going to be because you're getting this person at like their most engaged, right? If you think about right after somebody starts on a team, like that is the most engaged they may ever be. And so you want to take advantage of that. And so when you think about can absolutely respect the idea of like you set up the 30, 60, 90, but it's kind of like just like that first 30 is really what you're going to be looking at. How do you think about, you said, you know, in your first 30 days of your learning, do you try? Is that truly it? Or do you ever think about without overwhelming them, like trying to find small things that maybe they can really bite into early on.
Jeff Guido [00:10:11]:
Yeah, that's a good, it's a good redirect and a good point. The small things that they can do, that's if you're truly expecting nothing from them in the first 30 days, I think they're going to, they're going to get bored. So in my, in my work environment there are, there's a, it's a perennial problem. There are too many things to do all the time. I am happy to sign people up for meetings. I want them to hand them small. Hey, can you set up this next thing or take these actions and try and like find the right people to go solve that? Absolutely. As part of, that's part of the learning process.
Jeff Guido [00:10:47]:
But what I don't want, what I do want to protect them from is I. Maybe this is a facet of where I work, but it does sometimes feel like it can be a little bit more frantic and more chaotic and want to provide that sort of structure early on. So they are running in the right direction without burning themselves out too early. It hasn't been a problem in this context either because the people that we're hiring were lucky and fortunate that they're all really self motivated and driven so don't actually have to. It's more of like a hanging on to the. Or bounding the problems early on so that they are, it's, it's energy put in the vector that you want them to go and not just energy expended in all directions. So yeah, I think that's. And I think your point about them being most engaged early on, it makes a ton of sense and that's when they have the most time too.
Jeff Guido [00:11:40]:
You think that there's an opportunity there to make sure to use that time to have to build in the foundation for the most basic cultural things that we want them to take with them and their full duration at our company. Makes sense. Yeah. Cool. Yeah. After about 90 days though, they're pretty much running. And so from that point I do like to use like a more player coach type of model. We're happy to jump in at any time to play alongside them in whatever game metaphor we're using.
Jeff Guido [00:12:12]:
But in the long run it should be more of a coaching approach where you want them to bring the, to bring the effort and do the things that they need to do and feel empowered and that they're owning the situation. You're having to come in over on the top every time and that's, that's been real, real effective to build proficiency And a way of doing things that work within the culture of the company as well as do it in the way that, I mean, like me as the manager think is. Is the proper way to execute. And this is mostly in the context of program execution. Yeah, I'm talking about this.
Matt Gjertsen [00:12:45]:
Yeah, you use the word empowerment because I think that it's one thing to delegate, it's one thing to like, hey, go do this task or tell people what to do. But then it's a. I feel like it's that next level of like, okay, like, what am I, what do I need to give you? What do I need? What barriers do I do need to remove? What resources do I need to give you? How do you. You think about how involved to be and what resources to give in order to help them be effective and empower folks?
Jeff Guido [00:13:15]:
Yeah, the general rule that I'll apply in all these cases, and I'll get more in depth here, is the general rule is to try and delegate or delegate decision authority to the level below you. I've heard folks say, and I do mostly subscribe to this perspective as well, delegate as low as possible, which I generally think is the right, the right approach. But like I have control over the level beneath me and I'll leave it to. And if I really am giving them like true decision authority, then they can decide if that decision authority can go lower than them. But one way that I have been able to transition from someone that's doing a lot of the work to someone that's having others do the work, thereby opening up a lot of my bandwidth and capacity for other things, or to rise up to a more strategic level has been to ask my reports to make these decisions for certain program things or things that are clearly within their scope and continue to push that down every time. Now, it's one thing to just say here you make the decision, but I want it to be something that it's understood on a regular basis. This is the scope of their authority. And you can say that over and over again.
Jeff Guido [00:14:31]:
But I think you also have to show up to meetings, to social engagements, depending on how you want to say them, be they meetings, hallway conversations, whatever they are in the professional workspace and show up with a little bit of courage and willingness to stand up for your folks that need that empowerment. Because there are always going to be people that are trying to. Everyone's trying their best, but that are always trying to have their own influence applied on a particular situation. And I think what we're really talking about is leading with influence Here because empowerment can flow through that influence. But there's also a whole lot of empowerment that flows through some of the more harder ways of doing it. Like people that have higher fire authority, that have budget assigned to them and can make decisions on how budget is allocated, or actual signatory authority. Those are all things that I think companies and governments control really closely. But I don't think that's really what you're asking about.
Jeff Guido [00:15:25]:
You're asking about the kind of the other side of it. Leading with influence, which relies heavily on soft skills, how you aggregate information, how you guide that communication could definitely be a double edged sword there. Because if you're seen as constraining in communication, it can certainly undermine your credibility and influence. But do it in the right way. And if you're inclusive, influence can be oftentimes much more effective than the much more blunt instruments such as hire fire, budget and signatory authority. With my team, I make a point of outlining what I do think their scope of decision making authority is. They do this in one on ones and even if it can be a full time, full contact sport, sometimes with other teams or other stakeholders, knowing your unique way of approaching these situations allows you to represent your equities in a professional, sincere way. A little bit of courage as well.
Jeff Guido [00:16:19]:
But I've often found that like applying that courage makes it so that you can get what you need and have more often been rewarded positively for being a bit vulnerable in situations. To advocate for my people for sure. Yeah.
Matt Gjertsen [00:16:35]:
When you say just really quick, really quickly, when you say one of the things that you really focus on doing is kind of reinforcing where their scope of decision making is. Do you mean by that that you're finding that typically is it that you're trying to push people to make the decision or people trying to like overreach and then you're having to rein them in? Like is. Is it more that you're just having to say like no, remember you have the authority to do this? No, I want you to make the decision. Is that kind of the drumbeat that you have to keep reminding people of?
Jeff Guido [00:17:09]:
Yeah, I don't often have to rein folks in. I do think this is a cultural thing as well with our company is we do have a lot of decision making by consensus. And while that can work really well a lot of the time, and it can be effective way to garner alignment if costly from a time perspective, sometimes it does sometimes leave things stalled. And so being able to make clear, and we're getting better at this, at our company where we collectively can recognize that someone needs to make a decision. If we can make that clear in a social setting or even one on one, then usually people fall in line at our company when someone's just willing to be like, we need to do it this way for this and this open to feedback on this decision, but we have to move forward. And generally that works pretty well. I don't normally have to as a manager reinforce that to my reports. Very often I do think that partially their personality, they understand.
Jeff Guido [00:18:09]:
But when you have like a, like Satellite A that's in production or doing things to make a decision on a supply chain issue or a manufacturing flaw or something like that, doesn't touch Satellite B, which is a totally different satellite. Those mission directors that are over those missions, I mean, it's pretty straightforward how to do that. And then if there's a prioritization issue, which is definitely something that we have come across quite a few times, I expect those mission directors, as I've told them, to work it out among themselves if they need to figure out how to prioritize resources. And then only then if there's a need for a tiebreaker, then we all have a conversation about it. And I can weigh in on being the tiebreaker or my boss sometimes does that too. And that's how we've navigated some really tricky situations where you only have so many people that can work on the manufacturing floor at any given time. Being able to say, no, you should be working on Satellite A instead of Satellite B has helped us to stick pretty well with timelines and make it clear to the team as far as how they should be applying their effort most effectively. So that's been really helpful.
Jeff Guido [00:19:16]:
And one final thing I'll say on this and on empowerment is that that from time to time I'll disagree with my people and the decision that they want to make. But I think, like, if you want to maintain empowerment, you can't overrule them in the situation that you just that you disagree. Now, of course there are limits to that. There's definitely times where I certainly have to step in, but like, for the most part, if I disagree with their decision or direction, you can do a lot more damage to their empowerment by overruling them on a regular basis than you can by just sort of like sustaining that and just committing to the course of action and then also committing to learning from it if it doesn't go well. And oftentimes I'm more often than not pleased that I let them make the decision because they're closer to the situation so they understand the nuance better than I do and they have a deeper understanding of the issue as well. I've often found that it's just best to let people retain their agency. And through that we found greatness as a team in.
Matt Gjertsen [00:20:17]:
Yeah, that makes a lot of sense. I mean, I'm reminded of. It's usually used in a different context. You know, this concept of disagree and commit is usually used more in a context of like peers or something. But I think it applies here. And the way that I mean it to apply is one of the challenges that I always had with this disagree and commit is that okay, so we've reached a disagreement and now we're going to commit. But it doesn't necessarily give you a lot of guidance of to which direction to go. And the last company I worked at, they just talked about it's just simple like who's going to be more closely affected by the decision, you know.
Matt Gjertsen [00:20:51]:
And so in this, and that's, I think how it applies to your cases is the people below you are probably are. They're the ones closer to it, as you said, but then they're also going to be the ones probably most directly affected by it. And so if there is a disagreement, it's probably better for you to side with them anyway, you know, with that kind of methodology.
Jeff Guido [00:21:09]:
I think that's right. And on, on the disagree and commit side, I was ruminating on this recently. I think that when, you know, there's another model that's kind of similar but I think could be applied. You know, there's praise in public, punish in private type of thing and I think a similar set applies here. If I disagree and commit in a public way with one of my reports, that also undermines their empowerment and they're going to use that as a, even like unintentionally that's going to go into their feedback loop and how they make decisions in the future and be like, well, I don't want to have my boss say disagree and commit to me because then I'm going to maybe would make a different decision or be biased in the future if I'm at risk of them saying that. I do think that disagree and commit can be really useful in managing upward and I have used that from time to time with my management in a more private setting, like a small group of more senior leaders. I'm happy to say I don't agree, but I'm going to do whatever you all decide and I'm going to fully Commit to it when it's down, when it's coming downward, it has a different vibe to it. And so I try and stay away from that language when I'm the senior person or my report is the one that's obviously making the decision.
Matt Gjertsen [00:22:31]:
Yeah, that makes a lot of sense. That makes a lot of sense. Well then if we take this to the final level, because I know especially in some of the things you're doing now, I think you're working much more truly in that leading with influence where you're working with potentially organizations outside of your company. And there truly is not a lot of formal authority, but, but you're all having to work together. And I think this happens, this can happen between companies, this can happen between teams of companies. What are some of the techniques maybe that you've personally used to manage those kinds of relationships and make sure that they're effective?
Jeff Guido [00:23:08]:
This is a good question. And this, this is something I've really. It's interesting, Matt, because we, I think when we were trained as officers, words like relationships and relationship building were used like constantly, like all the time. And I did not appreciate the strength behind them. And really, like, maybe the wisdom is probably a better word for it of what I was, what was being conveyed to me when I was on active duty, but when it was only when I started working the Tanature program at Planet Our Hyperspectral mission that I really started to understand the true wisdom behind this and how you could leverage relationships to be something that made or break the mission or made you successful or didn't. And so like you say, now I'm a time in my career where these things matter more. And I think the relationships themselves just to kind of like pull the thread on that they really make up the fabric of a team. And if that team is going to be effective, we'll get into more tactics in a second or how we do that.
Jeff Guido [00:24:15]:
But basically like if the team is able to have at the one to one level, like single direct relationships with each other, if those are good and they're good across, then the team just kind of just works. But if they don't, or even if you have just a couple of weak links in that fabric to use to continue that metaphor, I find myself spending a lot of time repairing feelings and egos and it's, it's just, it makes work a grind and a bear. And so I, as a result, I've learned not only for myself but for, for my reports to be like, this is a core responsibility of yours. This is A core expectation that you invest in and build the relationships with all of the closest people that you work with. Like, it doesn't have to be everyone. Like, we, we just, like, there's just a fundamental drop off in our ability to do that as humans. But the core people you work with gotta have good relationships with them. And I think, personally, I think relationship building happens best in person when people are solving challenging problems together.
Jeff Guido [00:25:18]:
But, you know, we live in a world where we've derived a lot of value from virtual work or doing resume or things like that. So as a result, you know, we need to build in the opportunities for people to build those relationships remotely and then still bring people together quarterly or twice a year or whatever, so they can have a meal together or solve some, you know, deep strategic problems together in the same room. And so we do a lot of that at Planet, where while we have a strong push to come into the office regularly, we've also hired people all over the world across many different time zones. So we have this sort of like, hybrid approach where we try and bring in our remote people on a regular basis to the office so we can have on sites or at least just work together occasionally. And, you know, I think this all sounds nice and fun and warm and fuzzy, but, like, the real reason, the real output of why we're doing this is to build trust. And I think that, like, at the most fundamental level, if you don't have trust, that's what makes those links between the people not be sustainable. I'm really, I'm. I value or I like or appreciate Patrick Lencioni's work.
Jeff Guido [00:26:33]:
And I mostly think in this context, I mostly think about his five dysfunctions of a team. When I say trust, you know, and that's the lowest level of his framework. But if you can't get that trust level done, you really can't go anywhere else as a group. But once, once that's set and people have a, you know, requisite level of that and they're building, building trust, then I think you can build other structures upon that foundation, such as, you know, like, what are the roles and responsibilities of the team? How does decision making happen, Accountability for work and quality of work and timeliness, and then allow for, like an organically driven division of labor so you don't have to have the whole team show up to every meeting. Like, if people trust that other people are doing the things that they need to do and then that they'll let me know or let their peer know when they need to know something, then that's time that I then get back to go do other things or do some deep work or something like that allows us to be more effective as a team. And that's kind of where we've derived value from that. So just to kind of like, you know, recap, make it clear to folks that they have to, have to, have to build trust. That's part of their job.
Jeff Guido [00:27:39]:
They, you know, that's through building those relationships, build in the time to do that and then like come together physically as a group occasionally so that you can do that in person. And through that there's a, there's like a basis or like a, almost like a flywheel I guess, to actually like solving problems because you have some of that context of what each person wants and who they are and it helps smooth a lot of issues.
Matt Gjertsen [00:28:03]:
Yeah, I couldn't agree more with that. And I do think it's something that's particularly challenging when you're making that first transition, especially for technical individual contributors, if you think so much about the technical side of things to forget that people side of things. But yeah, I mean, I know Andreessen Horowitz, one of the biggest VC firms in the world, they do this where they're primarily distributed, but they come together quarterly for meetups. I've worked with the Xpress foundation, they're the same way. They're a very distributed team, but they make sure quarterly they have in person meetups because that's what provides the glue that allows you to work together so much, so much more smoothly for the rest of the time. And I also think it's, I always find it funny, interesting that you mentioned the military background because I think typically people think of the military as extremely hierarchical and you know, giving orders and everything like that. And that's true. But I mean, you know, Jocko Willink, former Navy seal, now author and you know, leadership consultant, he always says how like he doesn't remember a single time where he said I order you to do this.
Matt Gjertsen [00:29:05]:
Like that's not actually how most of the military folks functions. It really is all about the relationships. The kind of step ahead that the military tends to have is there's a built in layer of trust of everybody's made a certain commitment, everybody's committed in some way to a very specific mission. And that's one thing that maybe you have to get a little bit clearer on, be a little bit more deliberate about in the corporate environment because depending on the company, you know, maybe they're very mission driven or maybe it's just A job or maybe it's a stepping stone to somewhere else so people can be there for all kinds of different reasons. And so then that's you as the manager having to find that common foundation so that you can build those relationships on top of it. That's really interesting.
Jeff Guido [00:29:52]:
Yeah, no, I like that recap. It's good. And I think you're totally right with the military side. I don't think I ever uttered that sentence. That's an order, you know, other than like, is a joke, you know. Yeah, yeah. Like, it's so. It can be so ridiculous and you've failed in some fundamental way as a leader or it's a really extreme situation.
Jeff Guido [00:30:13]:
Like, I mean, let's give some space for that. But in the data, the regular day to day, like, there is. There's almost no reason to do that if you've done your homework beforehand and building the team, building the relationships. So 100% agree with what you're saying. Yeah.
Matt Gjertsen [00:30:31]:
Awesome. Well, this has been a fantastic conversation, Jeff. I know. I'm always following the work that planet is doing, watching you all. It's great reading Ashley Vance's book When the Heavens went on sale and seeing kind of the backstory, it really helped me appreciate what you all are doing and what you're hoping to do in the future. And then, yeah, it's been great knowing you. I think this has been a really great conversation. So thank you so much for your time.
Jeff Guido [00:30:55]:
Great. Thanks, Matt. I always, always enjoy it. It's always been, it's always fun talking with you, even offline, like just sort of like shooting, shooting ideas back and forth on how to lead properly. So thank you for your time and the invite.
Matt Gjertsen [00:31:08]:
Absolutely. Thank you.
Jeff Guido [00:31:09]:
Cool.
Matt Gjertsen [00:31:11]:
Thank you so much for listening to today's show. If you are looking for help turning your organization's great engineers into great managers, me and my team at Better Everyday Student Studios would love to help we deliver targeted and interactive training workshops that are designed to help build the three fundamental skills of any new manager. Building trust, giving feedback and setting goals. Reach out to me through Matt better everyday studios.com so we can start making your organization better every day.

