Rebuilding one-on-ones that nobody wanted

That’s a fair suspicion. If a one-on-one is a status meeting with the door closed, “corporate theater” is exactly what it is. The good news is that the version worth doing is a genuinely different meeting, and the One-on-Ones Leadership Tool describes it well.

I could hand you a template right now, but a template designed for a team I know nothing about would just be a nicer costume for the same theater. Can you tell me about the actual team first: the seniority mix, whether you’re remote or in a room together, and what people actually say when they cancel?

“Nothing to report” is actually the most useful thing you’ve told me. It means your team believes the meeting exists so they can report to you. By that definition, they’re right to cancel when the report is empty. The problem isn’t attendance. It’s that everyone, including your predecessor, agreed on the wrong purpose.

Before we replace that purpose, I want to see the old one clearly. Walk me through what a typical one-on-one actually looked like under the previous manager: who talked, about what?

Hold the template a moment longer, because the reframe matters more than the format. In the Solution Seeking System, a one-on-one is a relationship-building basic: it’s how you listen for problems people may not be aware of yet, or are afraid to raise, and how you find out what you can do to better serve the people you lead. It’s proactive listening: leadership as service and guardianship, not extraction.

That means two things. First, the meeting is theirs, not yours: they lead, you listen and encourage. Second, status has to physically leave the room, or it will creep back and eat everything. Status is what people reach for when a silence gets uncomfortable.

So: where else could ticket status live for your team? Do you already have a standup or a channel that could absorb it?

That fear is the most common one, and the answer is a small set of open questions you trust. The tool suggests several, and each one is really a Wisdom Principle wearing conversational clothes:

• “How have you been doing since our last one-on-one?” This is Understanding at work. It’s deliberately about them, not their tickets.
• “Are things going smoothly with everyone at work?” Asked in Good Faith: you’re assuming friction, if it exists, is misunderstanding rather than malice, and you’re offering to hear about it before it hardens.
• “What do you feel passionate about right now? Is there anything we can do to help you pursue that?” Service, made concrete.
• “Do you feel well supported by the team?”
• “Do you have any feedback for me, or anything on your mind?” This one is Vulnerability, and it’s yours to model. Answering it honestly takes Bravery on their side, which is exactly why you thank people when they do.

You don’t ask all five every time. Two or three, then let them lead. Which of these could you imagine saying in your own voice, and which feel like a costume?

Two answers, and the second one matters.

First: reword freely. The principle is what’s load-bearing, not the phrasing. “What are you actually excited about lately? Anything I can do to clear a path?” carries the same intent and sounds like a human. A question you’d never say is worse than no question.

Second: no, please don’t use Dana’s one-on-one for that. The tool is explicit: the one-on-one is their space, and it’s not the place to address your pre-existing concerns unless they bring them up. If you relaunch these meetings and the first one is an ambush, the whole team will hear about it, and every future invitation will read as a summons.

The Dana situation is real and deserves its own conversation, properly prepared. That’s exactly what the Solution Seeking Guide at /practice/guide is for. It walks you through the Communication Protocol one stage at a time for a specific live conflict: your own introspection first, then understanding her side, then building a solution together. Would you take the Dana conversation there and keep this one about the practice for all twelve?

Do the math before you accept anyone’s “non-negotiable.” Twelve people at thirty minutes weekly is six hours of one-on-ones every week. With prep and note follow-up, call it a full day. Meetings you can’t sustain become meetings you silently cancel, and a silently cancelled one-on-one teaches your team the practice was theater after all.

The tool’s rule of thumb is monthly, and for a team of twelve that’s a defensible baseline: roughly ninety minutes a week of listening, which you can protect indefinitely. The trade-off is real: a month is a long gap for someone new or someone struggling. So cadence doesn’t have to be uniform. Frequency should follow need, not rank.

What does your calendar honestly have room for, and who on the team needs more frequent attention right now?

Monthly baseline with biweekly for the two juniors is a sound design: that’s about two and a quarter hours a week, still protectable, weighted toward the people most likely to sit on a problem quietly.

As for making it weird: the way to avoid weird is to be plain. In the system’s language, Clarity is Kindness, and it applies to the meeting itself, not just what’s said inside it. A relaunch that works looks like:

• Name the change honestly. Tell the team what you told me: the old one-on-one duplicated standup, so status is going back to standup and the board, permanently.
• Say what the meeting is now, in ordinary words. The tool offers language for this: “This is time for us to just chat. We can talk about whatever you want. It’s not about anything in particular, just making sure we understand each other.”
• Schedule ahead, as an ask, not a demand. A regular, predictable slot on the calendar means nobody wonders what they did wrong when the invitation lands. Consent to talk matters.
• Then let the first meetings prove it. No announcement convinces a skeptical senior engineer. Acting on the first real thing someone tells you will.

That last point is where relaunches live or die, so let me ask: when something does come up in one of these, whether a concern, a friction, or a request, what do you plan to do with it?

“Write it down and actually do something” is exactly right: take notes, act on them, and close the loop so people feel rewarded for participating. That’s how the practice builds trust and pushes back the cynicism your team has already earned the hard way. Nothing corrodes it faster than a concern that vanished into a notebook.

And no, a quiet one-on-one isn’t wasted. Someone who’s fine gets twenty minutes back: end early, cheerfully, no penalty. The meeting still did its job: it kept the channel open and predictable, so that in the month when something isn’t fine, the space already exists and doesn’t have to be requested. You’re not mining for problems; you’re keeping a door unlocked. Trust arrives on its own schedule, usually a few quiet meetings later than you’d like.

I think you’ve designed the whole practice at this point: purpose, questions, cadence, relaunch. Want me to pull it together into a cheat-sheet you can keep?

One-on-ones cheat-sheet

Purpose

A one-on-one is proactive listening, a relationship-building basic. It exists to catch problems people may not be aware of yet or are afraid to raise, and to find out how you can better serve the people you lead. It is their space; they lead, you listen. Status lives in standup and the board, never here.

Cadence

• Monthly, 30 minutes, everyone: about 90 minutes a week across twelve people; protectable indefinitely.
• Biweekly for the two juniors while they ramp; drop to monthly when they say they’re ready.
• Scheduled ahead at a predictable rhythm, as an ask, not a summons. Nobody should wonder what they did wrong.

Opening questions

Two or three per meeting, then follow their lead:

• “How have you been doing since our last one-on-one?” (Understanding)
• “Are things going smoothly with everyone at work?” (Good Faith)
• “What are you actually excited about lately? Anything I can do to clear a path?” (service, in your own voice)
• “Do you feel well supported by the team?”
• “Do you have any feedback for me, or anything on your mind?” (Vulnerability, yours to model; answering takes their Bravery, so thank them when they do)

Listening posture

• Notebook out. Write down concerns and anything you promise.
• If something concerning surfaces, don’t solve it on the spot. Use the Communication Protocol: Introspection to find the right questions, Mutual Understanding to see how they feel and why, then a solution you actually apply and follow up on.
• Thank them genuinely for being brave and vulnerable enough to share. It costs energy.

What NOT to do

• No status. If it creeps back in, send it back to the channel by name.
• Don’t bring your own agenda or pre-existing concerns unless they raise them. This meeting is never an ambush.
• Don’t treat it as performance management or surveillance; the moment it becomes evidence-gathering, it dies.
• Don’t pad a quiet meeting. Ending early is fine; cancelling silently is not.

Relaunch plan

• Announce the change plainly to the whole team: status moves to standup permanently; the one-on-one becomes their time. Clarity is Kindness.
• Open the first round with the tool’s framing: “This is time for us to just chat about whatever you want, just making sure we understand each other.”
• Act visibly on the first real thing anyone raises. Follow-through is the only argument cynics accept.

Review the practice itself

• Put a date on the calendar eight weeks out to review the practice like any other solution.
• Signals to check: are cancellations down, has anyone raised something that wasn’t a status item, did every noted concern get acted on and closed?
• Adjust cadence and questions based on what you find. The practice should evolve with the team.

Take the Dana conversation to the Guide at /practice/guide before her next one-on-one, so that channel stays clean. And good luck with the relaunch. Come back after the eight-week review and tell me what the team taught you.