Efficient 1-1s and Working with HR

87% of millennial employees rate career growth opportunities as important to them at work, well ahead of older generations. That gap alone should change how you run your one-on-ones — because a 1-1 is one of the only recurring structures where career growth is actually supposed to be the topic, not an afterthought squeezed in when there's time left.

What a 1-1 is actually for

A 1-1 is a regular check-in between a manager and a direct report — and its value depends entirely on what it's used for. Set expectations clearly from the very first one: this is where issues, blockers, and concerns that affect performance get raised. It is explicitly not a status update — that belongs in standups and project tools, and letting it creep into the 1-1 is the single fastest way to make the meeting worthless. It's also where career growth, peer relationships, and goals actually get real airtime — and it's worth saying directly, early, that career growth belongs to the employee. You can support it — advocate for promotions, help find opportunities — but you're not the one driving it, and pretending otherwise sets a passive expectation neither of you can meet.

Ask better questions

The single highest-leverage habit in a 1-1 is asking open questions instead of closed ones. "Is everything okay?" invites a reflexive "yeah, fine." "Can you tell me what's been going on lately?" invites an actual answer. A few categories worth rotating through rather than repeating the same script every week:

• Check-in: What's on your mind this week? Last time you mentioned X was a challenge — how's that going?
• Alignment: How confident do you feel about where the company's headed? Any questions about [a recent change]?
• Progress: What's energized you lately? What's been hard? What did you learn this week?
• Relationship: How are things going with the people you work with? Any interactions worth discussing?
• Career: Where do you see yourself in two years? What skills do you want to build next? Who would you like to learn from?
• Closing: What are you committing to before we talk next? What can I help with in the meantime?

You don't need all 24 variants in rotation. You need enough range that the conversation doesn't calcify into the same three questions every week, which is its own way of quietly signaling you're not really listening for what's different this time.

Don't save feedback for the 1-1

It's tempting to treat the 1-1 as your designated feedback slot — jot notes through the week, deliver them all at once. In practice this backfires: by the time the meeting arrives, the details are fuzzy and the moment's already cold, so the feedback lands with less clarity and less impact than it would have in the moment. Give feedback close to when it happens instead, using something like the SBI model — situation, behavior, impact — rather than banking it. Save the 1-1 for the conversations that actually need the dedicated time: patterns, not single incidents, and — just as important — asking your report for feedback on you, not just handing it downward.

What good 1-1s actually deliver

Done consistently, 1-1s build real relationships, surface individual needs before they become problems, drive career development, and catch small issues while they're still small enough to solve in one conversation. They also fail in very recognizable ways: getting rescheduled or cancelled often enough that it signals "this isn't a priority," running with no agenda, never following up on what was committed to, tipping into a status report or a lecture instead of a two-way conversation, or skipping notes so nothing said last month is remembered this month. Every one of these is avoidable with basic discipline — protect the slot, keep light notes, follow up on commitments.

Making HR an actual partner

The same principle — regular, structured, two-way communication — applies one level up, to your relationship with HR. HR owns a real, wide scope: recruitment, training, employee relations, legal compliance, development. Knowing what's actually in that scope (and what isn't) is what lets you use them well instead of either over-relying on them or working around them.

Two patterns show up repeatedly in how the manager-HR relationship plays out. A blocker relationship happens when each side sees the other as an obstacle — HR as "compliance police," managers as resistance to HR's initiatives — and both retreat into tunnel vision instead of looking for shared ground. Picture HR rolling out a wellness initiative that managers privately know their teams don't want, but instead of saying so, they just quietly don't promote it — the initiative flops, and the mutual distrust deepens. An amplifier relationship looks like the same initiative, but with managers brought in early: HR asks what the team actually needs, the two sides land on something both believe in, and they promote it together. Same starting problem, opposite outcome — the difference is entirely in whether the two sides talked to each other before or after the decision was made.

Building the amplifier version deliberately comes down to a short list: find the goals you actually share before assuming you're on opposite sides; get explicit about who owns what, so friction doesn't come from ambiguity; keep expectations realistic on both sides; and close the loop with regular check-ins and honest feedback in both directions, not just HR checking in on you. None of this is complicated, and none of it happens automatically — it requires treating HR as a partner worth investing in, the same way you'd invest in any relationship on your own team.