Latest / Future of Work Tech with Fexingo: Remote Tools, AI Productivity, and Workplace Software / How the Four-Day Workweek Actually Works at Scale
Transcript
- Lucas: Luna, I want to talk about the four-day workweek — not as a headline or a perk, but as an operational reality. Luna: Good, because I feel like we've been hearing about it for years but I still don't know how it actually works at scale. Lucas: Exactly. So last year in the UK, a group called 4 Day Week Global ran a pilot with 61 companies — about 2,900 employees — and they just released the one-year follow-up data. I think it's the best real-world look we have. Luna: What were the headline numbers? Lucas: Revenue stayed flat or grew for 90% of the companies. Retention hit 92% — compare that to the UK average of around 80%. And sick days dropped by 35%. Luna: Those are hard to argue with. But I always wonder — is it really a four-day week, or is it just cramming five days of work into four? Lucas: That's the key question. And the pilot actually had two models. About half the companies went with a compressed schedule — longer Monday through Thursday, then Friday off. The other half went with reduced hours — they actually cut total weekly hours, usually from 40 to 32, and redesigned workflows to fit. Luna: The reduced-hours model sounds harder. How do you just cut 20% of your labour and still get the same output? Lucas: You have to be ruthless about what actually adds value. One fintech in the pilot, called Stitch, they analysed every recurring meeting. They cut 40% of them outright. Then they shifted the rest to async updates using Loom-style video messages and a tool called Twist for threaded conversations. Luna: So they replaced the default of 'let's meet' with 'let's record a three-minute update'. Lucas: Precisely. And they found that most decisions didn't require real-time discussion. The async model actually sped things up because people could respond on their own time rather than waiting for the next meeting slot. Luna: But I imagine some roles just don't fit. Customer support, for example — if your clients expect five-day coverage, you can't just close on Friday. Lucas: That's the real friction point. The pilot companies that succeeded didn't force the same schedule on everyone. A design agency called Gravity Road, they actually split their team: the creative side worked four days, reduced hours, but the client-facing account managers stayed on a five-day schedule with rotating Friday coverage. Luna: So it's not one-size-fits-all. It's more like a menu of options based on role type. Lucas: Right. And the companies that struggled were the ones that implemented it as a blanket policy without rethinking workflows. One retail company in the pilot actually dropped out after three months because they couldn't figure out how to handle inventory management with fewer days. Luna: That makes sense — a four-day week for warehouse staff is a completely different challenge than for software engineers. Lucas: Exactly. So the success stories all had something in common: they treated the four-day week as a redesign exercise, not just a scheduling change. Luna: And obviously, this is a show about the future of work tech. What software tools actually enable this? Lucas: Great question. The pilots leaned heavily on async-first tools. Slack was still used, but with strict norms — no after-hours pings, and channels organised by project, not by team. Then there's Notion for shared documentation, Loom for video updates, and a tool called Range for daily async check-ins. Luna: So it's not about having more tools — it's about using them differently. Lucas: Right. One company I read about, a marketing firm called Three Sixt, actually banned internal meetings on Wednesdays entirely. They called it 'deep work Wednesday'. And they used a tool called Focusmate — it's a virtual co-working platform — to pair people up for accountability during that time. Luna: That's interesting — using a tool to recreate the social pressure of being in an office, but only for focused work. Lucas: And it worked. Their output metrics — things like campaign turnaround time and client satisfaction scores — actually improved by about 15% after the switch. Luna: I wonder if we're seeing a broader shift in how we measure productivity. Moving from hours to output. Lucas: That might be the most important takeaway. The four-day week forces you to ask: what do we actually produce? Not how long do we sit at our desks. Luna: And if you can answer that honestly, you might find you can do it in four days. Lucas: Exactly. And that's a conversation that applies way beyond just the schedule change. Luna: Speaking of conversations that apply — this show stays ad-free thanks to listeners who support us. If today's tech conversation gave you something usable, you can buy us a coffee at buy me a coffee dot com slash fexingo. Lucas: Yeah, it really helps keep the lights on and lets us keep digging into these topics. No pressure — just if you find value. Luna: So back to the four-day week — one thing I want to dig into is the hidden costs. What do companies lose? Lucas: Sure. The most common issue is coordination overhead. When half your team is off on Friday, any project that spans the weekend can get delayed. One logistics company in the pilot reported that their project completion time increased by about 10% initially. Luna: But that seems like something you'd improve over time with better handoff processes. Lucas: They did. They created 'handoff documents' — essentially a one-page summary of where things stand at the end of Thursday. And they used a shared project management tool, Monday.com, to track dependencies. After three months, the delays were down to 2%. Luna: So it's a learning curve, not a permanent trade-off. Lucas: Exactly. And another hidden cost is cultural. Some employees actually missed the informal interactions that happen on a Friday — the watercooler moments. A few companies addressed this by hosting optional virtual social hours on Thursday afternoons. Luna: So you're deliberately building in time for serendipity, even on a shorter schedule. Lucas: Right. And the data from the pilot shows that employees who felt socially connected reported higher satisfaction even than those who just got the extra day off. Luna: That's a nuance I hadn't considered. It's not just about the day off — it's about whether the four days you do work feel meaningful and connected. Lucas: Exactly. And that brings us back to the redesign point. The companies that succeeded didn't just change the calendar — they changed how they collaborate. Luna: So if someone listening is considering a four-day week for their team, what's the first step? Lucas: Start with an audit of your current meetings and communication patterns. Track every recurring meeting for two weeks — ask: is this necessary? Could it be async? Could it be shorter? Most teams find they can cut 30% of meetings without losing much. Luna: And then pilot it with a single team first, not the whole company. Lucas: Exactly. The best pilots in the UK study started with one department — usually the engineering or creative team — ran it for three months, collected data, and then expanded. That way you learn the kinks before scaling. Luna: I think that's the most practical advice we've given on this show in a while. Lucas: Well, that's the goal. The four-day week isn't a magic bullet — it's a redesign project. But for the companies that do it right, the payoff is real. Luna: And the data keeps getting better. I'm curious to see how the next wave of pilots — especially in the US — will adapt the model. Lucas: Yeah, I think we're going to see a lot more experimentation in 2027. The conversation is shifting from 'should we do it?' to 'how do we do it well?'