A Manifesto for Agile Strategy: oxymoron or innovation?
“You can talk and think about stuff for ages and ages before doing something or other. Why not just do something straight away and learn from that?”
London was basking in unexpected sunshine and Tim Malbon (aka @malbonster) and I were wolfing down some fish and chips in Soho. His off-the-cuff comment stopped me cold – chip halfway to mouth – and in one way or another I have been thinking about it ever since (it was 6 months ago!).
‘Doing over planning‘ might be the simplest way to summarise the Agile philosophy that Made by Many so fervently pursues (a great non-tech articulation of the Agile approach to web apps is Getting Real by 37 Signals).
I was further prompted by Stuart’s excellent recent post exploring some of the differences between “Agile” the philosophy and “agile” the adjective, in which he concludes:
“Two of the most interesting questions for me is how is Agile going to scale beyond a team level? And how well can it be applied to processes outside software development? At Made by Many We have made a lot of ground in Agile interaction design but there is obviously much more to do and tools to create.”
So this is the question that has been haunting me: what role can or does strategy have in an Agile world? As Stuart alludes, we’ve been able to translate the Agile philosophy to things like interaction design (for example, see Isaac’s post ‘The future of wireframes‘), however strategy seems an altogether more challenging proposition.
By some definitions, strategy is pretty much only thinking and planning, so on face-value ‘Agile strategy’ seems like an incongruous pairing. However when you actually look through the four principles laid out in the Manifesto for Agile Software Development, the gaps immediately start to narrow:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
(The qualification to these guiding principles states; “That is, while there is value in the items on the right, we value the items on the left more.”)
The Agile software manifesto grew from discontent with heavyweight and unwieldy methodologies that had helped so many (perhaps most) software projects run way over time and over budget. So the real question to address (even before exploring whether Agile + Strategy can co-exist) is whether there is a need for an alternative, lighter-weight approach to digital strategy and planning.
My short answer to this, is most definitely.
Here are 4 quick observations from my own limited exposure to this industry to back this assertion up. Serendipitously, I’ve just finished the latest 37 Signals book Rework and it happens that there are some very apt quotes (included below) from the book that match my points:
1. Segregation
Although things are slowly changing, planners still occupy a hallowed and often completely separate part of the agency. They are the quintessential geniuses in the dark corner who are brought in for a specific and frequently one-off engagement. However this treats strategy as a singular event and not an ongoing process. This type of ‘baton hand-off’ process can create confusion and uncertainty amongst the team as the work gets further and further ‘away’ from the strategy. This can result in heavily compromised creative work, and while “flexing your intellectual muscles can be intoxicating” (Rework p.112), it’s surely time for planners to come down off those pedestals.
2. Insights as false idols
The obsession that so many planners have with identifying those 1-2″insights” is a constant source of bemusement. I don’t know where the practice of boiling down sacred diamonds (almost mystical in nature) stems from, but it seems ridiculous to me. I don’t know of any other business or industry that relies on such black magic. I know they’re supposed to be provocations but I think that insights often restrict creative thinking and more importantly are completely at the mercy of the planner’s whims (and style). What I think would be more helpful is a simpler (broader) statement of purpose that acts as a guiding philosophy to help the team develop and judge their thinking because “when you don’t know what you believe, everything becomes an argument” (p.44). This is more akin to the strategy I have seen work well in brands, tech companies and start-ups. Insights are often ‘hit and miss’, nebulous and even risky. As Dan Heath puts it in this excellent FastCompany article; “Simplicity [in strategy] allows people to act”.
3. Time & slow deduction
Deep research and immersion in complex problems is all good and well. However this approach is very much based on analytical thinking styles that tend to breed very deductive and often long-winded conclusions. Not only does this take a great deal of time, the rigidness and codification of the ‘ultimate solution’ presents an absolute with little room for argument. But too often this is simply an academic exercise in imagination, but perhaps 37 Signal’s advice to ”stop imagining what may work. Find out for real” (p.94) is a smarter alternative. More broadly, if you’re in the business of creative and innovative thinking, I think it’s time to move away from formulaic deductions and towards a more abductive, design thinking approach.
4. Change is the enemy
Given change is the only constant, the very concept of “planning” can get slippery. What often happens is that a great idea emerges (somehow) during the creative process that frequently bears little or no resemblance to the planning (or even the insights). But it is a good idea and the team is galvanised. So it’s left to the planner to backfill the strategy with retrospective justification. Don’t laugh, it’s a running joke in agency land that this is most of a planner’s job. It’s almost as redundant as an information architect changing their wireframes to match finished designs (ahem, this happens too). So let’s stop pretending that strategy is always the driver of good ideas. 37 Signals’ even more savage indictment is that ”planning is guessing”.
So, where does this leave everything? Well, assuming there’s the makings of a case for a new type of strategy, let’s see how we might adapt/mash/mix/invent a ‘Strategy’ version of the Agile Software Manifesto.
Manifesto for Agile Strategy Development
Collaboration & conversation over strategy decks & documentation
Don’t take a brief and disappear into planner world to create some 200-page deck grand reveal. Talk, discuss, argue and start shaping a shared understanding of what the real challenges are. And then stay with the process through to realisation.
Simplicity of purpose over ’sacred’ consumer insights
You want to make it easy for teams to make decisions and develop their thinking, not confuse or handicap them with insights that might – or might not – be right.
Testing hypotheses over long-winded research & deduction
Develop or invent hypotheses to test immediately. It’s about prototyping for opportunities, propositions and strategic themes rather than deep diving into deducing a singular ‘right’ direction over time.
Responding to change over following a plan
Strategy is a self-informing process so create a platform that accommodates and welcomes the inevitable changes in direction and thinking. Think iterations and renovations, not a fixed ‘build once’ structure.
(Eagle eyes will note the last tenet is unchanged from the Agile software methodology.)
Ultimately I think that ‘Agile strategy’ – or whatever you want to call it – needs to account for the fact that the strategic process is not only self-informing, but intimately integrated throughout the core of the project itself. So all the debate about ’strategy versus execution’ and ‘ideas versus implementation’ is missing the point. It’s all one thing. And in an Agile world, strategy needs to pull its socks up and get properly into the game.

+++
So whaddya think? Is there space for a new type of Agile Strategy? Does this go beyond what good/progressive planners are already doing? Where are the gaps? What’s missing? Jump into the debate in the comments or feel free to grab the graphic and talk in your own spaces. (I haven’t gone into specific examples of how we’re already using some of these principles in our own strategy work here at Made by Many, perhaps that’s another post). I welcome your comments, thoughts, suggestions and experiences. Thanks to Anel @thinkdsignchnge for the awesome illustration and MxMers Tim, Stuart & William for the various conversations that helped prompt this post.
See also:
- No similar posts
About the author
Justin is a digital thinker and strategist deeply suspicious of people who call themselves "digital strategists". Passionate about good coffee and discussing ideas, preferably together.
-
Comments (59)
-
Responses (9)
-
Manifesto for Agile Strategy Development « Soy un curioso
[...] Marzo 22, 2010 in Blogs, Estrategia, Innovación, ipublicidad Muy interesante reflexión en el blog de Made by Many: [...]
-
On Model-Driven Development and Agile Strategy - I Like Progress
[...] I haven’t been exposed to a corporate software engineering environment, but I know that this quote holds true for my own personal projects. I feel as though in this faster-than-ever changing world, MDD for consumer web services is old news. With the warmly accepted app store concept, an individual has an unprecedented medium to advertise and sell their application that could generate thousands in revenue per month. Smartphone app stores alone are expected to grow 70% each year for the next 3 years, surging to a $15.6 billion dollar market. If a company focusing on consumer facing applications does not already follow an agile strategy, they better be looking over their shoulders. A great quote from a great blog: “You can talk and think about stuff for ages and ages before doing something or other. Why not just do something straight away and learn from that?” (from Justin McMurray’s Made by Many post “A Manifesto for Agile Strategy: oxymoron or innovation?“) [...]
-
Planner Reads » Blog Archive » When I grow up I’d like to be more like a start-up
[...] ‘Agile versus Strategy‘ post has tapped an excellent [...]
-
Recommended Reading – 26th March 2010 « Curiously Persistent
[...] McMurray from Made By Many has laid out a manifesto for agile strategy. I particularly like the idea of simplicity of purpose over the reliance on a mystical [...]
-
Links. Good reads for Sunday Night. | davaidavai.com
[...] McMurray with his Manifesto for a new agile strategy. I don’t like the word Manifesto but the text is [...]
-
Strategy & Design » Manifest für agile Strategieentwicklung
[...] wenn man die Headline des Artikels “A Manifesto for Agile Strategy Development” zum ersten Mal liest, könnte man glatt meinen, dass es sich hier nur um eine [...]
-
The Web Is Social
[...] I’m into this….via Justin McMurry [...]
-
Re-imagining the agency proposition | eyecube
[...] of really well written pieces along these lines recently. Justin McMurray from Made by Many had a great piece that built upon that agencies “Agile” claims. The main thrust is a call to action that [...]
-
Random Reading – F#, Azure, PDC, MSBuild and More « Tales from a Trading Desk
[...] Manifesto for Agile Strategy: oxymoron or [...]
-
Actually I think it’s very much about two types of planners (or types of people); those who have to be right, and fight for their “true” strategy, and those who’ve done a good job arriving at some strategic thinking, cutting through and away stuff, and are alright with changing everything, a.k.a. getting off brief. If the arguments are good. If the latter happens not too far into a process, you’re on your way to a agile-ish way of working (and perhaps a manifesto is redundant).
Only a planner/strategist who take more pride in sparking ideas and conversations rather than fighting for “his/her” strategy, and regarding that as his/her product, is inline with this thinking.
Unfortunately that’s very much about personality type.
Olle
March 22, 2010
at 9:31 am
Yeah, good point Olle. I’ve certainly seen both types. That is the thing with planners; they’re such a disparate and varied lot that personal style can have a huge bearing on the output of the project. As for sparking things; I know of an extraordinarily successful businessman in Australia who, when asked to attribute his success, said that people around him had lots of good ideas.
Justin McMurray
March 22, 2010
at 10:09 am
yea it’s like deer hunting, innit?
marcus
March 22, 2010
at 9:39 am
Er, it could well be. I’d love to know how or why!
Justin McMurray
March 22, 2010
at 10:40 am
Great post. What’s missing is that strategists provide leadership. That all-important simplicity you mentioned is designed to guide, indeed, direct the creative process. Every creative ship needs a captain to find land. The talent of strategists lies in their ability to clearly see the path, regardless of the size of the waves. Maybe that’s an extended point of “simplicity of purpose,” a leader will collect and drive the thinking.
The point about conversation is so needed. As a so-called strategist myself, I find my thinking is shaped best through evolving conversations about the brand. The challenge at most agencies is to not sit alone in an ivory tower, but to immerse into the client issues and opportunities throughout the life of the brand. And I love the idea of testing hypotheses. I’ve never seen it as a distinct piece of the strategic program, because it happens so quietly, but it is one of the most important pieces of the process.
Gretchen Ramsey
March 22, 2010
at 9:42 am
Thanks for taking the time to comment Gretchen. Think you’re right that there is something slightly missing re strategy + leadership, although I must admit to mixed feelings about planners being *the* leaders and “directing” the creative team (it adds to the ‘us & them’ attitude). I believe that when the entire team/context/atmosphere/environment is instilled with strategic thinking, you get the best results. And to do that, yes absolutely, you need a special type of leadership to which I think you’re alluding.
Justin McMurray
March 22, 2010
at 10:21 am
great post. here are a few unrelated thoughts:
- it took advertising a long time (and Stanley Pollitt / Steven King) to figure out what account planning was and how it could make advertising more effective. Since then, planning / strategy has been codified into a discipline that helps brands create differentiation amongst lots of competition with a limited set of communications tools. Instead of the dancing on the head of a pin that this limited toolset resulted in however, strategists can now expand their horizons much further – which calls for a different sort of strategy. (and incidentally is exactly why I got into digital strategy – the wide open prairies were quite enticing).
- the single insight, the pre-testing, the quarterly tracking – all grew up in response to the exigencies of the media we were communicating in. ’strategy’ in the new world operates under completely different constraints, and so requires a different set of tools.
- content (and planning?) in any new medium adopts the conventions of what has gone before until we figure out what we ought to be doing. It’s taken us a while as marketing services is pretty conservative by and large, but your excellent post points us towards what the conventions for new planning / strategy might be.
‘Just do stuff’ sounds a pretty good start point to me.
nick stewart
March 22, 2010
at 9:47 am
Awesome reflections here thanks Nick. Love those “wide open prairies”! Very interesting remark about adopting past conventions until we figure new stuff out. I’m a relative newcomer to agency world and my perspective is more aligned to a start-up philosophy (who are the real pioneers/trailblazers in ‘digital’). Which partly explains my surprise at finding out there even was a planning discipline (!). So why don’t we take a leaf out of their books?
Justin McMurray
March 22, 2010
at 10:27 am
Justin – you’re right. the trailblazers in ‘digital’ aren’t the agencies, they’re the start-ups disrupting the old order of things. (The agencies are rarely the trailblazers in any circumstances but that’s another story). However, the people with the money – the clients – have a certain set of expectations about what their strategy should look like developed over years of working with old world agency planners. On top of this planning ‘comfort zone’, there’s also the increasing pressure for clients of all stripes to minimise risk, which is why we often find ourselves in a Catch-22 with innovation in creative work – doing new stuff is a good way to differentiate, but without the business case to back it up clients increasingly wary of signing up. I would anticipate a similar reaction to a new way of doing strategy.
So a new, innovative kind of strategy is going to come about only with certain types of client – perhaps those who share the start-up mentality with regard to innovation and risk.
btw, your comments platform doesn’t let me respond to your comment directly. which is why I had to do it this way…
nick stewart
March 22, 2010
at 12:40 pm
I think you’ve nailed a massive challenge there Nick. I guess we’re lucky at MxM because the way we’re setup and the work we do does attract the client already willing to take risks. (We actually have a slide in our creds deck featuring Godzilla with the words “We disrupt things and smash them up”. We like to note the client’s reactions to this; it’s our client selection litmus test!).
As for innovation, as design thinking author Roger Martin says, the two words that kill innovation are “prove it” (check out the video here: http://bit.ly/cbElwy).
We’re developing a range of strategic tools here at MxM that seek to bridge the requirement for strategic ‘output’ and client confidence, while still embracing the fuzzier notions of Agile-esque Strategy. It ain’t easy, but it’s quite fun.
Justin McMurray
March 22, 2010
at 12:58 pm
Justin, can the planners keep their cardigans?
Nice point Olle, totally agree. Personally I think that everything Justin’s said is really just about good strategy, not sure if it needs to be Agile as such. Good strategy should be agnostic of process.
mike
March 22, 2010
at 10:13 am
Yes Mike, planners can keep their cardies! I don’t disagree that this is (hopefully) a guide to better strategy, but good strategy can be done in any number of ways. The point is to explore whether, within the Agile philosophy, there are specific strategic principles that can be incorporated to seamlessly integrate with other Agile activities. A different way to vastly improve ‘planning’ would be to recruit a bunch of *real* behavioural economists (none of these pseudo-scientific pretenders), however throwing them into a *creative* / *digital* environment might cause some interesting frictions :).
Justin McMurray
March 22, 2010
at 10:36 am
Totally agree with the points you make Justin, but can’t help feel that the idea of an Agile Strategy can only be fully implemented when we live in a culture that accepts (and even encourages) mistakes as positive outcome of creation.
Stuart Witts
March 22, 2010
at 10:47 am
Geez Stuart, your comment depressed me (briefly)! Workplaces can be weird places indeed but surely any half-decent one knows how valuable ‘mistakes’ are. It’s even a tenet for the digital world; don’t be afraid to fail, but fail fast. It’s the very basis of a self-informing process. And if it’s not encouraged where you are, you need to find a place where it is.
Justin McMurray
March 22, 2010
at 11:19 am
Great thought provoking post, Justin.
When considering the point of leadership, I believe it’s much more related to the ability to articulate (not create) a *simple* idea that others can build upon.
I’ve personally enjoyed more working with people who have the ability to manifest macro-perspective on what I’m working on (particularly the connection between the evolution that occurs through the detailed development of an idea to elements that exist in its periphery) than those who holdfast to the rigid structure they’ve envisioned or those who leave everything to the discovery process of pure production / magic serendipity through action.
In this sense, it is those who can add elements/ideas/artifacts of cohesion of a ’sensible’ whole whom I consider the greatest planners and leaders.
It is this type of ’structure-as-a-platform’ planning that aids in getting good things done (not just going through the motions of a plan because it’s already been planned) within a reasonable timeframe (avoiding the, sometimes, unnecessarily exhausting and unfocused process where there is no structure whatsoever).
Mario Ramirez Reyes
March 22, 2010
at 11:23 am
Thx for your comment Mario. A point well made. I frequently find myself in the situation where I can intuitively grasp the simple purpose behind a project, however articulating it – and importantly facilitating the conversations around it – is pretty difficult. I certainly need to improve on this. One way we try to do it at MxM is to rely very heavily on visual strategy. Visuals (even basic diagrams) enable faster and more shared understandings than words or text alone. And it doesn’t matter if you’re a crap drawer like me!
Also like your point about “magic serendipity”. That only happens with truly extraordinary talents (occasionally), so there’s no doubt that planning can help ‘retain the magic while removing the mystique’ (which I think I’ve heard in the hallways of our neighbours at BBH…).
Justin McMurray
March 22, 2010
at 1:31 pm
OK, calling for any comments from more hard-core Agilists? And also keen to hear more counter-views (though def don’t want to create yet another ‘traditional vs digital’ yawnfest)…If anyone can make a robust rebuttal, it’ll be a battle-scarred planner.
Justin McMurray
March 22, 2010
at 2:13 pm
yea dude, totally with it. even downloaded the handy chart cuz its exactly what I believe and talk about. It is I believe how we should do work (in lots of other areas as well, not just marketing). Question is, how can we sell it?
So this just makes me think we make sure we work this way for success but until I can figure out a way to sell this to a client (aka the people the folks in mktg dept have to sell to like procurement, board, etc) I’m wondering if we will still have to harp on past experiences, ask for trust, and make “firmer” plans than we actually plan to use. Or something.
Matthew Scott
March 22, 2010
at 2:40 pm
This is a tough one Matthew. Certainly some of our best projects don’t come/go anywhere near the marketing dept. Increasingly there are innovation hubs and special projects – or even just rogue-ish elements – within client organisations that are crying out for something different. And to be honest, we still have to ’sell’ the Agile way very hard. We do this in a variety of ways; however when you actually do bring the client ‘inside’ and start co-creating stuff, they kinda get hooked. Of course we still find ourselves educating/learning constantly. It’s not unknown for us to suggest clients read a copy of ‘Getting Real’.
But there are clients out there who think what they have been getting from agencies (in terms of process as well as creative) is rubbish, and they have an appetite for something different. Not all but some. Ultimately, many clients do need to take some things on trust, but once they’ve been through an iterative/Agile/collaborative process, they don’t seem to ever want to go back.
Justin McMurray
March 22, 2010
at 3:23 pm
Whe I started working in a media agency five years ago, Strategy was fetishised as the potential saviour of media agencies’ developing financial woes; we were all going to offset the revenues lost from commoditisation by ’selling ideas’. This, unsurprisingly, turned out to be nonsense: no business on the planet actually buys ideas – the movie industry pays for the rights to a novel someone has spent years agonising over, pharmacutical companies licence partly-developed formulae and so on. Of course, we all know now that the real response to commoditisation is something to do with digital, data, performance and all that, though no-one has really put this stuff together yet in a way that persuades marketing folk to stop wanting to see ‘plans’.
There are several crucial insights and pointers in your post which suggest a way forward: the importance of trying stuff out and iterating; the patent fact that much ‘traditional’ advertising and media research is rampant post-rationalisation; the depressing truth that most planning is guessing – ‘intuition’ -another way of saying we’ll do something we’ve done before. It is essential that agencies understand that ‘planning’ needs to be superceded by a type of design – designing communications solutions.
Personally, I believe that to solve this, we need to change the whole conceptual framework we bring to bear on communications.Please excuse the plug, but I’m so exercised by this topic I’ve written a short book about it – anyone who would like a copy can email me – hubindustries@googlemail.com and I’ll send them a free pdf.
Steve Taylor
March 22, 2010
at 2:47 pm
You had me at “fetishised” Steve. Though I could possibly do without the word “communications” in your comment, I think you’re right in us needing a new framework. Although I’m less interested in it being ‘conceptual” and more about it being very real. I do like your reference to “designing” solutions – we don’t actually ever use the word “creative” at MxM (which is a very campaign/communications–centric concept); it’s about designing services and experiences. I reckon you would love, and I’d recommend, digging deeper into the philosophy of design thinking…
Justin McMurray
March 22, 2010
at 3:31 pm
Good stuff Justin. Really enjoyed it. I think the real issue here is that it turns out that lots of people can be strategic, not just us strategists. Honestly, if you’re not part of a project it’s not like strategy doesn’t happen, right? (I know at Barbarian Group it certainly still does.) I suspect what the real answer is is that we strategists are just members of the team like everyone else and we just bring our specific angle to the table while also throwing our two cents into interaction design, research, user experience and the like (which if you’re anything like me you’re already doing).
Noah Brier
March 22, 2010
at 2:51 pm
Hear, hear Noah. I still hesitate to tell people I’m a “strategist”. I mean, isn’t everyone to some degree? I like the idea of ’strategy’ kinda being invisible but sustaining (oxygen perhaps!). Or more precisely, strategy not being something tangibly handed on, but participatory activities that help surface collective understanding and insight for the team. Then the work becomes imbued with ’strategy’, not injected with it.
Justin McMurray
March 22, 2010
at 3:36 pm
Nice post, Justin. My concern is that the manifesto is too polarising. For example, the word ‘long-winded’ is problematic. I mean, who would agree that they do ‘long-winded’ research and deduction, even if that was what they were doing?
The original manifesto is notable for not being pejorative about the thing on the right – note that they say “comprehensive documentation” rather than ‘long-winded’. If you’re an Agilist, it’s clearly something that is bad, but if you are not, it doesn’t condemn your existing practice out of hand. It simply says that there’s something they value more highly. In fact, agile processes are entirely against comprehensive documentation, but I suspect that uptake would have been far slower had they said so back at the start.
I think there’s the same problem with the word ’sacred’. These are words that are antagonistic towards planners, rather than likely to help convert them into agile strategists.
I wonder if more moderate language would be better?
James Higgs
March 22, 2010
at 4:31 pm
I think you’re right James. In my aim to provoke responses, I verged to antagonism (with an amount of glee). Though I’m slightly disappointed that there haven’t been more counter-arguments (taking umbrage at the pejorative tone). Appreciate you pointing out this small but utterly crucial point. Once we’re back in the office, be good to continue the discussion and learn/understand more from the ‘native’ Agile software perspective.
Justin McMurray
March 22, 2010
at 5:09 pm
Maybe you shouldn’t be so modest about how good a case you have made, hence agreement breaking out all around you ;)
James Higgs
March 22, 2010
at 5:45 pm
As a battle-scarred planner….Justin, you make some excellent points and it’s a great provocation. I’m fascinated by the idea of Agile Planning and what it means but, perhaps predictably, I don’t think all old school planning skills are dead. It’s a question I struggle with too, when so many core planning skill seem geared towards reductionism- What is the single thing we want to say? What is this brand’s singular essence?-in a world that is increasingly pluralist and co-created. But I think there’s probably a managed tension here-a clarity about what a brand believes in and wants to achieve combined with a flexibility about how it gets there, a working model for how we think communications should work married to early real-world indicators that let us know whether it is working as planned.
There are too many projects in hand-in digital as well as traditional channels-that don’t answer some fundamental strategic questions-
-What is the business problem?
-How is this activity going to help?
-What do we want people to do as a result of this activity?
-and for me this is where rigour and analysis still have a huge role to play.
Rigidly clinging to a set view of how the activity should address these problems however, does feel unnecessarily rigid. As does the tyranny of the consumer insight-that said, I know very few planners today who believe that consumer insight is the only, or even the primary source of inspiration today. A creative solution is as likely to come from a clear articulation of the problem as from a consumer insight.
Pats
March 22, 2010
at 7:06 pm
Excellent and much-needed thinking thanks Pats. One thing that struck me in SXSW was that more than ever the digital kids are drinking waaay too much Kool-Aid. And the skills acquired from decades of marketing activities shouldn’t be laid to waste. I for one see ample evidence of younger ‘planners’ knowing everything about digital/social/interactive and being plugged into amazing networks and the latest/greatest thing, but having absolutely no idea when it comes to breaking down some ‘real’ planning challenges like the ones you noted.
Very useful distinction too btw generating consumer insights (and the many other tools/activities)… I just get riled up about insights and like to provoke. I kinda wish my prev Planning Director – himself the master of cracking insights – read this and really got stuck into me!
Anyways, planning nous is continuing to evolve and while I certainly don’t have the pedigree or experience to understand how it has worked, hopefully some naive thoughts about the brave new environment ’strategy’ finds itself in will provide one piece of a larger guide to its evolution.
And on your other note, we really should continue that discussion about reductivisim vs pluralism as a massive tectonic shift in how brands are starting to be shaped… maybe you could post abt that! Thx again for your comments.
Justin McMurray
March 22, 2010
at 8:08 pm
The reason Agile Strategy would seem to be an oxymoron to the Agile development community is that strategy represents the pinacle of the problem of Big Design Up Front (BDUF), one of the evil demons of Agile. Strategy is after all the forming of a plan, a design for the future. The BDUF for strategy is your common garden inflexible, long-term strategic plans for your business.
The BDUF strategy is challenged in the current environment of rapid change. As Neil Perkin, Bud Caddell and many other smart people have written recently, businesses increasingly operate as Complex Adaptive Systems much like software.
So is the answer the same for strategy as for software. Undoubtably not exactly but they will share some similarities.
If there is one principle not yet mentioned here that I think would be central to Agile Strategy, one of my favourites from Agile Development, it is this:
“Make decisions at the last responsible moment”
That’s it. The issue with typical planning and strategy is that it makes too many decisions, too early, things that can be left to discover and correction. A doing approach. It’s obvious why we do this, because it seems like it adds more value to a strategic process, while in effect it is just guessing.
So to your planner/strategist I believe this means, as Noah said, you need to be part of a team not a part of a chain (writing briefs for creatives) and you need to involved the whole way through, trying, discovering and correcting.
I’m also reminded of something William Owen said which is “Why does everyone want to be a strategist, why don’t they want to be tacticians”
@stueccles
Stuart Eccles
March 22, 2010
at 8:45 pm
Thanks Stuart. This is really starting to get into the nittier/grittier context of what Agile is really about. Absolutely; Agile Strategy needs to stand against the (awesomely acronymed) BDUF. The ‘make decisions at the last possible moment’ will surely be one of the most challenging principles to embrace from a strategic point of view. People, sometimes projects, often crave some type of definition or guideline to shape its evolution. That’s why I like the idea of ‘testing hypotheses’ so that you can quickly setup a proposition – even a ‘decision’ – and then if necessary tear it down again once you’ve concept-tested it. Of course, if it truly is going to be “Agile” strategy then you really need a hard-core Agilist with a strategic perspective to instil it into the team and the process, not just the tools/activities. I nominate you!
Justin McMurray
March 23, 2010
at 2:34 pm
Thanks for the nomination, I will add it to my list.
I need to make a clear distinction that it is “last responsible moment” not “last possible moment” and this makes a huge difference. Of course you need responsible people to determine the last responsible moment.
I think something that can be applied to marketing communications, business strategy is something from the world of start-ups and comes from a conversation with Noah that SF based start-ups will often swivel their proposition often acting like a shark until they hit on a success and then scale-up the idea. I think something people miss when thinking about test and learn is remembering you have to eventually scale-up.
Stuart Eccles
March 23, 2010
at 3:46 pm
Firstly, thanks for the post, really interesting development on the Agile theme, and I really enjoy this blog.
Design has always had these points of planning and strategy but during the creation and build phase of a project things are subject to change. This obviously negates a linear process as optimal and therefore iterative design cycles are the best way to go.
But I think the trouble is explaining this to clients as it seems confusing and chaotic to them. The problem as they see it is if the agency do not have a firm idea of what they are building at the start, how are they going to reach a satifactory destination? Therefore time and effort is dedicated to the planning stages. Do you not think that it is not as much for the agency, but more for the customer that slide decks are created?
Better a strategy sketches an idea, then the creation and build of a project is where the real application of those thoughts take place. We are dealing with wicked problems after all…
Regarding organisation I find that teams gathering around a project rather than being passed down the line, is in my experience, the way to garner full responsibility for a project from all team members, rather than passing the buck. This group hub idea, is the basis of how we should strive to work, but obviously company cultures and organisation charts tend to get in the way.
My beef with Agile is that the importance of having the right cultural environment is often not talked about enough. Teams fine, but where it really becomes important on a big scale is if a company thinks Agile – and it takes more than an IT department having SCRUM meetings everyday. It needs to be taken on at board level and communicated consistently to everyone. One day it will happen, but consider the petition currently running to get the British Government to adopt Agile methods – we are still a long way off in reality.
James Kelway
March 23, 2010
at 8:00 am
Super smart thinking here James. Like you introducing the concept of “wicked problems” and ‘linear vs iterative’ processes. It almost goes without saying these days that the problems we are all trying to solve are tremendously complex. Moving from (in essence) a ‘one->many’ communications model to a ‘many->some->one->many->many’ (or whatever) platform or ecosystem is a tough transition to make. Linear doesn’t cut it in this world.
It is very interesting that you – like many others – return to the problem of selling this ‘right but messy’ approach to clients. It certainly is one of MxM’s bigger challenges, but I’m starting to think we do it relatively well. Makes me think that a collaboration on the ‘business case for Agile thinking’ could be a good idea….
Justin McMurray
March 23, 2010
at 2:41 pm
An idea for discussion: the manifesto is the strategy. Real value is delivered in the tactical execution of a strategy.
Some suggestions for the manifesto: principles over methods, objectives over plans, do don’t talk, fail fast (and embrace it!) and (sort of Stuart’s thing) don’t commit until you have to.
Matt Williams
March 23, 2010
at 9:49 am
While it is a bit of a love-in, I do indeed (heart) this idea Matt. Although it can start to get semantically confusing when you discuss philosophy vs strategy vs manifesto vs approach etc. But I like the fact, as has been alluded, that in some ways Agile is about moving ’strategy’ beyond conceptualisation and into tangible points of action that are integrated with the rest of an Agile process. I think it could be time to start talking about these specific tools and “tactics” and stop seeing them as ‘dirty’ strategic words.
Justin McMurray
March 23, 2010
at 2:47 pm
Stuart’s point about rapid change draws the debate back to the ‘Why?’ of agile. Rapid change means we need to think and execute quickly (often nearly simultaneously) and focus closely on what delivers value first. We also have to broaden our scope. Justin’s excellent post alludes to this in ‘collaboration and conversation’ but we should probably make it more explicit in terms of systems thinking or whole service design.
We need to broaden scope because we can, in a way that 10 or 15 years ago wasn’t possible. If we look at the various strategy traditions we see that they’re not only linear (strategy > design > development) but they also restrict their thinking to departmental remits. Ad planning points to marketing opportunities, design strategy looks at product, technology strategy looks to technical solutions and business strategy to process and finance. That’s fine in a relatively static world seeking out incremental change, but when logical and physical systems start to merge we can and must look at every part of the system to find opportunities for innovation.
This is what we mean by whole service design. Yes, our starting point is usually the customer and how we can use the web to create value for them, but our solutions embrace product and service, communications and process, and sometimes they involve the creation of new business models. Crucially, we don’t restrict our thinking to one or the other. We look at how small changes in one part of the system can have big impacts elsewhere: this is one important attribute of design thinking. All variables can be changed, innovation touches every part of a business and this is why collaboration and conversation is so important.
I also thought that Mario’s point about leadership is really vital and we shouldn’t lose sense of the importance of overview throughout the lifetime of a project. A typical service design and development project runs from anything between 3 months and 12 months. Clients, agencies and partners need a solid grasp of the business drivers and how – through services principles and a synthesis of different disciplines – these translate into design decisions. Projects need a memory (why we’re doing this) and although we have to be able to accept changes (sometimes very big ones) we also have to understand how and whether these really live within the funnel of possibility that leads us to the ultimate goal. I’m not sure how that can be articulated as a manifesto point but it’s part of both simplicity of purpose and the need to see strategy as a *design strategy*, integrating the two disciplines, rather than as planning.
Lastly, there’s Matthew’s point, concerning money, which we shouldn’t ignore. Businesses are used to signing off large amounts of money in return for a well-crafted fiction about returns. An agile strategy needs to take this into account in terms of how projects are sold into companies and upwards into boards. Sometimes this means going under the radar, sometimes it means seeking influence at the highest level, sometimes it means keeping ambition at the level of discretely sized portions. That’s a blog post in itself though.
William Owen
March 23, 2010
at 1:09 pm
Geez William, your comment certainly deserves its own post!
Taking a holistic service design approach – which is what MxM seem to be doing more and more – is probably a way of encapsulating ‘Agile Strategy’ into and throughout the rest of the process (in truth, it shouldn’t be a new discipline).
I know there’s a good post brewing about the collision of ‘Agile’ & ’service design’ from @saulpims, As I think we’re mostly agreed, and as is explicit in the manifesto, segregating disciplines isn’t usually helpful for the final service.
By the way, your line; “Businesses are used to signing off large amounts of money in return for a well-crafted fiction about returns” is simply and savagely spot on. It’s time to take a stand against this, and as Paul Graham from Anomaly UK recently remarked to me, deploy some “radical honesty” in our dealings with clients.
Good point too about seeing this as the ‘design’ of strategy as opposed to ‘planning’… certainly most ‘planners’ could take umbrage at my implied pigeon-holing of them as control freaks obsessed with one-off insights ;). The good ones know it’s really a craft, not a one-dimensional input.
Also like the point about leadership, and in your words “project memory”, being utterly crucial. Haven’t we all been deep into a huge project, discussing various needs/stories/bells/whistles and there’s this nagging voice in the back of your head saying, ‘why the hell are we doing this?’.
The beauty of this – and going back to what Noah said – is that anyone can play this ‘helicopter’ role, not just the ’strategist’.
Justin McMurray
March 23, 2010
at 3:06 pm
I’m not sure that’s exactly what Noah said. It’s not that anyone can be a strategist, or a designer, or a developer – or should want to be – but what’s for sure though is that strength lies in sharing skills and valuing big crossovers in areas of expertise, and we all have more or less ability to synthesise different parts of the whole (business drivers, the opportunities afforded by technology, customer insights, etc.) into a set of requirements and more or less ability to articulate these into a coherent design.
William Owen
March 24, 2010
at 9:45 am
A few responses here.
To William Owen, I would agree that “Businesses are used to signing off large amounts of money in return for a well-crafted fiction about returns”. But I would also add that one element that Agile requires to work, is trust, and specifically the trust between a client and their agile partner to deliver the goods.
In a traditional BDUF world of TV and Print, this trust has traditionally been built on well-crafted plans, which have in turn been built on a mature production model with a relatively tried and tested way of working (like a feature film based on a true story, not complete blather).
In the world we work in, where even the traditional production models are changing, and the world of digital looks like a desert of constantly shifting sands, this BDUF approach can waste a lot of time and money, which could otherwise be focused on producing something of value.
But in this uncertain world, and especially in an Agile one, the trust to deliver a return on investment is still absolutely necessary for clients to part with their cash. This trust often requires an existing relationship, and will always require some well-crafted fiction, albeit delivered in a factual agile way (eg. “we can deliver this set of experiences with 90% certainty, this set with 75% certainty etc”).
To Justin. Strategists and planners spend the most time surveying the landscape and their clients to understand how the business terrain is shifting, so they are probably best placed to parachute these clients into the metaphorical high ground further down the line.
Following on from that point then, Strategy is then all about having a set of good ideas that can help lead the way at the start of a project, a sort of raison d’etre for clients parting with the cash, and then it acts as a useful set of guidelines as you get closer to the point of no return, the memory as William calls it of what you’re trying to achieve.
But, Planners aren’t the only folk who can dig out insights, in fact I’m a firm believer that a good idea can come from anyone, and can happen at any time. The main enemy here is time and cost. If you could get everyone’s insights from start to finish, you might consider it. if you could change the idea at any time, you would and should consider it. But more often than not, it’s not an option. You need to act responsibly to achieve the best results.
As far as budgets will allow, I think that Agile teams should be more blended from start to finish, so that “thinkers” are “doing” more later on the project, and “doers” can “think” earlier in the project. it’s a surefire way to ensure that
-you’re agreed as a team on what your overall objectives are
-that you’re using a common language of how to achieve said objectives
-that you understand how to embrace any change when the opportunity arises to actually change
Robin Wong
March 24, 2010
at 9:22 am
Hi Robin, thanks for your very well considered thoughts. It’s an awesome articulation of yours of one of the themes running through the comments, that you want a situation where:
.
Exactly.
Justin McMurray
March 24, 2010
at 2:16 pm
Everyone seems to want to “do-over” planning. Truth is there is good planning/strategy and bad planning/strategy and a lot of the bad gets a lot of the attention.
If Steven King, is the inventor of ‘old school’ planning you would expect his definition of planning to differ greatly from any ‘new’ definition such as ‘agile strategy’… With respect, I don’t see much difference. Below are a few selections from Mr King’s paper “Art and Science” published in 1982.
“You don’t start with observations. You start with what he [Karl Popper] calls a trial solution – what we call an idea.
…[Next] you have to have a vision of this ‘trial solution’, this is a non-logical process. An unconscious process, an extremely messy process.
…The next stage is experiments. The critical thing here is deliberately attempt to disprove your ideas…the world is utterly different from what we ever imagine.
…The final stage in the invention process is feedback…two sorts of feedback. One, into improving the idea. The Second, going back to modify the problem”.
So if this is what planning was meant to be, what happened?
The way the advertising industry has developed since Steven King’s paper in 1982 has made it very difficult for strategists to practice this type of iterative strategic thinking. Advertising agencies stopped making anything a long time ago. They outsourced production to directors, photographers, digital technology specialists etc and carved off media execution to separate media agencies. With no ability to prototype, experiment or execute in the real world, the only option for them was to focus on ‘conceptual thinking’ or ‘BDUF’.
Some forward thinking agencies seem to be addressing this, if only on a small scale, setting up labs for experimentation (a la Ogilvy, BBH, Media labs etc.); creating partnerships with content creators, VC’s and start-ups (who truly are the leaders in market agility and fast fail learning/prototyping).
The challenge to these agencies is that the core of their business is still unable to hypothesize, experiment and learn in the real world…and copytesting does not count as the real world.
There is a wonderful design exercise to test team work and creativity that involves making a freestanding structure from dried spaghetti and marshmallows. The goal is for the team to build as tall a structure as you can in 18 minutes. The interesting thing is that Kindergarten graduates perform much better (average 25 inches) than business school graduates (average 10 inches) because they pick up the marshmallows and spaghetti and start building where as the business school grads strategize and plan for most of the time.
This is one of the reasons that this strategist chose to work in an agency that makes in house most of what it produces. If you want to practice this type of strategy… William dot Charnock at rga dot com.
William Charnock
March 24, 2010
at 2:46 pm
Thanks William for the fantastic context you’ve set in the discussion. Fascinating to read King’s thinking from 1982. It does indeed read very ‘agile’, albeit in a more linear way.
I certainly wasn’t trying to provide a ‘new definition to planning. More an exploration of strategy in the context of building actual things (as you point out) in an Agile (capital A) environment. Because I totally agree that the separation of ‘thinking’ and ‘doing’ creates compromised results. They are actually mutually informing.
While you do see many agencies returning to a more ‘integrated’ proposition (discl: my last job was at R/GA London), I don’t think that new forms of agency ’structure’ provides the answer. And I don’t think that throwing large teams of ‘diverse’ people onto the problem is any elixir either.
That’s why I’m fascinated by Agile. It’s a real philosophy complemented by actual tools and techniques that seem to fit today’s digital/fail-fast/changing world.
ps – please let us know where should we send the bill for your job ad too! :)
Justin McMurray
March 25, 2010
at 10:09 am
agree with william that start-ups are an interesting place to look for inspiration.
early on in the life of a company, is more about exploration – i.e. what works vs what doesnt. how quickly can you find a working model. in my experience the best investors look more at the team and less at the plan. early on the plan seems to provide an education of sorts and a demonstration of thinking about the road ahead and what could happen.
later stage investments in more “mature” companies seems to be about exploitation – things like scaling and ramping and things that make financial analysts excited. at this point, there is much more focus on the plan and projections, because well, there is more that appears predictable because its about upping resources to get more output from the system discovered in the early stage. the team is still important but the details of the plan matter much more.
I think the hardest part, as some have pointed out, is selling like an early stage company to people used to buying later stage more predictable outcomes.
perhaps another post and discussion on how folks people are succeeding selling a more agile approach.
shaun abrahamson
March 24, 2010
at 4:08 pm
OK, the challenge has been set! People want/need a post showing the ways to (or at least we) ’sell’ Agile. This will be a test of our “radical open-ness”…. :)
Justin McMurray
March 25, 2010
at 11:21 am
Just a quick thought:
Isn’t the main problem we are discussing that most organisations and especially marketeers function and rely on linear processes, whereas creativity, innovation, people and actually the digital space are based on a more non-linear thinking and behaviour.
Would that mean that someone’s task (the planners’?) should be to bridge these worlds to create value for both sides? And has that not always been what a good strategist did, i.e. finding out what the question is that the client needs to have answered, giving direction and inspiration in finding the answer and then telling the client why the answer solves his question?
My thesis is, unless the world of big marketing changes from being mainly risk averse to risk welcoming, we will have to continue to bridge two worlds that are simply not thinking and functioning in the same way. Perhaps: Be rigorous on the outside and agile on the inside?
Nico Westermann
March 24, 2010
at 5:35 pm
A-ha, a great perspective from a planner I admire :). Thx Nico. It’s ironic as we’re always trying to ‘visualise’ / articulate the MxM approach and we can never really nail it because it tends to end up looking linear when it’s really not. And there are only so many circles with arrows and infinity symbols that one can use.
More seriously, the idea of planners bridging two worlds seems to be spot on and was perhaps one reason why the discipline emerged. To act as a bridge between the client and creatives, and between the business problem (linear) and the creative thinking/response (experimental/iterative).
Of course this heritage pretty much excludes the technology/digital perspective. And that’s partially the territory I wanted to explore; how the introduction of a successful/proven/growing technology philosophy (ie Agile) is influencing the equation.
Thanks again for your comments (and also those other links you emailed me!).
Justin McMurray
March 25, 2010
at 11:29 am
Wow – I really enjoyed reading your insightful post and the exiting debate around it. I agree with Nico Westermann, that the linear workflow in agencies is the core obstacle to agilility. Thinking linear is a relict from times less complicated :-)
Nevertheless I’am doubtfully to proclaim the “age of doing” after the “age of planning”.
Sure doing thing is great. And you can easily “over-strategise” a problem and block yourself and a company in a perfectionist search for the ultimate answer.
But agility is also risky:
1. Without a basic strategy or research there are no parameters for measuring success or failure. Clients hate that.
2. Complete agility can be a perfect excuse for being to lazy or unable to plan.
I think the problem is not strategy but the misconception of it in agencies. A strategy is not a magical roadmap free from failure, never to be touched again. It is a prediction into the future and it has to be open for tactical change and feedback all the time. Planning and doing are in a constant loop.
But before the rise of social media direct consumer feedback and context complexity was a very rare thing in the marketing world. So perhaps marketing executives started to believe in the magical power of strategies – simply because the feedback was not so visible.
I have written some more detailed thoughts on my posterous: http://creativeglasses.posterous.com/agile-strategy-tactics-and-the-story-of-a-dj
Christian Riedel
March 24, 2010
at 6:35 pm
Firstly, everyone reading this post/these comments should def read Christian’s piece linked above. The analogy of a strategist as a DJ is simply awesome.
In response to your thoughts, I definitely don’t advocate for the absence of strategy. Those strategic outputs like objectives, principles, measurements etc are all absolutely crucial, what I do advocate for is a different way of achieving/generating these… and in a meaningful/integrated way that is better suited for digital environments filled with complex “wicked” problems (but which forgives failure if it happens fast and is learnt from).
Justin McMurray
March 25, 2010
at 11:40 am
Thanks again for promoting my post.
Today I thought, perhaps our debate isn’t about strategy vs. agility in the first place. It seems to be a more philosophical question: How do we learn from the world and convert our knowledge into action?
The deductive way is about measuring things to check a hypothesis. We all learned in school, that this is a very, very scientific and truthful way. I guess that is why everybody owns a strong believe in numbers.
Although if we measure the wrong things – we won’t get results to work with.
Nevertheless deductive thinking is great, if you know what to measure and it helps you to understand things better, you already know to some extent. You can use it to make a print campagne more effective – a least mathematically.
Abduction on the other hand is needed to make new assumption about the world, based on the broadest variety of information available. That includes collaboration, ethnography,empathy, design thinking…..
Combining unrelated things and testing them is the only way to create something new and gain new knowledge.
For years marketing was accustomed to a known set of tools and did not feel the urge to innovate. Therefore most strategies were written deductively to make the given tools more effective.
But in today’s digital world we are forced to constantly invent new stuff. So the balance between deduction and abduction changes. Be abductive in the beginning and make sure to measure the outcome.
Christian Riedel
March 25, 2010
at 3:37 pm
I think one piece that is missing would be segregation vs. segmentation. Any thoughts? One suggests building walls while other suggests “buckets”. I think that segmentation becomes de facto segregation by not acknowledging the flux in behaviors and identities.
Robert Frolick
March 24, 2010
at 7:33 pm
Provocative post and thoughtful commentary! Thanks Justin.
When you wrote “What I think would be more helpful is a simpler (broader) statement of purpose that acts as a guiding philosophy to help the team develop and judge their thinking”, I was reminded of a post I made about team decision-making based on “Commander’s Intent” http://www.bobtuse.com/2009/08/team-decisions-commanders-intent.html. I think what you might be looking for is sometimes referred to as Commander’s Intent.
Also, your excellent post sparked a few of the ideas in my new post “A Strategy for New Products” http://www.bobtuse.com/2010/03/product-development-spawning-testable.html.
Cheers,
Bob
Bob MacNeal
March 25, 2010
at 10:04 pm
Great post Justin, and a great debate, with some really clever and thoughtful points made.
Lots of the comments have been about barriers to working in an Agile way in agencies. So I thought I’d chip in some practical experience from an agency who has been trying to work in this way for a little while now.
Several commenters talked about the importance of the workplace culture in enabling Agile ways of working. I’d say that’s definitely true. We had to start Albion because our previous agencies weren’t structurally capable of working in this way, and wouldn’t let us change the structure.
Once you’ve got the right structure and culture, you need the right people. We’ve worked hard to bring together a bunch of smart people who are naturally open, fast, and haven’t learnt bad habits in BDA’s (Big Dumb Agencies).
Then you’ve got to have the right clients. We’re lucky enough to have a bunch of entrepreneurial clients who want to try and do things in a different way. In the same way that Justin describes with MxM, it’s self selecting really.
Then you’ve got to find a focussed, nimble, collaborative way of working together. Interestingly, I’ve never heard any of our people or clients talk about “Agile”. But the way we work, at our best, is pretty close to it.
So, how have we practically addressed some of the barriers raised in the comments?
• How to get clients on board? Well, in our experience, don’t try to convert them to the cause. Don’t scare them by talking about Agile or giving them Getting Real to read (sorry Justin). Instead do something more basic to force them into the process – for example we insist that quite a lot of our clients work in our office, at least a day a week. We usually use ‘timescales’ as the excuse (and that’s often true), but it also means they’re on site, in the war room, having stand-up meetings, contributing to the work ‘live’.
• How to get Big Business to take the risk? Well, Big Business *is* risk averse when there’s a lot of money involved. And the amounts involved used to have to be big when the model was buying eyeballs during Coronation Street. But now we can talk with people much more cheaply. And, in my experience, Big Business can be happy to have a punt on something small. So try Agile working first on something small.
• How to break linear process habits? For us, it was a small thing that really helped – doing ‘beta’ versions of docs and decks, starting with 0.x version numbers. It’s a clear signal that this document is open to evolve. Doing this turns a brief from a tablet of stone into an Agile document. For example, the very first thing we do on a project is to write a v0.1 version of the brief – no matter how little we know at that stage. And then we try to do some work (‘planning’ and ‘creative’) against it which will, more often than not, show where it was wrong. So in the next ‘sprint’ (which could be an hour, a day) we write v0.2. And so on. This evolving brief helps keep the team aligned, and means we can always show the client our latest thinking (good Agile practice, I believe.)
• How to do it when everything’s outsourced? Sorry, but you probably have to start your own agency again to pull this off but then it’s simples: a) Do more in house – we just made a TV ad in house, for the craic. b) Only work with likeminded people – we’re working with the awesome Theo Delaney in a focused, nimble, collaborative way on our weekly Betfair Front Room ads.
This isn’t comprehensive and I’m not claiming it would work for you, but it works for us.
As for the role of ‘planning’ in an Agile world, I think the relationship between strategy and tactics is key. Tactics seem somehow to have been depositioned as unsexy in adland, but we need to recognise that they are as important as strategy. Look at many of the oft-quoted modern digital marketing case studies, and you’ll find that clever tactics played as big a part as clever strategy in their success.
For me, having a strategy is still key. But you have to be open to evolving that strategy every day, to keep pace with a rapidly changing environment. This means that the tactics need to be delivered in a live way, so the development process isn’t overtaken by the changing strategy. And of course, ‘planners’ need to stay involved through the whole process, contributing to the tactics too.
So we need a new way of working that can help us both evolve strategy ‘live’, and help us execute tactics against today’s strategy in a harder / better / faster / stronger way.
Justin posed the original question, can Agile and strategy co-exist? But I’d pose a different question: ‘Can an Agile-like methodology help us do advertising strategy and tactics in a way more suited to the real time media environment?’ Admittedly less punchy, but perhaps more accurate.
I think it likely can. But I’m also interested in looking beyond software development for inspiration. For example, lots of great modern advertising is getting increasingly topical/editorial. So I’m interested in journalism – how do newspapers produce 30k (?) quality words a day, or daily magazine shows (e.g. Newsnight ) produce 45 mins of quality TV per night? What’s their methodology, and how can we learn from that?
Glyn Britton
March 29, 2010
at 6:07 pm
Loads of great comments to this post but Glyn’s could well take the cake.
The client advice: “Don’t try to convert them to the cause” is a cracking line. (Don’t worry, it’s only our CTO who tells clients to read ‘Getting Real’!). Because if you can get them involved in an ongoing and meaningful basis, it’s a creeping realisation that this is the *only* to do it for now. They convert themselves.
Like the “strategy ‘live’” notion as well. That’s *what* I was talking about in a nutshell. Because I think – on reflection – that positioning all this as “Agile Strategy” actually brings about as much baggage as it seeks to remove.
This discussion has spilled over to Tim’s post (http://madebymany.co.uk/act-like-a-start-up-2-003513) with some comments about acting like a start-up and being “lean”; certainly my experience is that start-ups are more “lean” than they are “Agile”.
Of course, perhaps “Lean Strategy” doesn’t quite have the same ring to it.
Justin McMurray
March 31, 2010
at 6:39 pm
I think you have to use Agile as a tool to employ when you need it.
Agile was born out of a change in the way SOFTWARE was developed. Trying to apply this methodology for say the creation of a TV ad is bluntly using the wrong tool for the job.
You simply cannot use the iterative model in the same way, because at the end of the sprint you won’t have a testable delivery while you can with software. You also can’t iterate post launch to change your TV ad. So using a waterfall model is probably the best way.
Feeding back into the article, elements of an Agile approach to communications strategy could work in certain cases.
I totally agree that collaboration & conversation are key. You have to create briefs with input from the entire team (business, creative, comms planning, design, development) and make them media neutral if possible.
The simplicity of purpose over consumer insights point I slightly disagree with. Insights allow a hook or a jumping off point for the creative process. They should never be just ‘consumer’ insights as we oftern know that consumers don’t always really know what they want. We’ve often interviewed the teams behind the products to gain that quote or nugget of truth which allows us to hang our creative on.
I agree with the ‘Testing hypotheses’ point but only on software or product development projects. Putting an ad into consumer or focus group testing is quite an experience – one that can lead to highly skewed results.
I agree on the ‘Responding to change’ point but again I’m struggling to see how this would work outside of software or product development. The major problem with marketing is that it is mainly temporal – it is designed around a time for a specific reason (e.g product launch or major event). If the strategy was iterative and changed during the production, then the creative could now be off brief and the deadline wouldn’t shift accordingly. You would be up a certain creek without paddle.
So I commend you Justin for framing this question and would love to hear from people in more ‘traditional’ agencies on how they are appling Agile methods.
sermad
March 31, 2010
at 4:12 pm
Thanks for your detailed and thoughtful comments Sermad. I certainly think that in a linear world, a changing/evolving strategy is going to cause havoc for those downstream. My point though – perhaps not reflected in the actual 4 point ‘manifesto’ – is that there needs to be a degree of integration with the team, between ’strategy’ and design and production, btw tactics/execution etc – otherwise you get flawed results/output.
Thinking and creativity certainly don’t restrict themselves to linear planes, so it’s extraordinary that so many organisations insist on it as a working structure. “Agile” or “lean” or ‘live’ – or any other definition in the same vein – strategy is simply an alternative way that can (hopefully) produce more effective outcomes.
Of course, this is all discussion and ‘thinking’. Gotta get back to what I propose; doing + learning + adapting :)
Justin McMurray
March 31, 2010
at 6:47 pm
Sermad, actually we *are* iterating TV ads post launch.
We’ve sometimes played out a different version of a spot every day of the first week of a campaign, optimising the edit, call-to-action etc. to take account of ‘live’ feedback and analytics.
And now we’re designing TV campaigns to be more ‘editorial’. We film 6 new Betfair Front Room ads every 2 weeks, which allows us not only to be topical, but again to constantly optimise content and creative platform.
Pulling this off does require a nimble whole-team collaboration that does indeed look quite like Agile. (And Clearcast hate it!)
Glyn Britton
April 1, 2010
at 6:00 pm
Great blog post Justin prompting many fascinating responses here. I want to try this out:
“From a business’ point of view strategy is about providing the frameworks required to deliver the business goals.
For a project, strategy is about providing the best framework to deliver the clients’ outcomes.
Strategy is content-free, idea-free.
Agile is a methodology to deliver strategy.”
Talking about stuff for ages and ages is often a way to avoid taking responsibility. Agile as a methodology encourages individual and group responsibility which is why I love it.
Damian Watson
April 8, 2010
at 7:33 am
Also thought you might like a wordle of these responses: http://bit.ly/d7wWBb :)
Damian Watson
April 8, 2010
at 8:13 am
great post justin… i currently lead strategy at Euro RSCG in NY on IBMs global digital, and together we work Agile… and is true that it is a much easier approach to embrace in agencies that are solely digital based
I’m keen to talk to other people who are developing not only software/platform/tech based solutions but also creative communications in Agile…
I developed a creative agency process similar to various scrum/agile methods called collabor8 back in 2002 and find it to be a brilliant way to work – but only if you are prepared to truly embrace multi-discipline teams and integrated communications solutions…
keep up the good work ‘made by many’… i’m a fan…
Matt Donovan
July 17, 2010
at 9:47 pm