One-on-One Meetings: Agenda Template, Questions, and How Skip-Levels Fit In (2026)

Two managers, same company, same weekly 30-minute slot. The first asks where we are on the migration, hears that it is on track for Thursday, asks about the vendor, hears that they are waiting, asks if there is anything else, hears no, and gets eleven minutes back. Every fact in that conversation was already in Jira. The second asks what is on your list today, and finds out that a vendor has been stonewalling one of their best people for a month, that the person has started to think it is about them, and that the same thing is happening in the platform review. Same half hour. The difference is not that one of them is a better listener.

What is a one-on-one meeting?

A one-on-one, written variously as a 1:1 or 1 on 1, is a recurring private conversation between a manager and a direct report. It exists for the things that surface nowhere else: friction, ambiguity, frustration, ambition, and the early signals of a problem that has not happened yet.

That definition rules out what most of them become. If everything discussed could have been read in a project tracker, the meeting added nothing the tracker did not already contain, and both people will correctly feel it was a waste.

The cleanest diagnostic is who sets the agenda. In a working 1:1, the report brings most of the content and the manager brings context, feedback and priorities. In a status update, the manager works down a checklist and the report answers. There is no third option, and the drift is always in the same direction.

The one-on-one meeting agenda template

Five blocks in 30 minutes. The order is the design: whatever is discussed first establishes what the meeting is for.

Their agenda comes first and gets the most time.Open with "what is on your list today?" and then say nothing. If they genuinely have nothing, ask what has been hardest this week rather than filling the gap yourself. Starting anywhere else converts the meeting into your meeting permanently, and it is very hard to convert back.

Ask about blockers in the right shape."Are you blocked?" reliably gets a no, because it sounds like an accusation of not coping. "What is slower than it should be?" gets an answer. Then finish the block by assigning the blocker to a name, which is usually yours.

Your agenda is context and feedback, not announcements. Things they cannot see from where they sit, one specific piece of feedback, and priorities. Company news belongs in a team channel; using a scarce private conversation to broadcast is a waste of the only slot you have.

Growth goes in monthly, not annually. Ten minutes a month on the development plan beats a ninety-minute conversation once a year, because the annual version competes with a rating and the monthly version does not.

Close the loop in writing before anyone leaves. Read back the actions and who owns each, into a doc you both edit. Unwritten commitments that get forgotten are the single most reliable way to teach someone to stop bringing you real problems.

One-on-one meeting questions

Ask two or three, not twelve. A list worked through in order is an interrogation, and it produces the answers people give to interrogations.

The technique that matters is the second question."Fine" is not an answer, it is the end of the first one. Follow it with "what made it fine rather than good?" or "where else does that happen?" and then wait. The silence will feel longer than is comfortable, and the thing that arrives after it is the reason the meeting exists.

A few of these questions do double duty as early warning. How sustainable is your current workload, honestly? and when did you last feel genuinely proud of something here? tend to surface the conditions that show up months later in your turnover numbers, and they are considerably cheaper to hear now than in an exit interview.

How often, and how long?

Weekly, 25 to 30 minutes, as a default. Frequency should track tenure and rate of change, not seniority, which is the variable most organisations accidentally use.

Cancelling does more damage than any cadence choice. A slot cancelled twice in a row has told the other person exactly where they rank, and they will stop saving things up for it. If you have to, move it rather than dropping it, and say why. The cost of this is invisible until somebody resigns and you realise you had not had a real conversation with them since March.

The first one-on-one with a new employee

Whether they are new to the company or you are new to them, spend this one on how you will work together rather than on the work.

Step three is the one people skip and the one that buys the most credibility. Naming a specific thing others find frustrating about working with you does more than any amount of stated openness, because it demonstrates the behaviour instead of promising it.

Step four connects directly to whether this hire is still around next year. Agreeing what good looks like at day 30, 60 and 90 in writing is the same discipline as a 30-60-90 day plan, and the ambiguity it removes is what a large share of early exits trace back to.

If you are the report: what to ask your manager

The meeting is nominally yours and most people arrive with nothing, which is how it becomes a status update by default. Four questions carry most of the value.

• "What does great look like in this role six months from now?" The fastest way to find out whether your picture of the job matches theirs. Mismatches here are common and expensive.
• "What am I not seeing from where I sit?" Asks for context rather than reassurance, and usually gets it.
• "Is there anything you would want me to do differently?" A lower-stakes way to request corrective feedback than asking for a formal review, and far easier for a conflict-averse manager to answer.
• "What would make me ready for more?" Turns a vague ambition into a next step, and it pairs naturally with bringing a development plan of your own.

Beyond the questions, one habit outperforms all of them: bring a short list every week. A report who consistently arrives with three things gets a materially more useful manager than one who waits to be asked, and the difference compounds over a couple of years.

Skip-level meetings

A skip-level meetingis a conversation with your manager's manager, skipping the level between. Done as a routine it is one of the better information sources a senior leader has. Done occasionally and quietly, it corrodes trust in two directions at once.

Ask about the system, not the person in between. The most productive question in the set is is there anything you have raised that you feel went nowhere?, because it locates the places where feedback enters your organisation and quietly disappears. The question to never ask is how is your manager doing?, which invites an appraisal nobody can answer safely and puts the employee in an impossible spot.

Three rules keep it from undermining the manager. Tell them it is happening and roughly what you ask, beforehand. Give them the themes afterwards, framed as patterns, never the quotes. And route anything actionable back through them rather than acting directly, with the obvious exception of things that should not go through them at all, meaning harassment, safety or similar, which go to the channel that exists for them.

The framing matters as much as the mechanics. A skip level is for context, not an appeal court. Once people learn they can relitigate ordinary decisions one level up, the manager's authority erodes and you will spend longer repairing that than the information was worth. This is the same balance that makes structured processes work elsewhere: the value comes from the routine, not from the exception.

Notes, follow-through, and what happens between meetings

Keep a shared running document that both people edit. It solves two problems at once: the meeting that opens with awkward silence because nobody remembered their items, and the far more damaging one below.

The failure that ends candour is a manager who agrees to remove a blocker and then forgets. Once, and the report notices. Twice, and they quietly stop raising things, and from that point you are running a status update whether you have noticed or not. Nothing else in this article matters as much as closing the loop on what you said you would do.

One boundary worth holding: do not keep performance notes in the shared doc. Those belong in your own records. Someone discovering an assessment of themselves in a file they thought was collaborative is a breach of trust that does not get repaired, and it is entirely avoidable.

Remote and distributed one-on-ones

Hold them more often, not less. In an office you notice that someone is having a bad week without anyone saying so. Remotely, that information does not exist unless the meeting creates it, and the first indication can be a resignation.

• Video on, screen share off. The moment a screen is shared the conversation becomes a work review, which is the exact thing you were trying to avoid.
• The shared agenda doc matters more here. There is no corridor in which to mention a small thing, so items have to have somewhere to accumulate.
• Be deliberate about the first two minutes. Remote calls start abruptly, with none of the walk-to-the-room conversation that lets people warm up before saying something difficult.

The mistakes that turn a 1:1 into a waste of 30 minutes

• Running it as a status update. Duplicates the tracker and teaches both people the meeting is pointless.
• Opening with your agenda. Establishes whose meeting it is, permanently.
• Cancelling it. The most damaging single act available to you here.
• Filling the silence. The useful answer arrives after the pause that feels too long.
• Never asking a second question.Every answer stops at "fine", and you conclude everything is fine.
• Saving growth for the annual review. Where it has to compete with a rating and loses.
• Taking no notes, then forgetting an action. Quietly ends the flow of real problems.
• Using it to deliver team announcements. A waste of the only private slot you have.
• First corrective feedback given in a formal review. Turns a small correction into a surprise, and surprises in reviews cost trust out of all proportion to the substance. Our guide to performance reviews covers why nothing in one should ever be new.

Every one-on-one comes down to one test you can apply on the way out: did I learn something I could not have read somewhere else? If the answer is no for three weeks running, the problem is not the person on the other side of the table, it is that the meeting has quietly become a report. Give the agenda back, open with a question, and wait longer than feels comfortable. And when what you keep hearing at the 30-day mark is that the job is not the one the interview described, that is a hiring signal rather than a management one: paste the job description and your applicant batch into Rankid's bulk resume screening and check that the shortlist matches the work as it actually exists.