Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Says I Need More Ownership
Transcript
- Lucas: So, Luna, I want to talk about a phrase that's been popping up in my one-on-ones lately: 'I need more ownership.' It sounds great on the surface, but I've learned it can mean about six different things. Luna: I've heard that too. It's like the new 'I want a challenge' – but when you dig in, you're never sure what they're actually asking for. Lucas: Right. Last month, I was coaching a manager at a mid-sized SaaS company – let's call her Priya. She had a developer, Dan, who kept saying he wanted more ownership. Priya finally gave him a major project – full control over the new API integration. And what happened? He missed the first milestone, then started asking for help on decisions he could have made himself. Luna: Ouch. So he wanted ownership but wasn't ready for it? Or was he asking for something else entirely? Lucas: That's exactly the question. I think 'more ownership' is often a proxy for three things: more scope, more decision rights, or more visibility. And sometimes it's a mix. Dan, it turned out, didn't want more scope – he was already stretched. What he really wanted was to be seen as the person who owned the API, to be the go-to. He wanted recognition, not more responsibility. Luna: So how do you parse that? I mean, you can't just ask 'what do you mean by ownership?' – that might put them on the defensive. Lucas: You can, but you have to phrase it well. I've started using what I call an 'ownership audit.' It's a set of six questions that help you get to the root of the ask. Questions like 'What does ownership look like in your ideal week?' and 'What decisions do you wish you were making today that you aren't?' Luna: That's smart. It makes it concrete. Let me guess – the answers usually reveal that they don't want more work, they want a different kind of work. Lucas: Exactly. In Dan's case, when Priya asked 'What decisions do you wish you were making?', he said he wanted to approve code reviews for the new integration. That was it. He didn't want to manage the whole project timeline or the vendor relationship – he just wanted the authority to merge pull requests without asking. It was a tiny ask that had nothing to do with scope. Luna: So the fix was simple. But what about when they genuinely do want more scope? How do you handle that without burning them out? Lucas: That's the harder case. You have to be honest about trade-offs. I remember an employee I had – Sarah – she wanted to own our entire data pipeline. She was talented, but she was already at capacity. So we did a 'swap,' not an 'add.' She took over a critical part, but we moved her legacy maintenance work to someone else. That way she got real ownership, but her total load stayed the same. Luna: A swap instead of an add – I like that. It respects their ambition without ignoring the math. Lucas: And the other key is to define the boundaries of ownership clearly. Ownership doesn't mean 'no one else can touch it.' It means you're accountable for the outcome, but you still have to collaborate. I've seen people ask for ownership because they want to work in a silo – that's a red flag. Luna: So you're saying ownership isn't just about control, it's about accountability. And accountability includes working with others. Lucas: Right. And that's where psychological safety comes in. If an employee asks for ownership and then fails, how you react determines whether they'll ever take initiative again. You have to make it safe to fail – not celebrate failure, but don't punish it either. Luna: We actually have a listener question about that – from a manager named Tom. He says: 'I gave my employee more ownership, but they made a costly mistake. Now they're scared to make any decisions. How do I rebuild their confidence?' Lucas: Great question, and timely, because it's the natural follow-up. First thing: don't just say 'it's fine.' That's vague. You need to do a post-mortem without blame. Ask 'What did you learn?' and 'What would you do differently?' Then, give them a smaller decision to own – something low-stakes but real – so they can rebuild their decision-making muscle. Luna: So it's about gradually increasing the stakes. That reminds me of how you teach someone to drive – you don't put them on a highway after a fender bender. Lucas: Exactly. And you also need to check your own reaction. If you're hovering or second-guessing them, they'll feel it. Trust has to be rebuilt on both sides. Luna: Let's go back to the ownership audit for a second – you said six questions. Can you walk us through all of them? Because I think our listeners would love a checklist. Lucas: Sure. One: 'What does ownership look like in your ideal week?' Two: 'What decisions do you wish you were making today that you aren't?' Three: 'What part of your current work energizes you most?' Four: 'What part drains you?' Five: 'What would be the first sign that you had more ownership?' And six: 'Who do you currently rely on for approval that you'd like to not rely on?' Luna: I love that last one – it gets to the specific bottleneck. And you can use it in a one-on-one without it feeling like an interrogation. Lucas: For sure. And the answers often surprise you. I had an employee who said she wanted more ownership, and when I asked about the first sign, she said 'not being cc'd on every email.' That's a classic – they don't want more responsibility, they want to be trusted to handle the details without oversight. Luna: So the fix there is to simply stop cc'ing them. That's a two-second change that makes a huge difference. Lucas: Yeah. But you have to be careful not to over-correct. Some employees use 'more ownership' as a way to avoid collaboration. They want to disappear into their work. That's not ownership – that's isolation. I've seen teams where one person 'owns' a project so tightly that no one else can learn anything, and that's a failure of leadership. Luna: So how do you handle that? If someone says 'I want more ownership' but they're not a team player, what do you do? Lucas: That's when you have to reframe ownership in terms of shared goals. Say, 'You can own this project, but part of that ownership is ensuring the team can contribute and learn. Can you commit to weekly updates and pairing sessions?' If they resist, then it's not about ownership – it's about control, and that's a different conversation. Luna: Control vs. ownership – that's a crucial distinction. I think a lot of managers confuse the two, and that leads to micromanagement or, conversely, to employees feeling like they're just pawns. Lucas: Exactly. Ownership is about having a stake in the outcome, not about having a monopoly on the work. And that's the mindset I try to instill in my managers. Luna: Before we go further – I know we're getting to the end, but I want to mention something. We get so many emails from listeners who say they've used the strategies from these episodes in their own teams, and it's made a real difference. That's why we keep doing this, and it's also why we keep it ad-free. Lucas: Yeah, and if you've gotten value out of these conversations, a small contribution on buy me a coffee dot com slash fexingo is genuinely what keeps us going. It's just a couple of dollars a month, but it adds up and lets us keep investing in research and guest prep. Luna: Absolutely. No pressure, ever – but if you've been meaning to show support, that's where you can do it. We'll be right back to the topic. Lucas: So, back to the ownership audit – one more thing I want to flag. When you do this audit, don't just use it as a one-time exercise. Revisit it quarterly. People's motivations change, and what they meant by 'ownership' in January might be completely different in August. Luna: Good point. I've seen that too – someone gets the ownership they wanted, and then they realize it's not what they thought. Or they get promoted and they need a different kind of ownership. Lucas: Right. And that's where the manager's job is to keep that conversation open. It's not a one-and-done. It's a continuous dialogue. Luna: So, to wrap up our main segment – what's the one takeaway you want our listeners to have from this episode? Lucas: I think it's that 'I need more ownership' is a starting point, not a destination. Your job as a manager is to be a translator – to help the employee articulate what they really want, and then to align that with what the team needs. That's where the magic happens. Luna: And we have a resource for you – we'll put the six-question audit in the show notes, so you can use it in your next one-on-one. Lucas: Before we go, I want to leave you with a question to reflect on: if you were to ask yourself that same audit, what would you say? Because as a manager, you also need ownership over your own development. Thanks for listening, and we'll see you next week.