Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

The Impactful Engineer - Mentorship, Career Growth, and Personal & Professional Excellence for Aspiring Engineers

The Impactful Engineer - Mentorship, Career Growth, and Personal & Professional Excellence for Aspiring Engineers artwork

Episode 179 - Stop Talking Before You Lose Their Trust

Nov 2, 202622 minAudio
ShareXLinkedInFacebookWhatsAppEmail

Confidence can get you noticed. False confidence can destroy your credibility. Engineers often feel pressure to have every answer, especially when speaking to managers, executives, or experienced colleagues. But guessing, exaggerating, or overexplaining doesn't make you look competent. It makes people question whether they can trust you. In this episode, Steve and Jake break down how to communicate confidently without pretending to know everything, recover when you're wrong, and build credibility through preparation, clarity, and ownership. Not theory. Practical, tactical advice for engineers who want their words to carry weight. Key Topics Covered: • Why false confidence destroys credibility faster than admitting uncertainty. • How overexplaining exposes insecurity instead of demonstrating expertise. • The difference between being wrong and misleading people. • How to recover immediately when you give an incorrect answer. • Why vague answers like "I think" leave teams unable to make decisions. • How to respond confidently when you don't have the information. • Why early-career engineers need to prepare more thoroughly for meetings. • How to recognize when you've made your point and need to stop talking. • Why blaming someone else for information you present demonstrates poor ownership. • How concise, reliable communication builds long-term professional trust. Actionable Steps: • Admit uncertainty immediately rather than inventing an answer. • Correct yourself in the moment when you recognize a mistake. • Follow up with verified information when you can't answer accurately. • Prepare for meetings by anticipating the questions and decisions that matter. • Give direct answers first. Explain the supporting details only when needed. • Stop talking once you've made your point. Let others ask for clarification. • Ask what level of detail someone needs before diving into technical explanations. • Replace speculation with a clear commitment to verify and follow up. • Take ownership of every recommendation you present, even when the information came from someone else. • Review what caught you unprepared and improve your preparation for the next meeting. Who This Episode Is For: • Early-career engineers learning to communicate with experienced professionals. • Engineers who feel pressured to always have the right answer. • Individual contributors struggling to earn credibility and leadership trust. • Technical professionals who tend to overexplain or become defensive when challenged. • Aspiring engineering leaders who want greater influence in important conversations. Why It Matters: Your technical knowledge might earn you a seat at the table, but your credibility determines whether people listen when you speak. Every conversation is an opportunity to build trust or erode it. You don't need to know everything to become a respected engineer. You need to be prepared, communicate clearly, own your mistakes, and consistently deliver reliable information. That's how engineers earn influence and create opportunities for greater responsibility. Where to Listen: Spotify Apple Podcasts Or wherever you get your podcasts. Share: If this episode hit home, send it to someone. The Impactful Engineer grows by word of mouth, just like the best careers do.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

SPEAKER_02Engineers don't fail because they lack technical skills. They fail because they never learn how to lead, communicate, and take ownership. This is the Impactful Engineer. We give you the blueprint for career excellence and not textbook answers. I'm Steve Maxie, Senior Management and Senior Management? Good job. Senior management. Yep. So a senior manager in product development, and I'm here with my brother Jake, owner and principal engineer at NLS Engineering. If you're done with the status quo and ready to take control of your career, then you're listening to the right show.

SPEAKER_02And that is gonna how I'm gonna blame it on jet lag. There you go.

SPEAKER_00Two weeks in China, that'll do it to you.

SPEAKER_02Oh yeah. Yeah. So still still waking up at four in the morning.

SPEAKER_00Your airport sourdough sandwich. Yeah.

SPEAKER_02Yeah, which would blend into. Yeah. Don't don't eat uh fresh sourdough right before you get on a plane for for 14 hours or whatever it is.

SPEAKER_00Especially when you're like you're like no carb, very low carb diet.

SPEAKER_02I know, but it was so good. Oh man, it was it was not not a pretty odor. I'm just gonna put it that way. Jesus. GMI, GMI. All right. So um how's it going, Jake?

SPEAKER_00It's uh it's been a minute since we've recorded. It's it's the same. Yeah, I've been just doing my thing. And now you're back.

SPEAKER_02Yep, kicking ass, taking names, and hearing them.

SPEAKER_00Uh and then being a pain in the butt. The blink goes by and then you're back again.

SPEAKER_02Yeah. All right. Well, uh, I'll just run us through the housekeeping real quick. Um, within this podcast, we do have a couple episode types. Um, our most common type is uh Jake and I will get on here either both of us or one of us, uh, where we present a topic. We introduce the why and how around that concept, and we give some tips to inspire some action. Uh usually the solo ones are a little bit more passionate about, and we're just gonna yell in the microphone by ourselves.

unknownThat's right.

SPEAKER_02We gotta do more of those. I know, I know. It's we never do those. It's been a while, but hundreds, still good. Yeah. Um and then uh uh our long form, our hour-long episodes is about once a month or so. Uh we will have a guest on um and where we bring in an expert in a particular field to share their perspective, um, their mindset, and actionable tips around their area of genius. So those are awesome. Uh, we've had a good number of them recently, and I think we have some coming up too. So stay tuned. All right. So uh already did our pleasantries.

SPEAKER_02So let's let's talk about something. So when I was young and uh well, sort of young, because I was a late college guy, uh, when I was in college, I was a lot more extroverted, but I also um had a lot of foot and mouth uh egg on face type moments when I was when I was younger, uh, because I would just jump into a conversation like I knew what the fuck I was talking about, and I didn't. Uh and uh I had uh some some realizations during school that um well, because A, I was around smart people for once, um, you know, because we grew up in a small town, so it was it was a little harder.

SPEAKER_02They're all dumb. Yeah, they're all idiots. No, I know what you're saying. I know what you're saying. Yeah, there'd be some people who be like, all right.

SPEAKER_00Well, you're you're in a you're in a university with a bunch of other engineering students, you're gonna be around a bunch of it's the collection of all of the people that are intelligent and ready to pursue something fucking hard.

SPEAKER_02Yeah, exactly. So they get it. So I used to be used to go, that's a dumb sentence. But anyways, I I used to be foot and mouth. I know, exactly. Already. Um, I used to be the smartest one in the room, or so I thought, right? And and so I would just jump in and and act like I knew what I was talking about, right? I had like a false confidence in in whatever subject matter it was. Um, and normally people would just be like, oh yeah, yeah, that must be true, blah, blah, blah. Um, because they they knew I was, you know, relatively intelligent, etc.

SPEAKER_02But when I was in school, I was around a lot of smart people who are actually smart uh rather than myself. And they would call me out my bullshit, and it uh it humbled me pretty fast. Yeah. And so I almost like regressed into a more um uh introverted state, and I've kind of uh been coming back from that ever since. So it it's it's kind of been an interesting development in in my life, but uh I I do see other young engineers kind of get in the same similar situation, right? Where they they have this false confidence, they they they think they know what they're talking about and they'll jump into a conversation or or be leading a conversation and then they're just dropping facts or or or topics that are just straight up wrong.

SPEAKER_02And what I'd like to talk about is how can we uh prevent ourselves from doing that if we're in that situation? Um, how can we recover, right? Because that's I mean, everyone's gonna do it. You know, even if you are very uh aware of this, you're still gonna trip up and say something that oh shit, that wasn't right. So, how do you recover from that in the moment? So um, yeah, but what what are your thoughts on this? Like where where were you when you first started?

SPEAKER_00Pretty much the opposite of you. I was always quiet and calculated and listening first. And if I didn't know something absolutely outright, then it was very hard for me to prove to myself that I knew exactly, um, I just wouldn't say anything. You know, so I was just yeah, yeah, yeah. I wouldn't just I was not the one jumping into conversations talking like I knew what I was saying, because there's it's just so many ways that you can be wrong. So yeah, yeah. So I had to come back the other way as my career progressed.

SPEAKER_02Yeah, and and you think uh it did you did you come back to the point where you you were still jumping into conversations, but you were just never wrong?

SPEAKER_00Well, you're never not all you're never going to never be wrong. You will there will be times when you are wrong, always. You can't just be right all the time.

SPEAKER_02Yeah. Okay, so so how how have you recovered in those situations then?

SPEAKER_00Yeah, the best time to do it is right in that moment and say, nope, that's not right. Like immediately after. Immediately. Oh, yeah, yeah. On second thought. I just blow it off. I just make a joke. I'm just like, nope, that's completely wrong. Uh I'll I'll I know that that's gonna be off. I will get back to you with the actual concrete answer. But if you say something to where in your mind it's like, that would be better not in front of all these really high-level people to sit to crack a joke and say, nope, you know what, that's wrong.

SPEAKER_00Um, to follow up later or or recover with an email. You know, I just make a mental note to myself. It's like, hey, you know, what I said there is quite overstated. And so I will follow up later in an email, say, hey, during our conversation, I had stated X and realized that there could be I could zoom in a little more on that, and there could be something to the question that you had. And so I did the research. I I say it's a code thing. I looked really hard at the code, looked at every nuance, and in fact, there is a path that should be discussed.

SPEAKER_00And in fact, here are the criteria, review it, here's my recommendation, which still holds to the original, but there are these things to consider. Blah blah blah. You know, yeah, you could just you could say it later and and have them review it.

SPEAKER_02So I have a question here too, like a little bit of follow-up is in meetings, uh when I don't know something for a fact, but I need to speak to it. Often like myself, or I've seen it others do it as well, is I will say things like, I think, or etc. Like it was a very it's a very unsure response. The problem with that is that it uh solicits an opinion that you don't really know what you're talking about, or you don't have a handle on on the on the topic.

SPEAKER_02And so what would be a better way if someone comes in and asks you something on like say one of your projects and you don't know the answer? You think it might go one way, but you're not a hundred percent sure. Like how how do you confidently respond to who whomever is asking that question without s sounding like you don't have a handle on it?

SPEAKER_00I don't leave anything up for interpretation. So either we're in a position to where I can say, all right, give me a second. I'm gonna pull up the drawing and I'll give you the answer right now, if it's important. We could take it offline because I don't want to misspeak, and I'll send you the answer once I've had a chance to look. But we're not gonna stop the whole show right now to look that up. So it's you know, I don't want to say th because nobody can move on an I think or it may be and then and then the worst thing that you can do is like drown, just drone on and on with the I think thing, and just like it's just agonizing, man.

SPEAKER_00Everyone in the room is just like, get to the point. Yeah, you know, if there is no point, then move on. And if there is a point, then get to it.

unknownYeah.

SPEAKER_00Because you're wasting everybody's time and it's just painful, you know. You can just see it in people's faces.

SPEAKER_02Yeah. And so would it be good to say, hey, I I do have that point somewhere, I need to look it up. Um, you do you want me to take a second to look into it real quick? Uh or would you like me to take this offline and just follow up with you later? So you can kind of like turn around and that and and ask them a question.

SPEAKER_00Yeah. And if it's something that, like I said, don't leave anything to interpretation. So saying I think it's this, it's like, okay, so does that mean I could take what you said and run with it? Or are you gonna follow up with me? Or is it solid?

SPEAKER_02Yeah.

SPEAKER_00You know, it's like someone asks you, how much is it gonna cost for this? Well, it's twelve hundred dollars per KW. You can take that, run with that when you have your conversation. That closes the item. If you're like, well, you know, like the last project, you know, like you were kind of thinking it was like around twelve hundred but, you know, dollars a KW, and like, I don't know if that included this, and and you just start, it's like they wanted to know the the high-level cost of the thing in the meeting.

SPEAKER_00And so if you're just droning on and on and on, they're gonna get frustrated because that's probably like the easiest question they're gonna ask, and one little data point that they want, and you just drone it on and on just is gonna drive them crazy.

SPEAKER_03Oh, yeah.

SPEAKER_00So either you say with confidence, this is the number. But by the way, you can also come back later and say, Hey, I gave you this number in the meeting, I went back and looked harder. I want you to use this number instead, and here's why. Send.

SPEAKER_03Yeah.

SPEAKER_00Not like, oh, like I gave you that number in the meeting because it was this and this, and I was thinking that, and it's like just give like just give straight, confident, owned answers, but you can always say that you're gonna go that you're gonna follow up after you look hard at it, but it's around this yeah, you know, magnitude or something.

SPEAKER_02Yeah, I I've seen uh and and I've done this too, um, where if I'm not confident in an answer, I I almost feel like I need to prove that I I know the subject matter, and so I'll keep spewing shit like on and on and on, I like running on with more facts that don't really back up the original question, it's just just piles onto it, if that makes sense. Yeah, all it does is prove that you're lost. Exactly. Yeah. And it it reduces the confidence that the other person has in your ability to to articulate and also just have a handle on a project.

SPEAKER_00Yeah. Fail for the right reasons. So if the expectation of the people in the meeting is that you know your shit right away off the top of your head and you don't, then you fail because you don't know things off the top of your head. You don't fail because you gave bullshit answers that were clearly made up and degraded the confidence of everyone in the room. If you fail because you didn't have the answer, but you clearly communicated very quickly that you don't have the answer and we need to move on from this because I can't give it to you, they're gonna respect that more.

SPEAKER_00You could still lose the confidence and be switched out, or or somebody's gonna say to your boss or somebody that, hey, we need someone in here that knows what they're doing. That still could happen.

SPEAKER_03Yeah.

SPEAKER_00But at least it's not, hey, we need someone in here that's not gonna bullshit us and give us fake information and mislead us.

SPEAKER_02Yeah.

SPEAKER_00That's even worse.

SPEAKER_02Yeah, because all you're doing is eroding trust.

SPEAKER_00Yeah. So the trust does not go down when you tell them the truth, but the performance that they expect on the project could be not up to their standard, which is okay. That's fixable.

SPEAKER_02Yeah.

SPEAKER_00You know?

SPEAKER_02Yeah, absolutely. Yeah, because you because they can still have trust that you are going to put more effort the next time, right? And and prepare more, right? Because you know, and it kind of goes to another point is uh when you when you're young in your career, you are going to be required to have more preparation for for every big meeting or every conversation that's you know a project conversation. Because you don't have the decades or whatever of experience to to lean on. So you have to prep uh prepare more, you know.

SPEAKER_02Because it's not going to be just instant experience that you can pull from.

SPEAKER_00That's right. It's much easier for me to walk in less prepared to pretty much any meeting because I just have the experience. But when I do when I know the agenda and I know the out the general outcomes of the meeting and I prepare for it, it I'm just on fire. Like there's a clear difference between when I walk in unprepared versus prepared in my mind. Oh, absolutely. So always prepare, always, you know, be ready and make getting better at preparing on the right things, the goal, instead of getting better at bullshitting, you know, or like yeah, improve at your accuracy of what people care about, and then prepare on those things.

SPEAKER_00If you were hell really prepared for the meeting, but they asked nothing that you prepared for, then you still win because you prepared for the meeting. You just know now that you need to alter what you prepare for the next time. Make that the go the the win.

SPEAKER_02Yeah. Yeah. And just kind of circling back to the original thing is that you know, the more that you just spew nonsense and bullshit that is clearly not true, and and people get used to you doing that, you they're just not gonna ever have trust in what you say is correct. And that is really hard to come back from. Like, not impossible, but it's really hard. Because you're gonna have to overwhelmingly and like just massive volume of being right and having clear, concise information from that point forward to even build a small amount of trust again.

SPEAKER_00Yeah, just to get back to normal levels. Yep. Being reliable, having a reliable response, because we're still talking about just not faking it, right? We're still talking about just like because you can bullshit your way because you're a bullshitter, you can also be too um, you can like I don't know, you can say too much, you can go too far, you can be a little extravagant, you could be like, what's the word?

SPEAKER_00I'm like totally losing the word, but you can embellish, you can that's the you can exaggerate. There you go, there it is. You can uh before you know it even happens, right? And so that's happened to me before. And usually I go, nope, that's an exaggeration, that's not right. Still the right concept, but yeah, there's not a thousand of these things, there's you know, twelve, right? Yeah, so I was exaggerating a little bit. You can catch it there, or you can follow up if it's something like you know, way more technical, and you can get a sense like I should shut the fuck up right now.

SPEAKER_00Right, and that comes from getting burned and going down into the hole and trying to dig yourself out, but you're you're just digging a deeper hole, you know. So you'll you'll know when that's happening. So you kind of just cut that off, yeah. Pass.

SPEAKER_02You know, I think when you exaggerate, you can even uh reinforce uh the topic by by circling back and be like, oh, I was totally exaggerating, but I'm exaggerating to to make a point, right? Because it's a lot easier to see when things are exaggerated. Yeah. So you can even like you know lean into the exaggeration of like, hey, I'm just trying to illustrate a point here. It's only it's only 12, it's not a thousand.

SPEAKER_03Yeah.

SPEAKER_02But could you imagine if it was a thousand? Holy shit. You know?

SPEAKER_00Right. And how you so how you can tell when to stop talking is when you've made your point and no one says anything. Shut up and and and just be done and move to the next topic.

SPEAKER_03Yeah.

SPEAKER_00Because a lot of times you could be like, yeah, and so that's why we took it this direction and designed the distribution system this way. Because, you know, if we didn't, if we did it this other way, it it would be like this, you know, because it would cost too much to do it this other way. So like that's why we were considering the architecture, you know, the the arrangement that we were doing, that we're doing now. Because you, you know, copper versus aluminum, uh, with the distance that we're thinking, and you just keep adding. It's like just shut up. We did the arrangement this way, and there's our recommendation because it saves money.

SPEAKER_03Yep. The end.

SPEAKER_00Silence. And then somebody could ask a question, and then you go, okay. And depending on the question that they ask, if it's like, can you elaborate on that a little more? This is when you need to start being careful. Because depending on it, what your version of elaborating on it means, you know, you can start getting into defensiveness, you can start getting into too granular of detail for the for where the project is at the time.

SPEAKER_02Yeah. And and a good a good way to figure that out is just to ask them. Like, hey, how do you tell how detailed do you want me to be?

SPEAKER_00Yeah, what do you what are you really looking for?

SPEAKER_02Yeah. Yeah. Do you just want a cost analysis of this or or or do you want to know like everything?

SPEAKER_00Right. Because I've got all the calcs.

SPEAKER_02Yeah.

SPEAKER_00I've got all the comparisons that I did for hours to back up this information and recommendation I'm giving you. Which which part in particular do you want to dive into?

SPEAKER_03Yeah.

SPEAKER_00Because then you can protect yourself from this whole exaggerating thing and just burying yourself.

SPEAKER_03You know.

SPEAKER_02Yeah. And and that that brings me to another um topic in this whole conversation is and and I think we talked about it before we started recording. Was if you think you you know the answer, but you're not quite sure, you can actually turn it into a question to solicit uh more of like almost like a brainstorm of a conversation with the other person um to get to the answer, right? And so instead of saying something like, oh, you know, the this this water bottle can hold 80 gallons, you can say, Hey, how much water do you think this thing can hold?

SPEAKER_02You know, you you can you can ask people about the whatever the topic is, um, and and put in the the bit of information that you think is right, but you ask it in a question, and then they can give you a response, but like, ah, like that kind of seems like bullshit, you know. That's that's really exaggerated. But like, uh yeah, I okay. Oh, what do you think it is? You know, and I think you can you can get a better conversation that way, and then it doesn't uh put you in a position where people can just call you out on bullshit because you're asking instead of telling.

SPEAKER_00Yeah, instead of making a statement. And another thing that I was gonna throw out there is don't I would recommend you do not lead with well so-and-so said. And I'm reporting on what so-and-so said, so I'm gonna have to ask them. That is weakness. Yeah. That is you are if we're talking about you're you're being the presenter of the information and you're doing a status report, and and somebody starts picking apart your argument or or asking you more questions or diving deeper, and then the second you say, Well, this is the the this person is the one that said we should go this route.

SPEAKER_00So let me ask them more about it. It's like I would recommend against that because all it says is that you don't know and you're not taking ownership. And you're not taking ownership. That's correct. So uh don't do that. Stand by stand by the what you're saying, um, and you can always follow up. If the true answer is you don't know because someone else said to do it and you didn't fully vet it and weren't prepared to discuss it, you can just simply say that's a great question. I am not prepared to speak to that at this time.

SPEAKER_00I will immediately get back to you after this meeting is over. Yeah. Like don't blame other people.

SPEAKER_02All right, man. I think that I think that covers it. So you you good? You have any final thoughts? All right. So if you guys think you learned something today, uh or someone else needs to hear this point of view, please share the show. It's the best way we can grow the podcast and continue to create value and impact for the engineering community. And leave us a comment. Rate us, give us five stars if you think we're awesome, four stars if you think we need to get better.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Episode 181 - If You Keep Your Head Down, Don’t Expect Your Career to Take Off With Occie Norton

    Nov 16, 202654 minAudio

    Technical skills can get you hired. They won't build your career for you. In this episode, Steve and Jake sit down with Occie Norton, Industrial Facilities Practice Leader at T. Baker Smith, to challenge how engineers...

    Credit the people on this episode

  2. Episode 180 - Being Technically Right Isn't Enough With Ashwin Aravindakshan

    Nov 9, 20261 hr 4 minAudio

    Being the smartest engineer in the room means nothing if you're solving the wrong problem. In this episode, Steve and Jake sit down with Ashwin Aravindakshan, professor at UC Davis and former director of its Master of...

    Credit the people on this episode

  3. Episode 178 - Maybe It’s Not the Job. Maybe You Quit When It Gets Hard.

    Oct 26, 202610 minAudio

    When engineering gets difficult, what's your response? Do you step up, or start looking for a way out? Tight deadlines, complex technical challenges, rising expectations, and mounting pressure are part of professional...

    Credit the people on this episode

  4. Episode 177 - Nobody Needs the Whole Story. Give Them the Punchline.

    Oct 19, 202614 minAudio

    Technical expertise gets you into the room. Your ability to communicate determines how much influence you have once you're there. Too many engineers bury their message under technical details, unnecessary context, and...

    Credit the people on this episode

  5. Episode 176 - You Can’t Lead Everyone the Way You Want to Be Led, With Jeremy Doran

    Oct 12, 202656 minAudio

    Jeremy Doran, author and host of Neuroconversant Leadership, joins Steve and Jake to break down why strong engineers still struggle to communicate, influence, delegate, and lead people who think differently than they...

    Credit the people on this episode