One-on-ones that aren't a waste of time

It is a Tuesday at 3 p.m. Arun, a senior analyst, has been waiting for his weekly 1:1 with his manager, Divya, for forty minutes. She is still on another call. At 3:45, she sends a message: “Sorry, crazy day, let’s pick this up next week.” Arun closes his laptop and goes back to his task queue.

This has happened four times in six weeks. Arun is in the middle of deciding whether to accept a competing offer. He has not told Divya. She does not know he is deciding. She thinks everything is fine.

This is not unusual. It is the most common failure mode in the manager-report relationship, and it is entirely invisible to the person causing it.

What a 1:1 actually is

A 1:1 — a one-on-one meeting between a manager and a direct report, held on a regular cadence, usually weekly or biweekly — is the report’s meeting. Not the manager’s.

That distinction sounds minor. It is not. When a manager treats the 1:1 as a slot to run through project updates, to check on deadlines, to ask “where are we with that feature?” — they have inverted the purpose. Project status belongs in a shared document, a standup, or a project management tool. It is asynchronous information that does not require both people in a room at the same time.

What requires both people is everything else: the thing Arun is sitting on because there is no channel to raise it. The blocker that is technically his problem to solve but is actually a resourcing decision above his level. The feedback he has been wanting to give about how the team’s sprint planning works. The career direction question he is too uncertain to put in writing.

None of that surfaces in a status review. All of it shapes whether someone stays, grows, or quietly disengages.

The 1:1 is where you learn what is actually happening. A manager who skips them, or lets them drift into project check-ins, is running blind.

The three-part structure

There is a clean recurring structure that keeps 1:1s useful across weeks and months. Each part has a different owner.

Part one: their agenda. The report comes prepared with what they want to cover. Blockers. Something they are uncertain about. A conflict with another team. A decision they want to think through out loud. Feedback they want to give. The manager’s job in this section is to listen and ask. Not to solve immediately, not to reassign the problem upward, not to interrupt with “yes I know about that, I’ll handle it.” To understand what the person is carrying and whether it is stuck.

If the report shows up with nothing, that is itself a signal worth probing. “Is there anything weighing on you right now that we haven’t had a chance to talk about?” is a more specific version of “any updates?” One of them tends to open people up.

Part two: the manager’s agenda. The manager brings one to two things they want to share or discuss. A shift in organisational priorities the report should know about. Positive recognition for something specific. A performance observation that needs saying. Context about a decision that affects them. This part should be short. If the manager consistently has more to say than the report, something is wrong.

Part three: growth. The last five to ten minutes belong to the future. What is the person working toward? What is one thing from the past two weeks that they learned something from? What would make next month better than this month? This section will feel forced for the first few cycles. That is normal. It becomes natural around week four, and by month three it is where the most important conversations happen.

Questions that actually open people up

Most managers ask, “How are things going?” This is a closed question wearing an open costume. The answer is almost always “fine” or “pretty good,” because “fine” is socially safe and requires no vulnerability.

Here are questions with more traction:

“What’s the one thing slowing you down right now that you haven’t had a good forum to raise?” This is specific enough that it implies there is something — it gives permission to surface it.

“Is there a decision you’re waiting on someone else to make?” This catches blockers that the report has categorised as someone else’s problem and therefore not worth mentioning.

“What’s something you’ve been uncertain about this week?” Uncertainty is the precursor to both learning and disengagement. Naming it out loud either helps the person think through it, or surfaces something the manager needs to know.

“Is there anything you’ve been wanting to tell me but haven’t found the right moment?” This is the highest-yield question and the most uncomfortable to ask. Use it every four to six weeks, not every session. When asked with genuine curiosity — not as a managerial formula — it is the question that produces the conversation you did not know you needed to have.

The goal of these questions is not to perform psychological safety. It is to make the 1:1 a place where real information travels. Real information is the entire value of the meeting.

Following through on what you hear

This is where most managers drop the ball. The 1:1 surfaces something real — a frustration, a request, an ambition the person has shared — and then nothing happens. The manager nods, says “I’ll look into that,” and moves on to the next item. Two weeks later, at the next 1:1, neither person mentions it.

The report notices. They do not say anything. But they have updated their mental model: the 1:1 is a place where things get raised and then disappear. The next time there is something worth raising, the activation energy is higher. Over time, the 1:1 becomes a performance — a place where both parties show up and go through the motions.

Following through does not mean resolving everything. It means closing the loop, even when the answer is “I looked into it and here’s why it’s not something we can change right now.” A clear no with reasoning is more useful than silence. It tells the person their input was received and considered, not collected and discarded.

A simple practice: keep a shared note with the report, updated after each 1:1. A few lines capturing what was raised, what was agreed, and what needs follow-up. Both people can see it. Both people are accountable to it. This costs three minutes and changes the entire quality of the relationship.

Why cancelling quietly erodes trust

Back to Arun. Divya has not cancelled the 1:1 with malicious intent. She is genuinely busy. The competing call overran. She messaged as soon as she could. From her perspective, this is a scheduling inconvenience.

From Arun’s perspective, here is what has happened four times: he prepared, he cleared his schedule, he was ready to have a conversation, and then the message came: not today.

The message that travels is not “I’m busy.” The message is “you are lower priority than whatever else came up.” People are not fragile, and they understand genuine calendar chaos. But four times in six weeks, without a rescheduled slot offered each time, without any acknowledgment that something of value was lost — that pattern communicates something about how much this person’s development matters.

In a high-trust relationship — one built over months of consistent 1:1s — a cancelled meeting is a minor inconvenience. In a fragile or nascent relationship, it is a data point that compounds. The person most likely to leave is the person who has concluded, correctly or not, that their manager is not invested in them. Cancelled 1:1s are the clearest outward sign of exactly that.

The rule is simple: if you must cancel, reschedule in the same message, for the same week if possible. “Can’t make today — are you free Thursday at 2?” is not a small gesture. It is a signal that the meeting matters.

The 1:1 as a diagnostic tool

A manager who runs 1:1s well has an information advantage. When a project hits turbulence, they already know which team members are stretched, which ones are uncertain about their role, which ones have a quiet grievance that has been building for two months. They can act earlier. Their interventions are less disruptive because they are less delayed.

A manager who skips or degrades their 1:1s is operating on a lag. They find out about problems when those problems are already visible — in missed deadlines, in a resignation letter, in a team retrospective where finally, in a structured group setting, someone says what has been true for months.

The 1:1 does not solve organisational dysfunction. If the culture is broken, one good conversation per week will not fix it. But it is the cheapest, highest-return signal-gathering mechanism available to any manager. One hour, once a week, consistently held, with someone who genuinely owns the agenda. That is the whole investment.

Arun still has the competing offer on his desk. What would have happened if the last four 1:1s had run? He might have mentioned the offer. Divya might have had a real conversation about his trajectory. That conversation might not have changed his decision, but it would have been the conversation both of them deserved to have.

The meeting is on the calendar. The only question is what you do with it.