Tag : agile

Every designer has stories of the design that got away. The version that the client should have chosen or the version that was turned down because the client’s partner didn’t like purple... These are emotional reasons for a design not succeeding though. Here, I want to talk about the rational reasons behind work being rejected.

Toot toot! Picle 1.0.3 is in the app store. It isn't the overhauled socially integrated version that I wrote about previously, but it does include something that we have had a lot of requests for, converting picles into movies. There are also new notification screens for uploading stories and the uploading of individual Picles has had some improvement tweeks made. 

Last week we had our first Picle strategy meeting since getting back to blighty from SXSW. We have digested a lot of feedback from tweets, emails, reviews, articles, as well as testing it out ourselves, and it was time to step back and take a look at where we're at.

We started off by evaluating how the launch went and how people have responded to the concept of Picle. Stuart drew this rather rudimentary graph of the potential life span of Picle.

While scanning a recent study on crowd behaviour I started to ponder the hows and whens of launching a web service; how can we best drive an idea into the crowd?

The study begins by reminding us of a fairly obvious fact about opinion and crowd feedback, assuming wisdom is what you're going for (the crowd could equally decide your idea is doomed to failure, which is probably a good time to get out) this is pretty useful information:

[…]certain conditions must be met for crowd wisdom to emerge. Members of the crowd ought to have a variety of opinions, and to arrive at those opinions independently.

Makes sense, this is why we expend so much energy testing on diverse user groups before releasing a service into the wild. However, it then goes on to conclude that the wisdom of crowds can be polluted by the cross-pollination of opinions:

Not so long ago, Neil Perkin invited me to speak at the event he was arranging to take place at Google UK HQ. Neil was keen to explore what Agile Planning means and the event, named FireStarters, brought together a 100 or so planners to share in the discussion. What followed was an excellent evening that included Mark Earls giving us What She is Having and many breakout sessions on various themes over beers. Neil has a great write-up on his blog.

This was a great chance to expand on the Lean Startup based approach we are using at Made By Many and introduced at Planningness in NY back last September. Since then we have learn't alot and the presentation I gave (embedded after the jump) introduces what I think can become some best practice for developing "Lean Agencies", agencies built from the ground-up to search for innovation. 

(or How I Learned to Stop Worrying & Love the Obvious)

(also know as ‘The empty hamburger dilemma’)

Most new products and services fail. This is a depressing reality to swallow, however I am amazed by how few people ask why this happens. Or worse still all the people who have an in-built assumption and acceptance that most new things should fail. This shouldn’t be the case.

Here is a sad graph showing total product failures.

Why all this failure?

I’ve swithered about posting these notes, given their visual inferiority to Tim’s. But what they lack in beauty, I hope they make up for in utility. I certainly had fun making them. And as someone more adept with a viola in hand than a sketching pen, I’m not too ashamed of my efforts.*

Enjoy.

Over the last couple of weeks we’ve put everyone at Made by Many through a day of Agile Training with Simon Baker and Gus Power from Energized Work.

These guys really are the Penn and Teller of agile software development, and I thought the session was excellent. Most of us here have been trying to work in agile ways for  five years or more but this was an opportunity to get better at it by broadening our knowledge and understanding. Another post follows containing some more considered takeaways, but I wanted to share these sketch-notes I made during the day. They petered out towards the end of the day as proceedings became more discursive.

There are 10 pages in total, including a ‘page of evil’ where I tried to capture all of the things that we decided one way or another were EVIL.

See the whole set —->

Justin’s ‘Agile versus Strategy‘ post has tapped an excellent debate.

One of the most interesting comments comes from R/GA’s William Charnock, who makes the point that traditional ad agencies got rid of ‘the makers’:

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).

As William and other commenters say, it’s the start-ups who are the true leaders in this space – not least in terms of overall value creation. Indeed, you could argue that the ‘start up culture’ of high-growth tech start-ups has become a defining (and disruptive) force in work cultures well beyond tech, marketing and media.

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).