The 1:1 You’ve Been Running Wrong for Three Years
The standard manager 1:1 is a status report both sides agreed to call development. The coaching the role exists to provide almost never happens. Here is the test, and the repair.
There is a meeting on the calendar every week. It has a good agenda. The manager arrives with a list. The direct report arrives with an update. They cover what shipped, what slipped, what is blocked, what is next. The manager offers help on the blocker. They agree on two action items. The meeting ends on time, and both people leave feeling it was a good use of thirty minutes.
It was a good use of thirty minutes for project tracking. It was not coaching. And it has not been coaching for three years.
This is the most common 1:1 in professional life, and it is misnamed at the root. The meeting is called development. What it does is status. The gap between those two has a cost, and the cost is invisible because the meeting keeps happening and keeps feeling productive.
The meeting is coaching in name and status in function.
Walk through the agenda of a textbook good 1:1. Open with a personal check-in. Review progress against goals. Surface blockers. Discuss priorities for the coming week. Close with development. The structure is sound. Every template recommends some version of it.
Notice what the structure optimizes for. It optimizes for coverage. By the end of thirty minutes both people have a shared, current picture of the work. That is a real output. It is also an output a well-run project tracker produces without a meeting.
What the structure does not optimize for is the one thing a manager can give that a tracker cannot. The sharpening of a direct report’s judgment on the calls only they can make.
The development slot is where this is supposed to live. In practice it is the slot that gets compressed when the blocker conversation runs long, which it almost always does. The blocker is concrete and urgent. The judgment work is abstract and can wait. So it waits. Week after week, it waits, and the waiting becomes the pattern, and the pattern becomes three years.
Both sides are complicit, and neither is acting in bad faith. The manager is busy and the status is genuinely useful. The report wants help with the thing in front of them, not a Socratic detour. So the two of them agree, without ever saying it, to perform development for a few minutes and spend the real time on tracking. The meeting stays on the calendar. The coaching the role exists to provide quietly stops happening.
What is missing is judgment-formation, not information.
The work of a manager, stripped to its load-bearing core, is to raise the quality of the decisions made by people who do not report the decision up.
A direct report makes dozens of calls a week that the manager never sees. Which customer escalation to take seriously. When to push back on a deadline and when to absorb it. Whether a piece of work is done or merely finished. How hard to argue a position in a room where the manager is not present. These are judgment calls, and the quality of them compounds over a career far more than the quality of any single shipped deliverable.
The status conversation touches none of this. Status reports outcomes. Judgment is formed upstream of outcomes, in the moment of the call, before the result is known. By the time a decision shows up as a line in a status update, the judgment that produced it has already happened. The manager is reviewing the receipt, not shaping the purchase.
This is the operating reality the agenda hides. A manager can run clean, on-time, well-documented 1:1s for years and never once touch the part of the report’s work that actually determines their trajectory. The meeting feels like management. Most of what management is for is happening somewhere the meeting never goes.
The test is whether any judgment got sharper.
There is a single question that separates the two kinds of 1:1, and it can be asked of any direct report without warning.
Name one judgment you’ve sharpened in the last six months because of these meetings.
If they can answer, with something specific, a kind of call they now make differently, a read they now trust, a mistake they no longer make because the meeting helped them see it, the 1:1 is doing its job. If they pause, and then reach for something vague about feeling supported, the meeting is a status report wearing the language of coaching.
The pause is the diagnostic. It is not a verdict on the report. It is a verdict on what the meeting has been used for.
Most 1:1s are status reports both sides agreed to call coaching. Both sides leave on time. Neither side leaves changed.
The repair is less agenda, more diagnosis.
The fix is not a better template. A better template produces a better status meeting. The fix is a change in what the half-hour is for, and it comes down to three moves.
The first is to spend less time on the list and more time on the call. The list what shipped, what is blocked can move to a written update sent beforehand. Read it in two minutes before the meeting. That clears the time the status conversation was eating and protects it for the work the status conversation was crowding out. The blocker still gets handled. It just stops being the whole meeting by default.
The second move is to replace “what’s on your plate” with “what’s the call you’re sitting with.” The first question produces a list. The second produces a decision in progress, something live, unresolved, where the report’s judgment is actually being exercised right now. That is the raw material of coaching. There is always one. The job is to ask for it directly instead of waiting for it to surface inside the status.
The third move is to resist solving it. The reflex, when a report brings a live decision, is to give the answer. Giving the answer resolves the decision and teaches nothing. The work is to ask the question that makes the report’s own reasoning visible to them. What would have to be true for the other option to be right. What are they optimizing for that they have not said out loud. Where is the read coming from. The decision is theirs. The point of the meeting is to make the next hundred decisions like it sharper, and that only happens if the reasoning gets exercised rather than replaced.
None of this requires more time. It requires the same thirty minutes pointed at the part of the work that compounds, instead of the part that merely needs covering.
The diagnostic.
The 1:1 is one of the few pieces of a manager’s week that is entirely within their control. No budget approval, no cross-functional alignment, no headcount. Just two people and thirty minutes. Which is exactly why the way it gets spent is so revealing.
Two questions settle what kind of meeting it has been.
Could the last month of these conversations have been replaced by a well-maintained written update with no loss?
If yes, the meeting has been status, and the live half-hour has been spent on something a document does better.
And, for each direct report, name the specific judgment they make better now than they did two quarters ago, and the conversation that moved it. If the name does not come, the meeting has not been doing the one thing it is uniquely able to do.
The status will always feel more urgent than the judgment. That is the trap. The blocker in front of the report is concrete and this week’s; the judgment is abstract and the next decade’s. The meeting that defaults to the urgent thing is the meeting that quietly stops being worth having. The repair is not more meetings or longer ones. It is pointing the same half-hour at the work that only that half-hour can do.
About PIOL
We translate complexity into signal, helping leaders see what is changing, what it means, and where attention is required before risk compounds or opportunity passes.
If you’re new to PIOL – Practical Intelligence for Organizational Leadership, you can follow for free to get future issues or paid to expanded views for actionable guidance.
Visit piol.ai to learn more.