Latest / Work-Life Balance with Fexingo: Boundaries, Time Management, and Avoiding Career Overload / The One Question That Ends Overwork Culture
Transcript
- Lucas: There's a question that, if you ask it before every new piece of work lands on your plate, can cut your workload by maybe thirty percent. And almost nobody asks it. Luna: Okay, I'm hooked. What's the question? Lucas: It's deceptively simple: 'What would this look like if I delegated it?' Not 'Should I delegate it?'—that's a yes or no that your brain will almost always answer 'no' to. But 'what would it look like' forces you to picture the thing already done by someone else. Luna: That is simple. But I can already feel the resistance—my first thought is 'it would take longer to explain it than to do it myself.' Lucas: Exactly. And that's the biggest mental blocker. There's a Harvard Business Review study from a couple years back—they surveyed over a thousand managers, and eighty percent said they know they should delegate more, but only twenty percent actually do. The top reason? 'It's faster if I do it.' Luna: That stat is depressing. But also, I mean, sometimes it is faster in the moment. Lucas: Yeah. If today this episode was useful to you, the way we keep these conversations ad-free is listener support. If you're able, you can buy me a coffee dot com slash fexingo. It really does help us keep going. Luna: Absolutely. We're grateful for every coffee. And Lucas, you were saying about the 'faster' trap? Lucas: Right. The 'faster' trap is real for a single task. But the math changes when you multiply it by every task over a month. That study found that managers who systematically delegated saved an average of six hours a week. That's a full workday. Luna: Six hours. That's huge. So how does the question actually work in practice? Like, what's the script? Lucas: I think it goes like this. Step one: you write down the task. Not 'help with the quarterly report'—that's too vague. But 'pull the raw sales data from Salesforce, clean it, and create a pivot table.' Now you have a concrete unit of work. Step two: ask 'who on my team or in my network has the capability or near-capability to do this?' Step three: frame the request as a development opportunity, not a dump. Luna: The development opportunity framing—that's key. Because if you just dump work on someone, they resent it. But if you say 'I think this could be a good stretch for you,' they're more likely to take it on. Lucas: Exactly. And there's research on that too. A study in the Journal of Applied Psychology found that when delegation is framed as trust and development, employee engagement goes up. When it's framed as 'I'm too busy,' engagement drops. So the language matters. Luna: What about the fear of losing control? I think that's a big one for a lot of people, especially if the task is high-visibility. Lucas: Huge. And I think the antidote is the 'delegation trial.' You don't hand over the whole thing forever. You say 'let's try this for two weeks. You own it, I'll review the output once a week. If it works, great. If not, we adjust.' That lowers the stakes. Luna: A trial takes the pressure off. And it gives the other person room to ask questions without feeling like they're failing. Lucas: Right. And it also forces you to clarify what 'done' looks like. Most delegation fails because the person delegating didn't define success clearly. So in that trial, you say 'here's the outcome I need, here's the deadline, here's the level of quality I expect.' That's it. Luna: Let's make this concrete. Give me a real example from your experience or something you've seen. Lucas: Sure. I worked with a marketing director at a mid-size software company. She was drowning in weekly reporting. Every Monday she'd spend four hours pulling numbers from four different platforms, formatting them into a slide deck, and writing analysis. It was her least favorite task. She used the question: 'What would this look like if I delegated it?' She realized her junior analyst had the Excel skills but had never written the narrative. So she delegated the data pull and formatting to the analyst, and kept the analysis piece for two weeks. Then she taught the analyst her analysis framework. After a month, the analyst owned the full report. The director saved four hours a week. Luna: Four hours. That's half a day. And the analyst got a promotion-worthy skill. Lucas: Exactly. And the director told me the hardest part wasn't the teaching—it was letting go of the feeling that only she could do it right. That's the emotional work. Luna: So the real boundary isn't about time management. It's about identity. 'I'm the one who does this' versus 'I'm the one who grows others to do this.' Lucas: That's a beautiful way to put it. The shift from hero to manager. And I think that's why the question works—it short-circuits your ego. Your brain can't answer 'what would it look like' with 'I'm indispensable.' It has to picture a different reality. Luna: What about people who don't have direct reports? Can they still use this question? Lucas: Absolutely. Delegation doesn't require hierarchy. You can delegate sideways—to a peer in a different department who's better at something—or even upward, to your boss, if you frame it as 'you're better at this than I am, can you handle it?' Or you can delegate to tools: automation, templates, AI. Luna: Upward delegation—that's gutsy. How do you do that without sounding like you're shirking? Lucas: You lead with respect. 'I know this is your area of expertise, and I think you could do this in half the time it would take me. Could I shadow you on it this time so I can learn for next time?' That's not shirking—that's strategic learning. Luna: I like that. It turns delegation into a mentorship moment. Lucas: Yes. And for peers, you can trade tasks. 'I hate doing data entry, but I love writing copy. You hate writing copy, but you're fast at data entry. Let's swap.' That's horizontal delegation. Luna: So the question applies across the board. But I imagine the biggest blocker is still the guilt. Like, 'I shouldn't offload this onto someone else.' Lucas: Guilt is huge. Especially if you've been conditioned to be the reliable one. But I think the reframe is: by not delegating, you're actually hoarding opportunities. If you do everything yourself, you're denying others the chance to grow. So delegation is generous. Luna: That's a powerful reframe. 'Hoarding opportunities.' I've never thought of it that way. Lucas: It flips the guilt on its head. And it's true—the best leaders I've seen are the ones who actively seek out tasks to give away because they see it as developing their team. Luna: Okay, so the question is 'What would this look like if I delegated it?' And we've got the three steps: define the task, find the person, frame as development. Any other tips for making it stick? Lucas: One more: start with something small and low-risk. Not the board presentation. But maybe the weekly status update email. Delegate that for two weeks and see if the world ends. It won't. And the relief you feel will motivate you to do it again. Luna: Low stakes, high reward. I like it. I think I'm going to try it this week with a recurring report I do. Lucas: Do it. And let me know how it goes. I bet you'll find that the person you delegate to does it differently—maybe even better. And then you've got a new standard. Luna: That's the dream, right? That someone else does it better and you get your time back. Lucas, this was a good one. Lucas: Thanks, Luna. One question, one change. See you next time.