Revision · One-on-Ones & Feedback

Before moving on, it’s worth walking back through the ground this part covered — not page by page, but along the single line that runs through all of it. The part opened with a claim that was simple and a little uncomfortable: the raw material of management is not process, it’s conversations, and trust is built one at a time. Everything after that — the one-on-one, feedback given and received, hard conversations, recognition — was one long answer to a single question: how do you build, conversation by conversation, a relationship strong enough to carry real work?

This page ties those answers together so they hold in one piece. If the earlier chapters gave you the moves, this is the shape they make when you stand back and look at them all at once.

The reframe underneath everything

Start where the part started, because it sharpened the whole book to a point. Earlier parts answered the throughline — how do you turn a group of people and a goal into reliable outcomes, without chaos, burnout, or politics? — with structure: decide well, prioritize, run the work. This part added the thing that makes structure actually move: the individual relationship. A plan only produces outcomes when the people inside it are willing — willing to tell you the truth early, take feedback without armoring up, keep going through a hard week, and flag the risk before it becomes a disaster.

That willingness has a name: trust. And trust is not a feeling you generate with good intentions — it’s a track record, built one exchange at a time. You cannot install it, schedule it, or announce it in a memo. You earn it slowly, in dozens of small deposits: a check-in that actually listened, a piece of feedback that helped instead of stung, a hard truth delivered without cruelty, a thank-you that landed as sincere.

Enough deposits              →   Too few deposits
------------------------------------------------
bad news arrives small       →   problems surface late, already large
people disagree in the room  →   people disagree in the hallway
work gets done unwatched     →   management by surveillance and pressure

The right-hand column is the chaos-and-politics failure mode, and it starts in the gap where trust should have been built. So a group of people plus a goal becomes reliable outcomes only when the individual relationships are healthy — not warm, not conflict-free, but honest, safe enough to speak up, and repaired when they crack.

And one belief the part dismantled early is worth carrying forward: none of this is temperament. Every conversation here runs on learnable moves, not on being a “natural people person.” The awkward manager who practiced the moves reliably outlasts the charmer who relied on instinct, because deliberate skill holds under pressure and charm doesn’t.

The one-on-one is the container

The first move was to build the standing structure inside which every other conversation becomes easier. The One-on-One made the case for a recurring, private meeting between you and each person you manage — and its central, counterintuitive idea: it belongs to the report, not to you. It is their time to raise what’s on their mind, not your slot to extract a status update. The moment it becomes your progress report, it stops depositing trust and starts withdrawing it.

Three things make it work, and they’re worth holding as a set:

Protected cadence  — it happens on a reliable rhythm, and you don't cancel it lightly
Shared agenda      — both of you bring items; theirs come first
Their meeting      — the mindset that the time is for them, run at their pace

A Good Agenda then filled that container with real content so it wouldn’t decay into the status update it’s always tempted to become. The pull is strong: status is easy, concrete, and comfortable — and it’s also the one thing you can get from a dashboard or a message. The agenda that earns the meeting reaches past status to the things that only surface in a real conversation: how the person is actually doing, where they’re stuck or bored, what’s coming that worries them, how they’re growing, and — crucially — feedback flowing both ways. Cancelling the one-on-one when the week gets busy is the most common way managers quietly drain the trust account, because cancelling says this, and you, are the first thing I drop.

The common trap — the one-on-one that became a status meeting

The failure isn’t skipping the meeting — it’s holding it and hollowing it out. You keep the slot, but every week it’s the same walk through the task list, driven by your questions, aimed at what you need to know. It feels productive, so nobody notices it’s dead. But a status meeting builds no trust, surfaces no early bad news, and leaves the person feeling processed rather than heard. The fix is to hand them the first word — “what’s on your mind this week?” — and to genuinely mean it, even when your own list is burning.

Feedback is a two-way skill

With the container built, the part turned to its daily currency: feedback, in both directions.

Feedback That Lands covered the giving half. The whole art is to change behavior instead of triggering defenses, and three properties do that work:

Specific    — a concrete behavior, not a vague label ("you seem disengaged")
Timely      — close to the event, while it can still be acted on
Behavior    — about what was done, never about who the person is
not person

The tool to keep is SBI — Situation, Behavior, Impact. You name the situation (“in yesterday’s handover”), describe the observable behavior (“you skipped the medication changes”), and state the impact (“the next shift missed a dose, and the patient’s pain spiked”). SBI works because it stays on the ground of what actually happened — no mind-reading, no character verdict — so the person can hear it without their ego slamming the door. “You’re careless” starts a fight; “here’s what happened and here’s what it caused” starts a fix.

Receiving Feedback Well took on the harder, less-taught half — because feedback is a street that runs both ways, and if you can’t take it, no one will risk giving you the truth, and you’ll be the last to know how you’re doing. The core move is to stay curious, not defensive. When criticism lands, the ego’s instinct is to explain, justify, or counterattack — and every one of those teaches the other person never to bother again. The discipline is to treat feedback as data: get curious, ask a clarifying question, thank them for the risk they took, and separate hearing it from deciding what to do about it. You don’t have to agree; you have to make it safe to have said. A manager who takes feedback well is one who will keep receiving it — which is the only way to keep improving once you’re senior enough that few people will volunteer the truth unprompted.

In practice — the same skill, up and down

A café shift lead tells the owner, gently, that the new opening checklist is adding fifteen minutes to a rush the team can’t spare. The owner’s reflex is to defend the checklist she just designed. Instead she gets curious — “walk me through where it slows you down” — and learns two steps can move to the night before. Same person, same week, she also has to give feedback to a barista who keeps arriving five minutes late. Different direction, same underlying skill: specific and behavior-focused going out, curious and non-defensive coming in. Giving and receiving aren’t two topics; they’re one habit of honesty, practiced from both chairs.

Hard conversations and real recognition

The last two chapters sat at the two extremes of the emotional range — and shared, surprisingly, the same underlying discipline.

Hard Conversations Without Flinching took on the truths people avoid until they fester: underperformance, conflict, the thing everyone can see and no one will name. The principle that steadies these is a single balance — direct about the problem, soft on the person. Those two are not in tension; they’re what make the conversation both honest and survivable. Fail the first and you flinch: you soften the problem into vagueness (“just keep an eye on things”) until the person walks away with no idea anything was wrong. Fail the second and you crush: you’re so blunt about the person that they shut down and defend rather than change.

Vague about the problem  +  soft on the person   →  Flinching (nothing changes)
Clear about the problem  +  hard on the person    →  Crushing (they shut down)
Clear about the problem  +  soft on the person    →  the conversation that works

The trap is thinking kindness means avoidance. The kindest thing is usually to say the hard thing early and plainly, while it’s still small and fixable — silence isn’t gentleness, it’s a slow-motion ambush that lets a March problem become a November crisis.

Recognition and Praise Done Right closed the part with what sounds like the easy conversation but is where many managers quietly fail — either forgetting it entirely or doing it so carelessly it means nothing. The key insight ties the whole part shut: recognition needs the same specificity as criticism. “Great job, everyone” is the praise equivalent of “you’re careless” — a vague label that carries no information and therefore no weight. Real recognition uses the same anatomy as good feedback: name the specific behavior and its specific impact — “you spotted that the two orders were swapped before either shipped; you saved us a furious customer and a day of rework.” That the person can believe, because it proves you were actually watching. Generic praise, by contrast, teaches people you weren’t.

The evidence — what made teams work

When Google studied its own teams for several years (the effort became widely known as Project Aristotle, results shared around 2015-2016), it went looking for the traits of high-performing teams and found that who was on the team mattered less than how they treated each other. The strongest single factor was psychological safety — the shared sense that you can speak up, admit a mistake, or ask a naive question without being punished. Treat the specifics loosely; one company’s study is not a law of nature. But the direction matches everything this part teaches: safety isn’t a policy you declare, it’s the residue of many small conversations handled well — feedback that was fair, a hard truth delivered without humiliation, recognition that proved you noticed.

Where this leaves you

Stand back and the shape is clear. Reliable outcomes rest on healthy one-to-one relationships, and those relationships are built in conversations, not in systems. You build the container — a protected, shared one-on-one that belongs to the report — and you give it real content instead of letting it rot into a status update. Inside it you practice feedback in both directions: specific, timely, behavior-not-person when you give it (SBI), and curious-not-defensive when you receive it. You hold the hard conversations without flinching or crushing — direct about the problem, soft on the person. And you make recognition as specific as your criticism, so it proves you were paying attention.

Every one of those is a deposit, and the account they fill is trust — the one thing that turns a group of people and a goal into reliable outcomes rather than a fragile arrangement held together by pressure. That is why this part sits where it does. The trust you build here is the foundation the rest of managing people stands on: a person who believes you’ll deal with them straight will bring you the bad news early, take the stretch assignment, disagree with you in the room, and keep going through the hard week. Get the conversations right, one at a time, and the willingness that every plan quietly depends on stops being something you have to force out of people — and becomes something they offer, because you’ve earned it.