Latest / Executive Careers with Fexingo: VP, C-Suite, and Senior Leadership Career Strategy / How Senior Leaders Negotiate Their Mandate
Transcript
- Lucas: You know, I was rereading that Harvard Business Review piece on executive onboarding, and there's this one line that's been stuck in my head all week. It says something like, 'most executives don't fail because they can't do the job; they fail because they never understood what the job actually was.' Luna: That's a heavy thought. And it hits especially hard for someone stepping into a senior role where the job description is, like, two pages of vague aspirations. Lucas: Exactly. And it's why I wanted to spend today on the difference between a job description and a mandate. Because in my experience, the executives who thrive in the first year are the ones who quietly negotiate their mandate before they even start solving the big problems. Luna: So, just to be clear, a mandate isn't just 'what you're supposed to do,' right? It's something more specific. Lucas: Right. A job description is a list of responsibilities. A mandate is the explicit or implicit authority to act, the resources to back it up, and the criteria by which your success will be measured. It's the difference between 'you're in charge of supply chain' and 'you're in charge of supply chain, you can restructure the logistics network, and you'll be judged on a fifteen percent cost reduction by year end.' Luna: And if that mandate isn't clear from day one, you're kind of flying blind, aren't you? Lucas: You are. And that's where a lot of senior leaders stumble. They get hired, they dive into the operational weeds, and six months later they look up and realize their boss had a completely different idea of what 'good' looked like. We've talked about the thirty-day relationship map before, but I think there's a more foundational conversation that has to happen first. Luna: Okay, and before you go deeper, I've got a confession. I've been listening to this show for a while, and honestly, if today's episode helps me think through my own mandate, that's probably worth the price of a coffee. Lucas: Ha, I like that. And look, if today's episode does that for you, the link is right there in the show notes. It's buy me a coffee dot com slash fexingo. That's the whole ask. Luna: Yeah, and I know it sounds small, but it genuinely keeps the lights on here. No ads, no sponsors, just our voices and your support. Lucas: So, back to mandates. There's a story I keep coming back to. A few years ago, a friend of mine took a chief operating officer role at a mid-sized manufacturing firm. The offer was great, the board was excited, but the mandate was basically summarized as 'make things run better.' Luna: Oof. That's a recipe for confusion. Lucas: It is. But instead of accepting that vagueness, he scheduled a series of conversations before his start date. He sat down with the CEO, the CFO, and three board members, and he asked each of them the same three questions: What does success look like in twelve months? What would failure look like? And what authority do I have to make that happen? Luna: Did he get a consistent answer? Lucas: Not at all. The CEO wanted a leaner operation, the CFO wanted cost reduction, and one board member wanted him to focus on international expansion. Three very different mandates, and he had to surface them before he could align on a single one. That's the first move in negotiating a mandate: you have to know what's already out there. Luna: So it's almost like a mandate isn't just handed to you; it's something you have to actively construct, even if you're the new person. Lucas: Exactly. And the second move is to draft the mandate document yourself. Don't wait for HR or your boss to write it. You write a one-page memo that says, here's what I understand my mandate to be, here's how we'll measure progress, and here's the decision rights I need. Then you circulate it for comments. It's much easier to edit something than to create it from a blank page. Luna: That's smart. But I have to imagine there's some politics to this. You're a brand-new exec, you're asking for more authority, more resources—doesn't that make you look like a power grabber? Lucas: It can, if you frame it as 'I want more power.' But if you frame it as 'I want to make sure I deliver what you need,' it's a completely different conversation. You're not asking for authority for its own sake; you're asking for the clarity that lets you execute. That's the third move: you tie your mandate to the outcomes your boss cares about. Luna: Can you give me a concrete example of how that plays out? Lucas: Sure. Let's go back to my COO friend. He realized the CEO's real concern was that the company had missed its delivery deadlines three quarters in a row. So in his mandate memo, he didn't just say 'I need to restructure the supply chain.' He said, 'To get on-time delivery to ninety five percent, I'll need to consolidate our three warehouses into two, which will require a capital expenditure of two million dollars and the authority to renegotiate carrier contracts.' Now the mandate is concrete, it's tied to a business metric, and the CEO has a clear yes or no to give. Luna: That's a great example. It's almost like a mini business case for your own role. Lucas: Precisely. And the fourth move is to get the mandate in writing, even if it's just an email chain. Because later, when you're making tough calls—like cutting a popular product line or reallocating budget—you can point back to that document and say, 'This is what we agreed success would look like.' It protects you, and it also reminds your stakeholders that they signed off on it. Luna: I love that. So you're essentially creating a contract with your stakeholders, but it's a living document, right? It's not set in stone. Lucas: Right, and that's the fifth move. You revisit it. A mandate isn't static. The business changes, the CEO's priorities shift, and sometimes you need to renegotiate. I'd suggest checking in with your boss at least every quarter and asking, 'Is this still what success looks like?' That way, you're never caught off guard. Luna: I want to go back to something you said earlier, about the three conversations. You mentioned your boss, your peers, and your team. Can you break that down a little more? Lucas: Sure. The conversation with your boss is about authority and priorities. This is where you ask, 'What decisions are mine to make, and which ones do you want to be consulted on?' That's the decision rights piece. The conversation with peers is about interdependencies. You want to know, 'Where do our mandates overlap? Who owns this process?' Because if you and the chief marketing officer both think you're in charge of the customer experience, you're going to collide. Luna: And with your team? That's probably the most delicate one. Lucas: It is, because they're the ones who will feel the consequences of your mandate. You need to explain not just what you're trying to achieve, but why, and how you'll handle the changes that come with it. You're not just giving orders; you're bringing them into the mission. If they don't understand the mandate, they can't help you execute it. Luna: So in a way, negotiating your mandate is like a mini leadership exercise in itself. It requires clarity, communication, and a bit of courage. Lucas: Absolutely. And I'd add one more thing: it's not just about the first thirty days. The best leaders I know are constantly refining their mandate, especially when they take on new projects or the company pivots. It's not a one-time event. Luna: I was reading about a CEO who actually put his mandate on a single slide and presented it at the first board meeting. It had three columns: what I'm responsible for, what I'm not responsible for, and what I need from the board. It seemed to set a really clear tone. Lucas: That's a brilliant exercise. And it's so rare. Most executives would rather project confidence than admit they need clarity. But I think that kind of transparency actually builds credibility, because it shows you're thinking about the role strategically, not just trying to please everyone. Luna: So, if you're listening and you're about to start a new senior role, what's the one thing you should do this week? Lucas: I'd say, before your start date, ask your new boss for a list of the top three priorities they have for you in the first six months. Don't ask for the job description—ask for their priorities. Then, in your first week, sit down with them and say, 'I want to make sure I'm aiming at the right targets. Let's align on what success looks like, and what decisions I can make on my own.' That's the seed of your mandate. Luna: And if you're already in a role and realize you've been operating without a clear mandate? Is it ever too late to start this conversation? Lucas: Never. It's never too late. You can always say, 'The market has shifted, and I want to make sure my goals are still aligned with the company's priorities. Let's revisit my mandate.' In fact, doing that proactively can signal that you're adaptable and self-aware. It's a sign of maturity, not weakness. Luna: I really like that. It takes the pressure off having to have it all figured out on day one. Lucas: Exactly. Because the truth is, the most successful senior leaders I've worked with are the ones who ask for clarity early and often. They don't pretend to know everything. They know their mandate is the foundation, and they build it deliberately. If you can do that, you're already ahead of the curve. Luna: Well, I know my next coffee is going to be earned. Thanks for the framework, Lucas. Lucas: Always a pleasure. And if you've got a story about a time you had to negotiate your own mandate, we'd love to hear it. Until next time.