Skip to content
Nobody Missed It Yet All fifty notes

Thirty-eight removals, seventy-eight weeks

Nobody missed it yet

A four-day week works by taking things out of the week. Fourteen of the thirty-eight things taken out here have not been asked for since. Five turned out to matter, and the record took a median of thirty-one weeks to say so.

0132639526578WEEKS FROM THE START — THE TRANSITION TOOK 1178 WEEKS WATCHED
50notes on a week that got shorter by having things taken out of it
6parts, from what stopped to what it costs to find out late
38things written down as they stopped, during one organisation's move to a four-day week
14of them nobody has asked for in the 78 weeks since

Nothing here is a survey and nothing is a benchmark. Every figure on this site comes from one organisation's list, kept as the transition ran and marked up for seventy-eight weeks afterwards, and the only claim made for it is that it was kept. No person, employer or workplace is named anywhere. This site does not say whether anybody should work four days: it says what a shorter week costs to find out about, which is a different question.

Six parts, from what stopped to what it costs to find out late

Every note belongs to one of them. The line at the foot of each card is what that part came to on the record counted here, stated as a count rather than as a conclusion.

What stopped

What a shorter week actually removes

Four days hold fewer hours than five, and the hours that go take work with them. The thirty-eight things that stopped here, and what sort of thing they were.

thirty-eight removals in eleven weeks

The lag

When anyone noticed

The distance between taking something out and finding out whether it mattered. On this record it ran from one week to sixty-four, and the long end is where the trouble is.

median thirty-one weeks before a problem surfaced

The quiet ones

The quiet ones

Of the nine removals somebody argued about, none later surfaced as a problem. Of the seventeen nobody remarked on, four did. This is the finding, and it is not a coincidence.

none of nine argued, four of seventeen unremarked

What came back

What came back, and how much of it

Twenty-four returned in some form, at a median of just under half the load they carried before. The number that cuts against this site's own title.

median just under half the old load

Other shapes

Other shapes of week

Compressed hours, a nine-day fortnight, staggered cover and annualised time each force a different set of removals. What each one takes out, and where its own lag sits.

four shapes, four different lists

Taking things out

How to take something out

Write the list, mark the quiet ones, and set the review window to the thing rather than to the quarter. Three habits, none of which is an argument for a shorter week.

three habits and an hour

One transition, counted three ways

Three panels built from the same list: every removal written down as it happened, set against what became of it; the same removals sorted by how loud each one was at the time it went; and the ones that came back, set against how much of the old load came back with them. Nothing here is a survey and nothing is a benchmark. It is one list, kept as it ran, and the only claim made for it is that it was kept. Nobody is identified anywhere here — not a person, not an employer, not a place.

Thirty-eight removals from one eleven-week transition, and what became of each over the seventy-eight weeks after
Removal0132639526578What became of it

The quarterly reconciliation of the project ledgerAn audit asked for a year of figures and nobody could assemble them inside a fortnight

week 3 · surfaced after 31 weeks

Shadowing new starters through their first weekThree of the four people who joined that year left inside eight months

week 6 · surfaced after 47 weeks

Reading supplier contracts before renewalTwo renewals went through on terms nobody had read

week 2 · surfaced after 22 weeks

The standing slot for work with no ownerSmall jobs that belonged to nobody stopped happening at all

week 5 · surfaced after 14 weeks

Logging why a job was turned downThe same reason for refusing was worked out from scratch four times

week 9 · surfaced after 64 weeks

The Monday planning hour

week 1 · asked back after 2 weeks

Printed copies of the weekly rota

week 0 · asked back after 1 week

A second reviewer on routine changes

week 4 · asked back after 3 weeks

Visits to the two furthest sites

week 7 · asked back after 12 weeks

The written handover at the end of a shift

week 2 · asked back after 2 weeks

Keeping the stock list on paper as well

week 3 · asked back after 5 weeks

Month-end figures circulated to everyone

week 5 · asked back after 8 weeks

Tea and biscuits put out on ThursdaysThe fastest request on the list, and the only one nobody could name a cost for

week 8 · asked back after 3 weeks

The meeting held before the meeting

week 1 · crept back after 6 weeks

Two people on every delivery

week 4 · crept back after 9 weeks

The daily stand-up

week 0 · crept back after 3 weeks

A written note after every phone order

week 6 · crept back after 4 weeks

Checking the diary a day ahead

week 2 · crept back after 11 weeks

The Friday clean-down of the workshop

week 9 · crept back after 22 weeks

Chasing unpaid invoices every week

week 3 · crept back after 2 weeks

A named person on the phone until six

week 7 · crept back after 5 weeks

The spare key log

week 10 · crept back after 14 weeks

Counting stock on the first of the month

week 5 · crept back after 7 weeks

Keeping the induction folder up to dateThe slowest return on the list, and nobody can say who restarted it

week 8 · crept back after 29 weeks

The monthly slide deck nobody presented

week 1 · still not missed

Copying three managers on every order

week 2 · still not missed

The annual away day

week 11 · still not missed

Weekly timesheets broken down by task

week 3 · still not missed

Minutes of the standing meeting

week 4 · still not missed

The suggestion box

week 6 · still not missed

Signing in and out of the building

week 7 · still not missed

A second quote on purchases under fifty pounds

week 2 · still not missed

The printed catalogue kept at the front desk

week 5 · still not missed

Re-sending the rota as a reminder

week 0 · still not missed

The colour-coded wall planner

week 9 · still not missed

A written agenda for every one-to-one

week 6 · still not missed

Laminating the safety notices each year

week 10 · still not missed

The standing item for any other business

week 8 · still not missed

Not missed 14Crept back 11Asked back 8Surfaced 5

Thirty-eight removals were written down with the week each of them stopped. Fourteen of them have not been asked for in the 78 weeks since. Of the rest, eight were asked back, eleven crept back and five surfaced as a problem. The left edge of every interval sits inside the first eleven weeks, because that is how long the transition took. The right edge is spread across a year and a half. That difference between the two densities is what this site is about.

The same thirty-eight, sorted by how much noise each removal made on the day it happened

Arguedsomebody objected to losing it9 removals · 0 surfaced · median lag 4.5 weeks

The Monday planning hour

2 weeks

Printed copies of the weekly rota

1 week

A second reviewer on routine changes

3 weeks

Visits to the two furthest sites

12 weeks

The meeting held before the meeting

6 weeks

Two people on every delivery

9 weeks

The monthly slide deck nobody presented

not missed

Copying three managers on every order

not missed

The annual away day

not missed

Questionedsomebody asked about it, nobody objected12 removals · 1 surfaced · median lag 6.5 weeks

The standing slot for work with no owner

14 weeks

The written handover at the end of a shift

2 weeks

Keeping the stock list on paper as well

5 weeks

Month-end figures circulated to everyone

8 weeks

The daily stand-up

3 weeks

A written note after every phone order

4 weeks

Checking the diary a day ahead

11 weeks

The Friday clean-down of the workshop

22 weeks

Weekly timesheets broken down by task

not missed

Minutes of the standing meeting

not missed

The suggestion box

not missed

Signing in and out of the building

not missed

Unremarkednothing was said either way17 removals · 4 surfaced · median lag 18 weeks

The quarterly reconciliation of the project ledger

31 weeks

Shadowing new starters through their first week

47 weeks

Reading supplier contracts before renewal

22 weeks

Logging why a job was turned down

64 weeks

Tea and biscuits put out on Thursdays

3 weeks

Chasing unpaid invoices every week

2 weeks

A named person on the phone until six

5 weeks

The spare key log

14 weeks

Counting stock on the first of the month

7 weeks

Keeping the induction folder up to date

29 weeks

A second quote on purchases under fifty pounds

not missed

The printed catalogue kept at the front desk

not missed

Re-sending the rota as a reminder

not missed

The colour-coded wall planner

not missed

A written agenda for every one-to-one

not missed

Laminating the safety notices each year

not missed

The standing item for any other business

not missed

Of the nine removals somebody argued about at the time, none later surfaced as a problem; of the seventeen nobody remarked on, four did. The quieter the removal, the longer the wait: median weeks to the event were argued 4.5, questioned 6.5 and unremarked 18. Nothing about a removal's loudness was recorded in order to predict anything. It was written down because the person keeping the list wrote down what happened in the room.

The twenty-four that came back, and how much of the old load came back with them

Reading supplier contracts before renewalReinstated in full after the second unread renewal

100%

Printed copies of the weekly rota

100%

The written handover at the end of a shift

100%

Tea and biscuits put out on Thursdays

100%

Checking the diary a day ahead

100%

Chasing unpaid invoices every week

100%

The quarterly reconciliation of the project ledger

40%

The standing slot for work with no owner

35%

The Monday planning hour

45%

A second reviewer on routine changes

60%

Visits to the two furthest sitesFour visits a year instead of monthly, and nobody has reported a difference

30%

Month-end figures circulated to everyone

40%

The meeting held before the meeting

50%

Two people on every delivery

70%

The daily stand-upTwice a week, standing, and timed

30%

The Friday clean-down of the workshop

60%

A named person on the phone until six

45%

Counting stock on the first of the month

40%

Shadowing new starters through their first weekA named person to ask, instead of a week of sitting alongside

50%

Logging why a job was turned down

55%

Keeping the stock list on paper as well

25%

A written note after every phone order

40%

The spare key log

20%

Keeping the induction folder up to date

30%

Same 6Reduced 12Substitute 6

Twenty-four removals came back in some form, at a median of 47.5 per cent of what the same thing cost before. Six of them came back whole; the other eighteen came back smaller or came back as something else. The median here is the number that cuts against this site's own title: what came back came back at under half its old weight, so the reduction is larger than fourteen out of thirty-eight makes it sound.

The part of the argument nobody runs

Almost every published account of a four-day week reports the same two things: output held, and people were happier. The accounts disagree about almost nothing. That unanimity is the first thing worth being suspicious of, and the suspicion is not that anybody is lying.

A shorter week is not a change to how hard people work. It is a subtraction. Four days contain fewer hours than five, and the hours that leave take work with them. Something has to stop. Every successful transition is therefore a list of things that stopped, and every argument about whether it worked is an argument about that list — except that the list is almost never written down, and when it is, it is almost never looked at again.

This site is built on one that was. One organisation of about ninety people moved to four days over eleven weeks. As the transition ran, somebody wrote down each thing that stopped and the week it stopped: thirty-eight entries. Then — and this is the unusual part — the list was kept, and for the next seventy-eight weeks each entry was marked up with what had become of it.

Four things can happen to a removal

Nobody asks for it back. Fourteen of the thirty-eight. Nobody requested it, nobody reinstated it, nothing went wrong that anybody traced to its absence. This is the strongest evidence a shorter week has, and it is more than a third of the list. A substantial proportion of what an organisation does is done because it was being done.

It creeps back. Eleven. Nobody decided anything. The thing reappeared, usually in a slightly different form, at a median of seven weeks. Nobody noticed it returning, because nothing announced it.

Somebody asks for it back. Eight, at a median of three weeks. These are the easy ones. A request is a signal, it arrives fast, and it can be argued with.

Its absence shows up as a problem. Five, at a median of thirty-one weeks, and the slowest at sixty-four.

The four outcomes are not four degrees of the same thing. The first three are all forms of information arriving. The fourth is information failing to arrive until the cost has already been paid.

The finding

Each entry on the list also records how much noise the removal made at the time it happened: whether somebody argued against it, asked about it without objecting, or said nothing at all.

Of the nine removals somebody argued about, none later surfaced as a problem. Of the seventeen nobody remarked on, four did.

Put plainly: the things that turned out to matter were, at the time, the things nobody thought were worth discussing.

This is not a paradox and it is not a coincidence. A contested removal gets watched. Somebody objected, which means somebody has a stake in its absence being noticed, and when it starts to hurt they are the first to say so and they are believed, because they said it would. An unremarked removal has no such person. It stops, nothing happens, and the fact that nothing happens is taken as evidence rather than as the absence of a reporter.

The lags say the same thing a second way, and they line up in order. Where a removal was argued about, the median wait before anything happened was four and a half weeks. Where it was questioned but not opposed, six and a half. Where nobody said anything at all, eighteen. The quieter the removal, the longer the organisation took to learn anything about it.

The corollary is uncomfortable for both sides of the argument. Advocates get told that the quiet transitions are the risky ones. Sceptics get told that the loud objections are reliably the wrong thing to worry about.

Why the lag is the whole problem

Consider what a lag of thirty-one weeks does to an evaluation.

A standard pilot runs six months. Counting from the day the transition started, twenty-six weeks is up before three of the five problems have arrived: on this record they surfaced in weeks thirty-four, fifty-three and seventy-three, long after such a pilot would have reported, the report been written and the policy made permanent.

What a six-month trial would have seen is this. Eight removals asked back, nine crept back, two problems, and nineteen entries on which nothing whatever had happened. Read at week twenty-six, nineteen quiet entries look like nineteen things the organisation did not need. Five of them were not.

This is why the published accounts agree. They are not wrong. They are measuring an interval shorter than the thing they are measuring. Any evaluation window shorter than the longest lag in the system returns a verdict that is correct about the window and silent about everything after it, and nothing in the result itself tells you which you are looking at.

What came back, and how much of it

Twenty-four of the thirty-eight came back in some form, and the obvious reading is that the real saving is fourteen out of thirty-eight. That reading is wrong, and the record says so.

Of the twenty-four, six came back as what they had been. Twelve came back smaller — fewer people, less often, shorter. Six came back as something else doing the same job. Against the load each had carried before, the median return was forty-seven and a half per cent.

So the list understates the reduction. Most of what came back came back at under half its old weight, and the half that did not return is a real and permanent saving. A site whose name is Nobody Missed It Yet is obliged to say that the number cutting against its own title is the honest one, and that is this number.

It also sharpens the asymmetry. What comes back comes back cheaper. What surfaces as a problem surfaces at full price, and late.

What this does not show

It does not show that four-day weeks work, and it does not show that they fail. It is one organisation, one transition, one list kept by one person, and the distribution of lags on another list would be different. The method travels; the numbers do not.

It does not show that long lags are peculiar to shorter weeks. Any removal anywhere has this property. A four-day week simply forces thirty-eight of them at once, inside eleven weeks, which is what makes the distribution visible.

It does not identify which removal is which in advance. That is the point. If it were possible to tell, from the way a removal looks on the day it happens, whether it will be missed in fourteen months, none of this would be difficult. The record here says the obvious signal — how much fuss it caused — points the wrong way.

And it does not say that late-surfacing removals should not be made. Four of the five that surfaced were, on the record, worth the trouble they caused. The argument is about the evaluation, not the removal.

What is worth doing

Three things, and none of them is an argument for or against a shorter week.

Write the list. Not the policy, not the business case: the removals, one line each, with the week. It costs an hour. Without it there is nothing to mark up later, and the question of what the shorter week actually did becomes a matter of recollection.

Mark the quiet ones. The entries nobody said anything about are the ones with no reporter. They are the ones to go and ask about, because nobody will tell you.

Fix the review window to the thing, not to the quarter. A six-month review of a change whose slowest consequence takes fourteen months is not a short review, it is a different review. If you cannot run a longer one, the honest report says what interval it covers.

The order of the parts

There are six, and they follow the list rather than an argument.

Start with what a shorter week takes out, which is the thirty-eight themselves and what sort of things they were. Then the lag: the gap between stopping something and learning anything about it. Then the quiet removals, where the finding sits. Then what returned, and at what weight. Then the other arrangements — compressed hours, a nine-day fortnight, staggered cover, annualised time — and the different set of removals each one forces. Last, how to take something out in a way that tells you early whether you were wrong.

Nothing on any of those pages comes from outside the list. Thirty-eight rows, one organisation, nobody identified anywhere, and that will not change.

01 / 06thirty-eight removals in eleven weeks

What a shorter week actually removes

Four days hold fewer hours than five, and the hours that go take work with them. The thirty-eight things that stopped here, and what sort of thing they were.

02 / 06median thirty-one weeks before a problem surfaced

When anyone noticed

The distance between taking something out and finding out whether it mattered. On this record it ran from one week to sixty-four, and the long end is where the trouble is.

03 / 06none of nine argued, four of seventeen unremarked

The quiet ones

Of the nine removals somebody argued about, none later surfaced as a problem. Of the seventeen nobody remarked on, four did. This is the finding, and it is not a coincidence.

04 / 06median just under half the old load

What came back, and how much of it

Twenty-four returned in some form, at a median of just under half the load they carried before. The number that cuts against this site's own title.

05 / 06four shapes, four different lists

Other shapes of week

Compressed hours, a nine-day fortnight, staggered cover and annualised time each force a different set of removals. What each one takes out, and where its own lag sits.

06 / 06three habits and an hour

How to take something out

Write the list, mark the quiet ones, and set the review window to the thing rather than to the quarter. Three habits, none of which is an argument for a shorter week.

The short version

The quiet removals are the dangerous ones

Thirty-eight things stopped. Fourteen have not been asked for in seventy-eight weeks. Of the nine that somebody argued about at the time, none later surfaced as a problem; of the seventeen nobody remarked on, four did. The median lag before a problem surfaced was thirty-one weeks, which is longer than the pilot that would have reported on it.

Practical workplace guides

Communication, workflow, and content tools

Three differently structured guides for internal communication, shorter-week experiments, and executive content production.