Insights

← Back to Insights

The 1:1 Meeting Most Managers Are Running Wrong

Manager conducting a 1:1 meeting

A 1:1 where the manager says "so what's going on with project X?" and the direct report spends 45 minutes recapping status is not a 1:1. It's a standup with a private audience. The manager has confused the meeting's purpose: the 1:1 exists to develop the person, not to track the work.

This distinction sounds obvious, but it changes everything about how the meeting should be structured, who drives it, and what topics belong in it. Most managers running status-based 1:1s are doing so because nobody told them there was another way. There is.

The Direct Report Owns the Agenda

The highest-functioning 1:1 relationships we've observed across our 2,400 trained managers share one structural feature: the direct report owns the agenda. The manager may add items, but the starting point is always the direct report's list. This reversal of the typical dynamic - where the manager runs the meeting - changes what gets discussed.

When managers own the agenda, conversations skew toward what the manager wants to know. When direct reports own the agenda, conversations skew toward what the direct report needs help with. Those are very different meetings. The second version builds trust faster, surfaces problems earlier, and makes the direct report feel like the meeting is for them, not surveillance on them.

Practically, this looks like sending a shared document link the day before with three prompts: what are you working through right now? What do you need from me this week? Anything on your mind that's not work-related? Not every direct report will fill it out consistently, but the ones who do will have substantially better 1:1s within two weeks.

The Status Update Problem

Project status has a home - it's your project management tool. When a manager asks about project status in a 1:1, they are either not using their PM tool or they don't trust it. Either way, the fix is not to use the 1:1 for status. The fix is to make the PM tool work.

This is not a small point. Every minute spent on status updates in a 1:1 is a minute not spent on career development, team dynamics, cross-functional blockers, or the kind of candid reflection that only happens in private. A manager who spends 80% of their 1:1s on status updates is missing the meeting's only unique value: the private channel with a single person who reports to them.

There are legitimate status topics in a 1:1. If a project is going sideways and the direct report is stressed about it, that stress belongs in the 1:1. The project status does not. "I'm worried that the client isn't aligned and I'm not sure what to do about it" is a 1:1 topic. "The deliverable is due Friday" is not.

Four Questions That Actually Work

When managers in our cohort programs ask for a starting structure, we give them four questions. These are not prompts to read aloud - they're categories to work from:

1. What's taking more energy than it should right now? This question surfaces friction that doesn't show up in status reports. The direct report might mention an internal stakeholder who keeps moving goalposts, a process that creates unnecessary rework, or a relationship on the team that's gotten strained. These are the things you need to know and won't find out if you're asking about deliverables.

2. What have you learned recently that's changed how you think about the work? This question does two things: it signals that you expect ongoing learning (which raises the baseline), and it lets you see how the person is developing over time. If a direct report can't answer this question three 1:1s in a row, that's useful information about their engagement or growth trajectory.

3. Where do you want to be in 18 months? Career development conversations have a habit of getting deferred indefinitely. Putting a version of this question into the regular 1:1 rotation - even once a month - prevents the "we never talk about my career" feedback that shows up in exit interviews. The specific timeframe matters: 18 months is concrete enough to generate real answers but far enough out that people aren't defensive about it.

4. What do you need from me that you're not getting? This is the hardest question to ask because the answer is often uncomfortable. It requires the manager to be genuinely ready to hear criticism and to do something with it. But it's the question that turns 1:1s from one-directional development conversations into actual two-way relationships.

Frequency and Length

The research on 1:1 frequency is clearer than most managers expect. Weekly 30-minute meetings outperform bi-weekly 60-minute meetings for trust-building and issue surfacing. The reason is cadence: problems that surface weekly get addressed in small increments before they compound. Problems that surface every two weeks have often already calcified into interpersonal friction or project failures.

For new managers or managers with new direct reports, weekly 45-minute meetings for the first 90 days are worth the time investment. The relationship foundation you build in that period determines how much candor you get in year two.

Skip 1:1s have a documented cost. Harvard Business Review research on manager behaviors found that teams where managers frequently cancelled or skipped 1:1s had meaningfully lower scores on psychological safety and upward feedback. When you cancel a 1:1, you are not freeing up 30 minutes - you are communicating that the direct report's development is lower priority than whatever replaced the meeting.

When 1:1s Feel Awkward

New managers often report that early 1:1s with their former peers feel awkward. This is normal. The relationship has changed and neither party is sure of the new dynamic yet. The mistake is to resolve that awkwardness by filling the meeting with tasks and status - going back to familiar ground. The better move is to name it directly: "I know this is a different kind of relationship than we had before. I want to make these meetings useful for you. What would that look like?"

Most direct reports have never been asked that question. The act of asking it does more to reset the relationship than any technique or framework.

The Manager's Accountability in the 1:1

A 1:1 where the manager takes no notes and follows up on nothing is a performance, not a meeting. The direct report will notice within three sessions that nothing they said had any downstream effect. After that, the 1:1 becomes a formality that both parties endure.

The minimum viable follow-through is one committed action per meeting. "I'll connect you with the finance team lead by Thursday" or "I'll look into whether that process can be changed" or even "I'll think about that and come back to you next week." Commitments honored consistently build the trust that makes direct reports willing to bring real problems to the meeting.

For more on building the feedback relationship that makes 1:1s productive, see our piece on feedback that actually changes behavior. The 1:1 is where feedback happens - getting the meeting right and getting feedback right are inseparable skills.

Want help redesigning your 1:1 practice? Our cohort programs include a dedicated session on 1:1 structure, with peer review of actual agendas and follow-through systems. Explore cohort programs →