Assuming Your Supervisor Knows Your Work Style
A new supervisor walks in without the context of your past wins, your preferred pace, or the unwritten rules of your role. Expecting them to instantly understand how you operate is a common source of early friction. They are not mind readers, and assuming otherwise can lead to mismatched expectations and missed opportunities.
Instead of waiting to be asked, take the initiative to explain how you work best. This is not about making demands; it is about providing useful information that helps your supervisor manage you more effectively.
- Schedule a brief one-on-one early. Use the time to discuss your communication preferences—whether you prefer quick chat messages, scheduled check-ins, or detailed email updates.
- Describe how you contribute best. Be honest about whether you thrive on independent deep work, collaborative brainstorming, or structured deadlines.
- Clarify your current projects. Offer a simple, bulleted overview of what you are working on, including any immediate priorities and any tasks that are waiting on input from others.
- Ask about their expectations. Frame the conversation as a two-way exchange. Inquire about how they like to receive progress updates and what they consider a successful first month.
Keep this first conversation concise and focused on alignment, not on a full history of your work. Sharing a clear, practical snapshot of your workflow and preferences builds a solid foundation for trust. It shows your supervisor that you are invested in working well together and that you respect their time and perspective.
Overpromising and Underdelivering
When you’re new to a team, it’s natural to want to prove yourself. That often leads to agreeing to every request or committing to deadlines that look impressive on paper but are unrealistic in practice. You might think you’re showing dedication. In reality, you’re setting yourself up to break a promise, and a missed deadline or rushed deliverable will do more damage to your credibility than a firm, honest answer would have.
The core mistake is saying yes to everything without first checking your actual capacity. You may also be guessing at how long tasks will take before you’ve had a chance to learn the tools, the team’s workflow, or the expectations for quality. When you give a vague or overly optimistic timeline, your supervisor will plan around it. When you miss it, they’re not just disappointed in the schedule—they begin to doubt your judgment.
Instead of trying to sound capable, be transparent about your trade-offs. When asked for a timeline, propose one you can meet and briefly explain what you’ll prioritize to hit it. For example:
- If a task is new to you, build in extra time for research and revision.
- If you have competing deadlines, say which one you’ll complete first and why.
- If you need input from a colleague, note that dependency in your estimate.
If you do foresee a delay, communicate it early—before the deadline becomes critical. Offer a revised plan or an alternative solution, such as handing in a partial version on time. Your supervisor will trust you more for flagging a problem than for staying quiet and missing the mark. Over time, consistent, honest delivery will make your word count for far more than any impressive-sounding promise.
Hiding Mistakes or Delays
Nobody enjoys delivering bad news, but hiding a problem is one of the fastest ways to lose a new supervisor’s trust. When you delay telling them about an error, a missed deadline, or a looming issue, you remove their ability to act early. Supervisors need accurate information to make sound decisions, and they rely on team members to surface risks before they become crises.
The common mistake is waiting until a problem has escalated to the point where it’s unavoidable. Another version is briefly mentioning an error without context, which can make it seem careless or intentional. Both approaches put your supervisor in a reactive position and force them to question what else might be unreported.
Instead, surface issues promptly. When you bring up a problem, include three things:
- A clear statement of what went wrong or what is delayed.
- The current impact on the work or timeline.
- A proposed next step or a request for guidance.
Frame the conversation as risk management, not a confession. You are giving your supervisor the information they need to protect the team’s results. That is a valuable contribution, not a personal failing. Most supervisors would rather hear about a small issue early than discover a large one later.
Transparency also builds your credibility over time. When you consistently share accurate updates, your supervisor learns that your word holds weight. That reputation matters more than temporary discomfort. Show that you prioritize the team’s success over your own convenience, and trust will follow.
Skipping Regular Check-Ins
Some employees assume that consistently good work speaks for itself and that frequent communication is unnecessary. That approach can backfire with a new supervisor. Without regular updates, your supervisor lacks visibility into your progress, roadblocks, and workload. Silence can be misinterpreted as stagnation, confusion, or disengagement—even when your output is strong.
The mistake is going quiet for long stretches while you focus on delivering results. Your supervisor may not know what you are working on, when to expect completion, or where you might need support. This ambiguity creates avoidable friction during the early stages of the relationship.
Instead, establish a reliable cadence of brief status updates. The frequency should match the complexity of your work:
- Daily check-ins work well for fast-moving projects, tight deadlines, or tasks with many dependencies.
- Weekly updates suit ongoing responsibilities with clear milestones and less urgency.
- As-needed syncs are useful for independent work, but only if you still provide scheduled summaries.
Use these check-ins to highlight three things: what you completed, any blockers you face, and what you plan to tackle next. Keep updates concise and action-oriented. This habit prevents surprises and gives your supervisor reliable material for their own reporting. Over time, consistent communication builds a rhythm of trust that makes formal reviews easier and reduces the need for last-minute clarifications.
If you are unsure what cadence your supervisor prefers, ask directly during your first one-on-one. Most supervisors appreciate the question and will offer a clear preference. Once you settle on a rhythm, stick to it—even when things are quiet.
Relying Solely on Formal Communication
Emails and scheduled meetings are necessary for clarity and documentation, but they are not enough to build real trust. When every exchange stays strictly professional—no greeting beyond the subject line, no pause for context—you create distance. Your supervisor may read you as guarded or disengaged, which makes collaboration feel transactional.
The mistake is assuming that professionalism means avoiding casual conversation. In practice, trust often forms in the small, informal moments between formal tasks. A quick check-in about their weekend, a comment about a shared deadline pressure, or a genuine question about their perspective on a project can do more for rapport than a perfectly formatted status report.
Instead of keeping everything on a formal track, work in light, appropriate small talk. You do not need to become close friends, but you do need to signal that you see them as a person, not just a title. Pay attention to what they prioritize and how they prefer to receive information—some managers want detail upfront, others want the bottom line first. Adjusting your style shows respect for their working rhythm.
This human connection pays off most when pressure rises. If you have already built a comfortable rapport, asking a clarifying question or flagging a concern feels natural rather than risky. Without that foundation, even routine feedback can feel tense.
- Open a few conversations with a brief, work-appropriate personal question.
- Notice their communication patterns and mirror their level of detail and tone.
- Use informal moments—before a meeting starts, after a call ends—to check alignment, not just to chat.
Keep it simple and consistent. A short, genuine exchange every few days builds more trust than a quarterly performance review ever will.
Neglecting to Ask for Feedback
Many people wait for a formal performance review to learn how they are doing. That is a missed opportunity. By the time a review arrives, months of behavior and habits have already been set, and your new supervisor has formed impressions without your input. Relying on assumptions about your performance is risky, especially when you are still learning how your manager prefers to work.
Another common version of this mistake is becoming defensive when feedback is offered. If you immediately explain why you did something a certain way or shift blame, you signal that you are not open to coaching. A supervisor is far less likely to invest time in your development if they expect pushback.
Instead, take the initiative to ask for feedback on specific tasks or projects. General questions like “How am I doing?” tend to produce vague answers. More useful questions include:
- “On the client report I sent Tuesday, which section was clearest to you?”
- “What could I have done differently in the team meeting to move us toward a decision?”
- “Where did you see the most room for improvement in the project timeline I drafted?”
Request concrete examples of what worked and what could improve. This makes the feedback actionable rather than general. Then, apply what you learn and briefly follow up later to acknowledge the adjustment. This shows that you treat feedback as useful data, not criticism. Proactively seeking input demonstrates humility and a commitment to growth, which most supervisors appreciate.
Regular, informal check-ins around a specific deliverable are safer than waiting for an official review. They also give your supervisor a low-pressure way to guide you early, before small issues become patterns.