How to Run Your Work in Six-Week Cycles

A six-week cycle is six weeks of planned work followed by two weeks of lighter work reserved for planning the next six. You name the cycle, plan all six weeks before day one, and protect the two weeks at the end so the next plan actually gets made. I have run my companies this way since April 2016, six cycles a year, each one named after a city. It started with seven people at a creative agency and it survived scaling to a twenty person team across four countries.

Most of what has been written about six-week cycles is about shipping software. This is not that. This is how you run a business, and a life, on a rhythm that has a beginning and an end.

A cycle is eight weeks, and only six of them are for building

The full shape is six weeks on and two weeks off, repeated six times a year, one cycle per two-month block. The six weeks are scoped and planned in advance. The two weeks are for planning the next cycle, answering everything that piled up, and recovering.

People hear "two weeks off" and assume the six weeks are brutal to compensate. They are not. We work five days a week like everybody else. The two weeks get paid for by planning properly, not by working harder.

What you get in exchange is cognitive closure. Anyone who has run a business knows the feeling of never being done. You finish one thing and there are a thousand more behind it. A cycle has an end date, which means the work has an end date, which means for the first time there is a version of "finished."

Cycles are not sprints, and it matters what you call them

From the outside this looks like Agile. Jason Fried was specific about this: cycles are not sprints, so do not call them sprints. A sprint implies everyone at 110 percent until the deadline. A cycle is a controlled pace, deliberately set below capacity so the team can absorb the things that always come up.

Here is how it lines up against the frameworks it gets confused with.

The distinction is not pedantic. If you tell a team you are running sprints, they brace for six weeks of pressure. If you tell them you are running a cycle, the promise is the opposite: a known amount of work, at a sustainable pace, with a real break at the end.

The idea came from Basecamp, and I did not invent it

I was one of twenty people at a presentation at Basecamp's Chicago offices, on how Basecamp uses Basecamp to build Basecamp. Jason Fried talked about breathing room in a working environment, and how his team had landed on taking two weeks to plan the next six weeks of work.

My reaction, roughly: you can do that?

I took it home, started running it with my seven-person agency in April 2016, and have been refining it ever since. What is mine is a decade of running it, failing at it, and adapting it for a business that is not a software company. The core idea is Jason's, and he deserves the credit for it.

The method, in ten steps

If you want the entire framework without the reasoning, it is this.

1. Name the cycle.
2. List every task you can think of, out of your head and onto a wall.
3. Set up each week across the top of an overview sheet.
4. Set up each day on its own weekly sheet.
5. Grey out any day someone is off or working half.
6. Give every remaining day one focus, the single thing that has to get done.
7. Write the tasks required for each day underneath that focus.
8. Rearrange by priority until no day holds more than six hours.
9. Plan a celebration for the last day of the cycle.
10. Run it, and write down everything that broke.

Everything below is why each of those steps is there.

Naming the cycle gives it edges

A cycle with a name has a beginning and an end that people can talk about. "Before Medellín" and "next cycle" become real units of time in a way that "Q3" never quite does.

Basecamp named theirs after wars. I was deep on Hamilton at the time, so 2017 ran on US presidents: Washington, Hamilton, Adams, Hancock. When my team moved into travel and tourism we switched to cities, and I have never gone back. 2026 is Tallinn, Buenos Aires, Nice, Medellín, Kuala Lumpur, and Berlin.

Pick names that mean something to you and your organization. The point is not the theme. The point is that a named block of time is something you can plan toward, and something you can finish.

Get everything out of your head first

Before any of it goes on a sheet, it comes out of your head. Whiteboards, big pads of paper, or a to-do app if you must, though I lose all sense of scale when I only look at things on a screen. I lock myself in a whiteboard room for about four hours with a playlist and some dry erase markers.

The sequence I use:

1. Read all the instructions before you start.
2. List the major categories of every active project. Anywhere from two to twenty.
3. List every task under each category.
4. Decide what only you can do. Anything someone else can do moves to a separate list, assigned to them.
5. Write down how long each task will take.
6. Break anything longer than 90 minutes into smaller tasks.
7. Reward yourself, because that was genuinely a lot of work.

It will feel overwhelming and the order does not matter. Plan a full day for it, and expect to keep adding for a few days afterward as stray tasks surface.

The 90 minute rule is the one that does the most work. If a task cannot be described in under 90 minutes, you have not defined it yet, you have only named it.

Ask "and then?" until the task is real

Humans are terrible at estimating time, mostly because we skip the small steps hiding inside the big ones.

There is a scene in Dude, Where's My Car? where Ashton Kutcher's character orders fast food and the attendant keeps asking "and then?" after every item, until he loses it. That is the exercise.

Say I put "blog article, 1.5 hours" on my sheet. I am a decent writer. Ninety minutes, easy. Then I play the game:

I need to write an article.
And then? I need to find images for it.
And then? I should ask someone to proofread it.
And then? I need to get it ready to post online.
And then? I want it out on social and in the newsletter.

Now I have five tasks instead of one, and a realistic number of hours instead of a hopeful one.

There is a quieter benefit in there too. When I wrote down "ask someone to proofread it," I was planning someone else's time as well as my own. Planning your time in advance pulls the people around you into doing the same thing.

Plan six hours in an eight hour day

This is the number people argue with and then quietly adopt. A planned eight hour day looks like this:

Six planned hours leaves two hours of slack for the things you cannot predict, which is the entire reason "too much stuff comes up, we cannot plan ahead" stops being a valid excuse. You are not failing to plan for the unknown. You are planning for it explicitly.

Every task falls into one of three buckets: planning, communicating, or doing. Communicating is the one everybody underestimates. It is every meeting, every email, every reply in Basecamp or Slack, every client request. When we brought cycles into the Canadian company that acquired my team, we looked at an engineer's schedule. Forty hours on paper. Fifteen actually available for hands-on work once communication was counted honestly.

That gap is not a personal failing. It is what an unplanned week looks like when you finally measure it.

Plan in a spreadsheet, not on your calendar

We tried calendars first. A calendar forces you to commit a task to a specific hour weeks in advance, and then life moves one thing and the whole structure collapses like a waterfall.

A spreadsheet lets you move a task between days without wrecking anyone's schedule. It tallies hours per project in a column. It lets a manager look at someone's week and propose a meeting on a day that actually has room. And crucially it plans hours before they are spent, where most time tracking software records them after they are gone.

This is also why I do not hand planning to an AI. The value is not the plan. The value is what happens in your head while you make it, running the days forward and noticing the roadblocks before you hit them. Outsource that and you keep the document and lose the entire mechanism.

Parkinson's Law is the operating principle underneath all of it. Work expands to fill the time you allow. So allow less.

Two meetings hold the week together

Only two, and only during the six on-cycle weeks.

Monday check-in. Each person shares their week. You schedule any reviews, ask what could go wrong, ask what management should be focused on, and review last week's improvements.

Friday check-out. Two minutes of silence writing down what went well, then everyone shares. Two minutes on what did not, then everyone shares. Then the group talks about what to change.

The check-out became my team's favorite meeting. A teammate in South Africa, who I had never met in person, said "I look forward to meetings, which isn't something people normally say."

If you take one thing off this page and ignore the rest, take this one. I have written up exactly how to run a check-out meeting separately, and if your calendar is too crowded to fit them, start by deleting the meetings that should have been emails.

Run the team at seventy percent

Chicago has two train systems. The el picks people up every five to fifteen minutes around the city. The Metra runs out to the suburbs on a methodical, consistent schedule.

Metra holds that schedule by not running at full speed. They run at 60 or 70 percent, which leaves them room to push to 80 when something slips, and 100 when they are desperate. A train at full speed all the time cannot recover from the smallest problem.

Teams work the same way. Do not build a cycle that needs everyone at 100 percent every day. Build one that produces consistent results, and keep the headroom.

Then end the cycle with a celebration. Charles Duhigg's habit loop is trigger, action, reward, and the reward is the part most companies skip entirely. During planning, put one person in charge of the end-of-cycle celebration and give them a budget and time to plan it. We have done Blackhawks games, escape rooms, and comedy shows. Rotating who plans it keeps it from going stale.

It will not work the first time

I want to be straight about this, because pretending otherwise is how people quit in month two.

Our first cycle did not go according to plan. Neither did the second. The third was the most comically bad of all, made worse by me cheerleading "third time's a charm" going into it. On day two a project landed and wiped out the entire plan.

That happens. Projects land. Get over it.

The whole time we were failing we were also learning, noting what upset us and fixing that one thing next cycle. It was like patching a leaky boat. Every time we sealed one hole another opened. That is not the method breaking. That is what moving an organization from reactive to proactive actually feels like.

Like meditation, this can be practiced and never perfected. Be patient, and be persistent.

Who this is for, and who it is not

Six-week cycles are not the answer for every organization. They are a way to start a conversation about whether the people in your company are happy, and whether you are.

It works best if you are a founder, agency owner, studio owner, small business owner, solo consultant, or operations lead. Anyone who can actually change the rhythm rather than just survive it. It needs work that can be scoped in advance and a team small enough to be nimble, and I got lucky on both counts.

If your company does not run this way, you can still run it yourself. Draw up your own next six weeks and bring it to your boss for approval. You are entitled to know what work is ahead of you. Do the work for them, because in sales the whole game is making it as easy as possible to say yes. And if asking to plan gets you reprimanded, that tells you something worth knowing about where you work.

Common questions