The two weeks between cycles are two weeks of lighter work, not two weeks of no work. Most of the time goes to planning the next six weeks properly. The rest goes to clearing what piled up during the last six, and to letting people deal with the life admin that a full working cycle leaves no room for. It is the part that pays for everything else, and it is the first thing people delete when a cycle goes badly.
Jason Fried's version at Basecamp was two weeks to plan the next six weeks of work. When I first heard that my reaction was roughly: you can do that? Then I took it home and found out what actually happens in those fourteen days.
Half of it is planning, and that half is not optional
This is the bulk of it, and it is real work.
Everything gets emptied out of your head onto a wall. Tasks get estimated honestly. The cycle sheet gets built, days get a single focus each, and everything gets rearranged until no day holds more than six hours. Then the whole plan gets walked past the people who have to execute it, because they will immediately find the dependency you missed.
None of that fits into the six working weeks. That is the entire point of having the two.
The sequence is the brain dump, then the "and then?" game on every item, then the cycle sheet. Plan a full day for the dump alone, and expect stray tasks to keep surfacing for several days after.
Clear what the last six weeks buried
Every cycle produces a pile. Emails that got a holding reply. The invoice you kept meaning to chase. The thing a client mentioned in passing that turned out to matter.
Give it a defined slot rather than letting it leak. This is also when the cycle sheet's items to discuss and quotes columns earn their keep, because going back through them at the end of a cycle is usually what explains why a particular week went sideways.
The removed-task notes get read here too. Anything that came out of the cycle should have a reason written next to it, and the pattern across those reasons is the most useful planning input you will get. Sometimes you plan for the wrong things and do not realize it until it is too late.
Actually rest, and mean it
Here is where I have to be honest about my own version of this.
The break is not a vacation you feel guilty about. It is a built-in cool-down. And the reason it exists is not productivity, it is that people have lives that a rigid schedule pretends do not exist.
One cycle my product manager needed his gallbladder out, and then his step-father passed away. My developer needed his wisdom teeth removed, had to get his car in, had to take his six-month-old daughter back to the doctor, and then a pipe burst in his house during a Chicago cold snap.
That is not an unusual run of luck. That is life. Work needs to move with it rather than stand in front of it like a wall, and the two weeks are where that movement is allowed to happen without anyone having to ask permission.
We also let people work from home during the break, which the standard five-day-a-week model simply does not give room for.
Celebrate the one that just ended
Charles Duhigg's habit loop is trigger, action, reward. The reward is the part almost every company skips.
During cycle planning, put one person in charge of the end-of-cycle celebration, give them a budget and time inside the cycle to organize it. We generally ran ours on the last Friday of week six. Blackhawks games, escape rooms, comedy shows. Rotating who plans it keeps it from going stale and gives everyone a turn at picking something they actually like.
Give recognition too, at the end of each week and each cycle. People like being celebrated. If you do not have superiors of your own, find a peer group or a mastermind who will celebrate your wins with you, because nobody is going to volunteer to do it.
Set up the next sheet before you need it
By the end of the break, the next cycle's sheet should exist with its overview and weekly tabs ready, and the cycle after that should at least have a name.
That way, when something surfaces mid-cycle that clearly is not happening now, it has somewhere to go immediately. A big part of organization is just having a place to put things, and a named cycle is a place.
What not to do with it
- Do not fill it with recurring meetings. The check-in and check-out run during the six on-cycle weeks only. Load the break with standing meetings and you have deleted the break.
- Do not use it as your only holiday. Real time off is separate. Treating the break as your vacation allowance is how people come to resent it.
- Do not cancel it because the cycle went badly. This is the one that kills the whole system. A team that watches the break get cancelled the first time work slips learns that it was always conditional, which means it was never real.
- Do not let clients fill it. Publish the dates and define the emergency before one happens.
If a cycle overran and something has to give, protect the planning half and let the recovery half absorb it. Skipping the planning guarantees the next cycle also overruns, and then you have lost two breaks instead of one.
The whole method is in the guide to running your work in six-week cycles.