29 August 2026
The problem with most one-on-one question lists is that they're thirty prompts long and none of them lead anywhere. You need six or seven questions, grouped by what you're actually trying to learn, and a way to remember what the answer was last time.
Search for one-on-one questions and you get a list built for variety, not for depth. 'What's blocking you?' next to 'What's your favorite productivity hack?' next to 'Where do you see yourself in five years?' A manager reads three of these off a printout and the conversation feels like a survey, because it is one.
A good one-on-one question does one job: it opens a door the employee wouldn't have opened on their own. That means fewer questions, asked with a specific intent, not a rotating grab bag.
Group questions by what you're trying to find out, not by topic. There are really four things a manager needs from a one-on-one: what's stuck, what's changing, what's working, and what nobody's said yet.
Write down commitments, not opinions. If someone says they'll follow up with another team by Friday, that's a line in the notes with a date on it. If someone says they think the roadmap is too aggressive, that's not a note — that's a conversation, and writing it down changes what the conversation is.
The distinction matters because one-on-one notes have a second reader eventually: the employee themselves, six months later, wondering if anything they said mattered. Notes that are all commitments and follow-ups prove it did. Notes that are a transcript of someone's private frustration prove the opposite — that the room wasn't as private as it felt.
A rule that holds up in practice: write down what was decided or promised, skip what was merely felt. If a feeling turns into an action — 'I'm going to ask for more design review time' — that's worth a line. The feeling on its own isn't.
The failure mode of a good one-on-one is that it slowly becomes a status meeting, because status is easy to track and everything else isn't. The fix isn't to ban status — it's to give it two minutes at the start and move on, and to protect the thread that runs underneath it.
A thread is one open question that spans several meetings: the 'I think I want to move toward a lead role' conversation from six weeks ago, or the 'I'm not sure this project has a real owner' concern from last month. If you're not writing threads down separately from weekly notes, they die at the end of each individual meeting, and the person has to re-open the topic from scratch every time.
AVAY's transcript search helps here in a narrow but real way: if a manager wants to check what someone actually said about wanting more ownership three meetings ago, rather than what they remember them saying, they can search for it instead of relying on memory or flipping through old notes. It won't tell you which threads matter — that's still a judgment call — but it removes the excuse of 'I don't remember exactly how you phrased that.'
The template below is deliberately short. A one-on-one template with ten sections gets filled in once and abandoned; one with four gets used.
One or two, chosen deliberately, beats a rotating list of ten. A one-on-one is thirty minutes; spend it going deep on one thing rather than skimming five.
The commitments and follow-ups should be, since both people need to remember them. Anything that was said as a private concern rather than a decision generally shouldn't end up in a written note at all, shared or not.
Give status two minutes at the start, on purpose, so it doesn't expand to fill the meeting by default. Spend the rest on the one question and the open thread from last time.
An agenda is set before the meeting and mostly by the manager; a one-on-one template is a shape you fill in during the conversation, and half of it should be led by the employee. Treating it like an agenda is often what makes it feel like status.
Most don't, and for good reason — a one-on-one is often the one meeting where someone speaks more freely because there's no record. If notes are needed, a short written line on commitments serves the purpose without a transcript of the whole conversation.
A good one-on-one runs on a handful of specific questions, not thirty generic ones, and on notes that capture commitments rather than feelings — carried forward as an open thread instead of restarted from zero every two weeks.
AVAY is a video meeting platform that transcribes the call itself — no bot joins, because there is nothing to join. Start one at avay.ai, read how each part works in the documentation, or see what it costs.