Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Know-It-All New Hire
Transcript
- Lucas: So you hire someone with great experience, strong credentials, they walk in on day one full of confidence. Within a week, they are telling you — and everyone else — how things were done at their old company, and why your way is outdated. Luna: Right. The know-it-all new hire. I have seen this so many times. It is one of the most polarising dynamics a first-time manager faces. Lucas: And it is tricky because part of you wants to appreciate the fresh perspective — you hired them for that. But part of you also wants to say, 'Hey, you have been here five days. Pump the brakes.' Luna: Exactly. So how do you separate the genuinely useful friction from the kind that just alienates everyone? Lucas: Well, I want to look at a specific case. There is a mid-size logistics company based in Atlanta — about 400 employees — and they hired a senior analyst from a big competitor. Let us call him Mark. Mark was brilliant, came in with strong opinions about their routing software, their vendor management, everything. He started saying things like, 'At my old firm, we cut delivery times by 20 percent using a different dispatch model.' Luna: And I bet the existing team did not love hearing that. Lucas: They did not. Within two weeks, the operations lead — a ten-year veteran — was coming to the manager saying, 'This guy thinks he knows everything. He does not respect what we have built.' Luna: So the manager is caught between an experienced new hire who might actually have good ideas, and a tenured team member who feels threatened. Lucas: Exactly. And the worst move is to take sides immediately. The manager here — let us call her Priya — did something smart. She scheduled a one-on-one with Mark that was not about correcting him. It was about curiosity. Luna: What do you mean by curiosity? Lucas: She asked him to walk her through one of his suggestions in detail. Not just, 'we should do X,' but, 'Walk me through the implementation — what would it take, what would break, who would need to buy in?' And she listened. She did not defend the current system. She just asked questions. Luna: That is a great technique. Because it forces the new hire to move from abstract criticism to concrete planning. And a lot of times, they realise they do not have all the answers. Lucas: Exactly. In Mark's case, his big idea about the dispatch model actually had merit, but he had not considered that his old company had three times the truck fleet and a different union structure. Priya did not have to tell him that — he figured it out as he talked through it. Luna: And that is way better than the manager saying, 'No, that won't work here.' It lets the new hire save face, and it builds trust. Lucas: Right. And Priya then took it a step further. She said, 'I think there is a piece of this that could work. Let us test it on one route for a month. You lead the pilot, you gather the data, and then we present it together to the operations lead.' Luna: So she turned him from a critic into a collaborator, and gave him ownership. Lucas: That is the framework I want to share today. I call it the Three Lenses for managing the know-it-all new hire. First lens: validate the perspective — actually listen and take notes. Do not dismiss or defend. Second lens: probe the implementation — ask about specifics, trade-offs, timing. Third lens: channel the energy — give them a sandbox to test their idea in a low-risk way. Luna: I love that. And I have a real-world example from a friend who manages a software team. She had a new developer who kept saying their code review process was too slow and that at his last company they did continuous integration and deployed daily. The team had been doing weekly releases for years. Lucas: How did she handle it? Luna: She did something similar. She said, 'Great, I want to hear more. Let us set up a half-hour where you walk me through exactly what your old CI pipeline looked like, and then we can look at what we would need to change here.' And as they talked, she realized the new hire had not accounted for their regulatory compliance checks that take three days. So she said, 'What if we target daily deploys for non-critical services first, and keep the weekly schedule for regulated ones?' He agreed, and six months later they had cut deployment time by 40 percent. Lucas: That is a perfect example of channeling the energy into a workable pilot. And it protects the manager from being seen as either dismissive or weak. You are not saying 'no' — you are saying 'show me.' Luna: But what about the team dynamic? The tenured employees might still feel like the new hire is being given special treatment. Lucas: That is the hardest part. Priya dealt with that by being transparent. She told the operations lead, 'Mark has an idea I want to test on a small scale. I am going to give him a month to run a pilot, and then we will review the results together. If it works, great. If not, we will have data to show why.' She did not go behind anyone's back. Luna: So the manager is essentially using the new hire's own energy to create a low-stakes experiment, and the tenured team gets to see that their expertise is still valued because they are included in the review. Lucas: Exactly. And this is something we talk about a lot on Manager Mondays — the importance of separating the person from the behavior. The new hire is not a bad person for being opinionated. But the behavior of dismissing existing work is problematic. The manager's job is to redirect that behavior into something productive. Luna: It requires a lot of emotional labor though. Especially when you are a first-time manager and you are still figuring out your own authority. Lucas: Absolutely. And that is why having a simple framework helps. You do not have to be perfect — you just have to be curious and structured. One more thing: Priya also set a boundary. She told Mark, 'I love that you have ideas. But in team meetings, I need you to lead with questions, not declarations. Say, 'Have we considered X?' instead of 'We should do X.' That small shift changed how the team received him. Luna: That is such a practical script. I am going to use that. Lucas: A couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo, if you have gotten something out of them. Luna: Yeah, it really makes a difference. And we keep it ad-free because of that. Lucas: Right. So back to Mark — the pilot actually worked. Not exactly as he proposed, but the data showed a 12 percent improvement on that one route. Priya made sure he presented the results to the ops lead, and they jointly decided to roll it out slowly. Mark became the go-to person for process improvements, and the team started coming to him with ideas instead of resenting him. Luna: That is the ideal outcome. But what about the cases where the new hire is just not open to feedback? Where you try the curiosity pivot and they keep doubling down? Lucas: Then you have to escalate. If after a few attempts the person still dismisses the team's experience and refuses to adapt, it is a cultural fit issue. I would document specific instances — 'On three occasions, you said our process is broken without asking why it exists' — and then have a direct conversation about expectations. Some people are just not willing to integrate. Luna: And that is okay. Not every hire works out. But I think most of the time, the know-it-all behavior comes from insecurity or a desire to prove their value, not from malice. Lucas: I think so too. And the manager who can see that and redirect it will unlock enormous value. So the takeaways: one, validate before you correct. Two, probe for specifics. Three, give them a sandbox. And four, set a communication norm for how ideas are shared in group settings. Luna: That is a solid toolkit. I will definitely be using the 'lead with questions' line. Lucas: Let us know how it goes. That is it for this episode of Manager Mondays. Next week we are talking about what to do when your best employee wants to quit — and how to have the stay conversation before it is too late. Luna: Looking forward to that one. Thanks, Lucas. Lucas: Thanks, Luna.