The late work on your desk isn't a discipline problem. It's what your last piece of feedback left behind.

You gave someone feedback on a proposal on Tuesday. It was specific, it was fair, and you meant it to help. It is now Friday and the revision has not moved. You are deciding whether this is a person problem or a priorities problem, and you are leaning toward person.

A paper in Leadership & Organization Development Journal, dated 8 October 2026 in Crossref's record, gives you a third option: the feedback itself may be what decides whether the work gets started. The authors are Fanchao Zhuo (College of Economics and Management, Hunan University of Arts and Science), Chengcheng Cao (Business School, Hunan University), Yongping Li (College of Economics and Management, Hunan University of Arts and Science) and Ling Yuan (Business School, Hunan University). The title is "How developmental feedback from supervisors affects employees’ procrastination behavior."

How far I got. The journal serves only the abstract, so everything below comes from the published abstract and the author metadata. I did not read the full paper, its measures or its tables.

What they did. According to the abstract, they collected data from 311 full-time employees in a two-wave survey with a two-week interval, and analyzed it with hierarchical regression and bootstrapping. This is a survey, not an experiment. Nobody was randomly assigned to good or bad feedback.

What they found. Supervisor developmental feedback was negatively related to work procrastination. Two mechanisms carried that relationship: affective rumination and problem-solving pondering. A third variable, future time perspective, mattered in one place and not in another. It strengthened the link between feedback and problem-solving pondering, and the indirect effect of feedback on procrastination through problem-solving pondering. It did not significantly moderate the link to affective rumination. That is two mediators, one moderator, and one moderation test that came up empty. The abstract frames the mechanism this way:

Affective rumination and problem-solving pondering mediated this relationship, indicating that developmental feedback reduced procrastination by decreasing maladaptive emotional carryover and increasing constructive cognitive processing.Abstract, as published by the journal and carried in Crossref metadata

Read that plainly. On the account the authors give, the feedback works through what the employee does with their mind after you leave the room: either they keep replaying how it felt, or they start working the problem.

The limits, which are mine. The abstract does not say who rated procrastination, so I cannot tell you whether it was the employees themselves or someone else. A two-week gap between waves is better than one snapshot, but a survey cannot settle direction. People who put things off may also draw different feedback from their supervisors. The abstract uses causal language ("reduced"); I would hold that more loosely than the authors' wording does. I also cannot tell from the abstract where the 311 people work, which industries, or how large their companies are, so I cannot say it describes a firm like yours. Those cautions are mine, not the authors'.

Why this lands differently for the person at the top. Your feedback carries more weight than anyone else's in the building, because you also control the money, the role and the next assignment. The research is about supervisors generally, and it does not test leaders in your position. But it is reasonable to ask whether the emotional residue of a comment from you lasts longer than the same comment from a peer. You also rarely see what comes after. Nobody tells the person at the top, "your note sent me into a three-day loop." They go quiet, and the work slips. From where you sit, that looks like slow output, not a reaction to your own words.

The part the research doesn't say, but that I'll say plainly: the study measures feedback that is developmental. I would guess that how you frame it matters as much as what is in it, and that feedback aimed at the next version, with a clear first step, gives the mind a problem to work on instead of a verdict to replay. That is my inference. The abstract does not test framing, wording or delivery, and I would not attribute it to the authors.

One thing to do this week. Pick one person whose work has stalled after you gave them feedback. Do not ask why it is late. Ask one question: "What is the first thing you'd change, and what do you need from me to start?" Then see whether the delay was about the work at all. If you cannot name the first step yourself, the feedback may have been a judgment and not a direction, and that is worth knowing about your own habits.

If you want to see how you give and receive hard feedback before you guess, the Leadership Profile maps it for the person at the top. Start at the wiring map.