Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Says I'm Waiting on Feedback
Transcript
- Lucas: So we've all heard this from a team member: 'I'm waiting on feedback from so-and-so before I can move forward.' Sounds perfectly reasonable, right? But when it becomes the default answer week after week, it's often less about genuine dependency and more about a stall tactic. Luna: Oh, I've been there. I had a direct report once who used that line every single status update. At first I thought he was just being thorough, but after a month I realized he was using feedback as a shield to avoid making decisions. Lucas: Exactly. And the thing is, in most organizations, feedback is never truly complete. There's always another stakeholder who could weigh in. So waiting for it can become an infinite loop. Luna: So how do you break that cycle without micromanaging? I think a lot of managers struggle with that line. Lucas: The first step is to define what 'enough feedback' looks like. Give the employee a specific number of reviewers or a hard deadline. For example, 'You need sign-off from your two main stakeholders by Thursday at 5 PM. After that, we proceed with your best judgment.' Luna: Right, that sets a clear boundary. But what if the employee says they can't get the feedback because the stakeholder isn't responding? Lucas: That's where you flip ownership. Instead of the employee passively waiting, they become the driver. They schedule the meeting, they send the reminder, they escalate if needed. You're not the project manager for their feedback. They are. Luna: I like that. So you're basically redefining their role from 'wait-er' to 'chaser.' Lucas: Precisely. And as a manager, you can support them by setting up a feedback timetable at the start of a project. Map out who needs to see what by when, and build in buffer for delays. That way, when someone says they're waiting, you can point to the plan. Luna: What about the employee who genuinely has a slow-moving stakeholder? I've seen cases where the stakeholder just never replies, and the employee is stuck. Lucas: That's a different problem. Then you as a manager need to intervene—either by directly contacting that stakeholder or by giving the employee permission to proceed without that person's input. Sometimes the cure is to lower the bar for feedback. Luna: Lower the bar meaning...? Lucas: Meaning you can say, 'You don't need full approval; you need a simple thumbs up or a quick no.' Or even, 'Just proceed and loop them in after.' The employee is often waiting because they think they need formal sign-off, when in reality a quick email would suffice. Luna: So a lot of it is about clarifying the actual decision rights. I once worked with a product manager who would say 'I'm waiting on engineering feedback' for weeks. Turned out he only needed one engineer's quick review, not the whole team. Lucas: That's a classic. And that's where a premortem can help. At the kickoff, ask the team: 'If this project gets stuck because of feedback delays, what will have caused it?' Then you pre-empt those causes. Luna: Right, you identify the bottleneck before it becomes one. I've seen teams cut decision cycles by 40 percent just by doing that one exercise. Lucas: And that number—40 percent—is real. It comes from a study at a large tech company I read about. The premortem also builds a shared understanding that waiting is a team problem, not just the employee's. Luna: Speaking of team problems, I think this ties into something bigger. We often talk about feedback loops in management, and honestly, having conversations like this is why we love doing this show. If you're getting value from these episodes, we hope you'll consider supporting the podcast on a listener-supported model. It keeps us ad-free and focused on real examples. You can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, that support goes directly into research and prep time. And it means we can keep drilling into these specific, practical scenarios. So thank you to anyone who's contributed already. Now, back to the employee who's stuck in feedback limbo—what about when the pattern persists even after you've set deadlines and flipped ownership? Luna: Then it becomes a performance issue, right? At some point you have to address it directly. Lucas: Exactly. I think managers often avoid that because they don't want to seem harsh. But if the employee continues to use 'waiting on feedback' as a reason for not delivering, you need to have a candid conversation. Say, 'I've noticed you often say you're blocked by feedback. What's really going on?' Luna: And sometimes the answer is fear. Fear of making the wrong decision, fear of criticism. Lucas: Absolutely. So you might need to coach them on decision-making confidence. Give them a framework: 'When you have 70 percent of the information, make the call.' It's that Amazon principle, but it works. Luna: So the employee needs to feel safe to act without complete information. That's on the manager to create that psychological safety. Lucas: Right. And you can model it yourself. Share a time when you made a decision without full feedback and it turned out fine. Show them that waiting for everything is actually riskier because it kills momentum. Luna: What about when the employee is legitimately not getting responses? Should the manager step in proactively? Lucas: I'd say yes, but only after the employee has tried a couple of times. If they've chased and still nothing, then you go to the stakeholder directly and say, 'My team needs your input by end of week. What can you do?' That shows you're supporting your employee, not enabling their dependency. Luna: So it's a balance. You don't want to rescue them every time, but you also don't want them stuck on a legit blocker. Lucas: Exactly. A good rule of thumb is: if the employee has independently tried to get feedback at least twice, and the stakeholder still hasn't responded, then it's time for you to step in. Otherwise, they need to figure it out. Luna: That makes sense. So to summarize: define the feedback threshold, flip ownership to the employee, and use premortems to anticipate delays. If it persists, dig into the real reason. Lucas: And always tie it to the project's timeline. Next time someone says 'I'm waiting on feedback,' you have a toolbox to respond. Thanks, Luna. Luna: Thanks, Lucas. Great conversation.