Latest / Office Hours with Fexingo: Daily Career Q&A, Workplace Questions, and Professional Advice / How to Ask for a Work Schedule Change That Sticks
Transcript
- Lucas: You've been in your role eighteen months. Your performance reviews are strong. And you've realised the thing that would actually make you stay — not a bigger title, not more money — is a four-day workweek. Not the casual 'hey, I might work from home on Fridays' kind. A real, permanent compressed schedule. How do you ask for that without sounding like you're checked out? Luna: I think that's harder than asking for a raise. Because with a raise, the message is 'I'm worth more.' With a schedule change, the manager hears 'I want to work less.' That's a harder sell. Lucas: Exactly. And yet, the data on four-day weeks is pretty compelling. The big trial in Iceland — between 2015 and 2019, about twenty-five hundred workers shifted to a thirty-five or thirty-six hour week with no pay cut. Productivity stayed the same or improved in most workplaces. Microsoft Japan tried it in 2019, reported a forty percent productivity boost. So the argument isn't theoretical anymore. Luna: But the person listening right now doesn't work for Microsoft Japan. They work for a sixty-person accounting firm or a mid-size marketing agency. The manager's first thought is going to be 'who covers Tuesday afternoon?' Lucas: Right. And that's the core of the negotiation. You have to answer that question before the manager asks it. I want to walk through a real listener letter we got — Sarah, a senior accountant at a regional firm in Cleveland. She wanted to move to a four-day week, but she was up for senior manager in the next review cycle and didn't want to jeopardise it. Luna: So the stakes were real. It wasn't just a schedule change — it was a promotion path. Lucas: Exactly. And what Sarah did well was she didn't start with the ask. She started with a business case. She looked at her team's workflow and realised that Friday afternoons were consistently low-volume — maybe ten percent of the week's client work landed then. She proposed working Monday through Thursday, seven AM to five thirty PM, which gave her a ten-hour day and a total of forty hours. No reduction in hours, just a compression. Luna: That's smart because the manager can't say 'you'll produce less.' The hours are the same. Lucas: And she added a second layer: coverage. She identified that the only real Friday need was a client call that rotated among three senior accountants. She offered to take the Friday slot when it was her turn — just take the call from home, log an hour, and still keep her three-day weekend. That addressed the fairness concern: she wasn't dumping Friday work on colleagues. Luna: But I imagine the manager still worried about precedent. If Sarah gets a four-day week, everyone will ask. Lucas: And that's the third piece. She proposed a ninety-day pilot. Measurable output: number of monthly reports completed, client response times, internal project deadlines. At the end of the pilot, she and her manager would review the data and decide whether to make it permanent. That turned it from a permanent policy change into an experiment. Luna: A pilot is easier to say yes to. The manager isn't committing forever. They're saying 'let's try it.' Lucas: And that's the playbook. Three parts: business rationale — here's why it works for the company, not just for me. Logistics — here's exactly how coverage works, here's my schedule in detail, here's how I handle the Friday call. And a trial period with metrics. Sarah got her four-day week. She also got the promotion six months later. Luna: I want to talk about the psychology for a minute. Because I think a lot of people sabotage themselves by being too vague. They say 'I'd like some flexibility' or 'could I maybe work from home on Fridays?' The manager hears 'I want to slack off.' Lucas: Vague requests get vague answers. 'Let's revisit in six months.' Or 'I'll think about it' — which means no. The specificity is what forces a real decision. If you say 'I propose working seven to five thirty Monday through Thursday, with a thirty-minute lunch, and I'll handle the Friday client call from home when it's my turn' — the manager can't punt. They have to either say yes, or explain why the specific plan doesn't work. Luna: That's a good framework. But what about people who want a genuine reduction in hours? Not compressed, but genuinely fewer. Say a parent who wants to go to thirty-two hours a week. Lucas: That's a different negotiation, because now you're talking about less total work output. The playbook still applies, but the business case has to be stronger. You need to show that the role can be done in four days — that the fifth day is genuinely low-value. Or you need to show that you can redesign the role to fit thirty-two hours. Some companies are open to this, especially for roles with cyclical workloads. But the data from the UK four-day week trial in 2022 showed that about half the companies that tried a reduced-hours model kept it after the trial. So it's not impossible. Luna: One thing I want to flag: if you ask for a reduced schedule and your company says no, that doesn't have to be the end. You can ask 'what would it take to make this work?' Maybe they're worried about client perception. Maybe they need you to be available for one specific weekly meeting. You can often negotiate a version that works for both sides. Lucas: That's the thing about any career ask — it's a conversation, not a demand. And speaking of that, I want to mention something we don't do on this show. We don't run ads. No sponsors, no commercials. The reason is simple: we want to give you the most direct, unfiltered advice we can. If you've found this episode useful — or any episode — and you want to support that approach, you can do that at buy me a coffee dot com slash fexingo. It's a small way to keep the show ad-free and focused on what matters. Luna: Yeah, it's a nice model. No one trying to sell you a CRM or a mattress. Just career advice. So if that resonates, the link is there. Lucas: Alright, back to schedule changes. One more tactic I want to share: the 'reverse pilot.' Instead of asking for a permanent change, you say 'I'd like to try a four-day week for the next quarter. If productivity dips, we go back to the old schedule. If it holds or improves, we talk about making it permanent.' That's even lower risk for the company. Luna: I've seen that work. A friend in tech did exactly that — she proposed a three-month trial of a four-day week, with weekly check-ins. After two months, her manager said they didn't even need the check-ins anymore. The work was getting done. Lucas: And that's the proof. The best argument for a schedule change is the data from the trial. So if you're thinking about making this ask, start preparing now. Track your output. Know your team's workflow. Anticipate the objections. And then have the conversation with confidence. Luna: One last thing: what if your company has a formal policy against compressed schedules? Do you still ask? Lucas: That's harder, but not hopeless. Some companies have rigid policies but make exceptions for high performers. If you're a top performer, you can ask for an exception. Frame it as 'I know the policy, but I'd like to discuss a pilot for my specific role.' The worst they can say is no. And if they say no, you've at least planted the seed. You can ask again in six months. Luna: And if they say no and you're a top performer, that's useful information too. It tells you something about the company's flexibility. Lucas: Exactly. And sometimes the answer is 'not right now, but check back after this project.' So don't treat a no as permanent. Treat it as 'not yet.' Luna: Good advice. So the key takeaways: build a business case, get specific about logistics, propose a trial, and be ready to negotiate the details. Lucas: And remember, the goal isn't to trick your manager into saying yes. It's to show that a schedule change can work for everyone. If you go in with that mindset, you're already ahead. Luna: Great episode. Next time we'll talk about how to ask for a project that doesn't exist yet — creating your own role. Lucas: That's a good one. Until then, good luck with the conversation.