The presentation dispels the myth that money always works as a motivator for getting people to do what we want them to do. Rather its value is more noticeable as an anti de-motivator - Pink suggests that organisations need to pay people enough so that money is no longer an issue.

He goes on to detail research which shows that money doesn’t work as a motivator when a task requires even rudimentary cognitive skill which suggests it wouldn’t be all that effective in a software development context.

Following on with this logic Pink suggests that before he did his research he would have thought that if you wanted to get innovation in an organisation then that would best be achieved by giving out an innovation bonus. He now suggests this wouldn’t be effective.

We had an interesting example of this recently where the ThoughtWorks UK and Australia offices tried to run an iPad App competition with the prize of an iPad for the winning entry.

This worked fine in Australia but didn’t at all in the UK. Since the 'incentive' was the same in both cases I’m inclined to believe that the reason it worked better in Australia was due to the fact that the guys there managed to create a spirit of competition between the Melbourne & Sydney offices and between the participants.

Pink suggests that there are three main factors which lead to better performance & personal satisfaction - autonomy, mastery and purpose - and I think that to an extent we can get all of these with the agile approach to software development.

Pink suggests that people like to be self directed and direct their own lives and he gives the example of Atlassian’s Fedex days as an example of developers being given the freedom to do whatever they want for 24 hours and coming up with some really useful products at the end of it.

I think we have autonomy to an extent on software projects. We might not have the ability to choose exactly what problem we’re solving for our customer but we do mostly have the ability to choose how we’re going to solve it.

We can choose how we’re going to design the solution, discussing various trade offs with our customer if there’s more than one way to solve it…​

Pink points out that many people play musical instruments at the weekend even though they have little chance of ever earning money from doing so and he suggests that the reason for this is its fun and we have an urge to get better.

Software development is almost a perfect fit for mastery because there are so many different areas for improvement no matter how good you are.

Corey Haines has been pushing the idea of 'Learn To Type Week' which is just one example of this.

I thought I was pretty good at touch typing but after trying out the different exercises he’s been linking to I realise that there are still areas in which I can improve upon and it’s quite fun trying out the exercises and trying to get better.

Apart from that there are code katas, code koans, new languages and many other ways in which we can improve ourselves.

Pink describes purpose as "what gets you up in the morning racing to go to work" and suggests that we need something more than just making profit.

I mostly don’t feel that I’m actually "going to work" on the projects I’ve been on because the majority of the time the other two factors are being met and I have the opportunity to work with passionate people who want to deliver high quality software together.

I’m not sure if that quite gets to the essence of purpose but it certainly doesn’t feel that what I’m working on is pointless - we’re building something which helps solve a problem for our customer and that seems like a valuable thing to do to me.

I found this presentation really interesting and the way it’s presented with the cartoons is really cool as well.

I haven’t yet read Dan Pink’s book 'Drive' which presumably expands upon this talk but I’ve read 'A Whole New Mind' which was interesting reading so I’m sure I’ll read this one at some stage.