HackerTube 中文?
Learning signals and model behavior →

Beyond rewards, what helps good work happen?

A talk about motivation and a research organizer’s recollections separate pay, individual bonuses, room to explore and conditions for collaboration.

Questions in this reading · 5
  1. Separate adequate pay from adding a bonus
  2. Autonomy is not working alone
  3. What does a colleague’s success mean for me?
  4. When should colleagues see unfinished work?
  5. What should a team uphold when the process leaves room for judgment?

Separate adequate pay from adding a bonus

Pink introduces experiments relating reward levels to task performance, then stresses that inadequate pay itself affects motivation. “Money does not matter” misses that distinction. In his account, mechanical tasks and tasks requiring thought responded differently to rewards. Before applying that account at work, describe whether the task follows known steps or searches for an unknown solution. Then check the research’s participants, reward sizes, performance measures and time horizon. The animation alone cannot establish that a particular bonus will make your team perform worse.

Passages and timestamps · 1
pay people enough so that they're not thinking about money
RSA ANIMATE: Drive: The surprising truth about what motivates us · ▶ 5:00–5:06

Autonomy is not working alone

Pink uses autonomy, mastery and purpose to explain effort beyond extra bonuses. Simons’s recollection adds organizational conditions: recruit accomplished researchers, give them freedom and computing infrastructure, and create an environment where they talk to one another. He did not prescribe which predictive pattern each person had to discover. This is more specific than leaving experts alone: exploration can remain open while communication and experimental tools require deliberate support. Is the bottleneck unwillingness, or a lack of permission, feedback or tools to try? His retrospective success story does not isolate the causal effect of each arrangement, but it makes autonomy a set of conditions worth examining.

Passages and timestamps · 2
autonomy mastery and purpose
RSA ANIMATE: Drive: The surprising truth about what motivates us · ▶ 5:13–5:19
everyone talks to everyone else
Jim Simons (full length interview) - Numberphile · ▶ 33:02–33:07

What does a colleague’s success mean for me?

Simons also emphasizes sharing profits: a colleague’s useful discovery benefits others. That does not directly contradict Pink’s criticism of some individual performance bonuses. Base pay, a reward contingent on one task and longer-term shared gains are different arrangements. Reducing them to one opposition between external rewards and intrinsic motivation loses those distinctions. Ask a narrower question: do current incentives encourage sharing failed attempts and helping colleagues, or keeping knowledge private? This is a question suggested by the comparison, not proof that profit-sharing always works or that one firm establishes a universal rule.

Passages and timestamps · 2
everyone's shared in the profits
Jim Simons (full length interview) - Numberphile · ▶ 34:49–34:55
pay people enough so that they're not thinking about money
RSA ANIMATE: Drive: The surprising truth about what motivates us · ▶ 5:00–5:06

When should colleagues see unfinished work?

Catmull recalls Pixar showing unfinished shots to colleagues every day, while there was still time to change the work. Roosendaal describes bringing artists and developers into film production. Fur and grooming needs that artists raised during production became concrete tasks for developers. One practice brought feedback into the making of each shot. The other let production shape which tools the team built. The two accounts suggest different questions. Does a review give colleagues a chance to identify what can still change? Does a tool request identify the step in production that artists need to improve?

Passages and timestamps · 2
We show it every day when it's incomplete.
Ed Catmull, Pixar: Keep Your Crises Small · ▶ 6:43–6:47
To get artists on board to work together with the developers
"Money doesn't interest me" - Ton Roosendaal 2017 Interview · ▶ 28:24–28:29

What should a team uphold when the process leaves room for judgment?

Cantrill distinguishes priorities from principles. A team can rank frugality and quality differently, while honesty and integrity should guide its judgment in gray areas. Martin approaches the question through Agile practices such as continuous integration and collaboration, describing them as commitments teams make. The two talks suggest asking two questions before changing a process. Which priorities can shift with the circumstances? Which commitment did the process help the team keep, and how will it keep that commitment now?

Passages and timestamps · 3
values are expressions of relative priority
Principles of Technology Leadership | Bryan Cantrill | Monktoberfest 2017 · ▶ 2:23–2:31
principles have to be elucidated if you want people to exercise sound judgment
Principles of Technology Leadership | Bryan Cantrill | Monktoberfest 2017 · ▶ 50:15–50:22
they are promises you make they are not tasks to follow
"Uncle" Bob Martin - "The Future of Programming" · ▶ 62:20–62:27

Try it on your own example

Choose a real task and name its most missing condition: adequate pay, clarity, autonomy, feedback, tools or a way to share in results. After changing one condition, observe quality and collaboration as well as output. These sources help formulate the questions; they do not guarantee the answers.