For about a year, my 1-on-1s went like this. I'd ask "how's the API work going?", the engineer would walk me through their open tickets, I'd nod, we'd both agree things were "on track", and then we'd give each other eight minutes back. I thought I was being respectful of their time. I was actually just running a slower, more awkward standup.
Gallup found that employees whose managers hold regular meetings with them are nearly three times as likely to be engaged. But "regular" is doing a lot of work in that sentence. Holding the meeting isn't the thing. I held mine religiously and still learned almost nothing about the people in them.
Here's the uncomfortable bit: the fix wasn't a better template or a fancier tool. It was me shutting up.
How 1-on-1s actually die
There are two failure modes and I've run both.
The status recap. You spend the time re-narrating work that already lives in Jira, the standup channel, and the PR queue. If your manager could reconstruct the whole conversation from your board, you didn't have a 1-on-1. You had a meeting that should have been a link.
The friendly void. The opposite trap. "How's things? Good? Cool, anything you need? No? Great." Twelve minutes of pleasantness and zero signal. Nobody admits a problem because nothing in the conversation invited one.
Both feel fine in the moment. Both leave you blind. The first time one of my best engineers told me she'd been quietly interviewing elsewhere, I realised I'd had roughly forty 1-on-1s with her that year and not one of them had gone anywhere near the thing that was actually bothering her.
What changed
I made four changes over about six weeks. None of them are clever. All of them were harder to do than to describe.
I gave away the agenda. We keep one shared doc per person. They add topics during the week, I add mine underneath, and theirs go first. The blank-page panic at 2pm disappeared because the doc was never blank. The first week I tried this, an engineer added "I think we're testing the wrong things" as a bullet. That conversation would never have happened if I'd owned the agenda.
I went quiet for the first ten minutes. Genuinely quiet. I'd ask one open question and then sit in the silence instead of rescuing it. People fill silence with the stuff they've been sitting on. I learned more in those awkward ten-second pauses than in any amount of my own talking.
I banned the status recap from my side. No "so where are we on the migration". If I needed a project update I got it async, before the meeting, so the 1-on-1 itself could be about friction and not facts.
I started writing down who owns what. Two lines at the end: my commitments and theirs. Then I'd open the next session with them. The single biggest trust-killer I've found is raising something real and watching it evaporate, so I stopped letting it evaporate.
Where the status camp is right
I want to be fair to past-me, because there are real cases where a more directive 1-on-1 is the correct call.
New hires in their first month need more structure, not less. They don't yet know what's normal, so "anything on your mind?" gets you a blank look. You drive more, ask narrower questions, and check understanding.
Same for anyone in a genuine crisis week. If prod is on fire, the 1-on-1 can absolutely be tactical, and pretending otherwise to protect the format is silly. The point isn't that status is forbidden. It's that status should be the exception you choose, not the default you fall into because neither of you prepared.
Questions that aren't "any blockers?"
The fastest upgrade after handing over the agenda is having better questions ready for the weeks the doc is thin. "Any blockers?" trains people to say no. These don't:
- What's the most annoying part of your week that you've stopped mentioning because you assume it can't change?
- If you imagine quitting in six months, what's the most likely reason in that story?
- What's something you shipped or fixed recently that I probably didn't notice?
- Who or what is making your work harder right now, and is that mine to fix or yours?
- What do you want to be spending more time on that you're not getting to?
Rotate them. The same five questions every week become their own kind of status meeting.
The part where I mention the tool
I work on Kollabe, so apply the appropriate grain of salt here. The patterns above generalise; if your stack does this differently, swap in the equivalent and ignore the plug.
The thing I reach for when the agenda doc is thin is our free 1-on-1 question generator. You tell it your role and what you want to dig into, say career stuff with a senior engineer who's gone quiet, or a first 1-on-1 with someone you just inherited, and it gives you a tailored set to pull from. I don't read them off like a script. I skim, pick two that fit the person, and let the conversation wander from there. It mostly exists to kill the blank-page problem on a Monday when my brain isn't online yet.
That's the only product bit. Any notebook and a bit of discipline gets you most of the way.
A rule of thumb you can use Monday
Here's the test I run on myself now, in the last minute of every 1-on-1:
Could a Jira board have told me everything I just heard?
If the answer is yes, I ran a status meeting and I wasted the one slot in the week that's supposed to be theirs. If the answer is no, if I heard something a board could never surface, a frustration, an ambition, a quiet "I'm not sure this is working", then it was an actual 1-on-1.
It's a low bar. I failed it for a year.
The reframe that finally stuck for me: the 1-on-1 isn't your meeting to run, it's their meeting to use. Your job is mostly to make it safe enough that they bring the real stuff, and then to not talk over it when they do. Try giving away the agenda for a month and see what lands in that doc. Worst case you get your eight minutes back. Best case you find out what your team has been quietly not telling you.
Top comments (0)