Development plans, handover and being away

Each review ends with a plan for next year, and the classic mistake is that the lead writes it alone and hands it over. A development plan is written with the person: they draft, you add. A plan written for someone is a list of your wishes; one they drafted is a commitment.

A good plan has five parts:

1. One or two growth areas, in the person's own words. Olha's: "plan the September restart on my own".
2. Real work to practice on: acting as lead during your October leave.
3. Support: what you, Iryna or a colleague will provide.
4. How you'll both know it's working.
5. A review date: a monthly check-in in your one-to-ones, the first review in December.

Two things don't belong. A ranking against a colleague turns growth into a contest. And courses picked by the lead with no link to a real task rarely change how anyone works.

People grow mostly by doing harder real work with feedback, not by collecting courses. A stretch assignment is a task a little beyond what the person does today, done for real, with support and regular feedback.

For each growth area, the plan's key line is the real work they'll practice on. Bohdan wants to get better at teaching newcomers, and his 36 mentoring hours this year show he's already good at it. The stretch: run the onboarding of the next seasonal hires, with feedback from you after each week. Olha's stretch is acting as lead during your October leave. Maryna, who wants depth, could own the refund help articles.

Courses have their place: when they feed a real task. A short course on writing help articles makes sense if Maryna is about to own them. A certificate with no task attached rarely changes how anyone works. And protect the time: a stretch on top of a higher ticket target isn't growth, it's overload.

Not everyone wants to climb, and a development plan isn't a ladder to management. Olha wants to lead one day. Maryna says she isn't interested in managing anyone, at least not now. Both are valid answers.

For Maryna, growth goes deeper: she could own the refund help articles, or review tricky replies for quality, building on the team's lowest reopen rate. Depth is growth too, and it deserves the same recognition as a step toward leading. Bohdan's mentoring hours suggest another path: ask whether he'd like teaching to become a named part of his role.

Three replies get this wrong. Dropping her plan ("then there's not much to plan") stops her development. Forcing your idea of a career on her ("everyone should aim for a lead role") ignores what she said. And judging her by age ("you're young, you'll change your mind") has no place in any work conversation. If someone doesn't want a plan at all for a while, that's allowed: ask what keeps the work interesting and keep the door open.

The other half of growing people is making sure no piece of work depends on one of them, including you. The bus factor is how many people would have to be suddenly away before something stops. A bus factor of one means a single absence stalls the work.

Klasna Support has two: only Olha decides refund exceptions, and only the lead does the rota and Iryna's monthly report. It's tempting to read that as a compliment ("she's irreplaceable"), but it's a risk, both to families and to the person. In a distributed team where outages and lost connections are part of normal planning, an illness, a leave or a day without power stops the work. And the person can never fully switch off: Olha herself says she'd like to actually rest on vacation.

Being the only one who can do something isn't how value should show. Teaching others is. Olha offers to teach Bohdan the refund exceptions, if Iryna agrees he can decide them when she's off.

A bus factor drops only when a second person can really do the work. That takes three things, and each covers a different gap.

1. Know how. Write down the steps: for the rota, the rules (the 45-minute first-reply rule, who covers evenings, how vacations rotate), the inputs and where the file lives.
2. Have done it for real. Let the second person do it once while you're still around to answer questions: Olha builds the November rota in October, before your leave, and you review it with her.
3. Have the right to decide. Agree in writing what they may decide without you, and with whom to check: the rota is hers while you're away; anything outside the refund policy stays with Iryna.

Two shortcuts don't work. Pre-building the rota for two months only hides the risk until the first sick day. And "message me if anything changes" keeps the bus factor at one, with you on a beach as the single point of failure.

Before any leave, a lead writes a handover note, so the team can work without them. Iryna wants yours a week before your two weeks in October, with the name of who acts for you: she doesn't want Support messaging you on the beach.

A useful note covers six things: what's running now; decisions already taken (so nobody reopens them); what's pending, with dates, such as next month's rota; who decides what while you're away; where things live (the decision log, the structure table, the files); and when to go to Iryna instead of waiting.

Olha as acting lead fits the goal she set in her coaching conversation: a real stretch assignment, with clear limits. Agree it with her and Iryna, and tell the team in writing, so nobody keeps writing to you.

Two things undo the note. An open invitation to "message me for anything" means it was never really handed over. And private notes on people's weaknesses have no place in a document the whole team relies on.

The heart of a handover note is a short list of who decides what while you're away, built on the same decision rights the team has used all summer. Four groups cover most cases:

• Day-to-day running moves to the acting lead. Swapping two shifts because Taras is ill, adjusting the rota: Olha decides.
• Routine work stays where it always was. A family's question about a lesson package is answered by whoever is on shift, as usual.
• Decisions outside the policy stay with Iryna. A refund outside the refund policy is hers, with or without you.
• Hard-to-undo decisions that aren't urgent wait for you. Whether to offer a seasonal contract for next spring can wait two weeks.

Write each one down, with an example, and send it to the team and Iryna. Without it, people either guess, or message you on leave, or stop and wait, which is exactly what the note is there to prevent.

When you come back, review what the acting lead decided. That review is the feedback that turns two weeks of covering into real growth. But review isn't undo. If Olha moved the evening rotation in a way you wouldn't have, ask her reasons first; they may be better than yours, since she was there. Then decide together whether anything changes.

Overrule an acting lead quietly even once, and everyone learns that her decisions don't really count. Next time she, and the team, will wait for you instead of deciding, and the bus factor is back to one. Saying nothing is no better: she gets no feedback on her first real calls as lead.

The same rule applies to you. You need a development plan too: hand work over earlier, decide with incomplete information. You draft it, Iryna and the team add, and you set a date to look back.

How it fits together: plans written with people, growth through stretch work in depth or toward leading, no bus factors of one, a clear handover and a respectful review. The case brings it together: four evaluations and four plans, on the facts.