About this series: Over the years I’ve hired dozens of people into leadership roles, developed team leads from within, and watched a lot of capable agents struggle through a transition that nobody properly prepares you for. This Mentorship Series is for junior managers, new team leads, and anyone navigating the early stages of a leadership career in CX and support. The posts are written to stand alone, but they build on each other. If you want context on where I’m coming from, start here.
The best agent on your team gets promoted to team lead. Everyone celebrates. And then, about six weeks later, something quietly starts to go wrong.
They’re still trying to be the best agent. They’re still the one jumping on the hardest tickets, handling the most complex calls, stepping in when anything goes sideways. The team likes them. The customers like them. But nobody’s being developed. Nobody’s being coached. The team is performing at roughly the same level it was before the promotion — because the person who was supposed to be leading it is still doing individual work.
This is the most common failure mode in frontline leadership, and it happens so reliably that it’s almost a rite of passage. Research from the Center for Creative Leadership shows that the hardest challenge first-time managers face isn’t learning new skills — it’s unlearning the identity that got them promoted. Moving from individual contributor to leader of others requires a fundamental shift in how you define your own value. And nobody tells you that before you take the job.
I’ve been on both sides of this. I was that agent. And for nearly two decades I’ve been the person trying to accelerate that transition for people who report to me. Here’s what I know about the first 90 days.
Your value has completely changed. Your instincts haven’t caught up yet.
As an agent, your value was measured by your individual output. Tickets resolved. Calls handled. CSAT score. The metrics tracked you, personally, and high performance meant doing more of the thing you were good at.
As a team lead, your value is measured by your team’s output. Your individual ticket count is irrelevant. What matters is whether the people on your team are resolving tickets well, handling calls effectively, and delivering consistent customer experiences. Your job is to make eight people better — not to be the ninth-best agent on the floor yourself.
That sounds obvious. It does not feel obvious when you’re six weeks in, the queue is backing up, and your hands are itching to just handle it yourself because you know you can do it faster than anyone else on the team.
Resist it. Every ticket you handle is a development opportunity you’ve taken from someone else. Every time you step in to solve a problem, you’ve taught your team that the right response to difficulty is to wait for you.
The hardest thing about being a new team lead is learning to sit on your hands while someone struggles through something you could do in your sleep — because the struggling is how they get better, and your job is to coach them through it, not to do it for them.
The first 30 days: listen more than you change.
New leaders often feel pressure to demonstrate value immediately — to make a visible change, implement a new process, put their mark on something. I understand the impulse. I’d caution against acting on it.
Your first 30 days should be spent primarily in observation mode. Sit with your team. Listen to calls. Read tickets. Watch how people work, where they get stuck, what the informal norms are, what the actual pain points are versus the ones that get talked about in meetings. Have one-on-ones with every person on your team — not to set direction, but to understand what they see from where they sit.
The reason this matters is simple: the view from the team lead chair is different from the view you had as an agent, and it’s different again from the view your manager has. Neither of your previous perspectives gives you the full picture of what’s actually happening in the team. You need to build that picture before you start making changes to it.
This is also the period where you establish the kind of leader you’re going to be. People are watching how you handle information. Whether you use what they share with you against them, or whether you actually use it to make their lives better. Whether you’re consistent. Whether you follow through. The reputation you build in the first few weeks is remarkably sticky.
Days 31–60: establish structure before you try to improve performance.
By week five or six, you should have enough context to start building the operating rhythm your team will run on. This is not about introducing a dozen new initiatives. It’s about putting three or four non-negotiable structures in place and then holding them.
One-on-ones. Weekly, same time, theirs — not yours. The purpose is not status updates. The purpose is their development, their blockers, their questions about the work. If you’re filling the time with queue metrics and scheduling updates, you’re running a status meeting, not a one-on-one.
Team huddles. A brief, structured touchpoint at the start or end of each shift. Ten minutes. What’s happening today, what’s changed, what to watch for. Consistent. Not optional. The ritual matters as much as the content.
Clear expectations in writing. As I wrote in the Barbershop Leadership Series, the single most common root cause of performance problems is that expectations were never made explicit. Your first 60 days is the right time to put in writing what good performance looks like on this team, under your leadership. Not as a threat — as a foundation.
You may also want to think about how the team structures its own documentation. One of the most impactful things I’ve seen done in a support operation is rebuilding the training framework so that skill levels and development paths are defined and visible — not just tracked informally in a team lead’s head. That kind of structure doesn’t happen overnight, but planting it in the first 60 days pays dividends for years.
Days 61–90: start coaching, not just managing.
By day 60 you should know your team well enough to know who needs what. Who’s ready to take on more responsibility. Who’s struggling and why. Who has potential that’s not being developed. Who might be in the wrong role.
This is when the real leadership work begins. And it’s the work that separates team leads who stay at that level from those who grow into broader leadership roles.
Coaching is not correcting. It’s not sending someone a feedback email when their CSAT drops. It’s a regular, intentional conversation about how they’re developing — what they’re working toward, what’s getting in the way, what you see in them that they might not see in themselves yet.
The practical version of this is simple: every one-on-one should have a development thread. Not every one-on-one can be entirely about development — there are operational realities that take up space. But every conversation should have at least a few minutes dedicated to the question: how are you growing in this role?
If you can’t answer that question for each person on your team by day 90, you have work to do. Not because they’re failing — because you haven’t built the structure to find out.
The thing nobody tells you about managing former peers.
If you were promoted from within — if the people on your team were your peers last month — there’s an additional layer to navigate that most leadership development programs don’t address directly.
Some of your colleagues will adjust quickly and support the new dynamic. Some won’t. You may have someone on your team who wanted the role you got, and is making their feelings about that known through passive resistance. You may have a close friend who now reports to you, and who expects the friendship to translate into special treatment.
Neither of those situations resolves itself. They both require a conversation — clear, warm, direct — that acknowledges the change in the relationship and sets the expectation for how the professional side of it will work going forward. That conversation is uncomfortable. Not having it is more expensive.
The most important thing I can tell you about managing former peers is this: be consistent. Apply the same standards, the same accountability, the same recognition to every person on your team — regardless of history. Favouritism, even unintentional favouritism, will erode your credibility faster than almost anything else. And once it’s eroded, it’s very hard to get back.
The first 90 days won’t make you a finished leader. Nobody is finished. But they’ll establish the patterns — the cadences, the habits, the expectations — that everything else gets built on. Get the structure right early, and the rest is iteration. Skip it, and you’ll spend the next year reacting to problems that the structure would have prevented.
The best team leads I’ve worked with over the years share one thing in common: they stopped trying to be the best agent the moment they became a team lead. Not because they didn’t care about the work anymore, but because they understood that the work had changed. Their team’s performance was the new measure. And they treated that responsibility with the same intensity they’d previously brought to their own output.
That shift — from me to we — is the whole job.
Hutch Morzaria is a Director-level CX and Support Leadership professional with 19 years of experience building global support organizations across SaaS, Fintech, and enterprise technology. He has hired dozens of support and CX leaders across his career and holds ITIL Expert certification across V3 and V4.
