Hey, Priya — come in, come in. How are you doing? Before we get into anything — how's the week been? You've had a lot on.
David doesn't open with "so, updates?" He opens with "how are you doing?" and gives it space ("before we get into anything"). A 1:1 is not a status meeting — the first minute sets whether it's a human conversation or an interrogation. Starting personal, even for thirty seconds, changes the whole tone.
Honestly? A bit full-on. Good, though. That decision meeting last week took it out of me a little, but — no, I'm okay. Thanks for asking.
"A bit full-on. Good, though." — Priya is honest (it's been hard) without turning it into a complaint. "took it out of me a little" = tired me out. This is a good register for a 1:1: real, but composed. You don't have to pretend everything's perfect, and you don't have to unload everything either.
Yeah, I could see that. And actually that's — that's part of what I wanted to say. The way you handled the scope decision. You came in wanting full scope, you argued it hard, and then when the room moved, you got behind it. Fully. That's, that's not easy to do.
David doesn't say "great job last week." He names exactly what was good: argued hard, then committed fully. Specific praise lands because the person knows you actually saw it — "the way you handled the scope decision", not a vague compliment. Generic praise feels like a warm-up before bad news; specific praise feels real.
And Marco told me afterwards your prep was what made the numbers hold up. He said he just pointed at your model and it answered everything. That's the kind of thing that doesn't always get said out loud, so — I wanted to say it.
David relays a compliment from Marco. Second-hand praise ("Marco told me...") is powerful — it shows the good work travelled beyond the room. And he names why he's bothering to say it: "doesn't always get said out loud". A good manager collects and passes on the quiet credit people earn.
Oh — thank you. That, that actually means a lot. I wasn't sure how it came across, if I'm honest. I thought maybe I pushed too hard at the start.
Priya takes the praise simply — "thank you, that means a lot" — instead of brushing it off ("oh it was nothing"). Then she does something useful: she voices her own doubt ("I pushed too hard at the start"). Without knowing it, she's just opened the exact door David wanted to walk through. Naming your own uncertainty invites honest feedback.
Well — since you say that. There is, um, one thing I'd love to talk about. Nothing major. More of a — a "you're really good, and here's the thing that would make you even better" kind of thing. Is now okay for that?
David flags what's coming: "one thing I'd love to talk about... nothing major", and frames it as growth, not failure ("even better"). Then — crucially — he asks permission: "is now okay for that?" Signposting stops the other person from bracing for an attack, and asking permission gives them a second to get ready. "Can I give you a bit of feedback?" before the feedback is one of the most respectful moves there is.
Yeah. Yeah, of course. Now I'm a little nervous, but — go on.
"go on" — Priya doesn't get defensive before she's even heard it. The light joke ("now I'm a little nervous") keeps it human. Signalling openness — "yes, tell me" — makes it far easier for the other person to be honest with you, which is ultimately a gift to yourself.
So. When you're deep in something you care about — the presentation to the client a couple weeks back, a bit in the decision meeting too — you go very technical, very fast. And you sometimes, um — you come in over people. Not rudely. It's just, the passion runs ahead of the room.
Notice what David does NOT say: he doesn't say "you're arrogant" or "you interrupt people" as a label. He describes the behaviour ("you go very technical, very fast", "come in over people") and the impact ("the passion runs ahead of the room"). Behaviour + impact, with specific examples — never a character verdict. "Not rudely" protects her intent while still naming the effect.
Like — in the presentation, Tom asked a fairly simple question about timelines, and the answer he got was, was three layers of architecture. Which was all correct. It just wasn't what he asked. And I watched him kind of, kind of nod and go quiet.
David grounds the feedback in a single, specific moment: Tom's simple question, the over-technical answer, the nod-and-go-quiet. "Which was all correct. It just wasn't what he asked." — he separates being right from being useful. Vague feedback ("you're too technical sometimes") is easy to dismiss; one concrete example you both remember is impossible to argue with and easy to act on.
And the reason I'm raising it — it's not a problem, it's a — it's the one thing between "really strong technical lead" and "person the client turns to in the room." Does that, does that land? Or does it feel unfair?
David connects the feedback to Priya's own growth ("the one thing between X and Y") — so it's for her, not at her. Then he checks: "does that land? Or does it feel unfair?" Inviting disagreement ("or does it feel unfair?") shows the feedback isn't a verdict being handed down — it's the start of a conversation.
Hmm. My, my first reaction is — a little defensive, honestly. Because when I go technical it's because I actually — no. No, wait. Let me actually sit with it for a second.
This is the most valuable moment in the pack. Priya feels the defensiveness — and instead of acting on it, she NAMES it ("my first reaction is a little defensive") and then stops herself ("no, wait — let me sit with it"). Almost nobody does this. Catching your own defensive reflex and choosing to actually consider the feedback is a rare, career-defining skill. Watch how she buys herself a second instead of arguing.
Okay. Yeah. No, you're — you're probably right. In the client presentation I definitely lost Tom at one point. I saw his face. I just, I didn't slow down. I think I do that when I'm nervous, actually — I speed up and go deeper instead of stepping back.
Priya doesn't just accept it — she gives evidence back ("I lost Tom, I saw his face") and then goes further than David did ("I do that when I'm nervous"). When you can take a piece of feedback and build on it with your own honesty, two things happen: the feedback sticks, and the other person trusts you more. This is receiving feedback at its best.
And just — to be clear, I'm not saying dial down the expertise. The expertise is the whole point. It's more, um — read the question you're actually being asked. Sometimes the client wants the headline, not the engine room.
David quickly heads off a common misread: "I'm not saying dial down the expertise." Good developmental feedback is surgical — it changes one behaviour without asking the person to become someone else. "The headline, not the engine room" gives Priya a crisp, memorable rule she can actually use in the moment. A vivid phrase like that is worth more than a paragraph of advice.
No, that's — that's a really useful way to put it. Headline first, engine room if they ask. Yeah. I can work with that.
Priya repeats the idea back, compressed into her own version: "headline first, engine room if they ask." Playing feedback back does two things — it confirms you actually understood it, and it turns someone else's advice into your own rule. Notice she's now slightly ahead of David, building on the idea rather than just absorbing it.
Can I — actually, while we're being honest, can I raise something from my side?
A 1:1 is not just your manager talking at you — it's yours too. "Can I raise something from my side?" is how you open that door cleanly. Many people, especially earlier in their careers, treat a 1:1 as a review they receive. The strongest people use it to raise their own needs. Priya asks for the floor — and gets it.
Please. That's — honestly, that's exactly what these are for. Go for it.
David actively hands over the space ("that's exactly what these are for"). A good 1:1 is roughly half theirs, half yours. His job here is just to open the door wide and listen.
So — I want more of the client-facing side. I know I just agreed I go too deep, and I'll work on that. But that's, that's kind of my point — I want to be in that room MORE, not less. I feel like I get handed the hard technical bit and then, and then someone else presents it.
Priya states a clear ask ("I want more of the client-facing side") and connects it to the feedback she just accepted ("I'll work on that — but that's my point"). She names the frustration without blaming anyone ("someone else presents it", not "you always sideline me"). A clear, non-accusatory ask is far more likely to get a yes.
And I get why — the presenting is the safe pair of hands, and I'm the one who might go too deep. But I'll never get better at the room if I'm never in the room. That's, honestly, that's the bit that frustrates me.
Priya does something advanced: she voices David's likely reasoning herself ("I get why — I'm the one who might go too deep") before making her case. Naming the counter-argument shows maturity and disarms it. Then the line that lands it: "I'll never get better at the room if I'm never in the room." Acknowledging the other side and still pressing your point — calmly — is exactly how you manage up well.
Okay. No, I — that's fair, and honestly I hadn't clocked it from your side. Let me, let me think out loud. The next client check-in — what if you take the delivery section? Not just the technical answer if it comes up — you actually run that part of the room.
David doesn't just say "sure, more client work someday." He offers something specific and soon: "the next client check-in, you take the delivery section." And he admits his own blind spot ("I hadn't clocked it from your side"). A request met with a vague "yes" dies; a request met with a concrete next step becomes real.
And I'll be in the room, so if it, if it starts running long we can tag it between us. But it's yours to run. That work?
David offers a safety net ("I'll be in the room... we can tag it between us") but is careful to keep ownership with Priya: "it's yours to run." Good delegation gives someone real ownership plus a backstop — not a task with the manager hovering. "That work?" checks she's genuinely on board, not just being handed something.
Yeah. I'd, I'd really like that. And I'll — okay, deal: I run the section, and you tell me afterwards if I lost the room. Direct. Same as today.
Priya connects the two threads herself: she gets the opportunity (run the section) AND invites the feedback loop ("you tell me afterwards if I lost the room"). She's turned "criticism" into "coaching I asked for." "Same as today" = she's naming that this honest 1:1 is the model she wants. That's a person who's going to grow fast.
Love it. Okay, so — two things written down. You run the delivery section at the next check-in. And we both keep an eye on the pace-and-space thing — you flag if you feel yourself speeding up, I'll flag if I see it. Deal?
Even a personal conversation ends with clarity: two concrete things, each with an owner, one of them shared ("we both keep an eye on it"). Making the growth area a shared commitment — not just "Priya's homework" — turns feedback into partnership. A 1:1 without a clear "here's what we each do next" tends to evaporate by Monday.
Deal. And — thank you, really. That was a good one. I came in a bit tired and I'm leaving actually kind of fired up.
The conversation ends where it began: human. "I came in tired and I'm leaving fired up" — that's what a good 1:1 does. Naming it ("that was a good one") is generous and honest, and it tells David the honesty was welcome — so he'll keep doing it. The bookend of a warm open and a warm close is what makes the hard bit in the middle safe.
Good. Me too. Go get some rest this weekend — that's an order. Talk Monday.
David closes with warmth and a small joke ("that's an order"). After honest feedback in both directions, ending light re-affirms the relationship is solid. The feedback was real; so is the care. That combination — candid AND kind — is the whole point of a good 1:1.