A performance conversation months into someone’s tenure often traces back to a single, avoidable root cause: nobody was ever genuinely specific, at the very start, about what success in the role actually looked like. The employee assumed one thing; the manager assumed another; and the gap between those two assumptions quietly widened for months before it finally surfaced as a “performance issue” that was, in truth, an expectations issue from day one.
Why Vague Expectations Cause More Damage Than They Seem To
A new employee arriving without genuinely clear expectations doesn’t simply muddle along neutrally — they actively fill the gap with their own reasonable-seeming assumptions, often shaped by a previous role, a general sense of professional norms, or simple guesswork. These assumptions frequently diverge from what the manager actually had in mind, and the divergence isn’t usually discovered until well after real behaviour and habits have already formed around the wrong assumption, making it considerably harder to correct than it would have been to prevent in the first place.
What “Clear Expectations” Actually Requires
Specificity about what success looks like, not just what tasks need doing. A list of responsibilities describes activity; a genuine description of what good performance in those responsibilities actually looks like describes the actual standard being expected. The gap between these two is where most unspoken assumptions live.
Explicit priorities, not an implicit assumption that everything matters equally. When several responsibilities compete for time, a new employee needs to know which ones genuinely matter most if trade-offs become necessary — without this, they’re left guessing at priorities that may differ considerably from what the manager actually has in mind.
Clarity about communication norms specifically. How often should they check in? What warrants an immediate flag versus a routine update? What’s the expected response time to a message? These norms feel obvious to an experienced manager and are genuinely unclear to someone new, who has no established baseline yet for what’s normal in this specific team.
A concrete description of what “too slow to escalate” and “escalating too much” both look like. New employees frequently struggle with exactly where the line sits between appropriate independence and appropriate escalation — being explicit about this, with actual examples, removes a genuine source of anxious guesswork.
An honest account of what’s still being figured out, where relevant. Not every expectation is fully settled at the point someone joins a role — being honest about genuine ambiguity, rather than presenting false certainty, is itself a form of clarity, since it tells the new employee where they can expect things to still be evolving.
How to Actually Deliver This
Have a dedicated conversation, not a scattered set of comments over the first weeks. Expectations delivered piecemeal, as they happen to come up, leave real gaps where nothing was ever actually said explicitly. A dedicated, deliberate conversation early on covers the ground more comprehensively than relying on expectations to surface organically over time.
Put the core expectations in writing, briefly. A short written summary — even a few bullet points — gives both people something concrete to refer back to later, and it protects against the natural tendency for a verbal conversation’s details to be remembered somewhat differently by each person involved.
Invite genuine questions, and treat them as useful rather than a sign of inadequate preparation. A new employee who asks a clarifying question is doing exactly the right thing — treating these questions as an annoyance, even subtly, discourages exactly the behaviour that prevents costly misunderstanding later.
Revisit and adjust expectations explicitly as the role evolves. Expectations set on day one won’t necessarily still be accurate three months in, once someone has genuinely settled into the role — treating the original conversation as a fixed, permanent document rather than a living one that gets revisited misses this.
Check for actual understanding, not just delivery. Asking someone to briefly restate their understanding of what’s been discussed — not as a test, but as a genuine check — often reveals a gap between what was said and what was actually understood, before that gap has a chance to cause a real problem.
Why This Matters More at the Very Start Than Later
Early assumptions, once formed, tend to be genuinely sticky — a habit or expectation someone settles into during their first weeks becomes considerably harder to shift later than it would have been to set correctly from the outset. This is exactly why the investment in genuine clarity at the start pays off disproportionately: the same conversation, delivered three months later after incorrect assumptions have already calcified into habit, requires considerably more effort to actually change anything.
The Balance Between Clarity and Overwhelming Someone New
It’s worth being clear that comprehensive clarity doesn’t mean overwhelming a new employee with an exhaustive list covering every conceivable scenario on their very first day. The goal is genuine clarity on what matters most — priorities, communication norms, what success looks like in the core responsibilities — delivered at a pace that’s absorbable, with the understanding that some detail will reasonably continue to be filled in as specific situations actually arise.
Setting Expectations for an Existing Team Member in a New Role
The same principle applies, often with even more importance, when an existing team member moves into a new role or takes on significantly expanded responsibilities. It’s tempting to assume that because someone already knows the team and the organisation, expectations don’t need the same explicit treatment they’d get for a genuinely new hire — in practice, a role change often carries just as much room for divergent assumptions as a new hire’s first days do, since the person’s own prior experience in a different role can actually work against clarity, leading them to import assumptions that don’t actually transfer cleanly to the new responsibilities.
What to Do When You Realise Expectations Were Never Actually Set
If you’re a manager who recognises, partway through someone’s tenure, that genuinely clear expectations were never actually established, the right response isn’t embarrassment or avoidance — it’s a direct, honest conversation now. Naming the gap explicitly — “I don’t think I was as clear as I should have been early on about what success looks like here, so let’s establish that properly now” — resets the relationship on a considerably more solid footing than continuing to operate on assumptions that were never actually confirmed, regardless of how far into the working relationship this correction happens to occur.
A Practical Scenario
A manager brings on a new analyst and, in the interest of not overwhelming her in the first week, keeps the initial conversation fairly general — a rundown of responsibilities, with the assumption that specifics would naturally emerge over time. Three months later, a performance conversation reveals that the analyst had been prioritising thoroughness over speed on a specific recurring deliverable, while the manager had actually needed speed prioritised over exhaustive thoroughness for that same deliverable — a genuine, costly divergence that had never been made explicit at the outset.
Recognising the root cause wasn’t the analyst’s judgement but his own lack of specificity early on, the manager restructures his approach for the next new hire: a dedicated conversation in the first week covering explicit priorities among competing responsibilities, a brief written summary afterward, and a check two weeks in specifically to confirm the new hire’s understanding matched his own intention. The next new hire settles into the role with considerably fewer of the costly, months-long misalignments the previous hire had experienced — direct evidence that the earlier problem had been a clarity gap, not a performance gap.
Common Mistakes
Delivering expectations piecemeal over the first weeks rather than in a dedicated conversation. This leaves real gaps where nothing was ever actually said explicitly, filled instead by the new employee’s own reasonable-seeming assumptions.
Listing responsibilities without describing what success in them actually looks like. A list of tasks describes activity, not the standard being expected — the gap between these is where costly misunderstanding tends to live.
Treating a new employee’s clarifying questions as a sign of inadequate preparation. This discourages exactly the behaviour — asking rather than assuming — that prevents genuine misunderstanding later.
Never revisiting expectations after the initial conversation. Expectations set on day one don’t necessarily stay accurate as a role evolves, and treating the original conversation as permanent misses this.
Action Steps
- If you’re bringing on a new team member, schedule a dedicated conversation specifically about expectations, rather than letting them emerge piecemeal.
- Prepare a brief written summary of core expectations — priorities, communication norms, what success looks like — to share after the conversation.
- Explicitly name which responsibilities matter most if trade-offs become necessary, rather than leaving priority implicit.
- Ask a new team member to briefly restate their understanding of what’s been discussed, to check for genuine alignment rather than just delivery.
- Set a specific point, a few weeks or months in, to revisit and adjust expectations as the role settles into its actual shape.
Key Takeaways
- Unclear expectations don’t leave a new employee neutral — they actively fill the gap with their own reasonable-seeming assumptions, which frequently diverge from what the manager actually intended.
- Genuine clarity requires specificity about what success looks like, explicit priorities, and clear communication norms, not just a list of responsibilities.
- A dedicated conversation, followed by a brief written summary, covers the ground more comprehensively than expectations delivered piecemeal over time.
- Early assumptions are genuinely sticky, which is why investing in clarity at the start pays off disproportionately compared to correcting a misunderstanding later.
- Expectations should be revisited explicitly as a role evolves, rather than treated as a fixed, one-time conversation.
Conclusion
A significant share of performance problems that surface months into a role are, at root, clarity problems that trace back to expectations that were never made genuinely explicit at the start. Investing deliberately in a dedicated conversation, specific priorities, and a brief written summary — and checking for genuine understanding, not just delivery — prevents the kind of costly, slow-building misalignment that’s considerably harder to correct once early assumptions have had months to calcify into habit.
Frequently Asked Questions
How much detail should be covered in an initial expectations conversation?
Enough to cover genuine priorities, communication norms, and what success looks like in the core responsibilities — comprehensive on what matters most, without attempting to cover every conceivable scenario in a single, overwhelming session.
Should expectations be delivered verbally or in writing?
Both — a verbal conversation allows genuine dialogue and questions, while a brief written summary afterward protects against the natural tendency for verbal details to be remembered somewhat differently by each person involved.
How can a manager check that a new employee actually understood the expectations discussed?
Asking them to briefly restate their own understanding, rather than simply asking “does that make sense,” often reveals a genuine gap between what was said and what was actually understood.
What if expectations need to change after the initial conversation?
This is normal and expected as a role settles into its actual shape — revisiting and explicitly adjusting expectations at a set point protects against treating the original conversation as permanently fixed.
Is it a bad sign if a new employee asks a lot of clarifying questions early on?
Generally the opposite — clarifying questions are exactly the right response to genuine uncertainty, and treating them as useful rather than a burden encourages the behaviour that prevents costly misunderstanding later.
How can a manager avoid overwhelming a new employee with too much information at once?
Focus the initial conversation on what matters most — priorities, communication norms, definition of success — and be explicit that some detail will reasonably continue to be filled in as specific situations actually arise.
Do existing team members moving into a new role need the same explicit expectations conversation as new hires?
Yes, often even more so — their prior experience in a different role can lead them to import assumptions that don’t actually transfer cleanly, making explicit clarity just as important as it is for a genuinely new hire.
What should a manager do if they realise expectations were never properly set with an existing employee?
Name the gap directly and have the conversation now — a direct, honest reset is considerably more useful than continuing to operate on assumptions that were never actually confirmed.