Fictional teaching case. During a team meeting, a manager tells an analyst, “You are careless and never pay attention to details.” The analyst becomes quiet and later argues that the manager ignores a recurring system problem. Other employees avoid asking questions because they fear being criticized in public.
The core idea
The manager intended to improve report accuracy, but the feedback focused on a character judgment rather than observable work. The issue also had a hidden system element: the report source was often updated after the submission deadline.
How to apply it
- Move the discussion to an appropriate private setting.
- Identify specific observed events: which report, date and error are in question?
- Explain the impact on the decision or customer, rather than attaching a negative label to the person.
- Listen for constraints and corroborate any system issue independently.
- Agree on a correction, a prevention step, the relevant support and a review date.
A workplace example
The manager says, “In Tuesday’s report, two totals differed from the source file. The leadership team used those figures in its briefing. Can we review what happened?” The analyst demonstrates the late data refresh. They agree on a verification checkpoint and an adjusted cutoff. The manager still expects accuracy, but now addresses both behavior and process.
What to watch out for
Public recognition and public accountability are not opposites, but corrective feedback involving individual performance often needs appropriate privacy. Feedback should be fair and evidence-based. Formal disciplinary procedures, where required, are separate from an informal coaching exchange.
Practice and reflect
Write a better opening sentence for a feedback conversation you have been postponing.