Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Why First-Time Managers Fail At Role Clarity
Transcript
- Lucas: The most dangerous phrase in a new manager’s vocabulary isn’t 'I don’t know,' it’s 'we’ll figure it out as we go.' I spent last week reviewing performance improvement plans from a mid-sized logistics company, and nine times out of ten, the root cause wasn’t incompetence. It was role ambiguity. Luna: That makes sense. When people don’t know who actually holds the pen for a final decision, they either freeze or step on each other’s toes. Lucas: Exactly. And the irony is that companies spend thousands on leadership seminars but skip the basic work of defining who decides what. In that logistics firm, we looked at their operational manuals. They had three hundred pages of process descriptions, but zero clarity on escalation thresholds. Luna: So staff were waiting for permission to act on things they should have handled, or worse, acting on things they shouldn't have. Lucas: Both. You get paralysis on low-risk items and chaos on high-stakes ones. The company realized their issue wasn’t skill; it was signal. They introduced a simple rule: if the financial impact is under five thousand dollars, the shift lead decides. No approval needed. Just documentation. Luna: That five thousand dollar line seems arbitrary, but it creates a hard boundary that stops endless emails back and forth. Lucas: It does, and it freed up about thirty percent of the manager’s time within six weeks. But here is where most first-time managers stumble. They try to define roles by listing tasks instead of defining them by decisions. They write job descriptions that say 'responsible for client communication' instead of 'authorized to negotiate contracts up to ten percent variance.' Luna: Tasks are just activities. Decisions are actual authority. One tells people what to do, the other tells them when they can stop asking for help. Lucas: Right. A task list creates a to-do list mentality. Decision rights create ownership. When I talk to executives, they often confuse visibility with control. They want to see every email because they are afraid of losing control, not because they need the data. Luna: But if you give someone clear decision rights, you don’t need to see every email. You only see the exceptions. Lucas: Precisely. And that is why so many new managers fail at delegation. They delegate the work but keep the decision-making power. That isn’t delegation; that is assignment. Assignment kills motivation because the employee knows they aren’t trusted with the outcome. Luna: So the manager ends up doing all the thinking while the team just executes. That feels exhausting for everyone involved. Lucas: It is unsustainable. I saw a tech startup where the junior developers were blocked on every deployment because the manager required a sign-off for minor code changes. The result? Three senior engineers quit within a month. They didn’t leave because of pay. They left because they felt like typists, not engineers. Luna: That is a classic case of bad hiring followed by bad management. But the initial hire was good. The system broke them. Lucas: The system did. And fixing it requires something counterintuitive. You have to let people make small mistakes. If you remove their ability to decide, you also remove their ability to learn. The logistics company mentioned earlier learned this the hard way when a junior manager denied a vendor contract over a forty dollar discrepancy. Luna: Because he was afraid of being wrong, he cost the company far more in lost goodwill than the forty dollars was worth. Lucas: Exactly. So they rewrote the protocol. Now, any decision under fifty dollars is automatic. Any decision over fifty dollars requires a brief note explaining why. The manager doesn’t approve it; he just reviews the rationale afterward. It shifts the dynamic from policing to coaching. Luna: Reviewing rationale is so much better than pre-approving. It forces the employee to articulate their thinking, which improves their judgment over time. Lucas: And it gives the manager visibility without the micromanagement. But there is a second layer to role clarity that nobody talks about. It is the negative space. Knowing what you are NOT supposed to do. Luna: Oh, I like that. Boundaries are defined as much by what you exclude as what you include. Lucas: Right. In that same logistics firm, they explicitly stated that shift leads were not responsible for long-term strategic planning. They removed the expectation that they needed to attend quarterly strategy meetings. This reduced anxiety and allowed them to focus on immediate operational excellence. Luna: Because trying to do both usually means failing at both. People spread themselves too thin when they think everything is equally important. Lucas: Spot on. And this brings us to the hardest part for new managers: enforcing these boundaries when the rest of the organization ignores them. Marketing might send an urgent request to Engineering, bypassing the product owner. If the manager doesn’t protect those decision rights, the whole structure collapses. Luna: So the manager becomes the gatekeeper again. Which defeats the purpose of having clear roles in the first place. Lucas: It does. I worked with a project manager who was terrible at saying no. She let stakeholders pile work onto her team until everyone was burned out. Her problem wasn’t time management. It was a lack of political courage to defend her team’s scope. Luna: That is tough. Saying no to senior leadership requires confidence that comes from knowing your role is solid. Lucas: It does. And you build that confidence by having written agreement on those decision rights. When someone pushes back, you don’t argue feelings. You point to the charter. 'Our agreement was that I handle resource allocation. You handle priority setting. Let’s stick to that.' Luna: It sounds rigid, but it actually builds trust. People respect leaders who have clear boundaries. Lucas: They do. Ambiguity breeds resentment. When people feel like the rules change daily, they disengage. Clarity, even if it is strict, provides psychological safety. You know exactly what is expected of you. Luna: So for anyone listening who just got promoted, the first thing they should do is sit down with their direct reports and rewrite those decision matrices? Lucas: Yes. Don’t wait for annual reviews. Do it in the first two weeks. Ask each person: 'What decisions can you make without me? What decisions do you want to make but currently can’t?' Then fill in the gaps. Luna: That is actionable. It turns a vague promotion into a concrete operating system. Lucas: It really does. And remember, clarity is not a one-time event. As the business changes, those decision rights will shift. You have to revisit them regularly. Luna: Otherwise, yesterday’s clarity becomes tomorrow’s bottleneck. Lucas: Absolutely. If you've gotten value from these conversations about building better teams and clearer structures, know that listener support keeps this independent. You can buy me a coffee dot com slash fexingo. Even a small amount helps maintain the ad-free experience we strive for. Luna: Yeah, it really does make a difference in keeping the production quality high and the content focused on what matters. Lucas: Back to the topic though, because I want to circle back to that logistics example. Did they measure the impact beyond just time saved? Luna: They did. Employee satisfaction scores went up by twenty points in six months. People felt heard and empowered. Lucas: That is the metric that matters. Efficiency is nice, but engagement is durable. When people understand their lane, they drive faster. Luna: And they don’t crash into each other. Lucas: Exactly. So the question for you, whether you are a manager or an individual contributor, is this: Who is actually deciding what in your team right now? Is it written down? Luna: If it isn’t, that is your first project. Start there. Lucas: Agreed. Because clarity is kindness. And in a chaotic market, it is the only thing that scales.