The five-minute meeting prep that replaces a thirty-minute one-on-one

A typical one-on-one runs thirty minutes. The first ten are status update, what the report is working on, what blockers they have, what's coming up. The next ten are management housekeeping, career conversation, performance feedback, the thing the manager wanted to follow up on. The last ten, if they exist, are the conversation worth having: the work problem that's been quietly bothering the report for a week, the team dynamic they're trying to figure out, the thing they came to the meeting actually needing to talk about.

Most one-on-ones never get to the last ten.

This is not because the manager is bad or the report is bad. It's because the first twenty are eating the budget. The status update is real, the manager does need to know what's being worked on, but the status update was written in the project tracker, the Slack channel, the standup. The manager already has it. They're reciting it for the form of the meeting, not for the information.

The fix isn't to skip the status update. It's to move it out of the meeting.

A one-on-one that opens with a shared note, what the report worked on, what they're stuck on, what they want to talk about, runs differently. The manager has read the note before the meeting starts. The status update doesn't happen, because the status is already shared. The first sentence of the meeting is: "Tell me about the thing you're stuck on." Not "Tell me what you've been working on."

The five-minute prep before the meeting is not a project status. It's the report's structured thinking about the conversation they want to have. What's surfacing for them this week. What they want to push back on. What they need from their manager that they didn't get last time. The manager prepares too, briefly, read the note, write one sentence about what they want to surface, ten seconds of reflection.

What changes is the texture of the meeting. The career conversation doesn't get buried under status. The honest concern about the team direction doesn't get raised at minute twenty-eight. The thirty minutes opens with the conversation that justified the meeting, not the recap.

The teams that have figured this out don't have a special template. They have a habit: the report writes the prep note the day before, the manager reads it the morning of, the meeting opens with whatever surfaced from that. The first sentence of every 1:1 is informed by the last twenty-four hours of the report's actual work, not by whatever they remember in the moment.

If your next 1:1 is tomorrow, the test is simple: what would you talk about, if the first twenty minutes of status update didn't happen? Whatever that is, that's the meeting. The prep before is just the thing that lets you skip to it.