The 1:1 as the primary instrument

You are responsible for the careers of the people who report to you. Over a year, what each of them learns, what they get exposed to, what they get shielded from, and how clearly they see themselves all come back to choices you make. The 1:1 is the recurring, confidential conversation where you carry out that responsibility. What it is for is simple: pause, take stock of where the person is, correct course if needed, keep moving. A checkpoint in their career rather than a meeting with a deliverable.

The 1:1 has to exist because of the power asymmetry between leader and report. As a leader, anything you say gets taken more seriously than you meant. And when a report has something hard to say back to you, they usually hedge or leave it out. Every other channel makes it worse. A thread plays to an audience, a group meeting is full of other people, a survey forces multiple choice, and a dashboard hides who said what. The 1:1 is the one meeting designed to cut through that hedging.

One contrarian view says most 1:1s are wasted and the answer is to delete them, but that gets cause and effect backwards. Wasted 1:1s come from running each meeting as if the only thing that matters is what gets said inside it. Run it instead as a regular practice whose real value is that, over months, your report stays willing to say hard things to you. That willingness builds, even on the days when nothing important comes up. Seven moves follow.

Defend the 1:1 itself

Each 1:1 turns out to be one of three things:

• The report walks in with a real thing and says it directly. Rare, and not what you should plan for.
• The meeting is quiet on the surface and you read indirectly: tone shifts, a question skipped, a teammate's name that did not come up, an answer three words shorter than usual.
• Something has already broken, and the 1:1 is the place they bring it to.

Two rules protect the 1:1. First, what is said in the 1:1 stays in the 1:1 unless the report gives you permission to share it. One breach gets back to the team faster than you would expect; from then on no one trusts the room. Second, reschedule instead of cancelling. One cancellation is forgivable; cancel repeatedly and the whole thing falls apart.

Default monthly, step up only with a reason

The default is monthly, thirty minutes. Step up to biweekly or weekly only when the situation needs a faster feedback loop, which usually means a report whose performance you are working on, or a new hire still ramping up.

The math is simple. Thirty minutes a week, across six direct reports, is roughly five percent of your bandwidth, and a recurring meeting on each of their calendars that they cannot decline. Default weekly looks safe, but it is an expensive choice that most leaders pay without noticing. It also feels very different to the report than it does to you. To you, weekly 1:1s feel like care; to an experienced engineer on a stable team, they feel like surveillance, or like you are trying to manufacture material that is not there.

Use informal channels for everything else

The honest reason people add weekly 1:1s with senior reports is that they want to stay close. The 1:1 is the wrong instrument for that. Stay close through informal channels: random chats, dropping into a thread, a coffee, a five-minute walk past someone's desk. None of it goes on the calendar. The 1:1 stays the structured checkpoint; staying close lives outside it. Mixing the two inflates the calendar and dilutes the 1:1.

Keep a shared running doc, live on screen-share

Every 1:1 is captured in a shared running doc, one per report, and you type into it during the meeting itself: what came up, what got committed to, and where the next checkpoint sits. The report has access to the doc; nothing in it is your private file. Writing it in the meeting, where the report can see it, is what closes the gap between "what we talked about" and "what got written down."

I learned this from the opposite side. As a report, I once had a manager who kept no running doc. I would raise something one month and they would commit to working on it. Next month they would open with "what's up?" and have no memory of what we had discussed. Their memory was fine; what was missing was anything that tied month one to month two. After a few cycles I stopped voicing anything new, because the conclusion settled in on its own: if the leader cared, they would have remembered. The 1:1 was still on the calendar. The willingness had drained out.

The running doc is the rule that prevents this. It holds you accountable to follow up, and it turns a string of separate 1:1s into a real journey the two of you are on together. A private file in your notes app is just as bad as no notes, because the report cannot see the continuity.

Benchmark against the ladder periodically

Less often than monthly, somewhere around quarter mid-points, half-years, and the run-up to a performance calibration cycle, pull the running doc alongside the ladder rubric and read them against each other in the 1:1:

• Where has the person demonstrated the level above?
• Where are the gaps?
• What does the next checkpoint look like, measured against the rubric rather than vibes?

This is a leveling check rather than a promotion decision. Do it monthly and it becomes a ritual you stop learning from. If you never do it, the report's self-assessment drifts away from yours, and that is how surprise downgrades happen at review time.

Extract inputs upward, with specific asks

The 1:1 is bidirectional. You need ground truth about the team, the working environment, and you, and reports will not volunteer it unprompted. The asymmetry that makes them cautious about being honest with you about themselves makes them just as cautious about being honest with you about you.

Closing with "any feedback for me?" reliably returns "no, all good." The asks have to be specific and prepared in advance:

• What is friction in the team that I am not seeing?
• What did I do or fail to do in the last sprint that got in your way?
• What would you change about how we run planning meetings if it were your call?

Ask these consistently and don't flinch at the answers, and the report learns that this part of the conversation is real.

Keep notetaker bots out of the room

Even when AI notetaker bots are running on every other meeting in your calendar, the 1:1 is the one document you maintain personally, with no third-party transcription and no automatic summary. The doc is yours, on screen-share, typed in real time.

The reason is not productivity but willingness. Every other move in this list depends on the report being willing to say things they have not told anyone else. A bot in the room turns a confessional conversation into a recorded one. That is a different kind of conversation rather than a more efficient one. The willingness to raise the hard thing does not survive once the report knows a transcript will exist somewhere afterward. "Just for action items" is the version of this argument that sounds harmless, but isn't.

None of these moves are exotic; most of them are decades old in some form. The practice works because you treat the 1:1 as a recurring commitment that keeps your reports willing to say hard things to you over many months, and because you do not let any other channel chip away at it. The 1:1 is the leader's primary instrument because it is the only one designed against the asymmetry.