Twelve minutes and a resignation a month later

September 2023, Thursday, 14:00. Max on the calendar, a mid-level, three years in, even code, reviews, help for juniors.

The meeting took 12 minutes. How are you, what are you doing. Finishing the auth refactor. Blockers? Not yet. Anything else? Not really. Keep it up.

I left pleased: fast, to the point, nobody's time burned.

A month later, a resignation. HR wrote down: no growth, stuck, nothing to talk about with the lead except tickets. The new place promised a mentor and a plan.

I replayed "nothing to talk about with you" three times. I was not a villain. I had mixed respect for other people's time with a short interrogation about tickets. Standup exists for status. This slot exists so a person can talk about themselves before they write a resignation.

If I speak more than a third of the meeting, I stole it.

Why this hour, if not for control

After Max, in two years, zero departures with the line "no growth". One a year used to feel normal. People who look forward to the slot, instead of cancelling it in their head: about 30% became about 85%. A dozen problems surfaced before they blew. Four mids reached senior in eighteen months.

Half an hour every week beats two hours once a month. Context does not go stale. The slot sits on their calendar, not mine. They pick the topics. A move only if production is on fire or they are sick. A regular cancel reads simply: I am not a priority. A closed room or cameras, not the open-space kitchen.

For six people I spend 4 hours a week. Monday Anya 30 minutes and Dima 45, Tuesday Sveta 30, Wednesday Pasha 45, Thursday Max 30, Friday Lena 45. It looks fat until you price replacing a mid.

Four pieces in 30-45 minutes

First, how they feel, 5-7 minutes. Not "how are you". How did this week feel, one to ten, what was good, what burned.

Anya, a junior, said "fine". Silence. On a scale? Five. What keeps it from seven? PRs sit three days, she waits, she thinks she is slowing the team. In two days we set a reviewer rotation. A month later she was at eight. "Fine" I always dig now. I wait three to five seconds, ask whether it is a tired fine or a living one, put it on a scale, ask what would move it two notches.

Then work, 10-15 minutes, without diving into AUTH-123. What eats time, where they are unsure, what can be taken off, whether any of it is even interesting.

Dima had been on legacy a third week. "Cleaning stables, I cannot see an edge." If someone took the test migration, he would finish the logic. We moved it that day. The refactor ended in seven days, mood from four to seven. Burnout is treated by changing the task, not by a speech about drive.

Third piece: growth. What they tried, which skill they want, which task they have not been given.

Sveta wanted architecture. She could write code, not a system. I gave her the notifications module: her decisions, my review. In two weeks she designed it and showed the team. In three months she was assembling small pieces herself. In nine she was a mid. People grow on a task that scares them and does not paralyse them.

Every meeting ends with at least one step: a book, a slice of work, a teardown. If there is no step, we only talked.

Fourth: feedback both ways. What I noticed that was good. What specifically sagged. What I do crookedly.

I told Pasha: reviews got deeper, juniors learn; growth edge: a week on Redis versus Memcached, give yourself two hours to research and pick. He agreed. Back: he lacks why the business wants the ticket. Since then I drag product context into planning. "You are slow" is useless. "The estimate was two days, it took five, let us see where we lost it" is work.

I name my own hole first. Last week I approved a feature without an architecture review, now we are rewriting. After that it is easier to say "I am stuck". If someone says they do not know, the worst answer is figure it out, you are a mid. The better one: thanks for saying, where exactly is the jam.

Once a quarter I ask how comfortable it is to tell me about problems, one to ten, and what keeps it from ten. Without that slot the meeting becomes a play: the person says what the lead wants to hear.

Questions you cannot dismiss with "fine"

"How are you", "what are you doing", "any problems", "all good" almost always close the room.

These open it: how comfortable, one to ten; what is easy, what is hard; one thing in the work they would change; where they get stuck; what eats time and feels spare; which task they want and have not been given; what to learn in three months; what I do crookedly as a lead.

Five that almost always shift the talk.

What is interesting now, and what is dull. If you were lead for a day, what would you change. Which task in two months felt most alive, and why. Imagine you leave in a year in a good way: where, and why. What I should know that you are not saying because it seems small.

If we stall: one thing in the project a wand would change. What I do that gets in the way a little. Which skill next to the job they want, and what space it needs.

After the meeting I write three thoughts and reread them before the next one. Otherwise I become the lead there is nothing to talk about with.

Not every meeting is the same meeting

Once a quarter, an hour about a year ahead. Dima said he wanted senior. We wrote it down: in a quarter two modules with my hand, in half a year alone, plus Anya to mentor. Fourteen months later the grade happened.

So "I want to grow" does not hang in the air, we keep a skill table from minus two to plus two, with an example, not a feeling.

Once a quarter we sit for an hour and move the cells. Without the table "I want senior" stays a toast.

When pace drops, why first. Pasha had been late three weeks, more holes in the pull requests. It was a third month of legacy sawdust. I gave him the next new feature. Pace came back. I no longer push speed without asking the reason.

If someone is already leaving, I do not talk them round. I listen to what was best, what they would change, what I could have done earlier. Late for them, early for the next person.

How I used to break the slot

Eighty percent on tickets. I switch: tickets later, now you on those tickets.

I talk more than I listen. I hold a rule: they get about 70%.

I cancel more than once a month. If it moves, a new cell goes on the calendar at once, not "later sometime".

I do not write agreements down. After the slot: what we agreed, what they do, what I do, dates. Before the next meeting I read it out: last time we agreed X, how is it.

I hear "tired" and ride toward the sprint. I stop. What exactly is tiring.

A day before the slot I read last notes, their pull requests, tickets hanging more than a week, and I prepare one concrete praise and one edge. I send them a short list in advance: what to discuss, questions for me, what they want to change. Then "I do not know what to talk about" happens less.

# 1-on-1 with Dima, 14.12.2025
Mood: 5/10
Talked: third week of legacy, wants a new slice, interested in events
Him: finishes the refactor by 20.12, reads SAGA
Me: find a task on the notifications module
Next slot: 21.12

He sees the shared file. The private one holds the hypothesis "looks like a clash with Pasha" and the thought that he is looking elsewhere. The private file is there so I do not burn the bridge out loud before I have a fact.

Notes come in threes. Shared with them: steps, goals, solid feedback. Private: hypotheses, health, a thought about leaving, a draft of a hard talk. Formal: performance, a raise, a PIP. Shared by default. I do not drag the private file into the shared one "for transparency".

The tool is secondary. I keep a Notion table: name, date, mood, topics, steps. It can be Confluence or a plain doc. What matters is that a week later I am not asking the same thing in the voice of a person who did not listen.

If the slot already exists and still smells like standup, I cut along four seams. They started with a ticket: "AUTH later, now you on that task". I talk more than a minute straight: I stop and put a scale on it. A third move in a month: a new cell at once, with the reason said out loud. Last meeting had a step and I forgot it: I start with that step, even when it is awkward.

Max did not leave over pay. He left because twelve minutes every week confirmed there was no room here to talk about him. This slot either fixes that, or it becomes a short interrogation about a refactor again.