Six-week cycles are not sprints, and the difference is not semantic. A sprint is two weeks of continuous full-speed delivery for a software team. Shape Up is six weeks of product work for a product team. Quarterly OKRs are thirteen weeks of goals for a leadership team. Six-week cycles are six weeks of planned work plus two weeks off, for an entire business, run at a deliberately controlled pace.
They get confused constantly, mostly because Shape Up and six-week cycles share a length and a source. Here is what each one is actually for.
The comparison, in one table
| Six-week cycles | Shape Up | Two-week sprints | Quarterly OKRs | |
|---|---|---|---|---|
| Built for | A whole business and a whole life | A product team | A software team | A leadership team |
| Length | 6 weeks on, 2 weeks off | 6 weeks plus a 2 week cooldown | 2 weeks, continuous | 13 weeks |
| The break is | The point | For bugs and planning | Not built in | Not built in |
| Target pace | About 70 percent | Full but bounded | Full | Unspecified |
| Unit of work | The task, in hours, on a sheet | The pitch | The story point | The key result |
| Who plans it | Everyone plans their own days | Leadership shapes and bets | The team, each sprint | Executives, each quarter |
| Covers non-product work | Yes, that is the point | No | No | Partly |
| Who it fits | Founders, agency and studio owners, solo operators | Product organizations | Engineering organizations | Executives |
Cycles are not sprints, and the word matters
From the outside, this methodology looks like Agile. Jason Fried was specific about the distinction: cycles are not a sprint, so do not call them sprints.
It is not about everybody going 110 percent for six weeks. It is a controlled pace.
The word does real work here. If you tell a team you are running sprints, they brace. They have been through sprints. Sprints are where the estimate gets committed to publicly and then everyone works late to hit it. Tell them you are running a cycle and the promise inverts: a known quantity of work, at a pace that leaves room, with a real break at the end.
Chicago has two train systems and they explain this better than I can. The el picks people up every five to fifteen minutes. The Metra runs out to the suburbs on a consistent published schedule, and it holds that schedule precisely because it does not run at full speed. It runs at 60 or 70 percent, so it can go to 80 when something slips and 100 when it is desperate. A train at full speed all the time cannot recover from anything.
Sprints run the train at 100 percent and then act surprised when the schedule slips.
Shape Up is the closest relative, and still a different animal
I owe the six-and-two rhythm entirely to Basecamp. I heard it from Jason Fried at a presentation in their Chicago office and took it home to my agency the same week. Shape Up, written later by Ryan Singer, is the formal version of how Basecamp does it.
So the shapes match. The scope does not.
Shape Up organizes a product team. Work arrives as pitches, leadership bets on which pitches get a cycle, and teams are given room to figure out the how. It is excellent, and if you run a software product with designers and engineers, read it before you read me.
Six-week cycles organize a business. That includes the client work, the sales calls, the hiring, the bookkeeping, and the fact that your developer's daughter has a doctor's appointment on Thursday. There is no pitch process because most of the work in a small company is not shaped like a feature.
The other difference is what the two weeks are for. In Shape Up the cooldown is for bugs, cleanup, and figuring out the next bet. In my version the two weeks are the reason the whole thing exists. It is the part where people get their lives back, and if you fill it with cleanup work you have quietly deleted the benefit.
Two-week sprints are too short for anything but increments
Two weeks is enough time to move something forward and not enough time to finish anything that matters. Which is fine, if you are shipping software continuously and the increment is the point.
For a business, it produces a specific failure: you never get cognitive closure. Anyone who has run a company knows the feeling of never being done. Work is rarely over at the end of a day, a week, a quarter, or a fiscal year. Finish one thing and there are a thousand behind it. A two-week rhythm gives you twenty-six opportunities a year to notice you are not done, and no natural moment where the work has actually ended.
Six weeks is long enough to complete something real, and short enough that you can still picture the finish line from day one. That combination is what makes the plan feel worth making.
Quarterly OKRs answer a different question entirely
OKRs are not competing with cycles. They are one layer up.
An OKR says what matters this quarter. A cycle says what gets done in the next six weeks, by whom, on which day, in how many hours. One is direction and the other is execution, and plenty of companies run both without conflict.
Where quarters fall down on their own is duration. Thirteen weeks is long enough that by week five the plan has stopped feeling real, and long enough that nobody is tracking whether the daily work still points at the objective. The plan becomes a document you revisit at the end rather than something you run your week from.
Which one you should use
- You run a software product with a real product team. Shape Up. It was written for exactly you.
- You run an engineering org shipping continuously. Sprints are fine. Add a real cooldown, because they do not include one.
- You are an executive setting direction across departments. OKRs, plus something underneath them that decides what happens on Tuesday.
- You are a founder, agency owner, studio owner, or solo operator whose work does not fit in a backlog and whose calendar is also your life. Cycles.
The honest version: none of these are magic, and I do not think six-week cycles are the answer for every organization. They are a starting point, and a way to open a conversation about whether the people at your company are happy, and whether you are.
If that sounds like the conversation you want to have, the whole method is written down.