How to write to your manager
Writing to your manager is the professional communication skill that most directly affects your career, and it's the one least explicitly taught. The core challenge is asymmetry: your manager is reading dozens of messages a day from multiple reports, peers, and their own leadership. Your email is one of many. This means that every message you send needs to earn its attention, deliver its point quickly, and make it easy for your manager to respond or act.
The most useful framework for writing to a manager is: conclusion first, context second, detail last. If you need a decision, put it in the first sentence: "I'd like to push the launch to the 22nd — here's why." If you're giving an update, lead with the headline: "Project X is on track for Friday delivery." If you're raising a problem, state the problem and your proposed solution before diving into the background. Managers don't want to read three paragraphs of setup before discovering what you need from them. They want to know the ask, then decide how much detail they need.
Knowing when to email versus when to message versus when to walk over (or call) is an underrated skill. Use email for anything that needs a paper trail: decisions, approvals, timelines, commitments. Use instant messaging for quick questions that don't need to be archived: "Is the 2pm still happening?" or "Should I include the appendix?" Walk over or call when the topic is sensitive, ambiguous, or likely to require back-and-forth. An email about a teammate conflict, for example, is almost always a mistake — that conversation needs tone of voice and real-time feedback.
Pushing back on your manager is necessary and possible, but it requires framing. Never say "I can't do that" — say "here's what that would require." If your manager asks you to deliver a project in two weeks that you believe needs four, the response is: "I can hit two weeks if we cut the testing phase and skip stakeholder review. If we keep those in, four weeks is more realistic. Which version would you prefer?" This gives them the decision while making the trade-offs visible. You're not refusing — you're informing.
When your manager gives you feedback, your written response matters. "Thanks for the feedback — I'll incorporate that into the next version" is almost always the right reply, even if you disagree. Save the disagreement for a live conversation if it's significant. Written pushback on feedback reads as defensiveness, even when it's thoughtful.
Status updates should be boring. That's a compliment. A status update that says "on track, no blockers, next milestone is Thursday" tells your manager everything they need to know and lets them move on. If you do have a blocker, name it and name what you need: "Blocked on the API spec from engineering — I've followed up with Priya and expect it by tomorrow. If it's later, the Thursday milestone slips to Monday."
One pattern that separates strong communicators from everyone else: telling your manager things before they ask. If you know a deadline is at risk, flag it early. If a client gave difficult feedback, share it. If you made a mistake, own it before it surfaces. Managers hate surprises far more than they hate problems. A problem delivered early is manageable. A problem discovered late feels like it was hidden, even when it wasn't.
Finally, match your manager's communication style. If they write in bullet points, use bullet points. If they send one-line replies, don't write essays. If they use formal language, hold the emojis. This isn't about being inauthentic — it's about reducing friction. When your message looks and feels like communication your manager is used to processing, it gets processed faster.