How to Adjust to a New Manager in English

A change in management resets a lot of unwritten context — priorities, working styles, and informal agreements you had with your previous manager may not carry over automatically. This guide gives you the English for the first conversation, clarifying expectations, and re-establishing anything important that isn’t written down anywhere.

---

Opening the First Conversation

Set a collaborative tone rather than waiting to be told how things will work.

• “I’d love to understand your working style and what you’ll expect from me and the team going forward.”
• “Before we dive into specifics, I want to get a sense of your priorities for this team over the next few months.”
• “What’s the best way for you to get status updates — do you prefer async writeups, or a quick sync each week?”

Re-establishing Prior Agreements

Some things won’t transfer automatically and need to be raised explicitly.

• “I had agreed with [previous manager] on a hybrid schedule of two days in office — I want to make sure that’s still the understanding going forward.”
• “We’d discussed a path toward a team lead title by the end of this quarter — I wanted to flag that so it’s on your radar too.”
• “There was an informal agreement about compensation for the extra on-call load I’ve been carrying — is that something you’re aware of?”

Clarifying Expectations

Ask directly rather than guessing at what’s now considered important.

• “What does success look like for you in this role over the next quarter?”
• “Are there things my previous manager prioritized that you’d weigh differently?”
• “Is there anything about how the team currently operates that you’re planning to change?”

Flagging Concerns Diplomatically

If a new manager’s early decisions raise concerns, name them constructively.

• “I want to share some context that might not have been visible yet — this decision affects a dependency the team relies on.”
• “I don’t want to assume you have all the history here, so let me walk through why we do it this way currently.”
• “I’m open to changing this, but I think it’s worth understanding why the previous approach was chosen before we move away from it.”

Building the Relationship

Invest in the working relationship directly, not just the logistics.

• “I’d like to have a regular one-on-one so we can stay aligned — does a weekly slot work for you?”
• “Let me know how you prefer to receive feedback, so I can make sure I’m communicating in a way that’s useful to you.”

---

Vocabulary Reference

Term	Meaning
Working style	An individual’s preferred way of communicating, planning, and managing work
Skip-level	A meeting or relationship with a manager’s manager, bypassing the direct manager
Informal agreement	An understanding not documented formally, at risk of being lost in a transition
Onboarding (for managers)	The process of a new manager learning team context and history
Async writeup	A written status update shared without requiring a live meeting

---

Key Takeaways

• Use the first conversation with a new manager to understand their working style and priorities directly.
• Proactively re-raise informal agreements from your previous manager, since they don’t transfer automatically.
• Ask explicitly what success looks like under the new manager rather than assuming continuity.
• Provide context diplomatically when a new manager’s early decisions might be missing important history.
• Invest early in the working relationship, including a recurring one-on-one and clarity on feedback preferences.

Navigating Nuances: Professional English for New Managers

Adjusting to a new manager is a significant shift in any professional environment. It’s more than just learning someone’s name; it’s about understanding their communication style, expectations, and how they prefer to work together. While the core advice – being proactive, asking questions, and demonstrating your commitment – remains universally important, developers who are still honing their English skills can face particular challenges in fully grasping subtle cues and expressing themselves effectively. This is especially true when dealing with feedback, updates, or simply initiating a conversation. Let’s focus on some common scenarios where precise phrasing can make all the difference.

One of the biggest hurdles often isn’t understanding what to say, but how to say it politely and professionally while simultaneously conveying your ideas clearly. Consider a code review comment. Instead of a blunt “This doesn’t work,” which might sound critical and potentially defensive, try something like: “I noticed a potential issue with the logic in this section. Specifically, the conditional statement here seems to be handling edge cases incorrectly. Could we explore adding a test case to cover this scenario?” This phrasing uses softer language (“potential issue,” “seems to be”) and focuses on the problem rather than directly criticizing the developer’s work. Similarly, when describing your pull request, avoid simply stating “Fixed bug.” Instead, frame it as: “Implemented a fix for [Bug ID] which addressed [brief description of the bug] by [brief explanation of the solution]. I’ve included updated tests to ensure this resolves the issue effectively.”

Another area where precision matters is in Slack conversations. A simple “Let me know if you have questions” can be interpreted differently depending on the recipient’s background and experience. A more effective approach would be: “I’ve documented the changes thoroughly in the PR description and added relevant comments within the code. Please don’t hesitate to reach out if anything is unclear or if you’d like a deeper dive into any specific aspect.” This demonstrates transparency, offers support, and invites open dialogue. Remember, demonstrating your English proficiency isn’t about sounding perfect; it’s about conveying your message clearly, respectfully, and with confidence.

Finally, when setting expectations – perhaps clarifying priorities after a handover – it is vital to use language that establishes mutual understanding. Instead of saying “I’ll handle this,” consider “I’m prioritizing the task of [task name] and will keep you updated on progress every [frequency - e.g., day/two days]. To ensure alignment, could we briefly review the key objectives for this project together to confirm our shared understanding?” This proactive approach showcases your commitment to collaboration and emphasizes a desire for clear communication.

---