Leader vs. Manager: You Are Not Their Daddy
Leader vs. Manager: You Are Not Their Daddy
The "work family" myth doesn't build closeness, it builds dependency. Real leadership means getting in the trenches with your team and teaching them to win the room with outcomes, not taste. Here's the difference.
4 min read

Listen to this article
Listen to this article
0:00/1:34
You don't earn a team's trust by being loved. You earn it by being right, with a number to prove it.
You don't earn a team's trust by being loved. You earn it by being right, with a number to prove it.
There's a phrase that shows up in every corporate Slack channel, every recruiting pitch, every all-hands: "We're a family." It sounds warm. If you lead a design team, it's actually a trap.
Your team isn't your family, and you're not their parent. But don't mistake that for coldness. What you owe them is bigger than comfort. You owe them the trenches.
Real belonging on a design team isn't built in a 1-on-1 where you absorb their anxiety. It's built the moment you're both staring at the same broken flow at 9pm before a launch, and you're not delegating the fix, you're finding it with them. You design together. They ship it alone. That's the deal. You show them what the work actually takes by doing it beside them, not by describing it from a slide.
That's the version of leadership people actually run through a wall for. Not because you made them feel safe. Because you made them good, and you were in it with them while it happened.
Train them out of "career designer" mode.
Here's the thing that actually weakens a design org, and it's not a lack of warmth. It's "blue looks better than green."
Every time a designer defends a decision with taste instead of a goal, they hand the rest of the company a reason to question the next ten decisions too. Product starts overriding you. Engineering starts negotiating your specs. Execs start treating design as a coat of paint instead of a function that moves the business. One un-defensible decision and the whole org's design posture goes from robust to shaky, because now everyone in the room has permission to have an opinion on aesthetics, and nobody has a way to argue back.
The fix isn't more taste. It's demanding a goal behind every call. Not "this looks cleaner." "This reduces checkout from five steps to three, and we'll know it worked because completion rate moves." Not "the old nav was confusing." "Users were dropping at this exact point, here's the number, here's what we expect to change." Train your team to talk in outcomes, not preferences, and the next time someone in a review says "I just don't love it," your designer has an answer that ends the conversation instead of starting a debate they can't win.
That's what makes a design org hard to argue with. Not confidence. Evidence.
Reset the 1-on-1.
Next time someone comes to you venting about a stakeholder, don't fight the battle for them. Ask: "What's the goal this design is supposed to hit, and how will we know if it worked?" If they don't have an answer, that's the actual coaching moment, not the politics.
The goal isn't to be liked. It's to build a team that doesn't need you, because you built it with them.
You're not their family. You're not their work-daddy. You're the person who was in the trenches with them long enough that they don't need you in there anymore, and who taught them how to win the argument before it starts. That's worth more than being loved. It's worth being trusted.
There's a phrase that shows up in every corporate Slack channel, every recruiting pitch, every all-hands: "We're a family." It sounds warm. If you lead a design team, it's actually a trap.
Your team isn't your family, and you're not their parent. But don't mistake that for coldness. What you owe them is bigger than comfort. You owe them the trenches.
Real belonging on a design team isn't built in a 1-on-1 where you absorb their anxiety. It's built the moment you're both staring at the same broken flow at 9pm before a launch, and you're not delegating the fix, you're finding it with them. You design together. They ship it alone. That's the deal. You show them what the work actually takes by doing it beside them, not by describing it from a slide.
That's the version of leadership people actually run through a wall for. Not because you made them feel safe. Because you made them good, and you were in it with them while it happened.
Train them out of "career designer" mode.
Here's the thing that actually weakens a design org, and it's not a lack of warmth. It's "blue looks better than green."
Every time a designer defends a decision with taste instead of a goal, they hand the rest of the company a reason to question the next ten decisions too. Product starts overriding you. Engineering starts negotiating your specs. Execs start treating design as a coat of paint instead of a function that moves the business. One un-defensible decision and the whole org's design posture goes from robust to shaky, because now everyone in the room has permission to have an opinion on aesthetics, and nobody has a way to argue back.
The fix isn't more taste. It's demanding a goal behind every call. Not "this looks cleaner." "This reduces checkout from five steps to three, and we'll know it worked because completion rate moves." Not "the old nav was confusing." "Users were dropping at this exact point, here's the number, here's what we expect to change." Train your team to talk in outcomes, not preferences, and the next time someone in a review says "I just don't love it," your designer has an answer that ends the conversation instead of starting a debate they can't win.
That's what makes a design org hard to argue with. Not confidence. Evidence.
Reset the 1-on-1.
Next time someone comes to you venting about a stakeholder, don't fight the battle for them. Ask: "What's the goal this design is supposed to hit, and how will we know if it worked?" If they don't have an answer, that's the actual coaching moment, not the politics.
The goal isn't to be liked. It's to build a team that doesn't need you, because you built it with them.
You're not their family. You're not their work-daddy. You're the person who was in the trenches with them long enough that they don't need you in there anymore, and who taught them how to win the argument before it starts. That's worth more than being loved. It's worth being trusted.