Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Says I Can Figure It Out
Transcript
- Lucas: Have you ever managed someone who, every time you assign a task, says 'I can figure it out' and then disappears into their own world? Luna: Yeah, I have. And sometimes it works great. Other times it's a disaster. Lucas: Right. That's the nuance we're after today. Because on the surface, 'I can figure it out' sounds like confidence, self-reliance, all the traits we say we want. But in practice, it can create serious problems. Luna: Let me guess — knowledge silos, missed deadlines, and a team that feels like they're working around one person instead of with them. Lucas: Exactly. I want to anchor this in a specific case. A friend of mine manages a team of backend engineers at a mid-size SaaS company — about forty million in revenue, maybe two hundred employees. One of his senior engineers, let's call her Priya, was the team's star. She could ship code faster than anyone. And her default answer to any new assignment was 'I've got this, I'll figure it out.' Luna: Which sounds great until it doesn't work. Lucas: Right. The problem was that Priya never asked for help, never updated her status, and never documented anything. When she hit a wall — and she did, about once a month — she'd bang her head against it for two days before saying anything. By then, the sprint was blown. Luna: And the rest of the team had no idea what she was doing, so they couldn't help even if they wanted to. Lucas: Exactly. Her independence became a bottleneck. And my friend, the manager, was afraid to push back because Priya was so good. He didn't want to micromanage her or kill her motivation. Luna: So how did he handle it? Because I think a lot of managers listening have been in that exact spot. Lucas: He did three things, and I think they're really replicable. First, he shifted his own mindset from problem-solver to coach. Instead of saying 'let me know if you need anything,' he started scheduling regular, brief check-ins — fifteen minutes, twice a week — with a specific agenda: 'What's one thing you're stuck on, even a little bit?' Luna: That's smart because it normalizes asking for help. It's not an emergency meeting when you're drowning. It's just part of the rhythm. Lucas: Exactly. Second, he made 'asking for help' a visible part of performance expectations. He told Priya that part of being a senior engineer was mentoring others and sharing knowledge. He said, 'Your code is excellent, but your impact is capped because only you understand it. I need you to write docs, pair program with juniors, and flag blockers within two hours.' Luna: That's a harder conversation. Did Priya push back? Lucas: Initially, yes. She said 'I don't need hand-holding, my work speaks for itself.' And my friend said, 'I agree, your work is great. But team performance is what I'm measured on, and your current approach creates risk. I'm not asking you to change your style overnight. I'm asking you to try a new process for two sprints, and we'll look at the data together.' Luna: Data — that's key. Concrete outcomes. So what happened? Lucas: After two sprints, Priya's personal output stayed the same, but the team's throughput went up by about twenty percent. And she admitted that having juniors take over some of her smaller tasks freed her up for the harder problems. She became a force multiplier instead of a solo contributor. Luna: That's the dream outcome. But I bet not every manager gets that result. What if the employee still resists? Lucas: That's the third move: have a direct conversation about trust. If someone says 'I can figure it out' and consistently delivers, but the process hurts the team, it's often a sign that they don't trust others to do the work well. Or they're perfectionist. Or they've been burned before by teammates who dropped the ball. Luna: So you have to get at the root cause. Are they protecting themselves from bad outcomes, or do they genuinely believe they're faster alone? Lucas: Right. The manager's job is to say, 'I trust you. But I also need you to trust the team.' You can offer to pair them with someone they respect, or let them set the terms for collaboration. But the expectation is non-negotiable: you cannot be a black box. Luna: I've seen this dynamic with really junior employees too. A new hire who wants to prove themselves and says 'I'll figure it out' because they're afraid looking incompetent. Lucas: That's a slightly different problem. With junior staff, 'I'll figure it out' often means 'I don't know how to ask for help' or 'I think I should know this already.' The fix there is more structure: clear milestones, daily stand-ups, and a mentor who explicitly asks what they're stuck on. Luna: And you normalize not knowing. You say out loud 'I don't know, let's look it up together.' Lucas: Exactly. The senior version and the junior version require different responses, but the principle is the same: autonomy without accountability is isolation. And isolation kills team performance. Luna: I want to go back to Priya for a second. Did she ever admit that she had been holding the team back? Lucas: She did, actually. After about three months, she told my friend, 'I didn't realize how much time I was wasting on things someone else could do. I thought I was being efficient. I was actually being stubborn.' Luna: That's a huge realization. And it shows that the conversation wasn't about criticizing her — it was about unlocking her potential as a leader. Lucas: Exactly. And that's the frame I'd offer any manager listening. Your goal isn't to break someone's independence. It's to channel it so it doesn't become a liability. Luna: Speaking of unlocking potential — if this episode helped you think about a team member differently, or gave you a specific script for a conversation, that's exactly why we make these episodes. And if it was worth a coffee to you, you can buy us one at buy me a coffee dot com slash fexingo. That kind of listener support is what keeps the show ad-free and focused on real management stories. Lucas: Yeah, we really appreciate that. And we mean it — no pressure, just if it's useful. Now, back to Priya's story. One thing I didn't mention is how my friend handled the first check-in where Priya said she wasn't stuck. Luna: Ooh, that's a common obstacle. The employee says 'I'm fine, nothing to report.' Lucas: Right. So my friend had prepared for that. He said, 'Okay, then walk me through what you worked on yesterday for ten minutes. I want to understand your approach.' And within five minutes, Priya mentioned a design decision she was unsure about. She hadn't even realized it was a blocker until she said it out loud. Luna: So the structure of the conversation forced the reflection. Lucas: Exactly. That's a technique called 'talk-throughs' — you ask the person to narrate their thought process. It works because it's not interrogating, it's collaborative. And it surfaces ambiguities the person didn't know they had. Luna: I love that. I'm going to try it with one of my reports who has a similar tendency. Lucas: Let us know how it goes. I think the takeaway for today is this: the employee who says 'I can figure it out' is often your most talented person. But your job as a manager is to make sure their talent scales. And scaling requires connection. Luna: Connection over independence. That's a good mantra. Lucas: Yeah. And next episode, we'll look at the flip side — the employee who can't figure anything out without asking you first. Luna: That's going to be a good one. See you next Monday.