Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Always Says I Cant
Transcript
- Lucas: You ask someone to take on a new task — could be a stretch project, could be something routine — and before you finish your sentence, they say 'I can't.' It's a reflex. And if you manage a team, you've heard it more than once. Luna: Yeah, and it's one of those responses that's hard to push back on without sounding like you don't respect their workload. Lucas: Exactly. So let's talk about what's actually behind that 'I can't.' There was a study in the Journal of Applied Psychology last year — 2024 — that looked at why employees reject new tasks. They found that 67 percent of the time, it wasn't about capacity. It was about fear of failure. Luna: Interesting. So the default 'I can't' is often 'I'm afraid I'll mess this up.' Lucas: Right. And when you hear it that way, your response changes. You stop arguing about their calendar and start addressing the anxiety. There's a technique I've seen work well — it's sometimes called the 'micro-yes.' Luna: Micro-yes. What does that look like in practice? Lucas: Instead of asking for a big commitment upfront, you ask for a tiny one. Something they can't say no to without feeling unreasonable. For example: 'Would you be willing to spend 15 minutes tomorrow looking at the data and just telling me what you notice?' That's a micro-yes. It's a small, low-risk ask. Luna: And psychologically, once they say yes to the small thing, they're more likely to say yes to the bigger thing later. Lucas: Exactly. It's the commitment consistency principle. But there's another layer. Some 'I can't' responses are actually learned helplessness — the employee has been shot down so many times or has had ideas ignored, so they've stopped trying. In that case, the micro-yes is also about rebuilding their sense of agency. Luna: So how do you distinguish between genuine overload and learned helplessness? Lucas: Good question. One signal is whether they say 'I can't' to everything or only to new things. If they're consistently delivering on existing responsibilities, it's probably not capacity. If they say 'I can't' even to small, low-effort asks, that's more likely a pattern of avoidance. Luna: And if it's genuine overload, you should respect that. But if it's fear, the micro-yes is a good first step. Lucas: Right. Let me give you a concrete example. I worked with a manager at a mid-sized software company — about 200 employees. She had a senior developer, very competent, but every time she proposed a new feature or a new approach, he'd say 'I can't, I don't have the bandwidth.' She started using the micro-yes: 'Can you just look at the requirements doc and flag any major blockers? That's it.' He agreed. Luna: And then what happened? Lucas: Within a week, he'd sent her three thoughtful comments on the doc. Two weeks later, he was leading the implementation. Over three months, his ownership of new projects went up 40 percent. The blocker wasn't time — it was the fear of committing to something he might fail at. Luna: That's a pretty dramatic shift. But I wonder — what if the employee still says no to the micro-yes? Lucas: Then you have a different problem. At that point, you need to have a direct conversation. Something like: 'I've noticed you often say no before you've had a chance to consider something. Can we talk about what's driving that?' And then you listen. It might be that they feel undervalued, or they've had a bad experience with a past project. Luna: So the goal is to understand the root cause, not just to get a yes. Lucas: Exactly. And sometimes the root cause is that the employee doesn't trust the process. If previous projects were poorly scoped or constantly changed, they've learned that saying yes leads to chaos. In that case, your job is to rebuild trust by delivering on your promises — clear scope, no scope creep, support when they need it. Luna: That's a long-term fix. But in the moment, when you're in a 1-1 and you hear 'I can't,' what's a good script? Lucas: I like: 'I hear you. Can I ask — what specifically feels impossible about this?' That opens the door to a real conversation. They might say 'I don't know the technology' or 'I've never done this before.' Then you can address the actual barrier. Luna: And if they say 'I just don't have time'? Lucas: Then you ask: 'What would need to change for you to have time?' Maybe they can deprioritize something else. Or maybe you realize you need to reassign their workload. But the key is that you're not accepting 'I can't' as a final answer — you're treating it as a starting point. Luna: I think a lot of first-time managers hear 'I can't' and immediately jump to problem-solving mode. They say 'Okay, I'll help you' or 'Let me do it.' And that reinforces the behavior. Lucas: That's a huge trap. If you solve the problem for them, they learn that saying 'I can't' gets them out of work. You want to be supportive, but you also want to build their capability. The micro-yes is a way to be supportive without taking over. Luna: So the manager's role is more like a coach than a fixer. Lucas: Exactly. And this ties into something we talk about a lot on this show — the shift from doing the work to enabling the work. It's hard, especially when you're used to being the doer. Luna: You know, speaking of enabling — this show is entirely ad-free, and that's deliberate. We don't want sponsors dictating what we cover. If you find these conversations useful, supporting us at buy me a coffee dot com slash fexingo helps keep it that way. Lucas: Yeah, it's a small gesture that makes a big difference for us. And we appreciate everyone who's done that. Luna: Alright, back to the 'I can't' challenge. One more thing I've seen — sometimes the employee says 'I can't' because they're a perfectionist. They don't want to deliver something that's not perfect. Lucas: That's a great point. In that case, the micro-yes can be framed around a draft or a prototype. 'Can you just put together a rough version? It doesn't have to be polished.' That lowers the bar and makes it feel safe. Luna: And once they see that a rough version is acceptable, they're more willing to iterate. Lucas: Right. The key is to create a culture where 'good enough for now' is valued. That takes time, but it starts with one conversation. Luna: So to wrap up — the next time you hear 'I can't,' don't take it at face value. Ask what's behind it, use a micro-yes to lower the stakes, and address the root cause. Lucas: And remember, if it's genuine overload, respect it. But if it's fear or learned helplessness, your job is to coach them through it. That's what good management looks like. Luna: Thanks for listening, and we'll see you next week on Manager Mondays.