Your output is now the team's output

A team lead is judged by what the whole team delivers, not by what the lead delivers personally. Your output is now the team's output: how many families get a good answer, how many tickets come back, and whether the team still works on the days you're away.

That's a real change of job, not a promotion inside the old one. As a senior coordinator you were valued for closing tickets fast and well. As lead, the same habit can work against you: every hour you spend on your own queue is an hour nobody spends making four other people better at theirs.

At Klasna the numbers make it plain. In January you closed 176 tickets yourself, a respectable pile. Yet that was only 13.60% of everything the team closed. The other 86% depended on Olha, Taras, Maryna and Bohdan, and that's where most of your influence on the result now sits.

A new lead's sense of how the week went is usually wrong, because the urgent work feels like the important work. A calendar audit replaces the feeling with a record: for a few weeks, log every hour by category, then add the categories up and turn them into shares.

The method is simple. Pick a handful of categories that match your real work (own tickets, escalations, team questions, one-to-ones and meetings, planning, admin). Log honestly, by the week. Then divide each category's hours by all hours logged.

Your January log at Klasna: 186 hours in four weeks, 26 more than four 40-hour weeks. Own tickets took 22 + 24 + 23 + 15 = 84 of them, so 84 / 186 ≈ 45.16%. Almost half the month went to the same work you did before the promotion.

Shares matter more than totals: a long week with the same mix is still the same job.

Once the hours are logged, sort the categories into three kinds:

• Doing: work a coordinator could do, such as your own tickets and escalations you solve yourself.
• Enabling: work that makes the team better at its job, such as answering their questions, one-to-ones and team meetings, planning.
• Overhead: admin and tools that keep things running.

The tricky one is escalations. They feel like lead work, because they reach you as the lead. But if you end up solving the ticket yourself, it's doing. Enabling is when the coordinator solves it and you made that possible.

Your January split: doing 117 hours (62.90%), enabling 51 (27.42%), overhead 18 (9.68%). Almost two-thirds of the month went to work someone else on the team could have done, and barely a quarter to the work only a lead can do.

The three kinds turn a long list of categories into one question: is the balance right for the job you have now?

Why move hours from doing to enabling if you're good at doing? Because the two kinds of hours pay back differently.

An hour on your own tickets closes about two tickets, once. An hour spent teaching Olha a tricky refund case, removing a blocker from Taras's week or agreeing a clearer hand-up rule keeps paying: the coordinator handles that kind of case every week after, without you. That's leverage: the effect of an hour multiplied through other people.

The pay-back isn't instant. The first week a coordinator solves a hard ticket alone, it takes longer than if you'd done it, and a customer may wait a little. The return comes over the following weeks, which is exactly when a lead needs it: before the spring peak, when the team has to carry far more tickets than you could ever close yourself.

Being the best at tickets is still useful. Use it to teach, not to replace the team.

A common trap for a lead promoted from inside: you're still the fastest person on the team, so the hardest work flows to you. It feels responsible. In fact the team stops practising the hard cases and learns that passing them up is the quickest route.

At Klasna the hardest tickets (a refund dispute, a lesson lost to a video failure) numbered 69 in both December and January. What changed was who solved them. Your share rose from 47.83% (33 of 69) to 75.36% (52 of 69). The coordinators' hard tickets fell from 36 to 17, and tickets handed up rose from 42 to 101. Olha went from 14 hard tickets to 6 without getting any worse. Your own first replies slowed too, from 11.75 to 21.5 minutes.

Read such numbers as a system, not as people failing. Volume was flat, so nobody got overloaded or worse; the work simply reached you first. In March, with the exam peak and two new hires, that route makes the lead the bottleneck.

An audit is only useful if it changes the next week. After week 3 you looked at the log and moved hours on purpose. The test is the share, not the feeling of being busier or calmer.

Week 4 (25 January) had 47 hours: own tickets 15, escalations 9, team questions 8, one-to-ones and meetings 7, planning 4, admin 4. Own tickets: 15 / 47 ≈ 31.91%, down from 48.89% in week 1 (22 / 45). The week was no shorter; enabling grew from 11 hours to 19. And for the first time the coordinators solved more hard tickets than you: 9 against 8, with Olha back to 4.

One line didn't move: escalations stayed at 9 hours. Calendars change faster than habits, because hand-ups keep arriving until the team trusts the new route. Expect that lag, keep measuring, and don't declare victory after one good week.

The answer to the promoted-star trap isn't to stop doing tickets. A lead who never touches the queue loses touch with real customers, can't judge what's hard any more and can't step in on the worst cases.

Set a target week instead: a realistic split of 40 hours you can steer towards. For Klasna's Support lead: own tickets 8 hours, escalations 5, team questions 10, one-to-ones and meetings 6, planning 6, admin 5. Doing is 13 hours (32.5%), enabling 22 hours (55%).

Compare it with where you are. From week 4 that means 7 more hours out of own tickets (15 → 8) and 3 more hours for enabling (19 → 22). It's a direction, not a rule to hit every week: an outage day will blow it up, and that's fine.

The balance is what changes. Hard tickets move to the team gradually, and your remaining queue hours become a way to stay close to the work.

Moving hard tickets to the team is a skill, not a switch. Hand them over in steps, so customers stay safe while people learn: first agree which ticket type moves and to whom; then solve a few together while the coordinator watches; then the coordinator solves and you check before the reply goes out; then the coordinator solves alone and you look at a sample afterwards.

Three habits undo this faster than anything. Grabbing hard tickets before anyone else sees them. Answering a question when a question back would do: “what would you try?” And taking every hand-up yourself instead of routing it to someone who is learning that type.

In a remote team the second habit matters most. If the lead answers every chat message within minutes, people stop trying first.

How it fits together: the audit shows where your hours go, the three kinds show what they should go to, and handing over in steps moves them. The next lesson plans your first 30 days: listening before you change how the team works.