SPEAKER_1: Alright, so last lecture we landed on this idea that the right question is the leadership — Socratic inquiry as a strategic tool, not just a soft skill. That reframe was sharp. But now I'm thinking about the moment where questions alone won't cut it: when Justin actually has to deliver hard feedback to someone with twenty-plus years in the industry. SPEAKER_2: And that's where everything built so far gets stress-tested. The inquiry framework and the first one-on-one — all of it either holds or collapses the moment a young leader has to tell a veteran that something isn't working. SPEAKER_1: So what's the core mistake most young leaders make when they walk into that conversation? SPEAKER_2: They lead with opinion instead of observable fact. The moment feedback sounds like a personal judgment — 'you're not collaborative enough,' 'your approach feels outdated' — a veteran's defenses activate immediately. The fix is the Objective-First method: start with what actually happened, not what you think it means, ensuring feedback is data-driven and constructive. SPEAKER_1: Can you make that concrete? What does Objective-First actually sound like versus the alternative? SPEAKER_2: Sure. Instead of 'you're dismissive in LP meetings,' you say 'in Tuesday's LP call, you cut the portfolio founder off mid-sentence twice.' One is a character judgment. The other is a behavior description. The first invites a debate about personality. The second opens a conversation about a specific, changeable action. That distinction is the entire difference between feedback that lands and feedback that triggers a standoff. SPEAKER_1: So it's less about what you think of the person and more about what you observed. But here's what I'd imagine Justin wondering — how many data points does he actually need before walking in? Is there a number? SPEAKER_2: Three to five KPIs is the practical range. Enough to show a pattern, not so many that it feels like a prosecution. The goal is to make the feedback undeniable without making it feel like an ambush. Critically, those data points should connect directly to fund performance metrics, ensuring feedback is grounded in objective data. SPEAKER_1: That's the framing shift, right? Future fund performance over personal style. SPEAKER_2: Exactly. 'Your communication style bothers me' is a dead end. 'LP re-up rates dropped twelve percent in Q3, and here's where I see the connection' — that's a conversation a veteran can engage with professionally. It removes ego from the equation and anchors everything to shared stakes. SPEAKER_1: Okay, but what happens when the veteran pushes back hard? There's a specific dynamic there — what's it called? SPEAKER_2: Seniority Defensiveness. It's the pattern where an older subordinate rejects feedback not because the data is wrong, but because the source feels illegitimate to them. They're not disputing the numbers — they're disputing your right to deliver them. If the feedback lacks respect or clarity, that reaction is almost guaranteed. SPEAKER_1: So how does a young leader manage that in the moment without either backing down or escalating? SPEAKER_2: Two moves. First, ensure psychological safety before the feedback even starts — the recipient needs to feel the conversation is a partnership, not a verdict. Second, when defensiveness surfaces, pivot explicitly to the shared mission. Something like: 'I'm raising this because I need your expertise working at full capacity for this fund to hit its targets.' That language reframes the feedback as a request, not a reprimand. SPEAKER_1: That's a meaningful pivot. And after delivering the feedback — what's the structure for the rest of the conversation? SPEAKER_2: Four steps, in order. Invite them to respond — don't just deliver and wait for compliance. Check that the feedback was actually understood as intended. Agree on specific, feasible next steps together. And offer genuine partnership: 'What do you need from me to make this shift?' That last one is critical. It signals that the leader is invested in the outcome, not just the correction. SPEAKER_1: And if the feedback still doesn't land — if they leave the room and nothing changes? SPEAKER_2: Schedule the check-in before you leave the room. Don't wait to see if they follow through. A follow-up meeting already on the calendar signals accountability without confrontation. And if resistance continues, stay curious rather than punitive — test whether the gap is intent versus impact. Sometimes the veteran understood the feedback but disagreed with the framing. That's a different problem than someone who simply refuses to engage. SPEAKER_1: So for someone like Justin, what percentage of that feedback conversation should actually be grounded in data versus qualitative observation? SPEAKER_2: Aim for roughly seventy percent data-driven. The remaining thirty percent is context — the 'why this matters' layer that connects the numbers to the mission. Pure data without narrative feels cold and bureaucratic. Pure narrative without data feels personal and arbitrary. The blend is what makes feedback both credible and human. SPEAKER_1: So for our listener, what's the one thing to carry out of this lecture? SPEAKER_2: Effective feedback for a veteran has to be anchored in observable facts and fund performance data — not personal style, not gut instinct. When Justin walks into that room with specific behaviors, three to five KPIs, and language that connects the issue to shared stakes, the age gap stops being a credibility problem. The data speaks first, and the leader's role is to ensure the conversation remains a constructive partnership, not a power struggle.