Skip to content
davthecoder
Effective One-on-One Meetings: A Field Guide for Engineering Managers
mindset

Effective One-on-One Meetings: A Field Guide for Engineering Managers

By David Cruz Anaya, Independent Senior Mobile Engineer (Android, Kotlin Multiplatform, Rust)

engineering-managementone-on-onesleadershipemployee-engagementcareer-developmentteam-managementtrust
Share:

Most engineering managers inherited their one-on-one habits from a manager who was winging it too. So the meeting drifts into a status update, the kind a project board already answers. That drift is expensive. In 2025, Gallup reported that global employee engagement fell to 21% in 2024, a decline that cost the world economy an estimated $438 billion in lost productivity (Gallup, State of the Global Workplace: 2025 Report). The one-on-one is where a manager can move that number on their own team, one report at a time. What follows is how to run one that earns its place on the calendar.

Key Takeaways

  • Managers account for at least 70% of the variance in team engagement (Gallup, 2015).
  • Employees who have regular one-on-ones with their manager are almost 3 times as likely to be engaged (Gallup, 2018).
  • A one-on-one is the employee’s meeting: growth, blockers, and trust come first, status updates last.
  • Weekly or biweekly, 30 minutes, employee-owned agenda, and never quietly cancelled.

What is a one-on-one meeting, really?

A one-on-one is a recurring, private check-in that belongs to the employee, not the project. In 2018, Gallup found that workers who have regular one-on-ones with their manager are almost 3 times as likely to be engaged as those who don’t (Gallup, Employees Want a Lot More From Their Managers). A board already tracks the tickets. This is the one slot that tracks the person behind them.

Two engineering colleagues having a focused one-on-one conversation at a table

New managers often get this backwards. A status update flows information up, so you feel informed. A one-on-one flows attention down, so your report feels supported. Same half hour, pointed the other way. When you already know what someone shipped this week, making them recite it burns the rare slot where they might have raised the thing they are scared to say out loud.

Quick test: if you could replace the meeting with a Slack message or a dashboard, it was never really a one-on-one. The value lives entirely in the part that does not fit in a status field.

So what goes in that slot? Growth, obstacles, feedback both ways, and the slow build of trust. None of those reliably come up in standups, retros, or sprint reviews. They need a protected, predictable space to surface, which is the whole reason the one-on-one exists, and why quietly skipping it costs more than it seems to.

For engineers who sit on the other side of the table, the same logic applies in reverse: a good one-on-one is your chance to manage up and shape your own path, not just report status.

Why do one-on-ones matter so much?

Because the manager is the single biggest lever on how a team feels and performs. Gallup has found that managers account for at least 70% of the variance in team engagement across business units (Gallup, State of the American Manager, 2015). If you want to know how engaged someone is, knowing their manager predicts it better than almost anything else. The one-on-one is where that influence is delivered, week after week.

The manager effect on engagementThe manager effectVariance in team engagement attributable to the manager70%driven by the manager
Source: Gallup, State of the American Manager, 2015 (reaffirmed in the 2025 report).

The macro picture sharpens the point. Gallup estimates that low engagement costs the global economy roughly $8.9 trillion a year, about 9% of global GDP (Gallup, State of the Global Workplace: 2025 Report). And the 2025 report carried a warning aimed straight at people leaders: manager engagement itself fell from 30% to 27%, while individual contributor engagement held steady at 18%. Managers are carrying the decline.

Think of the one-on-one as the transmission belt. The 70% manager effect doesn’t reach your team through org charts or OKRs. It reaches them through the repeated, personal conversation where you actually pay attention to one human at a time.

For an engineering leader, that 70% figure is the whole argument for guarding these meetings (Gallup, 2015). The biggest lever you have on team engagement turns out to be the most ordinary one: sitting down with a single person, on a regular cadence, and actually paying attention.

How often should you hold one-on-ones?

Weekly is the strong default, biweekly is the floor, and monthly is barely a heartbeat. The cost of getting cadence wrong is concrete: Gallup estimates that replacing a departing employee costs one-half to two times their annual salary, with voluntary turnover draining over $1 trillion a year from U.S. businesses (Gallup, This Fixable Problem Costs U.S. Businesses $1 Trillion, 2019). Skipping one is free this week and expensive the month someone resigns.

Two coworkers talking informally in a modern office during a regular check-in

How long? Thirty minutes suits most reports. New hires, anyone in a rough patch, and the newly promoted usually need closer to 45. A senior engineer cruising along might be fine with 30 minutes every other week. What matters far more than the length is whether the meeting actually happens, every time, without fail.

Cancelling a one-on-one rarely feels like a money decision, but it is one. Set against a replacement cost of half to two times someone’s salary, the half hour you reclaimed by bumping the meeting can quietly turn into the most expensive slot on your quarter.

What about the manager who is already drowning? Fair objection, and Gallup’s 2025 report names the problem directly, pointing to manager burnout as one driver of the engagement decline. Dropping one-on-ones is still the wrong cut. Protect them, and claw the time back from status meetings that a written update could handle. When the one meeting shown to move retention is the first thing to fall off a busy week, that is worth sitting with. Treat the slot like production, and do not bump it casually.

What should you actually talk about?

Lead with growth, blockers, feedback, and trust, in that spirit if not that exact order. Career development is not a soft topic: McKinsey found that 41% of people who quit during the Great Attrition cited a lack of career advancement as a top reason, just ahead of uncaring leaders at 35% (McKinsey, The Great Attrition Is Making Hiring Harder, 2022). The one-on-one is where you answer the question they’re quietly asking: is there a future for me here?

Two colleagues reviewing growth plans together at a desk

Professional growth

Growth is a retention lever that hides in plain sight. In its 2018 Workplace Learning Report, LinkedIn found that 94% of employees would stay at a company longer if it invested in their career development (LinkedIn, Workplace Learning Report, 2018). Spend part of the meeting on where they want to go: the skill they want next, a project that would stretch them, what the level above them actually takes. And keep it a running thread, instead of something you only remember at review time.

Unblocking challenges

Then clear the road. Ask what is slowing them down that they cannot fix on their own: a flaky pipeline, a review stuck in someone’s queue, a dependency on another team, a spec nobody will pin down. This is where you have leverage they do not. You can escalate it, bump its priority, or simply make the call they are not allowed to make. An engineer who stays blocked for three weeks is usually an engineer who has quietly started interviewing.

Feedback in both directions

Feedback works best when it is frequent and specific. Gallup found that 80% of employees who received meaningful feedback in the past week were fully engaged, whether they worked remote, hybrid, or onsite (Gallup, Organizations Can Redefine Feedback by Including Recognition, 2023). Give it often, and ask for it just as often. A plain “what is one thing I could do differently as your manager?” does more to flatten the hierarchy than any skip-level survey.

Building trust

None of the first three work without trust. Growth talk sounds like a script, and the real blockers stay buried, when people do not feel safe being honest. The next section gets into how to build it. The short version: trust comes from how you handle the small, awkward moments, and almost never from the annual offsite.

How do you build trust in a one-on-one?

Trust gets built slowly, mostly through being consistent and doing what you said you would do. The numbers back the unglamorous version. Gallup found that only 2 in 10 employees strongly agree their performance is managed in a way that motivates them, while those who feel their manager holds them accountable fairly are 2.5 times more likely to be engaged (Gallup, Do Your Measures Make Employees Mad?). People put their trust in fairness and follow-through long before charm.

Psychological safety keeps coming up in this research for a reason. Google’s multi-year study of its own teams, Project Aristotle, found it to be the most important quality of effective teams (Google re:Work, 2015). A weekly one-on-one is about the smallest room where that safety gets built or broken: one person, behind a closed door, slowly learning whether honesty here is actually safe.

In practice, that comes down to a few habits. Talk less than half the time. Resist the urge to fix the first problem you hear, since people often just need to think out loud first. Keep what is shared in confidence unless safety demands otherwise, and say that rule out loud so they know it exists. When you promise an action, write it down and close the loop the following week. Nothing erodes trust faster than a manager who forgets.

Across Gallup’s data, the managers people rate highest are the predictable, fair ones rather than the charismatic ones. A weekly one-on-one hands you about fifty chances a year to be exactly that kind of manager.

Quick gut check: across your last few one-on-ones, who did most of the talking? If it was you, the meeting has quietly turned into your meeting instead of theirs. The repair is not a new template, just the discipline to ask a question and then wait through the silence until they fill it.

How do one-on-ones work in remote and hybrid teams?

Remote and hybrid work make these meetings more important, because distance strips out the casual signals you used to pick up in the hallway. In 2022, Microsoft’s Work Trend Index found that 85% of leaders said the shift to hybrid made it hard to feel confident their people were being productive (Microsoft, Work Trend Index: Hybrid Work Is Just Work, 2022). The teams that handle this well answer it with a steady, predictable one-on-one, where they actually find out how the work is going, rather than reaching for another layer of monitoring software.

For a remote or hybrid team, what changes is mostly the discipline. Default to cameras on, but stay relaxed about it, since the goal is connection rather than a productivity check. Hold the meeting even more reliably than you would in an office, because there is no hallway to catch the thing that never made it onto the agenda. And pay closer attention to the quiet ones, since it is easy to coast unnoticed behind a muted tile.

In its hybrid-work research, Gallup reported that only about 3 in 10 hybrid managers had received any formal training on how to lead in a hybrid setting (Gallup, Global Indicator: Hybrid Work, 2024). Most managers are improvising remote leadership in real time. A deliberate, predictable one-on-one rhythm is the cheapest way to close that gap without waiting for a training budget.

One practical tweak: send a short written agenda before remote one-on-ones, and let your report add their own items to it. A little async prep makes the live 30 minutes calmer and gives quieter engineers an easier way in. The job has not changed with the office. You are still there for the person more than the project.

The most common one-on-one mistakes

Most one-on-one failures come down to the same short list of mistakes, which is oddly reassuring, since the same mistakes are easy to catch once you know them. The most common by far is running the meeting as a status report. Gallup’s finding that only 2 in 10 employees feel their performance is managed in a motivating way (Gallup) points right back at meetings that audit work instead of growing people.

Engagement fell in 2024, and managers fell with itEngagement fell in 2024202320240%35%23%21%30%27%All employeesManagers
Source: Gallup, State of the Global Workplace: 2025 Report. Bars compare 2023 and 2024 engagement.

Cancelling without rescheduling tells your report they rank below whatever was in your inbox, so move the meeting rather than dropping it. Talking too much teaches them to stop bringing the hard stuff, because they can see you would rather fill the silence yourself. Forgetting your follow-ups turns the whole ritual into theater. And meeting only your direct reports leaves you half-blind, because skip-level one-on-ones surface the things your managers cannot, or will not, tell you.

One more sits at the org level. Gallup reports that companies fail to pick the manager with the right talent for the job 82% of the time, and that only about 1 in 10 people have real talent for managing (Gallup, State of the American Manager, 2015). If most managers were never chosen for their people skills, the one-on-one is simply where those skills get built. Nobody starts good at this. You get better one conversation at a time.

For more on the gap between technical skill and leadership skill, see how impostor syndrome becomes the pike effect for software developers.

A one-on-one framework you can use tomorrow

A framework only helps if you can recall it under pressure, so keep this one light. Since the biggest win comes from holding the meeting at all (Gallup, 2018), structure matters less than consistency. One 30-minute shape that tends to hold up:

Minutes Focus Sample opener
0 to 5 Their agenda first “What’s on your mind this week?”
5 to 15 Blockers and priorities “What’s slowing you down that I can clear?”
15 to 22 Growth and goals “What do you want to get better at next?”
22 to 28 Feedback both ways “One thing I should keep doing, one I should change?”
28 to 30 Recap and actions “Here’s what I’ll follow up on by next week.”
Small habits, big engagement multipliersSmall habits, big multipliersRelative likelihood of engagement or motivation (Gallup)Regular one-on-ones3.0xFair accountability2.5xDaily vs annual feedback3.6xSource: Gallup engagement and feedback research, 2018 to 2023
Source: Gallup. Multipliers reflect relative likelihood versus the comparison group in each study.

For a brand-new report, swap the first meeting for onboarding questions: How do you like to get feedback? What does a great week look like for you? When were you happiest at work? Those answers become the operating manual for every one-on-one that follows. Want to go deeper on growth? Anchor each conversation to a clear career ladder, so “what do you want to get better at?” connects to a visible next level instead of a vague someday.

If you change one thing after reading this, make it this: pick a single report, put a recurring weekly slot on the calendar for the next quarter, and let them set the first agenda. For more writing on engineering leadership, subscribe to the blog, or keep reading below.

Frequently Asked Questions

How long should a one-on-one meeting be?

Thirty minutes is the right default for most reports, with 45 for new hires or people in a tough stretch. Length matters less than consistency. Gallup found employees with regular one-on-ones are almost 3 times as likely to be engaged (Gallup, 2018), so a reliable 30 minutes beats an occasional hour.

How often should one-on-ones happen?

Weekly is the strong default and biweekly is the floor. Frequency drives the feedback that fuels engagement: Gallup found 80% of employees who got meaningful feedback in the past week were fully engaged (Gallup, 2023). Monthly check-ins are usually too sparse to catch problems while they’re still small.

What should a manager not do in a one-on-one?

Don’t turn it into a status report. Only 2 in 10 employees feel their performance is managed in a motivating way (Gallup), and status-only meetings are a big reason why. Avoid cancelling without rescheduling, talking more than half the time, and forgetting the actions you promised.

Are one-on-ones worth it for senior engineers?

Yes, the topics just shift toward growth, scope, and influence rather than task help. Retention is the payoff: replacing a senior engineer costs one-half to two times their salary (Gallup, 2019), and 94% of employees say they’d stay longer if a company invested in their development (LinkedIn, 2018).

Conclusion

Nobody quits over a single bad one-on-one. People leave after fifty mediocre ones that slowly taught them their manager wasn’t really listening. That’s what makes this hard. There’s no dramatic moment where you earn or lose someone’s trust, just a long stretch of ordinary 30-minute slots where you either show up curious or show up distracted.

So keep it boring and consistent. Book the next one, and when you promise to chase down a blocker, chase it down. If you want a sense of what your engineers might not be saying out loud in those meetings, read how impostor syndrome becomes the pike effect for software developers.


Sources

Share:

Comments

Loading comments…