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: pause, take stock of where the person is, correct course if needed, keep moving. It is a checkpoint in their career, and it does not owe anyone a deliverable.

The 1:1 has to exist because of the power asymmetry between leader and report. Anything you say as a leader gets taken more seriously than you meant it, and when a report has something hard to say back to you, hedging is the rational move, because the cost of candor lands on them while the benefit lands on you. Every other channel makes this 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 the hedging.

There is a case for deleting 1:1s outright, on the grounds that most of them are wasted, and it 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, a willingness that 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. This is rare, and not what you should plan for.
• The meeting is quiet on the surface and you read indirectly: a tone shift, 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.

Two rules protect the room. 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, and from then on nobody trusts the room, because the whole arrangement only ever ran on their belief that it was safe. Second, reschedule instead of cancelling. One cancellation is forgivable, but a pattern of them tells the report exactly where they sit in your priorities, and since nobody complains about getting thirty minutes back, the whole thing falls apart without anyone saying so.

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 means a report whose performance you are working on, or a new hire still ramping up.

The arithmetic is worth doing once. Thirty minutes a week across six direct reports eats five percent of your bandwidth and puts a recurring meeting on each of their calendars that they cannot decline. Default weekly looks like the safe choice, and it is an expensive one, paid by a leader who never sees the invoice. It also feels very different from the other side of the table: to you, weekly 1:1s feel like care, while to an experienced engineer on a stable team they feel like surveillance, or like an attempt 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, and the 1:1 is the wrong instrument for that. Stay close through informal channels: a random chat, dropping into a thread, a coffee, a five-minute walk past someone's desk, none of which goes on the calendar. The 1:1 stays the structured checkpoint, the closeness lives everywhere else, and mixing the two inflates the calendar while diluting the meeting.

Keep a shared running doc, live on screen-share

Every 1:1 gets 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, and nothing in it is your private file. Writing it in the meeting, where the report can watch the words go in, is what closes the gap between what you 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, and the next month they would open with "what's up?" and have no memory of the conversation. Their memory was fine in every other context, so the problem was not recall but the absence of anything tying month one to month two. After a few cycles I stopped raising anything new, because the conclusion settles in on its own: if the leader cared, they would have remembered. The meeting stayed on my calendar long after the willingness had drained out of it.

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 one long conversation the two of you are having across months. A private file in your own notes app is just as bad as no notes, because the continuity you are maintaining is invisible to the only other person who needs to see it.

Benchmark against the ladder periodically

Less often than monthly, at 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 against vibes?

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

Extract inputs upward, with specific asks

The 1:1 runs in both directions. You need ground truth about the team, the working environment, and yourself, and reports will not volunteer it, because the same asymmetry that makes them careful about their own troubles makes them careful about being honest with you about you.

Closing with "any feedback for me?" reliably returns "no, all good," because the question asks the report to criticize the person who writes their review, on the spot, and "all good" is the only answer with no downside. 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 do not 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 stays 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.

This has nothing to do with productivity. Every other move in this list depends on the report being willing to say things they have not told anyone else, and 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 version of the same one. The willingness to raise the hard thing does not survive the report knowing a transcript will exist somewhere afterward, and "just for action items" is the version of the argument that sounds harmless while producing exactly the same transcript.

None of these moves are exotic, and most of them are decades old in some form. They add up to a meeting the report can rely on: the same doc every month, the same confidentiality, and a leader who remembers month one when month two starts. Some months nothing important comes up, the doc gets a short entry, and that is fine.