The intro post goes up, same as any new hire. "Please welcome Dana, joining as our new engineering manager." Wave emojis accumulate. Except this time the new person is your boss, and the usual playbook, the breezy DM, the "ask me anything, the dumber the better", suddenly doesn't fit, because the geometry flipped. You're not orienting a peer. You're sending your first writing sample to the person who'll run your reviews, and you can feel that whatever you send is data.
Two facts to hold before typing, because they cut the anxiety down to size. First: incoming managers are more nervous than you are. They've joined a team with existing bonds, inherited someone else's systems, and they know everyone is quietly comparing them to the last boss; a warm early message from a team member is genuine relief to them, not noise. Second: yes, your message is data, and that's fine, because the data you want to transmit is easy to transmit honestly. Warm, secure, useful. That's the whole target.
What that message looks like, inside their first week:
Welcome! I'm Priya, I run the reporting pipeline and the vendor integrations on the team. Really glad you're here. Happy to walk you through how any of my stuff works whenever it's useful, and if you want the honest map of which docs are current versus wishful thinking, I keep one. No rush on any of it, week one is a firehose.
Unpack why each piece is there. The self-intro with your actual territory does something a wave emoji can't: it starts building the map every new manager is desperately assembling, who does what, and puts your name on your ground early, in your own words, before anyone else describes your work for you. The offer is specific and low-pressure, "whenever it's useful" hands them the timing. And the docs line, or whatever your version of it is, offers the thing new managers value most and can't ask for: a little truth about how things really work. One honest, unforced note of insider warmth reads as secure. It says: I'm not auditioning, I live here, welcome to the neighborhood.
Now the holds, because the upward welcome fails more by excess than absence. Hold the pitch. Week one is not the moment for your priorities, your project's case for more headcount, or the thoughtful document about what the team should change; managers notice who arrived selling, and early lobbying reads as exactly what it is. There will be a real venue for all of it, almost certainly a 1:1 they'll schedule, and raising your substance there, when asked, gives it ten times the weight of a DM ambush. Hold the history, harder. When the new boss asks about a process and the true answer involves your old manager's failures, resist the download. "That area's been underloved, happy to walk you through where it stands" gives them the map without handing them a grudge, because here's what the venting version transmits: this person will narrate me to my successor too. And hold the flood: one good message, then let them breathe. Three DMs in week one from the same person is a pattern they notice.
Then, the underrated second act. When they do schedule those first 1:1s and ask their standard question, "what should I know? what's working, what isn't?", that's the invitation the welcome message was patiently waiting for. Come with something real: one thing genuinely working they should protect, one friction worth their attention, framed as terrain rather than complaint. The colleague who's warm in week one and substantively honest in week three, in the right rooms, at the invited moments, is the one new managers learn to rely on. Which was the entire point of the welcome.
The message takes four sentences. The impression takes a season. Send the four sentences, then let the season do its work.