The Imaginary Wednesday: What Your Team Would Really Do With an Extra Workday
Photo by Photo by Brands&People on Unsplash on Unsplash
Ask a room of UK office workers what they'd do with a spare day each week and you'll usually get two answers. One is sleep. The other is "finally sort out the thing" — and nobody says which thing. Both are honest. Only one is useful.
The eight-day week is a thought experiment, not a policy proposal. Nobody is suggesting your operations director can find an extra 24 hours behind the sofa. But as a diagnostic it works surprisingly well, because it removes the two excuses that kill most capacity conversations — "we haven't got time" and "we'd need to hire" — and forces a team to say out loud what they'd actually spend the time on. The answer is almost never what the org chart implies, and it is rarely fixed by a headcount request.
Why a Fake Day Beats a Real Survey
Capacity surveys ask people to estimate percentages. Almost nobody is good at this, and the people who are good at it are usually the ones with the least representative week. Ask someone what proportion of their time is "strategic" and you'll get a number invented on the spot to sound reasonable.
An imaginary day asks a different question. It doesn't ask people to describe their work — it asks them to reveal their preferences. Preferences are much harder to fake, and much more revealing. If eight people in a team independently say they'd spend the day on the same backlog, that backlog is real. If the answers scatter across nine different priorities, you've learned something else entirely.
The exercise also dodges the trap of the four-day week debate. That conversation instantly becomes about contracts, HR and whether anyone has read the pilot evidence. This one is about where the work goes. It's a workflow question dressed up as a joke, which is often the only way to get a straight answer.
The 45-Minute Format
You need between six and twelve people, ideally a mix of those who do the work and those who receive it. A room or a decent video call. A timer. That's it.
Minutes 0–5: Frame it properly. Say the rules out loud. The day is imaginary, it costs nothing, it can't be traded for overtime, and it doesn't come with a budget. It's just an extra Wednesday that arrives fully staffed and fully paid.
Minutes 5–15: Silent writing. Everyone writes down what they'd genuinely do with it, in two or three specifics. Silent, on paper or in a shared doc, no discussion. This step matters — the first person to speak sets the frame for everyone else.
Minutes 15–30: Group and name. Go round, read them out, and sort into three piles without arguing about it: the backlog, the busywork, and the deferred thing.
Minutes 30–40: Dot voting. Three votes each, no campaigning. Then look at the top four items.
Minutes 40–45: One question. For each of the top four, ask: "What's stopping us doing this on a normal Wednesday?" Write the answers verbatim. Don't solve anything yet.
Three Piles, and What Each One Is Telling You
The backlog is the easiest to spot and the least interesting. If most of the day goes here, the team is telling you it's carrying work it never agreed to finish — usually the tail end of a project that got declared done in a slide deck months before it was.
The busywork is where it gets uncomfortable. If people would spend a fantasy day on tidying a shared drive, rebuilding a spreadsheet or chasing a report that nobody reads, that isn't a capacity problem. That's a process that has quietly outgrown its purpose and is being propped up by habit. An extra day would simply give it more room to grow.
The deferred thing is the interesting one. It's the migration nobody's booked, the handover that's still living in one person's head, the documentation that would take a day to write and would save forty. It's always known about. It's never scheduled. When it tops the vote, you've found the gap between what the team believes matters and what the calendar permits.
The Tells Worth Watching For
Read the room, not just the votes. If the same four names appear in every pile, that's a dependency, not a workload. If the answers split neatly along team boundaries — one group says backlog, another says the deferred thing — you probably have two workflows sharing an office rather than one.
And watch for the person who says, quietly, that they'd use the day to catch up on everything they're behind on. That's not a preference. That's a signal that the ordinary week has no slack left, and it's worth a follow-up conversation the same week.
It's Almost Always a Workflow Problem
The tempting conclusion is that you need more people. In our experience of running this with teams across Leeds, Bristol and the usual London postcodes, that conclusion arrives far too fast. More often, the imaginary day exposes a queue that nobody owns, an approval that takes four days because it waits on one person's inbox, or a recurring report that three teams maintain separately.
Those are all workflow problems. They're fixable without a recruitment round, and — importantly — they'd still be there after a hire. Adding a person to a broken queue mostly adds someone else waiting in it.
Do It Again in February
Run the exercise once and you have a snapshot. Run it again after a quarter and you have a trend. If the same item tops the vote twice, that's not a wish — that's an overdue decision. If the answers have shifted entirely, something changed in the work and nobody told the people doing it.
Either way, take the top item from the vote and put it in a real calendar for a real day. Not as a transformation programme. As an afternoon. The point of the imaginary eighth day isn't to get one. It's to find out what you'd do if you had one — and then wonder why you're not.