1:1 Meeting Template for Managers: Questions and Cadence
A 1:1 meeting template that isn't a status update — the questions that surface real issues, how often to meet, and the three ways these meetings quietly fail.
The most common way a 1:1 fails isn't that it doesn't happen — it's that it happens on schedule and is entirely status updates, indistinguishable from something that could've been an email. The entire value of a 1:1 is the conversation a status update format doesn't allow.
The cadence that actually works
Weekly, for anyone newer than about six months, anyone in a fast-changing role, or anyone a manager has specific concerns about. Problems compound quickly without frequent enough contact to catch them early.
Biweekly, for established employees in stable roles where weekly starts to feel like unnecessary overhead for both sides.
Never monthly, if it can be avoided. A month is long enough for a small frustration to become a resignation letter, and long enough that a manager finds out about a problem well after it started rather than while it was still small.
Twenty to thirty minutes is enough. Longer meetings tend to get filled with the status-update content that belongs somewhere else — a project tool, a written update — crowding out the actual conversation.
A structure that isn't a status report
Open with them, not with you. "What's on your mind this week" or "how are you feeling about things" hands the first few minutes to whatever the employee actually wants to talk about, rather than an agenda the manager brought in.
Ask what's frustrating, specifically. Not "how's it going" — that invites "fine." Ask what the most frustrating part of the week was, or what took longer than it should have. Specific questions get specific, useful answers.
Ask what they need that they're not getting. This is the question that surfaces resource gaps, unclear priorities, and blocked work before they become a missed deadline someone else discovers first.
Ask if there's anything hard to bring up. Not every week, but periodically — this is the question that catches the thing an employee has been sitting on because it felt too small, too awkward, or too late to raise on their own.
Close with something forward-looking, but keep it brief. A minute on priorities for the coming week is plenty; the meeting shouldn't end up as a project status meeting that happened to open with a personal check-in.
Questions worth rotating in
- What's the most frustrating part of your work right now?
- What do you need from me that you're not currently getting?
- Is there anything about your workload that feels off — too much, too little, or the wrong kind?
- What's something you wish I understood better about your work?
- Is there feedback you've been holding back?
- How are you feeling about your growth here, separate from your current project?
Not every question every time. Rotating through a few keeps the conversation from becoming as scripted as the status update it's meant to replace.
The three ways 1:1s quietly fail
They become status meetings. The manager asks "what are you working on," gets an update, and the meeting ends. This is the single most common failure mode, and it's easy to slide into because status is the comfortable, low-risk default topic for both people.
They get cancelled first when things get busy. Cancelling a 1:1 sends a clear, if unintended, signal about where it ranks in priority — and it's usually the weeks that feel too busy for a 1:1 where something actually needed to be said.
The manager does all the talking. A 1:1 dominated by the manager's updates, context, and direction isn't a 1:1 — it's a briefing. The ratio should tilt toward the employee talking more than the manager does.
These three patterns map closely onto specific, recognizable management styles — a short interactive diagnostic can help identify which one is quietly shaping how your own 1:1s tend to run.
Making time off part of the conversation, not a separate process
A 1:1 is also a natural place to notice patterns a request form never surfaces — someone who hasn't taken meaningful time off in months, or who mentions being tired without connecting it to their own unused balance. Bringing it up directly ("you've got twelve days sitting unused and the year's half over — want to plan something?") does more than any policy reminder, and it's a genuinely easy thing to check if balances are visible at a glance rather than something someone has to dig for.
What to do with what you hear
A 1:1 loses its value fast if what's raised there consistently goes nowhere. If an employee mentions a blocker or a frustration and nothing changes by the next 1:1, they learn quickly that raising it wasn't worth the discomfort, and the meeting reverts to status updates because that's what feels safe. This doesn't mean every issue needs to be solved immediately — sometimes the honest answer is "I hear this, here's why it's not fixable right now, and here's when I'll revisit it" — but it does mean following up matters more than the conversation itself. Keeping a short private note of what came up each week, and checking it before the next 1:1, is a simple way to make sure nothing raised in confidence quietly disappears.
Adjusting the format for a new manager
A first-time manager running 1:1s for the first time often defaults to status updates because it feels safer and more structured than an open-ended conversation. If that's the situation, it helps to pick two or three questions from the list above and use the same ones consistently for the first month or two, rather than trying to run a fully organic conversation from day one. The specific questions matter less than building the habit of asking something other than "what are you working on" — that skill develops with repetition, and a slightly scripted 1:1 that actually surfaces something real beats a free-flowing one that quietly becomes a status meeting.
The short version
A 1:1 earns its time when it surfaces something a status update wouldn't — frustration, a blocker, feedback that's been held back. Keep it short, weekly or biweekly, employee-led more than manager-led, and resist the pull toward status updates, which is where most 1:1s quietly become worthless without anyone deciding to cancel them outright.
Frequently asked questions
How often should managers have 1:1s with direct reports?
Weekly or biweekly for most roles. Weekly works better for newer employees or fast-moving work; biweekly is often enough once someone is established and the role is stable. Monthly is usually too infrequent to catch small problems before they grow.
How long should a 1:1 meeting be?
Twenty to thirty minutes is enough for most weekly or biweekly 1:1s. Longer meetings tend to get filled with status updates that belong in a different format, rather than the actual point of a 1:1 — a real, two-way conversation.
What's the difference between a 1:1 and a status update?
A status update is one-directional: what did you do, what's next. A 1:1 is the manager's chance to hear what a status update never surfaces — what's frustrating, what's unclear, what the employee needs that they haven't asked for directly.
What questions should a manager ask in a 1:1?
Questions that can't be answered with a project update: what's the most frustrating part of your week, what do you need from me that you're not currently getting, and is there anything you're not sure how to bring up. The specific list matters less than consistently leaving room for something other than status.