Tough Love? or Not?
A CSM submits an account review that is full of data slides but lacks actionable insights or optimization recommendations.
Manager says:
"This is a great start, but it doesn’t tell a story yet. Connect these data points to specific outcomes and bring back two recommendations for the client. I know you can pull out the 'why' behind these numbers."
Answer: Tough Love
Why:
Focuses on the Work: The feedback is specific to the output (the slides), not the person's character.
Sets a Clear Bar: It explicitly defines what is missing: a "story," "outcomes," and "recommendations."
Shows Belief in Capability: It ends with a vote of confidence, signaling that you are pushing them because you know they are capable of higher-level analysis.
A PM ships a feature that technically works but confuses admins.
Leader says:
"It’s live, but the friction is too high. Please revisit the UX and discovery process to resolve the confusion partner admins are reporting. Bring back something you’d be proud to demo to a Club Director."
Correct Answer: Tough Love
Why:
High Standards: It refuses to accept "technically functional" as the finish line.
Customer-Centric: Anchors the feedback in the actual user experience rather than personal opinion.
Empowerment: It challenges the PM to take pride in the quality of the output rather than just checking a box.
A sales rep submits a high-value deal for approval, but the CRM notes are messy and missing critical context.
"I cleaned up the notes myself because it was faster than explaining it to you."
❌ Answer: Not Tough Love (Just Being an Ahole)
Why:
Enabling vs. Coaching: You’ve removed the rep's accountability for their own work.
Scaling Issue: Doing it yourself creates a dependency that will burn you out.
Missed Learning: The rep won't know the standard expected for the next deal.
"A teammate misses a deadline that impacts another team’s ability to hit their own milestones."
Leader says:
“I know you have a lot on your plate right now, so let's not make a big deal out of the delay. We'll just pivot the other team's schedule to compensate.”
❌ Correct Answer: Not Tough Love (Just Being a Jerk/Enabler) (in disguise)
Why:
Avoids Accountability: It normalizes missing commitments without addressing the root cause.
Builds Fragility: The teammate never learns to manage pressure or communicate blockers early.
Shifts the Cost: It penalizes the high-performing team by forcing them to absorb the failure of another.
Direct Chapter 2 callout: "The Compassion Trap"
This is textbook "Compassion without Push." You are being "nice" to one person at the expense of the organization’s standards.
“This isn’t the level I expect from you. I’m pushing because I know what you’re capable of, and this draft doesn't reflect your best work. What do you need from me to hit the bar by Friday?”
✅ Correct answer: Tough Love
Why:
Validation through Challenge: It explicitly states why the bar is high—because you believe in their talent.
Unambiguous Standard: It removes the "guesswork" for the employee by clearly stating the current output is insufficient.
Maintains Agency: By asking "What do you need?", you offer support without taking over the task, keeping the ownership firmly with the individual.