You will be able to explain what a one-on-one is for and what it should be kept free of.
Hui Min has been on Wei Ling's team for eight months. For the last three weeks, Wei Ling moved their weekly one-on-one: once for a client call, once for a budget meeting and once to finish a report. (Hui Min, Wei Ling and the figures about them are an invented example.) Each time, Wei Ling sent a polite message suggesting they catch up later that week, and the catch-up never happened. Hui Min didn't complain, but she stopped putting anything on the agenda.
Wei Ling never heard what was going on. Hui Min was struggling with a new reporting tool and spending her evenings catching up. In week one, a ten-minute fix would have solved it: someone just needed to show her a shortcut. By week four she was tired, behind and quietly wondering whether she was cut out for the role. The problem stayed the same size the whole time. What grew was how she felt about it.
A one-on-one is a regular private meeting between a manager and one direct report. It looks like the easiest meeting to move, because nothing visibly breaks when you skip it. Over a few months, though, it is often the meeting that decides whether you hear about problems while they are small or only after they have grown.
The main reason to hold one-on-ones regularly is that they catch problems early. People rarely book a meeting to raise a minor frustration. They mention it when a slot already exists, the conversation is relaxed and someone asks. Meeting regularly also makes hard conversations easier, because raising something difficult becomes part of an ordinary routine. If you only meet when something is wrong, every meeting request you send feels like bad news.
Andy Grove, in his book High Output Management, described the one-on-one as the subordinate's meeting. In his view, the report sets the agenda and the tone, and the manager's job is to listen, ask questions and help. He saw it as the place where the manager learns what is really happening and where the report gets coaching on the problems they actually face.
Who sets the agenda changes what the meeting is for. If you set it, the meeting turns into you checking on their work. If they set it, it becomes the place they bring what worries them, what blocks them and what they want from you.
In practice, ask your report to add their topics first, and start the meeting with theirs. You can still add your own items, and some weeks you will need to. Keep an eye on the balance over time. If the agenda is mostly yours most weeks, the meeting has quietly become your meeting.
The most common failure is the one-on-one turning into a status update. You ask what they worked on, they list it, you nod, and neither of you learns anything a two-line message could not have said. That is thirty minutes spent on information a short note could carry.
Status belongs somewhere else: a short weekly written update, a team channel, or a tracker everyone can see. If you took the Communicate at work course, lesson 3.4, "Set up a weekly update you can send in ten minutes", covers the weekly written note from the other side. Once status lives in one of those places, the one-on-one is free for things that need a conversation.
Those are the things that are hard to write down. A client who is wearing the person down. A colleague they clash with. A task they don't understand but haven't admitted to. What they want to learn next. Feedback in both directions. And whether they are thinking about leaving.
Every manager has to move a meeting sometimes. The trouble starts when one-on-ones become the first thing moved, as Hui Min's were. People notice what gets dropped when your week fills up, and they draw the obvious conclusion about where they rank. Decide on your rule before the next clash, so you aren't making it up under pressure. A workable rule has four parts:
Move the meeting, and never cancel it. Do the moving yourself, and put the new time in the same message. A suggestion to catch up later in the week does not count, as Wei Ling found. If you truly cannot meet that week, say why and keep the next one. If the clashes keep coming from the same recurring meeting, move the one-on-one permanently to a safer slot.
There is no single right frequency or length. A common starting point for a new manager with a small team is weekly for 30 minutes. Another option is fortnightly for 45 to 60 minutes, which works especially well with experienced people.
Grove argued for setting the frequency by the person's experience with their current work, and meeting more often with someone who is new to a task. You will meet this idea again in lesson 3.2, "Match your involvement to their experience". That means the rhythm can differ from one report to the next, and it can change when someone takes on something unfamiliar.
Do the time arithmetic before you commit. Multiply each person's rhythm out across all your reports to get the weekly cost, then check that the total fits within your managing time. Wei Ling has five direct reports. Weekly 30-minute meetings with all five come to two and a half hours a week, which fits inside the managing time she set in her charter in lesson 1.4.
If your team is hybrid, a video one-on-one works fine. Keep cameras on and other windows closed. Take the call from somewhere quiet, away from a noisy open-plan desk where the other person can't speak freely.
Before you add anything else to your calendar, settle the rhythm for each person on your team and the rule you will follow when something gets in the way.
Decide how often you will meet each direct report and for how long. Write it down, along with what you will do when a meeting clashes with something else.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).