Devon is one of the strongest analysts on the team - two years of consistently sharp, well-caveated work. The last three deliverables have needed significant rework: numbers that didn't reconcile, a recommendation section that ignored a constraint the team had already flagged, a deck that went out with the wrong client name still in the header. Nothing catastrophic on its own. As a pattern, it's real, and it's starting to cost other people's time.
MBA Lab is independent and is not affiliated with, endorsed by, or an official representative of Virginia Commonwealth University. This scenario is an original MBA Lab analysis, not an official VCU case or case solution - see the FAQ below.
The conventional response
Wait for the scheduled quarterly review. Compile the list of issues. Present it as a single conversation: here's everything that's gone wrong, here's why it matters, here's the corrective plan going forward. The logic is efficiency - batch it, be thorough, move on.
The problem is timing and framing. By the time three months of accumulated small failures land in one sitting, they read less like specific, fixable issues and more like an indictment. Devon has also had no chance to course-correct in between - the first the pattern surfaces to them is at the same moment consequences are being discussed.
The poorly executed people-first response
Raise it, but soften everything on the way there. Frame each issue as a one-off ("things have just been busy lately"), emphasize that everyone knows Devon is talented, and - to avoid an uncomfortable moment - quietly start double-checking Devon's work before it goes out rather than naming the pattern directly.
This version feels kind in the room and fails Devon anyway. The standard stays implicit, so there's nothing concrete to actually fix. And the quiet double-checking is its own message, just an unspoken one: the team no longer fully trusts the work, without ever saying so.
A response that holds both the standard and the person
Prepare first. Before the conversation, get specific: which three deliverables, what exactly went wrong in each, and what the real cost was (rework hours, a client-facing near-miss). Notice your own frustration and set it aside rather than walking in to vent it.
Name the pattern, plainly. "The last three deliverables have each needed significant rework before they could go out - the reconciliation error, the constraint we'd already flagged, the client name in the header." Not "you've been sloppy lately."
Ask, and actually listen. "What's going on?" Recruiting season, a family situation, an unclear handoff from someone else, quiet burnout, or simple disengagement all produce the identical symptom from the outside. The answer changes what happens next more than anything else in this conversation.
Diagnose past the individual. Is this capability (a skill gap that wasn't there two years ago), capacity (too much on their plate), clarity (expectations that shifted without being restated), or motivation? Each has a different fix, and only one of them is really about effort.
Agree on something specific and checkable. Not "be more careful" - something like "final numbers get a second self-check against the source model before they go out, and we'll look at the next two deliverables together to see if the pattern breaks."
Set a real review point. A date to check back in, not an open-ended "let's see how it goes."
Keep recognizing the person's actual value while doing all of this. None of the above requires pretending Devon isn't good at the job - it requires not letting "Devon is good at the job" be a reason to skip the conversation.
How mindfulness shapes this
The main risk in this exact scenario is that a manager's disappointment - precisely because Devon is usually strong - curdles into a character judgment ("I guess they're just not as reliable as I thought") rather than staying a specific, addressable pattern. A pause before the conversation, and a real check of the evidence instead of the accumulated feeling, is what keeps it from turning into a prosecution.
How care shapes this
Care here means protecting Devon's dignity throughout - raising the pattern privately, listening for what's actually happening before assuming the worst, and offering real, proportionate support if the cause turns out to be capacity or circumstance. It does not mean deciding on Devon's behalf that the standard doesn't apply this quarter.
How accountability shapes this
Accountability means the standard, the evidence, the timeline, and who owns what next are all made explicit - not implied, not left for Devon to infer from a manager's slightly cooler tone in the following weeks.
Risks and tradeoffs
Too much process around a single pattern can itself delay a decision that needs to happen faster. Offering Devon support that another team member in a similar spot didn't get can look like favoritism, even with good reasons behind it - which is worth naming out loud rather than hoping no one notices. And it's possible, even with real effort on both sides, that the underlying issue is a genuine mismatch between the role and where Devon actually wants to be - in which case a caring, well-run conversation is still the right process, even if it doesn't end in the outcome either person hoped for.
For the full step-by-step version of this conversation structure, see how to hold someone accountable without humiliating them.