Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / The Silent Killer of Managerial Authority
Transcript
- Lucas: You spend years getting promoted because you were the person who had the answers. You were the spreadsheet wizard, the code reviewer, the sales closer who never missed quota. Then you get that corner office, or at least the corner desk with two direct reports, and suddenly nobody is buying what you are selling. Luna: And they do not say it out loud. They just start going around you. Or worse, they go to your boss to validate your decisions. Lucas: Exactly. It is the classic trap of the high-performer promotion. I was talking to a director in San Francisco last week who told me he spent three hours preparing for a one-on-one with his new engineering lead. He had anticipated every question, drafted every response, and memorized the project roadmap. The engineer sat down, looked at him, and asked a single question about resource allocation that the director had not thought through. And in that moment, the entire hierarchy collapsed. Luna: Because the director tried to perform competence instead of demonstrating clarity. Lucas: Right. And that performance failure is what we call a crisis of perceived legitimacy. It is not about whether you are actually smart or capable. It is about whether your team believes you can navigate the ambiguity they face daily. When you try to hide your gaps, you signal that you are more focused on protecting your ego than solving their problems. Luna: So the instinct to fix it is usually to double down on being right, which makes it worse. Lucas: It does. I see it constantly in management workshops. A new manager will ask, 'How do I stop my team from questioning my strategy?' And I tell them, 'Stop trying to answer the questions you do not have good data for yet.' There is a massive difference between ignorance and intellectual honesty. Ignorance is hiding that you do not know. Honesty is saying, 'I am not sure yet, but here is how I plan to find out by Tuesday.' Luna: That second part is crucial. The timeline shows you are working on it, rather than just shrugging. Lucas: Precisely. Let me give you a concrete example from a fintech company we worked with earlier this year. They had a senior product manager named Elena who was technically brilliant but notoriously rigid. She would veto ideas without explaining why, citing 'brand guidelines' or 'technical debt' as black-box reasons. Her team stopped coming to her. They started making small workarounds behind her back because they knew she could not articulate the logic behind her rejections. Luna: They were managing around her authority rather than engaging with it. Lucas: Yes. So Elena’s VP sat her down and gave her a strange assignment. He told her to write down every decision she made in the previous month where she said no. Then, for each one, she had to write down the exact trade-off she was weighing. Most of them had no trade-offs. They were just preferences disguised as policy. When she did the audit, she realized she was using authority as a crutch for indecision. Luna: That is terrifying self-reflection. Did she change her approach immediately? Lucas: She started doing something radical in team meetings. Instead of announcing the final decision, she would present the problem, list the constraints, and then explicitly state what she did not know. She would say, 'I think option A is best because of X, but I am worried about Y. What am I missing?' Suddenly, the engineers started contributing. Not because she asked them to, but because she had lowered the cost of dissent. Luna: It shifts the dynamic from interrogation to collaboration. Lucas: It does. And here is the counterintuitive part: teams respect leaders who admit uncertainty more than leaders who claim certainty. Because in a fast-moving business environment, certainty is often a sign of laziness. If you are certain about everything, you probably haven’t looked deeply enough. Uncertainty signals that you are actively processing complex variables. Luna: But there is a fine line. If you are too uncertain, people think you are incompetent. Lucas: There is. And that is where the framework matters. You want to use what I call the 'Controlled Unknown.' You acknowledge the gap, but you own the path to closure. 'I don't have the answer yet, but I will bring you a recommendation by end of day.' That keeps the authority intact while inviting input. It says, 'I am the driver, but I need your eyes on the road.' Luna: That feels like a very practical tool for someone who is still learning the ropes. Lucas: It is. But we have to talk about why this is so hard for us. Most of us were rewarded for having answers in our individual contributor roles. Being the smartest person in the room got you bonuses, promotions, and stock options. So when you become a manager, your identity is tied to being the source of truth. Admitting you don't know feels like losing status. Luna: Which is ironic, because in management, status comes from enabling others, not being the hero. Lucas: Spot on. And let me add one more layer to this. When you admit uncertainty, you also model psychological safety for the rest of the organization. If the leader can say, 'I was wrong,' or 'I don't know,' it gives permission for everyone else to take risks. If the leader pretends to know everything, everyone else has to pretend they know too. And that is how companies miss market shifts. Luna: Because no one wants to be the messenger of bad news if the messenger is already defending their own ego. Lucas: Exactly. So, before we go deeper into the mechanics of how to structure these conversations, I want to pause for a second. If today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. Luna: Yeah, it really helps keep the lights on and the research sharp. Lucas: Thanks for supporting the show. Now, let's get back to Elena. After she started using the Controlled Unknown, her team's velocity didn't just improve; the quality of their debate changed. They stopped asking her for permission and started asking her for perspective. Luna: That is a huge shift in mindset for employees who are used to waiting for instructions. Lucas: It is. And here is the metric that surprised her. Her retention rate went up. People stayed longer because they felt heard. They weren't just executing orders; they were helping shape the outcome. When you treat your team like junior partners in problem-solving, they act like owners. When you treat them like subordinates, they act like employees. Luna: Ownership requires autonomy, and autonomy requires trust. Lucas: Correct. So, how do you build that trust when you are new? Step one is to audit your language. Look at your last ten emails or Slack messages. How many times did you use phrases like 'Obviously...' or 'Clearly...' or 'As I mentioned...' These are dominance markers. They shut down conversation. Replace them with 'Here is what I am seeing...' or 'What is your take on...' Luna: That seems simple, but most people never do it because they are afraid of looking weak. Lucas: They are afraid of looking weak, but they are actually looking insecure. Weakness is admitting you failed and fixing it. Insecurity is pretending you didn't fail. There is a big difference. I recommend a practice called 'The Friday Check-in.' Every Friday afternoon, spend fifteen minutes with your top performer. Ask them, 'What is one thing I did this week that got in your way?' And then you just listen. You do not defend yourself. You do not explain. You just say, 'Thank you. I will work on that.' Luna: That must feel incredibly uncomfortable in the moment. Lucas: It is visceral. Your heart rate goes up. You want to justify your actions. But if you can sit with that discomfort for just five seconds, you will gain more credibility than you ever will from another PowerPoint presentation. It signals that you value truth over comfort. Luna: And that builds a culture where truth is valued everywhere, not just in your office. Lucas: It does. And let's talk about the ripple effect. When you model this behavior, your peers notice. Other managers start to realize that you are not trying to hoard information. They might even start seeking your input because they know you will give them honest feedback, not just political fluff. You become a node of reliability in the network. Luna: Reliability is currency in any organization. Especially when things are chaotic. Lucas: They always are. October is typically a busy quarter for planning cycles, and everyone is stressed. In that environment, a leader who admits, 'I don't have all the answers, but I am navigating with you,' is a stabilizing force. A leader who claims to have all the answers is a liability. Luna: Because when they inevitably get something wrong, the collapse is total. Lucas: Total. And it destroys psychological safety permanently. Once people realize you are bluffing, they never fully trust you again. You can repair trust, but it takes years. Bluffing burns bridges. Luna: So the lesson is to invest in transparency early, even when it feels risky. Lucas: Always. And one final tactical tip. When you do admit uncertainty, pair it with a hypothesis. Don't just say, 'I don't know.' Say, 'My hypothesis is X, but I could be wrong. Help me test that.' It turns your weakness into an invitation for collaboration. It shows you are thinking, not just reacting. Luna: It engages their brain instead of their compliance mechanism. Lucas: Exactly. You want their brain engaged. Compliance is cheap. Engagement is expensive, but it pays dividends. As you move into Q4, think about who in your team needs to hear you say, 'I'm not sure about this, but here is my thinking.' Try it next week. See what happens. Luna: I bet the results will surprise you, especially if you are used to carrying the weight alone. Lucas: We hope so. Because the goal isn't to be the smartest person in the room anymore. The goal is to make the room smarter than any one of us could be alone.