There's a version of the weekly 1:1 that most of us have been in. It opens with "Hey, how's it going," and someone — probably the person with less power in the relationship — says "good, yeah, pretty good," and then they run through a list of what they're working on. The manager nods, asks a clarifying question, maybe writes something down. Thirty minutes. See you next week.
That meeting is not a 1:1. That meeting is a status update that happens to have only two people in it.
The real 1:1 is the one meeting on the calendar where the work isn't the point. It is the place where a person and the person who reports to them get to talk about anything other than the ticket on the board. It's where an engineer mentions, halfway through, that they've been thinking about whether they even want to be an engineer. It's where a designer asks, finally, whether the last round of feedback was a stylistic preference or a sign that the manager didn't trust them. It's where someone gets a raise six months before they would have asked for one, because a perceptive manager caught a signal the org chart would never have shown.
These things do not happen in status updates. They happen in the kind of conversation that takes place because both people showed up and meant to.
The quiet disappearance of the 1:1
Here's what I've watched happen, again and again, in every team I've been on:
The manager gets promoted. They have eight reports. Each report gets thirty minutes a week. Three of them are new; three of them are shipping hard; two of them are the people the manager was peers with six months ago, and those meetings are a little weird, and the manager, without really deciding to, starts rescheduling them. Then skipping them. Then not booking them at all.
By month four the manager is down to four 1:1s a week. By month six, two. The reports who are thriving don't seem to mind. The ones who aren't thriving are quietly getting worse, but the manager doesn't know that, because the meeting where they would have mentioned it is the meeting that got cancelled.
This is the most common failure mode in management and it is almost never framed as one. It's framed as being busy.
Being busy is not the reason
Being busy is the symptom. The reason is that a 1:1 is the only meeting on the calendar without a deliverable, and a manager under pressure will, without exception, drop the meeting without a deliverable first.
This is a mistake that compounds. A missed 1:1 is not a zero-cost event. It's a small withdrawal from a trust account that the manager is unconsciously relying on. The engineer who doesn't get the promotion conversation they were expecting. The designer whose burnout was visible six weeks before they quit. The report who's been underperforming for a month and didn't realize it, because nobody told them, because the telling-them meeting kept getting pushed.
The currency of management is attention, and the 1:1 is where you pay it. Skipping it is not free. It's just deferred.
What makes a 1:1 sacred
Three things, I think.
Continuity. The fact that you and the other person are going to have this same meeting next week, and the week after, changes what can be said in it. A one-off conversation has to resolve inside thirty minutes. A conversation that resumes next Thursday can open a door and leave it open. It can surface something that neither party has a plan for yet, and trust that there will be time to come back to it.
Context. The 1:1 is the only place the work context and the person context meet at full resolution. Every other meeting has been optimized — the stand-up is fifteen minutes, the review is two hours and has six people, the quarterly has slides. The 1:1 is the one place where an offhand remark about a kid being sick can sit next to a specific concern about the architecture of a service, and both are allowed.
Asymmetry. The 1:1 is not a meeting between peers. There is a power differential, and pretending otherwise is a failure of honesty. The manager's job is to hold that asymmetry carefully — to make the meeting feel safe without pretending the stakes don't exist. That's hard, and it's the reason most managers are bad at 1:1s for their first two years. It takes practice, and the only way to practice is to have the meeting every week.
What we're building, and why
I've spent a long time trying to get this meeting right, for myself and for the people who reported to me. I've used Google Docs and Notion and Fellow and the back of envelopes. None of them were the problem, exactly. The problem was that the tools were general-purpose, and the 1:1 is not general-purpose.
So we built Meetmora. It is a meeting tool that does one thing: it helps you have a weekly 1:1 that is actually a 1:1. It prepares the agenda from last week's open threads. It captures the conversation without turning the meeting into a transcription exercise. It remembers every commitment, so you can follow through in week four on something you said in week one, without having to go search for it.
It's small. It's on purpose.
A closing ask
If you're reading this and you've been skipping 1:1s, I want to make a small case for not skipping the one on your calendar this week. Not because a blog post told you to, and certainly not because a tool company suggested it. But because somewhere on your team, there is a person who has been waiting for a chance to tell you something they can only tell you in a meeting like that one.
That conversation is not going to happen in Slack. It's not going to happen in the standup. It's not going to happen in the review.
It's going to happen in the meeting on Thursday at 3:00 that nobody else is invited to.
Don't move it.
—
Nick Jones is the founder of Meetmora. He was an engineering manager for six years before he wasn't, and he regrets a specific 1:1 he cancelled in November 2021.