Skip to main content

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.


What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's Motivation 3.0 foundation.  The subjects found enjoyment in the task and enjoyed solving the problems for the joy it brought them. Harlow found that one could also lessen the intrinsic drive by applying common reward and punishment on top of the intrinsic drive and thereby reduce the effects of the intrinsic drive.

So science has known and verified since 1949 the concepts of intrinsic motivation.  But business has yet to comprehend this lesson.

One of the very first persons I ever hired in software development was Bob. I hired him largely because of one of his statements. Bob said, "I would do this job for nothing, I just like programming." I had already verified that Bob was a competent programmer and could do the job, but when he gave me this insight into what made him tick, I knew instantly that he would be the person to hire. I never had to motivate Bob, just point him toward a problem we needed a program to solve and he came up with a solution. We also paid him.

Chapter 1  The Rise and Fall of Motivation 2.0


Opens with the contest of Microsoft's MSN Encarta vs Wikipedia.  Encarta with all the backing of the worlds largest corporation is now defunct, closed, nonexistent; while Wikipedia continues to grow and prosper.  What could possible explain this?  Answer: the power of intrinsic motivation and a good cause, with a touch of benevolent dictatorial leadership.

The Industrial Revolution was powered by the Motivation 2.0 (reward & punishment) methods.  Frederick W. Taylor's scientific management was created to drive the industrial complex, it is based on the carrot and stick (Motivation 2.0).  It served Ford very well in his creation of the assembly line.

See Also: Esko Kilpi's article on Productivity Revolutions - Medium. An interesting view of Taylor the socialist and troublemaker. And a prediction that "technological augmentation" is going be the next revolution in productivity for the knowledge worker.

Interesting that Taylor leads off his paper on the Scientific Management method by quoting President Theodore Roosevelt. The President said that "The conservation of our national resources is only preliminary to the larger question of national efficiency." In this Taylor takes up the great man's example of a leader and turns it into a method of leadership that does not require the great man (nor the great man theory).  Taylorism's main objective was to improve economic efficiency via labor productivity.  What we now call "working harder through doing more with less."

Pink notes that Abraham Maslow was a former student of Harry Harlow at Univ. of Wisconsin.  It is Maslow that is famous for man's hierarchy of needs (1943, A Theory of Human Motivation).

In the 1950's Fred Herzberg developed his Two-Factor Theory of Motivation.



In the 1960s the MIT management professor Douglas McGregor used Maslow's work to inform the business world that people were complex beings and required a more complex model than a two dimensional carrot or stick model to motivate them effectively.  McGregor developed the Theory X and Theory Y model.


I find it interesting that McGregor coined the term "Human Resource" thereby degrading all people to a fungible commodity in an accountant's ledger.  Where as he proposed a theory of management that would have Leader's treat people with respect and empower them to do their job well (Theory Y).  I've also read that he developed both theories as strawman theories and assumed more would be developed.  I guess no one bothered to stand up another theory after Y.  Dan Pink refers to McGregor's modest improvement to business's understanding as Motivation 2.1.



Motivation 2.0 leaves us with three "incompatibility problems."    "How we organize what we do; how we think about what we do; and how we do what we do" (p 21).

McKinsey Quarterly estimates that the US now gets only 30% of job growth from algorithmic work and 70% from heuristic work.

Dan Ariely - author of Predictably Irrational - TED speaker  addresses the band-aid problem: to rip it off quickly or slowly?



Teresa Amabile of Harvard Business School has found that external rewards and punishments (carrot & sticks) work well with algorithmic tasks.  However these same motivation techniques have devastating effects for heuristic tasks.  "Amabile calls it the intrinsic motivation principle of creativity, which holds, in part: 'Intrinsic motivation is conductive to creativity; controlling extrinsic motivation is detrimental to creativity.'" In other words, the central tenets of Motivation 2.0 may actually impair performance of the heuristic, right-brain work on which modern economies depend" (p 30).


 Chapter 2:  Seven Reasons Carrots and Sticks (Often) Don't Work.


A review of Newton's first law of motion:  A object in motion will stay in motion, and an object at rest will stay at rest, unless acted on by an outside force.  Is motivation of humans a law of nature or is it something of a completely different nature entirely?  Pink reasons that even the great Issac Newton didn't get the law of motion correct in all scales of the universe and evokes Quantum Mechanics of the absurdity small world of quarks as proof.  Then reasons that perhaps we need a new law.  "When rewards and punishments encounter our third drive [intrinstic motivation], something akin to behavioral quantum mechanics seems to take over and strange things begin to happen" (p 35).



The Sawyer Effect:  some practices can transform work into play - and - rewards can transmute play into work (a double edged effect).

The name is taken from Mark Twain's Tom Sawyer and Aunt Polly's fence painting episode.  Tom transforms the painting of the fence into intrinsic motivation and is then begged to allow his friends to paint.  Twain's principle: "that work consists of whatever a body is obliged to do, and that play consists of whatever a body is not obliged to do" (p 36).

Behavioral scientists have known about the double edged sward of the Sawyer Effect for 40 years.  See Edward Deci sutdy at CMU (p 5).

The Hidden Cost of Rewards  1978, edited by Mark R. Lepper & David Greene.
These guys studied pre-schoolers and their play - when the rewards turned play into work the students wouldn't play any more - see page 38.  Repeated experiments showed "over and over again, [...] that extrinsic rewards - in particular, contingent, expected, 'if-then' rewards - snuffed out the third drive" (p 39).

Alfie Kohn's Punished by Rewards (1993) reports this profound knowledge that is so often overlooked.

There is even evidence that higher rewards lead to lower performance.  See p. 40 - 41 Higher Performance.



Like rewards, goals may also have a weird behavior when applied in as Motivation 2.0 business would have them used.  Several well known business school professors write that: "Goals that people set for themselves and that are devoted to attaining mastery are usually healthy.  But goals imposed by others - sales targets, quarterly returns, standardized test scores, and so on - can sometimes have dangerous side effects" (p 50).  They suggest that goals should come with the warning label: "Goals may cause systematic problems for organizations due to narrowed focus, unethical behavior, increased risk taking, decreased cooperation, and decreased intrinsic motivation. Use care when appling goals in your organization."


See page 52 for why fines for tardness may not get people to your meetings on time - it decreases their intrinsic desire for punctuality and shifts the tardness to a transactional cost.  Punishment doesn't promote good behavior - it diminishes a sense of the group norm.

... more to come ... still reading the book ...


See RSA's rendering of Dan's speech, one of my all time favorite videos.

Was responding to a request for a beginning Product Manager's first books...  here's further reading:


Citations:
A.H. Maslow, A Theory of Human Motivation, Psychological Review 50(4) (1943):370-96.

Bradford C. Johnson, james M. manyika, and Lareina A. Yee, "The Next Revolution in Interaction," McKinsey Quarterly 4 (2005): 25-26.


Related posts:

Drive: How we Used Daniel Pink’s Work to Create a Happier, More Productive Work Place - InfoQ by David Mole

A trick for motivating people
Post a Comment

Most Popular on Agile Complexification Inverter

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

What belongs on the Task Board?

I wonder about these questions a lot - what types of task belong on the task board?  Does every task have to belong to a Story?  Are some tasks just too small?  Are some tasks too obvious?  Obviously some task are too larger, but when should it be decomposed?  How will we know a task is too large?

I answer these questions with a question.  What about a task board motivates us to get work done?  The answer is: T.A.S.K.S. to DONE!



Inherent in the acronym TASKS is the point of all tasks, to get to done.  That is the measure of if the task is the right size.  Does it motivate us to get the work done?  (see notes on Dan Pink's book: Drive - The surprising Truth about what motivates us) If we are forgetting to do some class of task then putting it on the board will help us remember.  If we think some small task is being done by someone else, then putting it on the board will validate that someone else is actually doing it.  If a task is obvious, then putting it on the board will take vi…

Refactoring - examples from the book

Martin Fowler's book Refactoring:  Improving the Design of Existing Code has a simple example of a movie rental domain model, which he refactors from a less than ideal object-oriented design to a more robust OO design. Included in this Refactoring_FirstExample.zip Zip file are the Java source code files of the Movie, Rental, and Customer classes. Along with a JUnit CustomerTest class. Using these example source files you too can follow along with the refactoring that Fowler presents in the first few chapters of his book.