How to run one on one meetings

I have run 1-1s badly for longer than I have run them well. For about two years they were a weekly status review with a friendlier tone. I asked what people were working on, they told me, I nodded, and we both went back to work feeling that thirty minutes had been spent politely.

The change came from a single piece of feedback. Priya, one of my senior engineers, wrote in an anonymous team survey that our 1-1s were the least useful meeting of her week. That stung, and it was correct. Everything below is what I rebuilt after reading that line.

What a 1-1 is actually for

The 1-1 belongs to the report, not to me. It is the one recurring slot where the agenda is set by the person doing the work, and where the topics that do not fit anywhere else can surface. Career doubts, friction with a teammate, a decision from leadership that made no sense, a family situation that is quietly draining focus. None of that comes up in standup.

Status has a home already. It lives in the tracker, in standup, in the weekly team sync. When status colonises the 1-1 it pushes out the only conversation that has nowhere else to go.

The useful mental model for me is this. Standup keeps the work aligned. The 1-1 keeps the relationship and the context alive. If I know how someone is doing, what they want in two years, and what is currently annoying them, I can make a hundred small decisions better without asking them anything.

Cadence and length by team size

Weekly, thirty minutes, same slot every week. That is the default and it works for most teams up to about seven reports. Weekly matters more than long. A thirty minute conversation every week beats an hour every other week, because the gap is where context decays and small problems grow quietly.

With eight or more reports, weekly thirty minute 1-1s eat a full day. At that size I moved senior people who were stable and self directed to biweekly and kept weekly for anyone new, anyone struggling, and anyone in the middle of a career conversation. That split was honest. Pretending I could hold twelve weekly 1-1s and still prepare for any of them was not.

Biweekly is a real option, but only if you say why. I told the two engineers who moved to a two week cadence exactly what I was doing and why, and I told them that anything urgent got a slot the same day. Silent downgrades read as loss of interest.

• Three to seven reports: weekly, thirty minutes.
• Eight or more: weekly for new, struggling, or in transition, biweekly for stable senior people, stated openly.
• Brand new report in the first month: weekly, and protect it above almost everything else.
• Skip level reports: monthly or quarterly, and never as a replacement for their manager's 1-1.

Preparation, five minutes that change the meeting

The difference between a 1-1 that lands and one that drifts is almost entirely what happened in the five minutes before it. Walking in cold means I spend the first ten minutes rebuilding context that I already had two weeks ago, and the person watches me do it.

My prep is small and always the same. I open the person's page, read the last two entries, and pick one thread to reopen. That is it. Something like a note from three weeks ago that said Marco was worried about owning the migration alone, so I open with how the migration ownership feels now rather than with how are things.

For a long time I did this by hand, and I skipped it whenever the day got loud. These days I write a couple of lines after each 1-1 and LeaderCues reads them back to me as a short brief before the next one, with the open threads and the things I said I would do, which means the prep happens even in the weeks when I would have skipped it.

If you do nothing else from this article, do the five minutes. It is the highest leverage habit in the whole practice.

How to open so the report talks first

Whoever speaks first sets the shape of the meeting. If I open with my updates, the next twenty five minutes are mine. So I open with a question and then I stay quiet longer than feels natural.

How are you does not work. It is a greeting, not a question, and the honest answer to a greeting is fine. What works is specific and grounded in something real.

• Last time you mentioned the on call rotation was wearing you down. Where is that now.
• What has been the most annoying part of the last two weeks.
• Is there anything you have been sitting on that you have not brought up.
• What do you want to make sure we cover today, before I add anything.

That last one is my default when I have nothing better. It hands the agenda over explicitly, and it tells the person that my topics are second in line.

There is a longer set of these grouped by what you are trying to learn in one on one meeting questions that get people talking, including the ones that backfire when you overuse them. When you want a set for a specific situation without reading the whole thing, the 1-1 question generator builds one you can copy in a click.

The quiet report

Some people give you three word answers for months. My instinct was to fill the silence, which made it worse, because they learned that if they waited about four seconds I would rescue the moment for them.

Three things helped. First, silence. I count to five in my head after asking something and I do not break it. Second, narrowing the question. Instead of how is the project going, I ask which part of the project you would rewrite if you had a free week. Concrete questions are easier to answer than open ones. Third, asynchronous room. I started sending one question the evening before, and some people simply think better in writing.

It also helps to accept that a quiet person is not always an unhappy person. Two of the most reserved engineers I have worked with were perfectly content. I was reading my own discomfort as their problem.

The report who fills the slot with status

The opposite failure is a person who arrives with a list of ticket updates and talks for twenty nine minutes. Usually this is not evasion. It is what they think the meeting is for, often because a previous manager ran it that way.

Naming it directly worked better than any technique. I told Daniel that I already read the board every morning, that I was not worried about his delivery, and that this half hour was for anything that the board does not show. It took three meetings before he stopped opening with the sprint, and then he told me he had been thinking about moving toward platform work for six months.

Commitments and follow through

Everything a 1-1 builds is built here. Trust is not created by good conversation, it is created by the pattern of what happens between conversations, repeated over months.

So I write down every commitment I make, with a date, in the same place as the notes. When I said I would find out whether the conference budget covered a workshop in Lisbon, that line went on the page with the date I said it. If I come back two weeks later with an answer, even a no, the person learns that saying things to me has consequences. If I come back with nothing, they learn the opposite, and they stop bringing me the things that matter.

The failure mode is rarely a broken promise. It is a forgotten one, which from the other side of the table looks identical. I wrote more about that in the follow-up problem managers underestimate.

Why canceling 1-1s costs more than you think

Cancelling one 1-1 for a genuine emergency is fine, as long as you reschedule it yourself and say why. Cancelling three in a row communicates a ranking, and the person on the other end reads it accurately. Their half hour is what you drop when things get busy.

I have been on both sides of this. A manager of mine cancelled five weeks running during a reorg, which was exactly the period when I most needed twenty minutes of his attention. I did not resign over it, but I stopped bringing him anything that was not already on fire, and that changed what he knew about my team for the rest of the year.

My rule now is simple. If I have to move a 1-1, I offer a new slot in the same message, inside the same week. If I cannot do that, I keep the original slot and cut it to fifteen minutes.

A first month plan if your 1-1s need fixing

Do not announce a new system. Just change your own behaviour and let people notice.

• Week one. Make one page per person. Write what you already know about each of them from memory, including the personal context. Notice how thin some pages are.
• Week two. Spend five minutes before each 1-1 reading that page. Open with a question drawn from it. Write three lines after each meeting, the same day.
• Week three. Start tracking commitments explicitly, yours and theirs, with dates. Close at least one open thread that has been sitting for a month.
• Week four. Ask each person directly what they would change about how you run these. Then change one of the things they say and tell them you did.

That last step is the one most managers skip, and it is the one that produces the fastest improvement. The people in the meeting know what is wrong with it.

For the format I keep those notes in, there is the 1-1 template I actually use every week. For the first meeting with someone who just joined, your first one on one with a new employee covers what that conversation should and should not try to do.

None of this is complicated. It is thirty minutes a week, five minutes of reading, and three lines of writing, held steady for a year. The compounding is the whole point.