A manager with eight reports meeting each weekly for thirty minutes spends four hours a week in one-to-ones. Over a year that's a significant portion of their working time, and it's frequently spent on the least valuable available use.
The failure mode is consistent and easy to describe: the meeting becomes a status update.
Why status updates are the wrong content
Status information is asynchronous by nature. What somebody is working on, what's done, what's blocked — all of this can be written down and read at leisure.
Using synchronous time for it wastes the one thing a meeting provides, which is the ability to have a conversation that couldn't happen in writing.
Worse, the status format tends to crowd out everything else. Thirty minutes of project updates leaves no room for the difficult conversation, and the difficult conversation is why the meeting exists.
There's also a subtle framing problem. A meeting structured around reporting progress positions the employee as accountable to the manager, which shapes what gets said. People don't volunteer that they're struggling in a forum designed for demonstrating that they're delivering.
Whose meeting it is
The most useful principle I've encountered: the one-to-one belongs to the report, not the manager.
That means they set the agenda. The manager's items get raised if there's time, and mostly there shouldn't be a queue of them, because manager-to-report information generally flows fine through other channels.
This inverts the usual dynamic and it changes what gets discussed. When the employee owns the agenda, the content shifts towards what they actually need — obstacles, decisions they can't make alone, career questions, things they're uncertain about.
Practically: a shared document where either party adds items during the week, and the report goes first.
What good content looks like
The things worth spending synchronous time on.
Obstacles that require someone with more authority. The single most valuable use. A person blocked by something outside their control, and a manager who can remove it.
Decisions with genuine ambiguity. Where the right answer isn't obvious and thinking aloud with somebody helps.
Feedback in both directions. Specific, timely, about something recent. Not saved for a review.
Development and direction. Where the person is heading, what they want to learn, whether the current work serves that. This gets consistently squeezed out and it's the thing people most want to discuss.
Context. What's happening in the wider organisation that affects them. People make better decisions with more context and managers systematically under-share it.
The cancellation problem
One-to-ones are the easiest meeting to cancel. There's no external party, no deadline, and something urgent always exists.
The signal sent by repeated cancellation is unambiguous and it's worse than not having the meeting at all. It communicates that this person's time is the flexible item in the schedule.
Rescheduling is fine. Cancelling repeatedly is not, and managers who do it are generally unaware of how it's read.
Frequency
Weekly is standard and isn't always right.
Weekly suits people who are new, in a changing role, or facing significant ambiguity. Fortnightly is often sufficient for experienced people in stable roles, and forcing weekly meetings when there's nothing to discuss trains everybody to fill time with status updates.
The better approach is to set a default and revisit it. Asking directly whether the frequency is right is a reasonable question and it's almost never asked.
The questions that work
Generic openings produce generic answers. Some that reliably get somewhere:
"What's frustrating you at the moment?" Direct, invites the complaint people are otherwise holding.
"What are you spending time on that you don't think is worth it?" Surfaces process problems and gives permission to criticise how things are done.
"What do you need from me that you're not getting?" Awkward and productive.
"What's something you'd like to be doing more of?" The development question, asked in a form people can answer.
And silence. The most underused technique in management. Ask a question, then wait. People fill silence, and what they fill it with is frequently the thing they weren't going to say.
Notes and follow-through
Whatever is agreed should be written down and revisited at the start of the next meeting.
The reason isn't administrative. It's that a commitment made in a one-to-one and never mentioned again teaches the person that the meeting doesn't produce outcomes, which means next time they'll bring less.
Credibility in this format is built entirely through follow-through, and it's destroyed quite quickly by the absence of it.
When the relationship is difficult
The format struggles most where it is needed most: when manager and report do not get on, or when performance is a live issue.
The temptation then is to make the meeting purely transactional — cover the work, keep it short, avoid the difficult ground. That is understandable and it guarantees nothing improves.
What works better is naming the situation directly and separating it from the routine. A specific, scheduled conversation about the difficulty, with a stated purpose, rather than letting it contaminate every weekly meeting indefinitely.
It is uncomfortable and it is the actual job. A manager who avoids that conversation for six months has usually made the eventual outcome worse for everybody, including the person they were trying not to upset.