On this page
Both failures are common and both are usually blamed on the manager's communication skills. Neither is really about that.
Failure one: too general
"Good shift." "That was a bit messy." "You need to be quicker on the well."
None of these can be acted on, because none of them identify a specific behaviour in a specific situation. The recipient agrees, intends to improve, and has no idea what to do differently on Tuesday.
Generality is not laziness. It is what you are left with when you have an impression of a shift rather than a record of it. A manager who worked the same busy service remembers the two things that went visibly wrong and a general sense of how it felt. That is genuinely all they have.
Failure two: too late
Feedback in a monthly review is about a period rather than an event. The recipient cannot recall the specific nights, so the conversation becomes about their general performance, which is exactly the conversation that produces defensiveness.
Worse, delayed feedback is usually delivered in a formal setting, which signals that it is serious. A small correction delivered formally becomes a large event.
The fix for both
Be specific, and be quick. Those are the same requirement, because specificity decays with time.
A workable standard: within two days, about one thing, describing what happened and what would have been better. Thirty seconds, standing up, not in an office.
"The two large rounds at nine went out at different strengths, I tasted them. Worth using the jigger when it is that busy." That is specific, it is close enough that the person remembers the rounds, it is about the drinks, and it takes no longer to say than "watch your pours."
Four things that make it land
Lead with the observation, not the judgement
What you saw, then what it means. Reversing that order puts the person in a defensive position before they know what you are referring to.
Make the standard the subject
The drink drifted. Not you drifted. This is not a euphemism, it is usually more accurate: most drift is caused by conditions rather than by the individual, and starting from the person gets you the wrong diagnosis as well as the wrong reaction.
Say the thing to do next
Feedback without a next action is a complaint. The action should be small enough to start immediately.
Notice when it works
The most skipped step. If somebody changes what they do and nobody mentions it, they learn that only failure is observed. That is the fastest way to make the whole practice feel like criticism.
What this requires operationally
A manager needs to know, within a couple of days, what actually happened on a shift at the level of specific products, timings and sections. Not to catch anyone, but because that is the raw material of a specific observation.
Without it you are working from impression, and impression produces general feedback, which is the first failure mode. The communication advice above is worth very little if the information underneath it is not there.
That is the practical connection between shift level visibility and how a team is managed, and it is why CoreTAP makes the shift legible within days rather than at month end.