The One-on-One, Done Right (It's Their Meeting, Not Yours)

It's the middle of July at a pest-control company and the routes are packed. The tech sits there and says nothing. The numbers were already on the screen before he walked in.

So the thing that matters never comes up. He has a recurring scheduling conflict that quietly costs the route two stops a day, and he's never had a slot to raise it. Two stops a day is real money for a residential company doing about $1.3M a year, and it compounds week over week.

The owner doesn't see it, because the meeting was never the tech's to talk in.

It's their meeting

To run a one-on-one that actually catches something, hand the report the agenda. Let them come in with what's on their mind, and spend most of the thirty to sixty minutes listening for the problem they wouldn't otherwise raise. The numbers you could read in an email aren't the meeting.

Most advice gets this backwards. It frames the one-on-one as the manager's status check, a list of questions the boss asks to find out where projects stand.

The better design runs the other way. It's the report's meeting, because the point is to hear what they're thinking before it hardens into a problem you find out about too late.

That owner has it flipped. He sets the agenda, he does the talking, and the tech becomes an audience. Hand the agenda over and the two-stops conflict comes out in week one, since the report finally gets to raise what they actually care about.

What you're really listening for

A status update tells you where the work is. A one-on-one tells you where a person is drifting, before that drift turns into how the whole crew operates.

That's the return. You catch it when it's still one tech with one scheduling workaround. And thirty to sixty minutes of a real conversation can lift the quality of someone's work for weeks, because you fixed a small thing before it set.

It shows up at sale, too. A manager who hears the two-stops problem holds the standard, so the owner doesn't have to walk the floor. That's the same owner-independence a buyer pays for, because culture is what happens when you're not in the room and so is your valuation.

Two habits that make it work

Both of these exist to get the real issue on the table before it leaks out as interruptions or stays buried.

• The hold file. You and the report each keep a running list of non-urgent stuff and save it for the one-on-one, so they aren't interrupting you eleven times a week with things that could've waited. The tech's scheduling conflict is a hold-file item: not a fire, just the kind of recurring drag that never gets a slot.
• The last-minute zinger. The real issue often comes out as the clock runs down, once the report has warmed up and decides to risk it. Protect the last five minutes and ask one more question. That's usually where the two-stops problem finally shows up.

Four questions to have them come ready for

These are written to surface drift. None of them asks for a status update you already have.

1. What's slowing you down that I can't see? This is the two-stops question. It invites the recurring drag they stopped mentioning because nobody ever did anything about it.
2. Where are you working around something instead of fixing it? A workaround is drift at its earliest, one person quietly lowering the standard before it spreads.
3. What did you decide this week that you weren't sure was your call? This shows you where authority is fuzzy, so you can confirm it was theirs to make and keep it off your desk.
4. What's one thing you'd change about how we work? The answer is often the zinger. Leave room for it, and ask again if the first answer is thin.

Weekly, same slot, no exceptions

Run it weekly, on a fixed slot, thirty to sixty minutes. It sits inside the weekly operating rhythm as one of the four meetings that replace you.

The rule that keeps it alive: a meeting without a fixed slot slides into "when there's time," and "when there's time" means never.

The Tuesday-morning owner shows the other failure. His one-on-ones do happen, but the slot is his to fill, so it fills with route numbers and never with the tech. A skipped or hijacked one-on-one costs you the week the problem went uncaught, and the report learns the slot isn't really theirs.

When it turns up something bigger

Sometimes what comes out is a standard being missed. If a report is consistently under standard and a quick note won't fix it, that's the accountaiblity conversation, which has its own structure.

Other times the drift points at a standard that's unclear or out of date. Resetting it is its own deliberate move: setting a standard that sticks.

Either way, the one-on-one catches the signal and hands it off. Don't try to resolve those inside it.

The format

Four parts you can run this week:

• Who owns the agenda: the report. They come prepared, you mostly listen.
• The four questions: the ones above, answered ready, aimed at drift.
• The hold-file rule: both sides save non-urgent items for the meeting.
• The zinger reminder: protect the last five minutes and ask one more question.

The format is artifact J4-OOO in the Operator's Leadership Toolkit, and it lives and builds up inside your Keystone operating record, getting tighter as you run it.

How much of your standard still rides on you walking the floor? Keystone is closed right now while the build finishes, but when the diagnostic opens it will answer that with three scores and your value range with the most likely figure locked, drawn from 10 years of BizBuySell Insight Reports and 1.6M+ SBA 7(a) loan records.

Save your spot on the waitlist at https://app.trykeystone.io.

The one-on-one installs the catch, and the cadence around it is what makes a manager hold the standard. A Full Operations Modernization installs that cadence as the Manager Accountability Structure (the authority matrix and weekly standup the one-on-one feeds), and the Keystone Manager Standup keeps it running after. Scoping begins on the Full Operations Modernization page.

FAQ

Who should set the agenda for a one-on-one?

The report sets the agenda, not the manager. The meeting exists to surface what is on their mind before it becomes a problem, so they come prepared and you spend most of the thirty to sixty minutes listening, while a manager-owned agenda turns it back into a status update you could have read in an email.

What questions should I ask in a one-on-one?

Ask questions that surface drift, not status: what is slowing them down that you cannot see, where they are working around something instead of fixing it, and what they would change about how the team works. The numbers you already have are not the meeting; the early signal you can only get in the room is.

How often should one-on-ones happen?

Hold one-on-ones weekly, on a fixed slot, for thirty to sixty minutes. A meeting without a protected slot decays into "when there is time," which means never, and a skipped one is the week a small problem went uncaught.

What is the difference between a one-on-one and a status update?

A status update tells you where the work is; a one-on-one tells you where a person is drifting before it becomes a team norm. The status numbers belong in an email, while the one-on-one is for the early signal a report will only raise when the meeting is theirs to talk in.