Managing Up and Getting Visible: Making Sure the Work, and the Judgment Behind It, Actually Gets Seen

DAY 4 | Managing Up When the News Is Bad - Staying visible and trusted even when what you have to report is a delay, a miss, or a mistake

The habit that has built more trust with every manager I have had than any good news update ever did is not how I report progress. It is how I report the weeks that did not go well. Most people default to one of two instincts when the news is bad. Bury it inside a longer update, hoping it slides past without becoming the headline. Or delay flagging it at all, hoping the situation resolves itself before anyone needs to know. Both instincts come from the same underlying fear, that bad news reflects badly on you specifically rather than on the situation. In practice, the opposite is usually true, if the news is delivered well.

Reusing SAID for your own manager

The SAID structure from the Difficult Stakeholders series, State, Acknowledge, Impact, Decide, works exactly as well pointed at your own manager as it does pointed at a difficult stakeholder, because the underlying problem is identical: someone needs a fact they do not have yet, delivered in a way that respects what it costs them and ends with a plan rather than just a disclosure.

• State the fact plainly, in the first sentence, with no lengthy preamble building up to it.

• Acknowledge what this costs your manager specifically, whether that is a commitment they made upward, a resourcing headache, or simply their own time now spent managing a surprise.

• Explain the impact if nothing changes, so the message has a clear reason to exist beyond just delivering discomfort.

• Decide by proposing the next concrete step, and explicitly invite their input on it, rather than leaving the message to end on the bad news alone.

A worked example: a delay that is not your fault

REPORTING A DELAY CAUSED UPSTREAM

You (State):

I need to flag that we're going to miss the Friday requirements sign-off. The finance stakeholder group hasn't reviewed the draft I sent ten days ago, and I don't have a firm date from them yet.

You (Acknowledge):

I know this affects the development start date you've already committed upward, and I wanted you to have this now rather than find out closer to Friday.

You (Impact):

If we don't have sign-off by early next week, development slips by roughly the same amount, since there's no other work that can absorb the gap.

You (Decide):

I'm planning to escalate directly to the finance lead tomorrow if I haven't heard back by end of day. Would it help if you sent a short note in parallel, or would you rather I handle it directly first?

Notice the message does not apologise for something that is not the analyst's fault, and it does not quietly absorb the blame either. It states the fact, names the real cost, and hands the manager a plan with a genuine choice in it. That combination is what makes bad news land as competence rather than as a problem to manage.

The harder version: when the mistake is actually yours

This is the conversation most people avoid the longest, and it is worth having a plan for before it happens rather than improvising it under stress. The instinct to soften or bury a genuine mistake is strongest exactly when it is most important not to give in to it.

REPORTING YOUR OWN MISTAKE

You (State):

I made a mistake in the requirements document, I missed a dependency on the payments API, and it wasn't caught until QA flagged it this week.

You (Acknowledge):

I know this is going to cost the team real rework time, and I take responsibility for missing it during review.

You (Impact):

Best estimate right now is about three days of additional work to fix, which pushes our buffer close to zero for the release.

You (Decide):

I've already started the corrected spec and can have it ready by tomorrow. I'd also like to walk through what I missed with you afterward so I can add a check for this kind of dependency going forward. Does that plan work, or would you want to handle it differently?

The instinct to disappear into embarrassment after a real mistake is natural, and it is also exactly the wrong move. A manager who hears about a mistake directly from the person responsible, with ownership taken cleanly and a fix already in motion, almost always comes away trusting that person more, not less. What damages trust permanently is not the mistake itself, it is finding out about it from someone else, or watching someone spend more energy managing the appearance of the mistake than actually fixing it.

Anyone can look competent when things are going well. The moments that actually decide whether a manager trusts you with bigger responsibility are the ones where something has gone wrong and you are the one telling them about it. Handle enough of those moments with the SAID structure, consistently, and the weekly habit and the four flagged moments from earlier this week compound into something much larger: a manager who has genuinely never been surprised by you in a way that damaged their trust.

The timing decision that matters as much as the structure

SAID handles how you deliver bad news well. It does not, on its own, answer the separate question of when, and that question causes almost as much damage when it is answered wrong. The instinct to wait until a situation is fully resolved before saying anything feels responsible, since it avoids raising an alarm prematurely, but it usually costs more than it protects, because the delay itself becomes part of what your manager eventually has to process and forgive.

A useful rule of thumb: flag it the moment you are reasonably confident it is real, even before you have a full plan, rather than waiting until the plan is polished. The worked examples above both include a Decide step that is honest about not having everything figured out yet. That is deliberate. A manager would almost always rather hear about a problem early with an incomplete plan attached than hear about the same problem later with a complete one, because early warning gives them options that a late one has already closed off.

Go out and be successful.

Oluwatosin Ogunkoya | Flotog BA Insights  |  www.flotogbainsights.com

TOMORROW

Internal Visibility and External Visibility Are the Same Muscle - Closing the series with how managing up inside your organisation reinforces the brand work outside it.