Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Get Your Team to Actually Own Decisions
Transcript
- Lucas: A few months ago I was talking to a VP of Engineering at a mid-sized software company — about two hundred people. And he told me something that stuck with me. He said his biggest frustration wasn't code quality or deadlines. It was that his seven direct reports kept bringing decisions to him that they should have been making themselves. Luna: That sounds familiar. I've seen that dynamic in a lot of teams — people run everything up the chain, and the manager becomes a bottleneck without even realizing they're enabling it. Lucas: Exactly. And this VP — let's call him Mark — he realized that he was the bottleneck. Every time someone came to him with a question, he'd answer it. He thought he was being helpful. In reality, he was training his team to not think for themselves. Luna: So what did he do? Did he just stop answering questions? Lucas: Not exactly. He introduced a two-question framework. Before anyone could bring a decision to him, they had to be ready to answer two things: first, 'What do you recommend?' and second, 'What data or reasoning supports that recommendation?' Luna: That's a classic approach — I've seen versions of it. But the key is how you enforce it. Did he just tell them, or did he actually change the behavior? Lucas: He changed the behavior by modeling the new norm. For the first two weeks, every time someone came to him with a question, he'd pause and ask, 'What do you recommend?' If they didn't have an answer, he'd say, 'That's fine — go think about it and come back when you do.' He didn't give them the answer. Luna: That takes discipline. Most managers cave because it's faster to just answer. Lucas: It does. But Mark said that after about three weeks, his team started preemptively coming with recommendations. They knew the question was coming, so they prepared. And after two months, he said the number of one-on-one meetings where he was just giving direction dropped by about 40 percent. Luna: Forty percent — that's huge. What did he do with that time? Lucas: He spent it on more strategic work — thinking about team structure, coaching his managers on their own leadership, and doing skip-levels with people two layers down. He said the quality of decisions actually improved too, because his team had to articulate their reasoning. Luna: There's a subtlety here though. If you just ask 'What do you recommend?' without creating psychological safety, people might give you a safe answer — something they think you want to hear, not what they actually believe. Lucas: That's a great point. Mark addressed that by explicitly thanking people when they brought a recommendation that disagreed with his initial view. He told me one of his best engineers recommended a completely different technical approach than what Mark had in mind, and Mark said, 'I disagree with your conclusion, but I love that you brought this — let's talk through the trade-offs.' Luna: That's the difference between performance and learning. When you reward the act of thinking independently, you get more of it. Lucas: Exactly. And the second question — about data and reasoning — is what separates real ownership from just having an opinion. Mark told me that early on, people would say, 'I recommend we use AWS instead of Azure,' and when he asked for reasoning, they'd say, 'I just think it's better.' That forced them to go back and actually compare costs, latency, and team expertise. Luna: So the framework also improved the quality of their preparation overall — not just for decisions they brought to him, but for all decisions. Lucas: Right. And that's the multiplier effect. Once people internalize that they need to have a reasoned recommendation before they raise an issue, they start thinking that way for everything. Mark said the team's decision speed increased by about two weeks on average for mid-sized decisions — things like choosing a vendor or selecting a technology stack. Luna: Let me push back a little. What about situations where someone genuinely doesn't have enough context to make a recommendation? If you're a first-time manager and your VP asks you to recommend a new hiring process, but you've never done that before — asking for a recommendation could backfire. Lucas: That's a fair concern. Mark's approach here was to distinguish between decisions where the team member had the relevant experience and ones where they didn't. For the latter, he'd provide context first — share what he knows about past attempts, constraints, stakeholders — and then say, 'Now, with that context, what do you recommend?' Luna: So he's not leaving them to guess. He's giving them the scaffolding, then asking for their judgment. Lucas: Exactly. And sometimes the recommendation will be, 'I recommend we don't make a decision yet — we need more data.' That's a valid recommendation too. The point is that the team member is owning the decision process, not just being a passive recipient of orders. Luna: What about the risk of false ownership — where someone makes a recommendation but doesn't really believe in it? They just go through the motions. Lucas: That's a real risk, and Mark saw it with one of his managers. The manager would bring a recommendation, but when challenged, he'd immediately fold and agree with whatever Mark said. Mark realized that was a sign of low psychological safety — the manager was afraid to hold his ground. Luna: How did Mark handle that? Lucas: He started specifically asking, 'What's the strongest argument against your recommendation?' If the manager could articulate that, even if he still recommended the same thing, Mark knew he'd thought it through. And if the manager couldn't, Mark would say, 'Let's think about the downsides together' — which built the manager's ability to do that independently next time. Luna: That's smart. You're training them to consider counterarguments, which is the core of real ownership. Lucas: Yeah. And it also helps the manager detect when he's advocating for something he doesn't actually believe — because if he can't defend it against a strong counterargument, he probably doesn't believe it. Luna: So the framework really has two layers: the surface layer of 'come with a recommendation and data,' and the deeper layer of 'be ready to challenge your own recommendation.' Lucas: That's exactly right. And I think that's the part most managers miss. They implement the first layer — 'don't come to me with problems, come with solutions' — and they think that's enough. But without the second layer, you get shallow ownership. People bring a recommendation, but they haven't stress-tested it. Luna: One more thing I want to touch on: how do you scale this from a team of seven to a larger organization? If you're a VP with multiple layers below you, you can't do this in every interaction. Lucas: Mark's approach was to model it with his direct reports and then expect them to model it with theirs. He told me that after three months, his direct reports were using the same two-question framework with their own teams. It cascaded naturally, because the first-line managers saw that their VP wasn't giving them answers, so they stopped giving answers to their teams. Luna: That's the ideal. But it requires the VP to be consistent. If he relapses and starts giving answers again, the whole chain breaks. Lucas: He admitted that happened once. He had a tight deadline and just told someone what to do. The next week, three people came to him with questions they could have answered themselves. He had to explicitly walk it back and apologize — said, 'I slipped, that was my fault, let's go back to the framework.' Luna: That's a good example of manager vulnerability, which we talked about in episode ten. Admitting you broke the norm actually reinforces it. Lucas: It does. And I think that's a key takeaway from this episode — building a culture of decision ownership isn't a one-time training. It's a daily practice, and it requires the manager to be disciplined about not taking the shortcut. Luna: Speaking of practice, if listeners want to try this framework with their own teams, what's the first step you'd recommend? Lucas: I'd say start with one recurring decision — something that comes up weekly, like approving time-off requests or choosing which project to prioritize next. Tell your team, 'For this one type of decision, I want you to bring me a recommendation and the data behind it.' Don't try to change everything at once. Pick one decision type, practice it for two weeks, and then expand. Luna: And when they bring a recommendation, even if it's not what you would have chosen, let them run with it at least once — as long as it's not catastrophic. That builds the trust that ownership is real. Lucas: Yes. The first time someone brings a recommendation that you disagree with, and you let them try it anyway, that's when the culture shifts. Because they see you're serious. Luna: And if we've helped you think about how to approach a decision with your own team — maybe you're a first-time manager trying to shift the dynamic — we'd love it if you considered supporting the show. It's what keeps us ad-free and focused on real, practical content. You can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, and completely optional — honestly, just knowing people are listening and using this stuff is the main reward. But if you want to help keep the lights on, that link is there. Luna: Alright, back to the framework. One thing I want to circle back to — Mark mentioned that decision speed increased by about two weeks. How did he measure that? Lucas: He tracked it informally by looking at the time between when an issue was first raised and when a decision was made. Before the framework, that cycle was often three to four weeks because decisions would sit in his inbox. After, it was more like one to two weeks. He didn't publish a dashboard or anything — just noted the shift. Luna: That's believable. The bottleneck was him, so removing the bottleneck speeds things up. Lucas: And that's the real lesson — sometimes the fastest way to improve team decision-making is to get out of the way. Not by abdicating responsibility, but by creating a structure where people can own decisions with confidence. Luna: And knowing when to step back in. Because you're still accountable. Lucas: Right. Ownership doesn't mean abandonment. It means setting clear boundaries — 'you own this decision, but if it goes wrong, I'll back you up and we'll learn from it.' That's the balance.