Leadership
One-on-Ones That Actually Matter
Sep 12, 2025
Most tech leaders know they should run one-on-ones. Yet many treat them as calendar clutter—easy to skip, rushed through, or reduced to status updates. The irony: done well, they’re one of the most reliable levers you have for engagement, retention, and performance.
The challenge isn’t knowing that one-on-ones matter. It’s making them work under real constraints: too many reports, too many meetings, and executives demanding visible delivery metrics. The key is shifting from seeing them as a box to check to treating them as a practical investment in your team’s growth and your own effectiveness.
Why They Fail
1. They turn into status reports. Michael Lopp, longtime engineering leader at Apple and Slack, and author of Managing Humans, put it simply: “I know how to use Jira.” Status belongs in dashboards or standups. If your one-on-ones are about task counts, you’re wasting time.
2. They lack preparation. Google’s Project Oxygen study found that effective managers plan regular check-ins that focus on people, not just projects. Without prep, one-on-ones drift into small talk and tactical filler.
3. They feel too safe. The most useful one-on-ones often include a moment of discomfort—asking about career direction, surfacing team tension, or giving feedback you’d both rather avoid. If every meeting feels “fine,” you’re probably not learning anything meaningful.
4. They ignore constraints. With 12–15 reports, many managers simply can’t run an hour a week with everyone. Pretending otherwise sets you up for failure.
What Success Looks Like
The goal isn’t a perfect agenda—it’s a meaningful connection. Gallup research shows that employees whose managers hold regular meetings are almost three times as likely to be engaged—meaning they show up with energy, advocate for the company, and stick around longer.
Effective one-on-ones tend to share three qualities:
They surface issues early. A skipped retro might hide a conflict; a one-on-one makes it visible before it festers.
They connect work to growth. Asking “What skill do you want to develop this quarter?” shifts focus from tasks to trajectory.
They build trust. Even short, consistent conversations reinforce that you care about the person, not just their velocity.
Making Them Work Under Real Constraints
Leaders often ask, “How do I do this with 15 reports and a packed calendar?” Here are pragmatic adaptations:
Shorter, consistent slots. Twenty minutes every two weeks is better than an hour that constantly gets rescheduled. Cadence matters more than length.
Async prep. Create a private Slack channel with each report. Throughout the week, either person drops topics, adding a ✅ emoji when resolved. Before the meeting, skim the thread and highlight two or three items for live discussion. That keeps the live time focused on conversation, not reciting statuses.
Rotate depth. If you have many reports, do deep one-on-ones with some each cycle, lighter check-ins with others, and rotate. Everyone gets attention, but you protect your bandwidth.
Prioritize the person, not the project. If time is short, ask: “What’s blocking you?” and “What’s one thing I could do to make work easier?” These two questions alone surface most of what matters.
I once asked an engineer, “What’s blocking you?” expecting to hear about a bug. Instead, he admitted he wasn’t sure who had final authority on design decisions. We clarified ownership the next day—a 30-second question saved weeks of churn.
Failure Modes to Anticipate
One-on-ones aren’t magic. Knowing when and how to adapt matters:
Skip vs. reschedule: If you and a report have spent 20 hours together in crisis mode, cancel guilt-free. If you miss a normal week, reschedule promptly—reliability is what gives the meeting credibility.
Escalating systemic issues: If a report says “our hiring process is broken,” don’t promise to fix it. Log it, raise it with peers or HR, and report back with what you did—following up matters as much as listening.
Minimalist preference: Some engineers genuinely want fewer meetings. Agree on a monthly 30-minute session supplemented with async check-ins.
How Much Time Does This Really Take?
Managers worry about the math. Here’s a realistic breakdown:
6 reports: ~1.5 hours per week at 15 minutes each.
12 reports: ~3–4 hours every two weeks if you rotate depth.
15+ reports: monthly deep dives + shorter weekly touchpoints.
The time commitment is real—but manageable with a structured approach.
How to Measure Outcomes
You can’t measure “trust” directly, but you can watch leading indicators:
Lower attrition and fewer surprise resignations.
Higher eNPS or engagement survey scores.
Faster cycle time when blockers surface earlier.
More upward feedback (“I need more context” vs. silence).
If these move in the right direction, your one-on-ones are paying off.
Practical Prompts
Use these prompts to spark conversations that matter:
“What’s one thing we’re not talking about that we should be?”
“When did you feel most energized in the past two weeks?”
“If you were in my role, what would you prioritize differently?”
“What skill do you want to develop this quarter?”
They’re not checklists—they’re conversation starters. The follow-ups are where the value happens.
The Payoff
Done poorly, one-on-ones are a tax. Done well, they create momentum: problems surface sooner, career paths become clearer, and trust grows deeper. That shows up in outcomes every leader cares about: engagement, retention, and performance.
Treat one-on-ones as investments in clarity, trust, and growth, and they’ll more than earn their place on your calendar. The question isn’t whether you have time for one-on-ones—it’s whether you have time for the problems they prevent.
