1
00:00:15,964 --> 00:00:20,288
Several years ago, here at TED, Peter Skillman introduced a design challenge called the marshmallow challenge.

2
00:00:22,399 --> 00:00:27,682
And the idea's pretty simple. Teams of four have to build the tallest free-standing structure out of

3
00:00:27,835 --> 00:00:32,961
20 sticks of spaghetti, one yard of tape, one yard of string and a marshmallow.

4
00:00:33,308 --> 00:00:36,543
The marshmallow has to be on top. And, though it seems really simple,

5
00:00:36,640 --> 00:00:41,390
it's actually pretty hard, because it forces people to collaborate very quickly.

6
00:00:41,798 --> 00:00:46,234
And so I thought that this was an interesting idea, and I incorporated it into a design workshop.

7
00:00:46,440 --> 00:00:49,114
And it was a huge success. And since then,

8
00:00:49,191 --> 00:00:55,190
I've conducted about 70 design workshops across the world with students and designers and architects,

9
00:00:55,300 --> 00:00:59,737
even the CTOs of the Fortune 50, and they're something about this exercise

10
00:01:00,151 --> 00:01:03,714
that reveals very deep lessons about the nature of collaboration,

11
00:01:03,854 --> 00:01:05,650
and I'd like to share some of them with you.

12
00:01:06,231 --> 00:01:11,681
So, normally, most people begin by orienting themselves to the task.

13
00:01:12,001 --> 00:01:15,141
They talk about it, they figure out what it's going to look like,

14
00:01:15,247 --> 00:01:19,188
they jockey for power, then they spend some time planning, organizing.

15
00:01:19,392 --> 00:01:20,852
They sketch in and they lay out spaghetti

16
00:01:21,050 --> 00:01:27,613
They spend the majority of their time assembling the sticks into ever-growing structures and then, finally,

17
00:01:27,684 --> 00:01:30,357
just as they're running out of time, someone takes out the marshmallow,

18
00:01:31,271 --> 00:01:39,333
and then they gingerly put it on top, and then they stand back, and Ta-da! they admire their work.

19
00:01:39,641 --> 00:01:44,076
But what really happens, most of the time, is that the "ta-da" turns into an "uh-oh,"

20
00:01:44,260 --> 00:01:48,761
because the weight of the marshmallow causes the entire structure to buckle and to collapse.

21
00:01:49,279 --> 00:01:53,465
So there are a number of people who have a lot more "uh-oh" moments than others,

22
00:01:53,693 --> 00:01:56,880
and among the worst are recent graduates of business school.

23
00:01:59,615 --> 00:02:04,554
They lie, they cheat, they get distracted, and they produce really lame structures.

24
00:02:04,996 --> 00:02:08,122
And of course there are teams that have a lot more "ta-da" structures,

25
00:02:08,234 --> 00:02:16,173
and, among the best, are recent graduates of kindergarten. And it's pretty amazing.

26
00:02:16,248 --> 00:02:19,685
As Peter tells us, not only do they produce the tallest structures,

27
00:02:19,769 --> 00:02:22,769
but they're the most interesting structures of them all.

28
00:02:22,797 --> 00:02:26,983
So the question you want to ask is: How come? Why? What is it about them?

29
00:02:26,895 --> 00:02:32,769
And Peter likes to say that, "None of the kids spend any time trying to be CEO of Spaghetti Inc."

30
00:02:33,156 --> 00:02:35,531
Right. They don't spend time jockeying for power.

31
00:02:35,494 --> 00:02:37,186
But there's another reason as well.

32
00:02:36,891 --> 00:02:42,953
And the reason is that business students are trained to find the single right plan, right.

33
00:02:43,137 --> 00:02:45,215
And then they execute on it. And then what happens is,

34
00:02:45,583 --> 00:02:47,691
when they put the marshmallow on the top, they run out of time,

35
00:02:47,858 --> 00:02:52,921
and what happens? It's a crisis. Sound familiar? Right.

36
00:02:53,672 --> 00:02:56,985
What kindergarteners do differently, is that they start with the marshmallow,

37
00:02:57,421 --> 00:03:02,359
and they build prototypes, successive prototypes, always keeping the marshmallow on top,

38
00:03:02,556 --> 00:03:06,241
so they have multiple times to fix ill built prototypes along the way.

39
00:03:06,388 --> 00:03:10,952
So designers recognize this type of collaboration as the essence of the iterative process.

40
00:03:11,380 --> 00:03:15,943
And with each version, kids get instant feedback about what works and what doesn't work.

41
00:03:16,568 --> 00:03:22,068
So the capacity to play in prototype is really essential, but let's look at how different teams perform.

42
00:03:22,602 --> 00:03:27,976
So the average for most people is around 20 inches, business schools students, about half of that,

43
00:03:28,150 --> 00:03:32,839
lawyers, a little better, but not much better than that, kindergarteners, better than most adults.

44
00:03:33,050 --> 00:03:37,422
Who does the very best? Architects and engineers, thankfully.

45
00:03:42,882 --> 00:03:46,320
39 inches is the tallest structure I've seen. And why is it?

46
00:03:46,257 --> 00:03:50,445
Because they understand triangles and self-re-enforcing geometrical patterns

47
00:03:50,446 --> 00:03:54,513
are the key to building stable structures.

48
00:03:55,376 --> 00:03:58,939
So CEOs, a little bit better than average. But here's where it gets interesting.

49
00:03:59,120 --> 00:04:03,621
If you put you put an executive admin. on the team, they get significantly better.

50
00:04:05,832 --> 00:04:08,934
It's incredible. You know, you look around, you go, "Oh, that team's going to win."

51
00:04:08,989 --> 00:04:10,802
You can just tell beforehand. And why is that?

52
00:04:10,913 --> 00:04:16,598
Because they have special skills of facilitation. They manage the process, they understand the process.

53
00:04:17,045 --> 00:04:24,481
And any team who manages and pays a close attention to work will significantly improve the team's performance.

54
00:04:25,162 --> 00:04:30,038
Specialized skills and facilitation skills, and the combination leads to strong success.

55
00:04:31,328 --> 00:04:35,392
If you have 10 teams that typically perform, you'll get maybe six or so that have standing structures.

56
00:04:35,324 --> 00:04:39,325
And I tried something interesting. I thought, let's up the ante once.

57
00:04:39,535 --> 00:04:42,721
So I offered a 10,000 dollar prize of software to the winning team.

58
00:04:43,051 --> 00:04:47,117
So what do you think happened to these design students? What was the result?

59
00:04:48,854 --> 00:04:53,105
Here's what happened. Not one team had a standing structure.

60
00:04:55,687 --> 00:04:59,437
If anyone had built, say, a one inch structure, they could have taken home the prize.

61
00:04:59,872 --> 00:05:03,684
So, isn't it interesting that high stakes have a strong impact.

62
00:05:03,996 --> 00:05:07,307
We did the exercise again with the same students. What do you think happened then?

63
00:05:07,674 --> 00:05:10,238
So now they understand the value of prototyping.

64
00:05:13,190 --> 00:05:17,252
So the same team went from being the very worst to being among the very best.

65
00:05:17,478 --> 00:05:20,227
They produced the tallest structures in the least amount of time.

66
00:05:20,611 --> 00:05:25,048
So there's deep lessons for us about the nature of incentives and success.

67
00:05:25,818 --> 00:05:30,468
So, you might ask: Why would anyone actually spend time writing a marshmallow challenge?

68
00:05:31,021 --> 00:05:36,396
And the reason is, I help create digital tools and processes to help teams build cars

69
00:05:36,498 --> 00:05:37,778
and video games and visual effects.

70
00:05:38,404 --> 00:05:43,532
And what the marshmallow challenge does is it helps them identify the hidden assumptions.

71
00:05:43,912 --> 00:05:48,786
Because, frankly, every project has its own marshmallow, doesn't it.

72
00:05:49,178 --> 00:05:54,682
The challenge provides a shared experience, a common language, common stance to build the right prototype.

73
00:05:55,158 --> 00:05:59,283
And so, this is the value of the experience, of this so simple exercise.

74
00:05:59,642 --> 00:06:02,663
And those of you who are interested, may want to go to marshmallowchallenge.com.

75
00:06:03,111 --> 00:06:06,238
It's a blog that you can look at how to build the marshmallows.

76
00:06:06,724 --> 00:06:08,344
There's step-by-step instructions on this.

77
00:06:08,879 --> 00:06:13,507
There are crazy examples from around the world of how people tweak and adjust the system.

78
00:06:13,884 --> 00:06:15,574
There's world records on this as well.

79
00:06:15,913 --> 00:06:20,726
And the fundamental lesson, I believe, is that design truly is a contact sport.

80
00:06:21,996 --> 00:06:24,683
It demands that we bring all of our senses to the task,

81
00:06:25,022 --> 00:06:27,837
and that we apply the very best of our thinking, our feeling

82
00:06:28,072 --> 00:06:31,635
and our doing to the challenge that we have at hand.

83
00:06:31,774 --> 00:06:34,961
And, sometimes, a little prototype of this experience is all that

84
00:06:35,021 --> 00:06:39,208
it takes to turn us from an "uh-oh" moment to a "ta-da" moment.

85
00:06:39,177 --> 00:06:41,239
And that can make a big difference.

86
00:00:00,000 --> 00:00:00,000
Thank you very much.


