The information doesn't change. The way you deliver it does, and getting that wrong is what makes people underestimate you before they've even judged the substance.
Here's the situation almost everyone in a first management job gets wrong at least once: something goes sideways on a project, and you have to tell three different people about it, your manager, an executive above your manager, and a client. The instinct is to write one version and send it to all three. That's the mistake. Each of those people is reading your message with a completely different question in mind, and if you answer the wrong question, you come across as either underprepared or evasive, even when you're neither.
Take a real example: you've just realized a project that was supposed to ship Friday is going to need another week. The facts are the same no matter who you're telling. What changes is what each person needs from you first.
Your manager is closest to the work and usually wants to understand your thinking, not just your conclusion. They're the person who can actually help you solve the problem, so it's worth showing your reasoning, what you looked at, what the real blocker is, and what you're leaning toward. This is the one audience where "thinking out loud" is a feature, not a weakness.
"We originally expected to finish this Friday, but after reviewing what's left, I think we need another week. The main issue is the integration testing turned up more edge cases than we scoped for. I've looked at a couple of options, we could push the date, or we could ship a reduced version Friday and follow up with the rest next week. I'm leaning toward pushing the date since a partial launch creates more support burden than it saves. Wanted your take before I commit to either."
An executive is several steps removed from the day-to-day and is usually reading dozens of updates like yours in a single sitting. They don't want your thinking, they want your conclusion, with the reasoning available if they ask for it. Leading with the recommendation instead of the backstory is the single biggest adjustment first-time managers have to make when they start writing to people above their own boss.
"Recommendation: move the launch to next Friday, September 12. We need the extra week to complete integration testing properly rather than ship with known gaps. This doesn't affect any other team's timeline, and we've already adjusted the internal schedule to absorb it. Happy to walk through the details if useful."
A client's real question is rarely "why," it's "should I be worried." They usually don't need, or want, the internal mechanics of what went wrong. What they need is confidence that it's handled and clarity on what it means for them specifically. Over-explaining the cause here tends to create more doubt, not less, because it invites them to start evaluating your process instead of trusting your outcome.
"We're moving the launch to September 12 to make sure final testing is done properly before this goes live. This won't affect your team's work during the transition, and we've put a plan in place to keep everything else on schedule. I'll send a short update once testing wraps."
Notice what stayed constant across all three: the actual facts, the honesty, and the fact that you're not hiding anything. What changed was the order of information and how much reasoning you showed. Your manager got the story because they can use it. The executive got the answer first because their time is the scarcest thing in the room. The client got confidence and impact because that's the actual question underneath "what happened."
"Does this person want my thinking, my conclusion, or my confidence?" Answer that first, and the rest of the message writes itself.
This same shift applies far beyond project delays, it holds for status updates, budget requests, staffing changes, anything you have to communicate up, down, or across. Before you write the message, ask yourself one question: does this person want my thinking, my conclusion, or my confidence? Answer that first, and the rest of the email writes itself.