Somewhere around 2015, the software development methodology known as Agile escaped from its natural habitat — engineering teams building digital products — and began colonizing the rest of the corporate world. Marketing adopted it. Creative agencies adopted it. Advertising departments adopted it. And with it came the vocabulary: sprints, standups, backlogs, velocity, retrospectives, story points. All applied to the production of campaigns, designs, and concepts that have approximately nothing in common with the iterative software development contexts for which these tools were designed.
The results have been, to put it diplomatically, mixed. For some teams in some contexts, the discipline of time-boxed work and regular review cycles has genuinely improved how creative work gets done. For many others, Agile in creative contexts has produced a new and particularly sophisticated form of organizational dysfunction: all the meetings and rituals of a structured methodology, none of the speed or clarity it was supposed to deliver.
What Agile Was Actually Designed to Solve
Agile was designed for a specific problem: software that needed to be built in conditions of genuine uncertainty, where requirements couldn’t be fully defined upfront because the technology was evolving, user needs were unclear, and the right solution could only be discovered through iterative testing with real users. In that context, the Agile principles — working software over comprehensive documentation, responding to change over following a plan — make a great deal of sense.
Creative work does involve uncertainty. But it involves a different kind of uncertainty than software development. A campaign’s requirements can and should be defined relatively clearly before production begins. The creative question — how to execute against those requirements in a way that actually works — is not best answered by two-week sprints and story points. It’s answered by thinking, by craft, by the kind of concentrated, non-interruptible creative work that standup meetings and sprint planning sessions actively disrupt.
The Standup That Kills Momentum
The daily standup — fifteen minutes, every morning, to answer three questions: what did you do yesterday, what will you do today, what’s blocking you — is one of Agile’s most exported rituals. In engineering teams, it serves a real coordination function. In creative teams, it often interrupts the most productive working hours of the day to have a conversation that could have been an email.
Creative work requires cognitive immersion. The state in which genuinely original thinking becomes possible is built over time, disrupted easily, and not recovered quickly. The fifteen-minute standup at 9:30 a.m. doesn’t cost fifteen minutes — it costs whatever creative momentum would have been built in the hour before it and the half-hour it takes to return to depth afterward. Multiply by five days a week, and the standup isn’t a coordination tool; it’s a productivity tax.
The Sprint That Contradicts Creative Time
The two-week sprint is Agile’s fundamental time unit. It makes sense for software: in two weeks, engineers can build a working feature, test it, get feedback, and iterate. In creative work, two weeks is often the time required to do the thinking that makes the actual making worthwhile. A campaign concept that’s been thought through for two weeks is likely to be better than one that’s been thought through for three days — but the sprint structure doesn’t distinguish between these; it just requires that something be delivered at the end of the two weeks.
The result is a bias toward ideas that can be executed quickly rather than ideas that can be executed brilliantly. Which is precisely the opposite of what most creative work actually needs. As we’ve argued in our breakdown of creativity by committee, process structures that prioritize speed and participation over depth and craft tend to produce work that’s fast and collaborative and forgettable.
What Actually Works: Borrowing Without Transplanting
The answer isn’t to reject all Agile thinking in creative contexts — some of it is genuinely useful. The answer is to borrow intelligently rather than transplant wholesale.
The Agile principle worth keeping: regular, structured reviews with real feedback loops. Not daily standups, but meaningful weekly checkpoints where actual progress is assessed against actual criteria. The principle of shipping something and learning from it rather than planning indefinitely has real value in creative contexts — especially in digital, where testing is possible and data is available.
The Agile practice worth abandoning: the sprint as a fixed time container regardless of the work. Creative briefs don’t all take the same amount of time. A brand identity takes longer than a social post. A campaign strategy takes longer than a banner adaptation. Forcing everything into the same two-week box produces consistent velocity and inconsistent quality — which is, for creative work, exactly the wrong trade-off.
And if your Agile implementation has produced endless retrospectives about the retrospectives, you may have arrived at the phenomenon we identified in design thinking as product: a process so elaborately designed that it has become the primary output of everyone’s time and energy.
Stuck in a sprint you’re not sure will ever end? Our shop is for people who want to move fast without breaking the things that matter. Including their sanity.
