In the February issue of Vanity Fair, Peter Biskind examines the ill-fated production of the mid-80′s comedy/model-of-epic-failure Ishtar. In it, the stars and the crew recount watching the film come undone even as they continued to push forward on it.
For many, Ishtar – like Battlefield Earth or The Postman – has come to define the concept of high-budget flop. Like nearly any great failure, hindsight clearly spells out why the film failed: Inexperienced director, bad cast chemistry, vague project goals, and enough time and money to do real damage.
At the same time though, it’s easy to see why the movie got made in the first place: Proven stars, talented writing, expert crew, and enough time and money to do something really great – more than most movies ever get.
Creating marketing programs can look a lot like making a movie and the Ishtar story isn’t unlike a lot of projects I’ve seen over the years. Call it the “Big Idea” process. You get great people together, you come up with the best idea you can using the budget you have, and hope it all works out. Sometimes it does, sometimes it doesn’t. The problem is, like Ishtar, when you’re in the middle of things, good projects can look an awful lot like bad ones. It’s not until the very end, when you’ve run out of time and money, that you have any indication which one you have on your hands.
What would be great is a way to test out ideas, identify the truly great ones early, and put your time, effort and money behind those, while side-stepping the Ishtars. With film that could difficult, but with digital marketing, it’s surprisingly straightforward.
If you’ve spent time either working in, or with, advertising agencies you’re familiar with the concept of the campaign. This is the core product of an agency and it defines the way that ideas are generated, how they are executed, and ultimately what constitutes success and failure. While each agency has their own take on the campaign, for the most part, they look something like this:
In the “Brief” phase, the agency gets some sort of assignment from their client outlining the needs or goals of the project. The agency then goes into some sort of “Ideation” phase, which includes the brainstorming sessions, the identification of the key idea for the project, and the proposal back to the client. With client approval, the project moves into the “Execution” phase. This where the bulk of the time, effort and money in a project gets consumed. The Execution phase includes all of the design rounds, all of the development, all of the QA; everything that goes into making a project launch. At the end of the project, when all the time and budget is gone, the project is evaluated. It’s this evaluation phase that presents the first problem with this campaign approach.
Because agencies wait until the “end” of a project to evaluate it, when the project is launched to the public and pretty much complete, it’s only real role is to ask “did this project work?” Analysts then descend on the site to see how people are using it, maybe look at conversion funnel metrics, and then make some recommendations about how to tweak things to get better performance. That’s good, but by the time it happens, the major effort is over. The information gathered can’t be used to make actual improvements to the project because the project is over.
If there was a real chance to make a deep impact on the project, it would be earlier.
Compounding this issue is the nature of the campaign culture itself which views each stage of the project, and each project itself, as an isolated event, unaware of the projects that have come before it, not meant to influence what comes next. Once execution has begun, there is no chance to revisit the merits of the original concept, and the launch of a project is considered the end, not the beginning. Working this way, any learnings from one project are unlikely to help improve the next, and there is no opportunity to adjust a project based on its success or changes in the technical or competitive landscape.
When these types of projects succeed, they succeed big (in part because if it’s not big, it’s not counted as a success). But when they fail, they fail equally big, and they fail much more than they succeed. Moreover, their failure was just that: a failure, because it came at the end of the project, when there was nothing to do but move on.
What if, rather than waiting until the end of the project to gather and analyze data, we focused on the middle of the project? What if the launch of a project was just the first step?
At Fight, we’re big fans of big ideas. We believe that great marketing can be transformative, both culturally, and for our clients’ bottom line. So, when we went about creating our company we put a lot of thought into how we could use the kinds of thinking that emerged from the digital space to help make sure that a big idea becomes a bona fide success. Key to this is the concept of iteration.
If you’ve been reading the Webtrends blog for a while, you’ve no doubt seen many references to “Iterative Marketing“. Taking it’s philosophical cues from agile development methodology, iterative marketing seeks to break down a larger strategy into smaller, but conceptually complete elements. By releasing these smaller elements to your audience, you can take advantage of analysis of real-world data early in a project’s lifecycle when the information can still inform project direction. This notion of optimizing the middle of a project, rather than the end, is key to iterative marketing. Building projects this way, not only do you preserve the fundamental drive towards big thinking, it actually enables you to achieve far bigger ideas than traditionally possible.
But more than just increased efficiency, iteration allows you to approach projects in a more web native way. By re-contextualizing your time frame from single, all-or-nothing campaigns to a more long-term, continuously improving approach to developing projects, you’ll be in a position to develop the kinds of projects that can more effectively deliver actual value to your audience and compete more effectively with digital native projects.
While working in an iterative way represents clear advantages in the digital space, it also presents a fundamentally different way of looking at projects organizationally. In the next installments, I’ll look at what the organization impact is of working in an iterative way and how to actually implement this within your organization.
Update: Part 2: A Culture for Change