You will be able to tell your manager about a problem early, clearly and with a recommended fix.
On Monday, Nadia, a project officer at a government agency, learns that the printer for a public outreach campaign has a machine fault. The brochures due on the 20th will probably be a week late. She tells herself she'll mention it once she knows more. On Wednesday the printer confirms the delay. On Friday her director, chatting with the communications team, hears about it from someone else and asks Nadia why she didn't say anything. The brochures are the smaller problem now.
Most people have held on to bad news like this at some point. It feels sensible to wait until you have the full picture, or until you've fixed it yourself. It almost always makes things worse.
A problem raised early comes with options. On Monday, Nadia's director could have moved the launch date, found a second printer, switched part of the run to digital, or warned the partner organisations. Each day of waiting closed one of those doors. By Friday, the only option left was to explain a late launch.
That is the cost of holding bad news. The problem itself doesn't change, but the number of ways to fix it shrinks every day, and the fixes that remain are usually the expensive ones: rush fees, overtime, a reschedule that other people have to absorb.
Waiting also changes how your manager sees you. A problem raised early makes you look like someone who has the work under control. The same problem raised late makes you look like someone who was hoping nobody would notice, even when that isn't true.
When you raise a problem, three things go in the opening lines: what happened, what effect it has on the deadline, budget or quality, and what you have already done about it.
Before:
"Hi Mr Ong, hope you're well. Just wanted to give you a quick update on the brochures. The printer has had some issues with one of their machines this week and they're working to resolve it. There may be some impact on timing but I'm monitoring closely and will update you if anything changes."
That message is technically honest. It also leaves Mr Ong unsure whether there's a problem at all. "Some issues", "some impact" and "monitoring closely" all soften the news until it's hard to find.
After:
"Hi Mr Ong, the campaign brochures will likely be about a week late, arriving around the 27th instead of the 20th. The printer has a machine fault, which they confirmed this morning. I've asked for a firm date by tomorrow noon and checked which other approved printers could take the job."
This is lesson 1.1 applied to bad news: the point comes first. It doesn't blame the printer or apologise at length, and it doesn't hide the date. Plain language can feel harsh to write, especially to someone senior. It reads as competence to the person receiving it.
A message that only says "there's a problem" hands your manager a task: work out what to do. A message that brings options hands them a choice, which is much easier.
Aim for two or three real options, with what each one costs or risks, and then say which one you recommend and why. Your manager may pick a different one, and that's fine. You've given them a starting point instead of a blank page.
Nadia's message continues:
"Three options. One, keep the printer and move the launch to the 28th, which means telling our partner agencies this week. Two, move the job to a second printer on the approved list, who can deliver by the 22nd at about S$800 extra. Three, launch on the 20th with the digital version and send the printed brochures a week later. I recommend option three: the launch date holds, there's no extra cost, and most of the audience reaches us online. Could you let me know by Thursday which you prefer?"
The S$800 is an example figure. The shape is what matters: options, costs, a recommendation and a date for the decision. That last part is easy to forget. Without it, the decision can sit in your manager's inbox while the options keep closing.
If you truly can't see any option yet, say what you're doing to find them and when you'll come back. "I'm getting quotes from two other printers and will send options by 3pm tomorrow" is still far better than silence.
There's one firm rule underneath all of this: your manager should never hear about a problem in your area from someone else first.
When that happens, the damage isn't really about the problem. It's about trust. Your manager now wonders what else they don't know, and starts checking your work more closely, asking for more updates, or going around you to get information. That's uncomfortable for both of you and takes months to undo.
So when in doubt, tell them early, even if all you can say is "This might become a problem. I'll know more by Wednesday." A heads-up that turns out to be nothing costs you one short message. A surprise costs you far more.
If you were brought up to be careful about bringing problems to someone senior, as many people in Singapore offices were, this can feel uncomfortable. It helps to see the early warning as part of the job you were given, and a good manager will treat it that way.
Look at the work you're carrying now. There is probably one task where the date already feels tight, or where you're waiting on someone who has gone quiet. That task is the starting point for the activity below.
Write a short message raising a real or likely delay in your work, with its effect, two options and your recommendation.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).