He Noticed Everyone Else Getting One on Ones

At the very end of the call, almost as an afterthought, he said something I haven't been able to stop thinking about.

We'd had a good conversation. Casual, easy. We talked about the integration he was working on. I asked if he needed anything. He said he was good. I asked if he had any feedback for me. He said not really. And then, right as I was about to wrap it up, he said this:

"This is the first time like we are talking one on one. If I can get a link with other team members also - this is the first time I have seen, like, who will - for all the team members, one on ones are going on."

He'd been watching. He knew the one-on-ones were happening across the team. He'd seen them. And he had waited, quietly, without complaint, without escalation, without any alarm being raised anywhere. He just noted it. Carefully. At the very end of the call. The first one-on-one he'd ever had.

That hit me harder than I expected it to.

The Exclusion Nobody Measures

There's a kind of exclusion that's easy to spot and easy to fix - the loud kind. Someone gets passed over for a promotion. Someone's not invited to a meeting they should be in. Someone's contribution goes uncredited. These things surface. People notice. You course-correct.

Then there's this other kind. The quiet kind. The kind where someone sits at their desk, doing their job, watching inclusion happen around them, and says nothing. They're not dramatic about it. They don't send a passive-aggressive Slack message. They don't cc anybody on a complaint email. They just observe, absorb, and keep working.

And here's what's actually happening inside them during that time: they're building a case. Not a legal case. A psychological one. Every day that passes without their one-on-one, they're filing away evidence. Evidence that they're slightly less important. Evidence that their concerns matter slightly less. Evidence that when the team talks about "everyone getting access," everyone doesn't quite mean them.

Nobody sees this happening. No dashboard metric moves. No retention risk flag gets raised. It's completely invisible until one day - maybe they leave, maybe they check out, maybe they just stop putting in the extra effort - and by then it's too late to trace it back to the real cause.

This is the most corrosive kind of organizational damage. It accumulates in silence.

Why One-on-Ones Are Not Optional

I've run a lot of teams across a lot of businesses. Agency teams, SaaS teams, content teams, sales teams. And the single biggest mistake I see founders and managers make - especially when things are moving fast and there's always something more urgent on the calendar - is treating one-on-ones as a nice-to-have.

They're not. They're the foundation of trust between a manager and an individual contributor. And trust, once eroded, is genuinely expensive to rebuild. Much more expensive than a 30-minute call every few weeks.

The reason one-on-ones feel optional is because skipping them doesn't cause an immediate visible problem. Unlike missing a client deadline or shipping broken code, there's no incident report when you fail to check in with your people. The cost is deferred. It shows up months later as disengagement, quiet quitting, or turnover - and by that point, everybody's forgotten that the root cause was something as simple and fixable as "nobody talked to him."

This developer was doing excellent work. In our call, he walked me through the integration he was building - handling the UI challenges, coordinating across a split team, communicating with two other team members on different parts of the project. He was professional, thoughtful, and clearly on top of his work. He wasn't struggling. He didn't need help. But he still needed the call. Not for problem-solving. For belonging.

The Observation Effect

What made his comment particularly striking was the precision of it. He didn't say "I've never had a one-on-one." He said he'd observed one-on-ones happening across the team. He had catalogued them. He knew the pattern.

That's the observation effect. People inside organizations are not passive. They're watching. They're tracking. They notice who gets face time with leadership and who doesn't. They notice who gets the benefit of the doubt in ambiguous situations. They notice who gets asked for their opinion in meetings and who gets talked over. They notice everything - and then they use what they notice to draw conclusions about their own value to the organization.

This is not unique to any one type of person or any one type of company. It's human. When you're part of a group, you're constantly calibrating your position within that group. You're asking: Do I belong here? Am I valued? Am I included? And you're answering those questions not based on what people say to you, but based on what you observe happening around you.

When he watched every other team member get one-on-ones except him, his brain was running that calculation. And the answer it kept arriving at was: probably not the top priority. Probably not the most valued. Probably not quite as included as the rest.

He never said any of that out loud. He didn't need to. It was already doing its work beneath the surface.

What Happens When You Finally Have the Call

I want to talk about what actually changed the moment the call happened. Because something interesting occurred.

When he made that comment at the end - noting that this was his first one-on-one and that he'd been watching the others happen - the tone was not accusatory. It wasn't resentful. It was almost… relieved. Like he was gently registering something that had been weighing on him, now that it was finally safe to register it.

That's what access to a leader does for someone. It doesn't just solve problems. It creates a container in which problems can be acknowledged - even small ones, even ones the person wasn't consciously aware they were carrying. The one-on-one itself was the remedy. Not anything that was said in it. Just the fact that it happened.

That's a wild amount of value to leave on the table by not scheduling a 30-minute call.

The Practical Part: How to Actually Do This

If you're running a team of any size and you don't have a structured one-on-one cadence, fix that this week. Not next sprint, not next quarter. This week.

Here's what I've found works:

• Make it recurring, not ad hoc. The moment one-on-ones are "whenever there's something to discuss," they stop happening. People don't want to seem like they're bothering you, so they don't initiate. You put them on the calendar first, and they're always there.
• Keep them short. Thirty minutes is plenty. The goal is not to conduct a full performance review every two weeks. The goal is face time. Connection. A chance to ask "how are things going" and actually mean it.
• Actually ask how things are going. In my call, I asked: Is there anywhere you need help? Is there anything you wish I could do differently? These are real questions, not formalities. Ask them and then actually listen to the answer. Most of the time people will say everything's fine. But occasionally they'll tell you something you genuinely needed to know.
• Don't rely on the person to surface their own problems. This developer wasn't going to email me and say "I haven't had my one-on-one yet." Almost nobody does that. The onus is on the manager. You have to go get the information. You cannot wait for it to come to you.
• Make sure the whole team is on the rotation. This sounds obvious and it's apparently not, because it's exactly what went wrong here. Someone fell through the cracks. It happens. Build a system - a spreadsheet, a recurring event, whatever - that makes it impossible to accidentally skip someone for weeks on end.

The Deeper Principle: Belonging Is a Felt Experience, Not a Stated Policy

I've seen companies put "people first" in their values doc and then functionally treat their team like interchangeable units. I've also seen scrappy bootstrapped operations with nothing written down anywhere that somehow make every single person feel like they matter. The difference is not the policy. It's the behavior.

Belonging is not something you can install by updating the employee handbook. It's something people feel through a thousand small interactions over time. A name remembered. A question asked. A call that actually happened when it was supposed to. These are not soft things - they're the infrastructure of a functional team. You cannot build a high-performance organization on top of a foundation where people are silently asking themselves whether they're actually part of the group.

And the tricky part is that the people most affected by this are often the least likely to say anything. They're not disruptive. They're not high-maintenance. They show up, they do their work, they navigate the challenges in front of them. They're the people you'd describe as "doing great" if someone asked - because from the outside, they are. The internal calculation they're running, the quiet file they're building, the erosion that's happening to their sense of belonging - none of that is visible to you. You only find out about it at the end of a call, almost by accident, when someone finally says: "This is the first time like we are talking one on one."

By the time someone tells you that, the wait has already done some of its damage. The goal is to make sure the wait never happens in the first place.

What This Cost vs. What It Would Have Cost to Fix

Let's be real about the math here, because I'm a numbers person and I think it's worth saying out loud.

A one-on-one call is 30 minutes of your time. That's it. Once every two or three weeks. For a developer who is actively building a core integration in your product - a person whose work directly affects the velocity and quality of your platform - the cost of that call is essentially zero relative to the cost of losing them.

Developer turnover is not cheap. Hiring, onboarding, ramp time, knowledge transfer - depending on the role and the market, you're looking at months of lost productivity and real recruiting costs. And most of that turnover is preventable. Not all of it, but most of it. The research on this is consistent and has been for decades: people don't leave jobs, they leave managers. Or more accurately, they leave situations in which they feel invisible.

Thirty minutes every few weeks is the cheapest insurance policy in the building. If you're not buying it, you're making a very expensive decision by default.

The Last Thing He Said

After he made the observation - that this was his first one-on-one, that he'd noticed them happening for the whole team - he said something else. Small thing. Easy to miss.

"That is a good thing."

He was saying: I'm glad it's happening. I'm glad I'm here now. I'm glad someone finally made the call.

Not resentment. Not bitterness. Just relief, and a quiet kind of gratitude, for something that should have been routine all along.

That's the thing about belonging. People don't usually need a lot. They don't need grand gestures or public recognition or a whole new system of perks. They need to know they're seen. A 30-minute call. A question asked in good faith. A calendar event that says: your turn.

Give people their turn. Don't make them watch everyone else get it first.