How to Structure a 1-on-1 Agenda That Actually Works

Published August 5, 2026

Most 1-on-1s don't fail because the manager doesn't care. They fail because nobody decided in advance what the meeting is actually for, so it defaults to the easiest available structure: a status update. The manager asks what's in progress, the report lists what they're working on, and fifteen minutes later everyone is relieved it's over. Gallup surveyed nearly 15,000 employees and found that only 16% said their last conversation with their manager was extremely meaningful. That's not a caring problem. It's a structure problem, and it's fixable with a few deliberate decisions about who owns the agenda, what belongs on it, and how long each part should get.

Who Should Actually Own the Agenda

Most people assume that because the manager runs the meeting, the manager should set the agenda. That assumption is backwards, and it is the single most consequential structural decision in the whole meeting.

When a manager fills the agenda, the report walks in to receive it. They answer questions, react to whatever the manager brought, and leave having said less than they meant to. When the report fills the agenda, they walk in to drive it. The same 30 minutes, the same two people, and a completely different conversation.

The mechanism is simple: give the report a place to add items before the meeting, not a blank page at the start of it. A shared, living agenda that both people can add to, with the report populating it first, does more to change the character of a 1-on-1 than any question list. The manager still gets to add their own topics. They just don't get to write the whole thing.

The Three Things Worth Covering Every Time

Camille Fournier, in The Manager's Path, describes a three-part structure that holds up better than the generic "wins, losses, and questions" format most templates default to:

Career. What is this person working toward, and is their current work actually moving them there? Not "how do you feel about your career," which invites a one-word answer, but something concrete: "the thing you said you wanted more of last quarter, has this month's work given you any of it?"

Current challenges. What's in their way right now, and is there anything only the manager can remove? This is deliberately narrower than "any blockers?" It's asking specifically for the blocker that requires the manager's authority, budget, or relationships to clear, not a technical problem the report is already handling.

Team dynamics. How are things going with the people around them, and is there friction that hasn't reached the surface yet? Most managers only hear about team friction once it's already a problem. Asking directly, in a private setting, is often the only way to hear about it earlier.

The reason this beats a vague bucket list is that each of the three questions forces something specific to fall out of the answer. "How's it going" invites "fine." "Is there anything only I can remove" invites a name, a decision, or a dependency.

How Long Each Part Should Actually Get

Gallup's research on manager conversations found that 15- to 30-minute conversations have a greater impact than 30- to 60-minute conversations, provided they happen regularly. The regularity matters more than the length. If a manager skips a few weeks, the next conversation has to run long just to catch up on everything that piled up in the gap, which is exactly the status-update trap this structure is trying to avoid.

A rough split for a 30-minute meeting: two or three minutes to actually arrive and settle in, ten minutes on current challenges, ten minutes on career or team dynamics (they don't both need airtime every single week), and the last five minutes closing on anything that needs a concrete next step. None of this needs to be rigid. The point of having a rough split is to notice when one topic is quietly eating the whole meeting every week, not to run a stopwatch.

Why the Same Five Sections Every Week Kills the Meeting

A fixed weekly agenda runs out of things to say. Most weeks, there is nothing new to report in the career section, so it either gets silently skipped, which signals to the report that it doesn't actually matter, or it gets padded with filler to fill the slot, which is worse.

The fix is to stop treating the agenda as one fixed document and start treating it as a set of sections that rotate. Current challenges and team dynamics are worth a quick check most weeks. Career and growth conversations are worth a real, unhurried slot monthly or quarterly, not a rushed five minutes wedged into a 30-minute meeting that also has three other jobs to do. A skip-level or performance-plan conversation needs its own structure entirely, not a bolt-on to the regular agenda.

This is where a static document starts to work against the manager. Restructuring a shared doc every few weeks, moving sections around, and remembering which version is current is exactly the kind of overhead that makes people give up and default back to "so, what are you working on."

A Practical Structure to Start From

A simple starting shape, before any customization:

  1. A quick check-in. One line on energy or workload, not a therapy session.
  2. What's in their way right now, and what specifically needs the manager's help to move.
  3. Anything about the team worth surfacing that hasn't come up elsewhere.
  4. Career or growth, on a rotating cadence rather than every week.
  5. Next steps, written down, with an owner attached to each one.

This is a starting shape, not a finished template. For a complete, ready-to-use version built for a specific situation, senior engineers, junior developers, onboarding, skip-levels, and a few others, the template library has full agendas already built out.

Build this agenda now, free.

Drag the sections above into place, customize them, and export a PDF. No account required.

Build Your Agenda Free

Or sign up to sync it automatically.

Frequently Asked Questions

Who should write the 1-on-1 agenda, the manager or the employee?

The employee should own most of it. When a manager fills the agenda, the report shows up to receive it and the meeting behaves like a status update. When the report fills it, they show up to drive it, and the same meeting behaves like a coaching conversation.

How long should a 1-on-1 meeting be?

Gallup's research found that 15- to 30-minute conversations have more impact than 30- to 60-minute conversations, as long as they happen regularly. Skip a few weeks and the next one needs to run longer just to catch up.

What shouldn't be in a 1-on-1 agenda?

Ticket status, sprint progress, and anything with its own tracking tool. If it already lives in Jira or a standup, repeating it here just burns the only 15-30 minutes you get with this person for something a dashboard already covers.

Related Guides