The twelve-week trap

Most studio engagements are sold as twelve-week projects because that is the length the industry has converged on. It is long enough to feel substantive. It is short enough that the client does not have to commit to a year. It is also the wrong length for almost every engagement we have seen run that way.

The problem with twelve weeks is not that it is too short. It is that nothing about the work itself is twelve weeks. The discovery phase is two weeks. The design phase is three to four weeks. The build phase is four to six weeks. The launch phase is one to two weeks. None of these add up to twelve unless they are all going at full intensity at the same time, which they almost never are.

The twelve-week project is therefore mostly a project management container. It has a kickoff, a midpoint review, a week of frantic effort before launch, and three to five weeks of slack distributed unevenly through the middle. The client pays for the slack, the studio absorbs the frantic week, and both sides finish slightly resentful.

We split that container into pieces. Each piece is the natural length of the work it contains. Discovery is two weeks because two weeks of stakeholder conversations and audit work yields a brief. Design is two weeks because two weeks of focused art direction yields a defensible visual language. Build sprints are two weeks because two weeks is the longest a piece of front-end work should go without a working build to test against.

The consequence is that twelve weeks of effort becomes six discrete sprints, each with its own brief, its own deliverable, and its own end. The work breathes. People notice when something is going wrong, because the next sprint cannot start until the current one is signed off. And nobody has to pretend that twelve weeks of effort is an unbroken arc.