The one-to-one that works

A one-to-one is a regular, private meeting between a lead and one report, where the report brings what matters to them. It's the main tool a lead has for hearing about problems while they're still small.

It isn't the same as a listening round. The round at the end of January was a snapshot: one conversation each, the same questions, to learn how the team works before changing anything. A one-to-one is a rhythm. Because it happens every week or two in the same slot, people don't have to decide whether something is “big enough” to ask for a meeting. Small worries, friction with a colleague, an idea, a wish to take on more: they come up while they're cheap to deal with.

At Klasna, February is days 1–30 of your plan, with a new rotation and the spring peak ahead. That's exactly when small problems grow fastest, and when a standing private slot with each of the four coordinators pays off most.

How often to meet depends on how much is changing. Weekly, 30 minutes for anyone new and for everyone in a busy season. Every two weeks for experienced people once things are calm. Always the same slot, so nobody has to ask for it.

Monthly is too slow: by the time you meet, the small problem has become a big one. “Only when someone asks” sounds efficient but favors the people who ask least, often the quietest or the most worried.

Remote work adds two rules. Pick a slot inside both time zones' working hours, since two of the team work abroad. And plan for outages: video when it works, camera optional; if the power goes, move the meeting within the same week or hold it in writing.

Moving a one-to-one is fine. Quietly cancelling it, especially when the queue is long, tells people they come last, exactly when they most need the slot.

The most important rule of a one-to-one: the agenda belongs to the report. Keep one shared doc per person. They add their topics before the meeting, you add yours below, and their topics go first, every time.

Why so strict? Because a one-to-one is the only place for things a group meeting or a ticket thread can't surface: doubts, friction with a colleague, what someone wants to do next. If the lead fills the time, those never come up.

The biggest threat is status. Ticket counts, queue length and the rotation's progress belong in the ticket thread or a short written update. Open a one-to-one by reviewing someone's numbers and it turns into a status check; people stop bringing anything real.

Olha says it plainly at Klasna: she'll put something real in the doc, but if it turns into a review of her ticket counts, she'll stop. That's a useful warning. Numbers can come up later in the meeting, when they help answer the person's own question.

When the doc is empty, keep a few standing questions. The rules are the ones from the listening round: ask about real recent events and don't lead the answer.

Good ones: “What took longer than it should this week?” “Where did you get stuck, and what did you try?” “What should I start, stop or keep doing?” “Which part of the work would you like more of?”

Two kinds of question waste the slot. Closed check-ins like “Is everything OK?” get “Yes, fine” almost every time. Leading questions like “You're happy with the rotation, right?” push towards a yes. A neutral question names the topic and leaves the answer open: “How is the rotation working for you so far?”

Then listen more than you talk. And know the edge of your role: if you hear about health, family or safety, offer what work can change, like hours or load, and point to a professional for the rest. You're the lead, not a therapist.

A one-to-one without notes is a nice chat that changes nothing. Write short notes in the shared doc, during the meeting or right after: what you discussed, and each next step with one owner and a date. Next week starts by checking them, which is how people learn that agreements here are kept.

The other half is confidentiality. What's said in a one-to-one stays between the two of you. Your manager doesn't read the notes, and neither does anyone else. That's what makes people willing to bring doubts and friction at all.

There are honest exceptions: safety, harassment and anything the law requires you to report. If you hear one, say openly that you have to take it further, rather than promising secrecy you can't keep.

What can go up is themes without names. “Two people find the hand-up note too long” helps Iryna; “Olha said…” breaks trust with the whole team the moment it travels back.

Half an hour goes fast. A fixed shape keeps the report's topics from being squeezed out and makes sure the meeting ends with something written down.

1. Last week's next steps: a quick check first, so agreements visibly matter.
2. The report's topics from the shared doc, the heart of the meeting.
3. The lead's topics, after theirs, never before.
4. Feedback both ways: what's going well, what to change, and what you could do differently as lead.
5. New next steps, each with one owner and a date. They become next week's first item.

The order does the work. If the lead's topics go first, they expand to fill the slot. If next steps aren't written, the next meeting starts from nothing.

Feedback gets a single line in this shape on purpose: how to give it well, on behavior rather than character, is the next lesson.

An empty agenda doc doesn't always mean there's nothing to say. Sometimes the person isn't sure yet that it's safe, or worth it, to raise something with a new lead.

At Klasna, Maryna's doc has been empty for two weeks. In the meeting she says “all fine” and waits for you. Maybe she really has nothing to raise. Or maybe she's quiet, new and still testing what happens to what she says.

Make it easy rather than pushing. Send two or three questions a day ahead, so she can answer in writing first; quiet people often say more after time to think than on the spot. Make the questions about what she has seen, not what she thinks of it, because observations feel safer to share than opinions. And keep showing what happens to what people say: small next steps that actually get done.

Don't fill the silence with your own topics. That teaches her the slot is yours.

Requests to skip arrive in busy weeks, and busy weeks are exactly when one-to-ones pay off. A backlog is a topic, not a reason to drop the meeting.

At Klasna Bohdan writes: “Can we skip this week? Big backlog.” Four replies are possible. Skipping until next month loses the rhythm and the chance to hear what's behind the backlog. Insisting on the full 30 minutes ignores a real constraint and makes the meeting feel like a rule rather than help. Asking for a written status replaces the conversation with a report.

The good reply keeps the rhythm and respects the constraint: “Let's do 15 minutes instead. I'd like to hear what's behind the backlog.” Maybe it's the outages, maybe a ticket type he's stuck on, maybe the new rotation. Fifteen minutes can find out, and the lead might be the one who can unblock it.

How it fits together: a fixed rhythm, the report's agenda, neutral questions, written next steps and kept confidences make one-to-ones the place problems arrive early. The next lesson fills the feedback slot: feedback on behavior, not on character.