Latest / Office Hours with Fexingo: Daily Career Q&A, Workplace Questions, and Professional Advice / How to Ask for a Stretch Assignment Without Sounding Lazy
Transcript
- Lucas: We got an email from James, a senior analyst at a midsize bank. He's been doing the same quarterly reports for eighteen months, and he's ready for something harder. But he's terrified that if he asks his manager for more challenging work, she'll think he's lazy or that he's complaining about his current assignments. Luna: That fear is incredibly common. Because the request can sound like 'I'm bored' which some managers hear as 'your work isn't good enough for me.' Lucas: Exactly. So today we're going to give James and anyone in that position a concrete script. One that frames the ask around business value, not personal ambition. And we'll talk about timing, because when you bring this up matters almost as much as what you say. Luna: Let's start with the mindset shift. Instead of 'I need more stimulation,' what's the better framing? Lucas: The framing is: 'I want to be more useful to the team and the company.' That's a line James can actually say. It's not about him; it's about the organization. He can say, 'I think I have capacity to take on something that solves a real problem we've been discussing.' That's hard for a manager to reject because it's offered as help. Luna: And it signals that he's paying attention to what the team needs, not just his own resume. Lucas: Right. So step one: identify a specific project or gap that matters to the business. Not just 'I want to learn data science.' Something like, 'I noticed our quarterly client review process still takes three weeks to compile. I'd like to build a dashboard to cut that to three days.' That's concrete. Luna: And it's tied to a metric. Managers love that. But what about the script itself? How does James actually open the conversation? Lucas: He schedules a one-on-one, and he starts with gratitude. 'Thanks for the opportunity to work on the Q2 report — I learned a lot.' Then he transitions. 'I've been thinking about how I can contribute more. I see we're struggling with X. I'd like to take a crack at solving it, even if it's a stretch for me. Could we discuss how to make that work?' Luna: I like the word 'stretch.' It acknowledges that it's outside his comfort zone without sounding like he's already mastered everything. Lucas: Exactly. And he should add one sentence that addresses the workload concern head-on: 'I'll keep my current deliverables on track. This would be additional, and I'm happy to reprioritize if needed.' That shows responsibility. Luna: What if the manager says, 'We don't have budget for that,' or 'It's not the right time'? Lucas: Great question. That's why he needs a Plan B. If the specific project gets declined, he can pivot to: 'Is there a different project I could shadow or assist with? Or could I spend 10 percent of my time cross-training with the analytics team?' The goal is to keep the conversation alive, not to get a single yes or no. Luna: So it's less about that one ask and more about opening a dialogue about growth. Lucas: Yes. And the best time to have this conversation is right after you've delivered something solid. James should wait until he's submitted a clean report, gotten some positive feedback, then schedule the one-on-one. That way the manager already sees him as competent. Luna: What about the opposite scenario — where the manager is the one who's overwhelmed and might worry that giving James more work will mean he drops existing tasks? Lucas: That's a real risk. So James can say, 'I know you're busy. I don't want this to add to your plate. I'll draft a proposal and we can review it together in fifteen minutes.' That reduces the manager's cognitive load. The ask becomes easier to say yes to. Luna: I also think there's a power in using the phrase 'I'd like to try.' It's less demanding than 'I need this.' Lucas: Absolutely. 'I'd like to try building that dashboard. If it doesn't work, we can pull the plug. But I think it could save us a week per quarter.' That's low risk, high potential reward. Luna: So to recap for James: prepare a specific proposal, time it after a win, start with gratitude, use 'stretch' language, and have a backup plan. Lucas: And one more thing: follow up in writing. After the conversation, send a short email summarizing what you discussed. 'Thanks for the chat. I'm excited to explore the dashboard idea. I'll send a one-pager by Thursday.' That shows initiative and makes it real. Luna: It also protects James if the manager later says, 'I don't remember agreeing to that.' Lucas: Right. Now, if that template saves anyone a week of agonizing over the right words, that's exactly why we do this show. Luna: Yeah, and it's also why we keep the show ad-free — listener support on Buy Me a Coffee lets us focus on real advice without sponsors. Lucas: Exactly. If today helped you, buy me a coffee dot com slash fexingo. Now, one more thing to consider before you schedule that meeting. Luna: What's that? Lucas: The emotional risk. Even with the perfect script, you might get a no. But that no doesn't mean you're stuck forever. It tells you something about the manager and the culture. If you get a flat 'we don't do that here,' that's data. You might need to find allies elsewhere or start looking at other teams. Luna: That's a hard truth. But better to know early than to stay underutilized for another eighteen months. Lucas: Exactly. So use the script, but also read the response. And if you get a yes, deliver on that stretch assignment like it's the most important thing you've ever done. Because it might be. Luna: That's a good note to end on. For James and everyone else, good luck. Lucas: Thanks for listening. See you next time.