
Tell your manager as soon as you know, before anyone asks. Say what changed, the new date you can stand behind, what it means for the people waiting on you, what you are doing about it, and exactly when you will update them again.
The message you are tempted to postpone
It is Wednesday afternoon. Amara owes her manager, Tomás, a vendor comparison by Friday noon, because he is taking it into a budget meeting at two. Today she learned that two of the four vendors will not send their pricing until Monday. She could still finish something on Friday, and part of her thinks the pricing might arrive early after all.
So she waits one more day. Nothing is wrong yet, and a message saying “this will be late” feels like announcing a failure before it has happened. Many people feel this pull, and it has a cost that does not show until Friday: Tomás has spent two days assuming the document is on track.
Why bad news travels slowly
Researchers who study information-systems projects call this the “mum effect”, a project member’s reluctance to report bad news about a troubled project. A laboratory experiment on it found that whether an outside vendor was responsible for the fault affected willingness to report, both directly and indirectly, and that time urgency affected it only indirectly. The authors suggest that stressing the short window left to fix a problem might raise willingness to report.
An earlier experiment on the same reluctance opens from the observation that “runaway” projects can be made worse by members’ reluctance to pass on negative information. Both studies are experiments about IT projects, so they suggest the pull toward silence is common. They do not measure what happens when you send a particular message to a particular manager.
There is a second reason to speak early. A study of thirteen dispersed teams by Cramton identified unevenly distributed information and difficulty interpreting the meaning of silence among the problems those teams had, and described how partners may misread such failures by explaining them through character rather than circumstances. Applying that to a manager and employee is our inference: a manager who hears nothing cannot tell whether silence means “fine” or “stuck”.
Five things the message needs
The list below is practical guidance, not a research finding. Before writing, work out each of these. If one is missing, the manager will have to come back with a question, and that is the follow-up you were trying to avoid.
- What changed, in one sentence, with the cause stated as a fact rather than a defense.
- The new date, and how firm it is. If it depends on something outside your control, name the dependency instead of hiding it inside a confident date.
- What it affects: the meeting, the person who builds on your work, the decision waiting on it.
- What you are doing now, including anything you can deliver sooner in a smaller form.
- When you will update them next, whether or not anything has changed.
A version that leaves the manager guessing
This message is honest and polite, and it still hands Tomás work. He has to find out which part is late, how late, and whether Friday’s meeting is at risk. The phrase “will do my best” also promises effort rather than a date, so he cannot plan around it.
“Hi Tomás, just a heads up that the vendor comparison is a bit tight this week. A couple of vendors are slow to reply. I’ll do my best to get it done by Friday.”
A version he can act on
This one is longer by only a few lines. It names the cause, offers a usable partial result, gives a date tied to its dependency, and removes the need for him to chase. It also does not apologize repeatedly or explain the history of the delay; the facts do the work.
Notice that the plan includes a fallback he can choose. That keeps the decision with the person who owns the meeting, which is where it belongs.
“Tomás, the vendor comparison will not be complete by Friday noon. Two of the four vendors, Harbor and Linden, say their pricing comes Monday. I can send you the two vendors I have, with their totals side by side, by Thursday at 4pm. For the two o’clock meeting you could present those and say the other two are pending, or move the decision to Tuesday. Tell me which you prefer. I’ll write to you Monday at 10am with whatever has arrived.”
If the reply is not what you hoped
Tomás may be irritated, or he may not answer for several hours. Neither means the message was a mistake. In our judgment, an early warning costs less than a late surprise, but nothing here tests how a particular manager will react.
If he sounds annoyed, acknowledge the cost without retreating from the facts. If he goes silent, do not fill the gap with a new promise. Go back to your own schedule: do the thing you said you would do, and send the update at the time you named.
If he asks why you did not say so yesterday, answer with the truth in one sentence and move to the next step.
“Fair question. I was hoping the pricing would come early, and I should have told you Wednesday when I knew it might not. From now on I’ll flag it the day I see it. For today, the two-vendor draft is on its way at 4.”
What the evidence does not show
The research here shows that reluctance to report bad news is real and can make projects worse. It does not show that any wording makes managers respond kindly, and the experiments used lab scenarios and information-systems projects, not everyday deadlines in every kind of job. Amara, Tomás and the vendors are invented for this example.
This advice also assumes a manager who can hear a problem. If speaking up has led to punishment in your workplace, you may need to put the facts in writing, copy a colleague, or raise the pattern through a formal channel. If the delay is part of a legal, safety or compliance obligation, follow that process instead of a friendly message.
Leetsoul has not been shown to cause better workplace outcomes; the practice linked below only lets you try a similar update in a different scene, so you can hear how the same five parts sound with other facts.
Practice telling your team before they ask
Try your response to a fictional conversation, then read the guidance and decide what you would change.
Open the practiceThree starter practices are free. Soulful opens the full library.Sources and limits
The scene with Amara, Tomás and the vendors is fictional, written for this article. The sources are abstracts of laboratory and team studies about reporting bad news; they show why people delay and what the cost can be, not that this wording will earn a good reaction.
- Overcoming the Mum Effect in IT Project Reporting: Impacts of Fault Responsibility and Time Urgency
Abstract of a controlled laboratory experiment defining the mum effect and reporting effects of fault responsibility and time urgency. Lab setting, IT projects only; it does not test any message wording.
- Keeping Mum as the Project Goes Under: Toward an Explanatory Model
Abstract of an experiment (lab setting not confirmed from the abstract) on reluctance to report negative project news and how it can worsen runaway projects. Shows the pattern exists; it is not evidence about everyday deadlines.
- The Mutual Knowledge Problem and Its Consequences for Dispersed Collaboration
Abstract of a study of thirteen dispersed teams describing uneven information, hard-to-read silence and dispositional blame. Teams were geographically dispersed, so co-located offices may differ.
Published by Leetsoul. Sources checked . Examples are fictional. Read our evidence approach.