This document outlines strategies for having fun in the workplace presented by Holly Cummins and Martijn Verburg. It begins with an introduction on quantifying and measuring fun. It then provides a 20 step plan for achieving fun that includes ideas like creating a Chief Fun Officer role and installing a ball pit. The document discusses how fun can be good for business by increasing productivity and reducing sick leave. It also examines what types of activities and tasks are inherently fun versus unfun. Finally, it provides suggestions for how to introduce more fun elements like pairing, reducing meetings and estimates, focusing on prototyping, and increasing automation.

1. #jspring
Holly Cummins, IBM | @holly_cummins
Martijn Verburg, JClarity | @karianna
May 2017
A Software Developer’s Guide to
FUN in the workplace
How to achieve Euphoria despite the Despair

2. I’m from IBM’s Bluemix Garage.

4. Is this a fun talk?

5. Is this a fun talk?
No. It’s a talk about fun.

6. Is this a fun talk?
No. It’s a talk about fun.
That’s different.

7. Is this a fun talk?
No. It’s a talk about fun.
That’s different.
Obviously.

8. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
20 step plan to achieve FUN.
1. Quantify and Qualify your FUN metrics
2. Create a Chief FUN Officer (CFO) role
3. Gamify your daily tasks to make them more FUN
4. Enthusiastically high five everyone each morning for FUN
5. Install a FUN ball pit
6. Inject a FUN word of the day into conversations
7. Wear FUN clothing, something with flair
8. Create FUN certificates with gold star systems - relive the fun of
kindergarten!
9. Nominate FUN assessors for each team
10.Laugh Out Loud (LOL) once a day in the office, others will enjoy your FUN

9. Let’s talk about your career.

10. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
“Dear Boss, you need to send
me to J-Spring so I can go to
the session on…. FUN.”

11. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
“Dear Boss, you need to send
me to J-Spring so I can go to
the session on…. FUN.”

12. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
, Having fun at work

13. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
, Having fun at work
Are you brave enough?

14. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
Are you brave enough?
I’m not :)

16. Wait. Where’s “fun-loving”?

17. We keep fun a secret.
Wait. Where’s “fun-loving”?

18. What is Fun?

19. A Fun Guy.
(Remember, fun means jokes.)

20. "Fun is a point on the intersection
of engagement levels and social
interaction for a given activity.”
Fun: An Exploration in its Relevance to Interaction Design - Elise Woolley, 2010

21. Aside:
When is fun not-
fun?

22. Aside:
When is fun not-
fun?

23. Aside:
When is fun not-
fun?
When it's your job.

24. Things that are Fun

25. Things that are Fun
Something
novel

26. Things that are Fun
Something
novel
Doing
something you’re
good at

27. Things that are Fun
Something
novel
Doing
something you’re
good at
Completing
a task

28. Things that are Fun
Something
novel
Doing
something you’re
good at
Completing
a task
Getting fast
feedback

29. Things that are Fun
Something
novel
Doing
something you’re
good at
Completing
a task
Getting fast
feedback
Creating
something
new

30. Things that are Fun
Something
novel
Doing
something you’re
good at
Completing
a task
Getting fast
feedback
Creating
something
new
Fixing
something
old

32. Fun

33. Fun

34. The Psychology of Fun
The brain has pleasure centres which are
triggered when you do something fun.

35. How do you measure fun?
Excerpted from Elise M. Woolley, B.S.,
Fun: An Exploration in its Relevance to Interaction Design

36. That was called the
Funtinuum.

37. That was called the
Funtinuum.
If you remember just one thing from this talk …

38. Programming is fun.

39. Programming gives pleasure
to both types of thinkers:
• Creative
• Logical

40. We get to control stuff when
we program.

41. Which
programming
language is the
most fun?

42. Which
programming
language is the
most fun?
• Clojure?

43. Which
programming
language is the
most fun?
• Clojure?
• Java?

44. Which
programming
language is the
most fun?
• Clojure?
• Java?
• Groovy?

45. Which
programming
language is the
most fun?
• Clojure?
• Java?
• Groovy?
• Javascript?

46. Which
programming
language is the
most fun?
• Clojure?
• Java?
• Groovy?
• Javascript?
• Python?

47. Which
programming
language is the
most fun?
• Clojure?
• Java?
• Groovy?
• Javascript?
• Python?
• Ruby?

48. Which
programming
language is the
most fun?
• Clojure?
• Java?
• Groovy?
• Javascript?
• Python?
• Ruby?
• Scala?

49. Which
programming
language is the
most fun?
• Clojure?
• Java?
• Groovy?
• Javascript?
• Python?
• Ruby?
• Scala?
• Visual Basic?

50. Which
programming
language is the
most fun?
• Clojure?
• Java?
• Groovy?
• Javascript?
• Python?
• Ruby?
• Scala?
• Visual Basic?
• Swift?

51. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
Say …
Making noise is kind of fun, isn’t it?

52. Why are most of our workplaces
Not Fun?

53. The 1980/90's Management Model
Very hierarchical
Control favoured over
autonomy
Technology seen as a
cost centre

54. http://www.defenceimagery.mod.uk

55. Puritan confronts ale drinkers
Howard Pyle

56. The value of Fun in the workplace

57. @holly_cummins
IBM Watson IoT Centre, Munich

58. IBM IoT Lab, Munich

59. @holly_cummins

60. Research shows:
Fun is good for
business.

61. Research shows:
Fun is good for
business.

62. Research shows:
Fun is good for
business.

63. Research shows:
Fun is good for
business.

64. Studies have shown...
Employee fun

65. Studies have shown...
Employee fun

66. Studies have shown...
Employee fun
Less sick leave

67. Studies have shown...
Employee fun
Less sick leave
Harder working

68. Studies have shown...
Employee fun
Less sick leave
Harder working
More productivity

69. https://hbr.org/2012/01/positive-intelligence

70. “Your brain at positive is 31%
more productive than your brain
at negative, neutral or stressed. "
https://hbr.org/2012/01/positive-intelligence

72. https://www2.warwick.ac.uk/fac/soc/economics/staff/eproto/workingpapers/happinessproductivity.pdf

73. "Individuals [who just
watched a comedy video]
have approximately 12%
greater productivity."
https://www2.warwick.ac.uk/fac/soc/economics/staff/eproto/workingpapers/happinessproductivity.pdf

74. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
Your brain needs breaks.

75. Practical example: Everyone loves lego trains.

76. Info Support funded their employees’ lego trains.

77. Thanks, @johanjanssen42!
Why? Good business.

78. How much fun can
you expect to have?
https://www.flickr.com/photos/paulesson/3065570366

79. How much fun can
you expect to have?
(Yes, this is a picture of lots
of fungi. You’re welcome.)
https://www.flickr.com/photos/paulesson/3065570366

80. Limits to Fun
• No one likes working on things that
aren’t valuable or useful.
• So if you take that to its extreme, and
only do activities if they’re fun and
enjoyable, will that work?
• Self-discipline is still needed.

81. Just because it's fun,
doesn't mean it's good.

82. Just because it's fun,
doesn't mean it's good.

83. "I love the smell of napalm in the morning
.... smells like victory.”
Bill Kilgore,
Apocalypse Now

84. "I love the smell of napalm in the morning
.... smells like victory.”
Bill Kilgore,
Apocalypse Now
Is everyone having fun?

86. Fun. What could possibly go wrong?

87. Fun. What could possibly go wrong?

88. Fun. What could possibly go wrong?
2008: A developer had a lot of fun with Groovy.

89. Fun. What could possibly go wrong?
2008: A developer had a lot of fun with Groovy.

90. Fun. What could possibly go wrong?
2008: A developer had a lot of fun with Groovy.
2009: The others who had to maintain the
code had less fun.

91. Enjoy fun.
Responsibly.

92. _
How to achieve fun
Warning: This is our context and our experience of Fun.
Your workplace culture may be different.

93.
A process being unfun
is a red flag that it’s not
adding value.

94. Step 1.
Find un-fun things.
Get rid of them.
... because they're probably waste.

96. Fun Not-Fun
Programming Meetings
Puzzles Mysteries
Collaboration Criticism
Just doing it Process/Ceremony
Learning Repeating
Designing Sizing
Doing Status reporting
Prototyping Hardening
Interactions Interruptions
Making a difference Being a cog

97. We can fix these.
Fun Not-Fun
Programming Meetings
Puzzles Mysteries
Collaboration Criticism
Just doing it Process/Ceremony
Learning Repeating
Designing Sizing
Doing Status reporting
Prototyping Hardening
Interactions Interruptions
Making a difference Being a cog

98. We can fix these.
Fun Not-Fun
Programming Meetings
Puzzles Mysteries
Collaboration Criticism
Just doing it Process/Ceremony
Learning Repeating
Designing Sizing
Doing Status reporting
Prototyping Hardening
Interactions Interruptions
Making a difference Being a cog
Pair
programming

99. We can fix these.
Fun Not-Fun
Programming Meetings
Puzzles Mysteries
Collaboration Criticism
Just doing it Process/Ceremony
Learning Repeating
Designing Sizing
Doing Status reporting
Prototyping Hardening
Interactions Interruptions
Making a difference Being a cog
Pair
programming
#noestimates

100. We can fix these.
Fun Not-Fun
Programming Meetings
Puzzles Mysteries
Collaboration Criticism
Just doing it Process/Ceremony
Learning Repeating
Designing Sizing
Doing Status reporting
Prototyping Hardening
Interactions Interruptions
Making a difference Being a cog
Streamlined
process
Pair
programming
#noestimates

101. We can fix these.
Fun Not-Fun
Programming Meetings
Puzzles Mysteries
Collaboration Criticism
Just doing it Process/Ceremony
Learning Repeating
Designing Sizing
Doing Status reporting
Prototyping Hardening
Interactions Interruptions
Making a difference Being a cog
Streamlined
process
Pair
programming
#noestimates
Self-generating
status

102. We can fix these.
Fun Not-Fun
Programming Meetings
Puzzles Mysteries
Collaboration Criticism
Just doing it Process/Ceremony
Learning Repeating
Designing Sizing
Doing Status reporting
Prototyping Hardening
Interactions Interruptions
Making a difference Being a cog
Streamlined
process
Pair
programming
#noestimates
Self-generating
status
Protect peace

103. Findable
documentation
We can fix these.
Fun Not-Fun
Programming Meetings
Puzzles Mysteries
Collaboration Criticism
Just doing it Process/Ceremony
Learning Repeating
Designing Sizing
Doing Status reporting
Prototyping Hardening
Interactions Interruptions
Making a difference Being a cog
Streamlined
process
Pair
programming
#noestimates
Self-generating
status
Protect peace

104. Findable
documentation
We can fix these.
Fun Not-Fun
Programming Meetings
Puzzles Mysteries
Collaboration Criticism
Just doing it Process/Ceremony
Learning Repeating
Designing Sizing
Doing Status reporting
Prototyping Hardening
Interactions Interruptions
Making a difference Being a cog
Streamlined
process
Pair
programming
#noestimates
Self-generating
status
Protect peace
MVP

105. Findable
documentation
We can fix these.
Fun Not-Fun
Programming Meetings
Puzzles Mysteries
Collaboration Criticism
Just doing it Process/Ceremony
Learning Repeating
Designing Sizing
Doing Status reporting
Prototyping Hardening
Interactions Interruptions
Making a difference Being a cog
Streamlined
process
Pair
programming
#noestimates
Self-generating
status
Protect peace
MVP
Self-directed
teams

106. Findable
documentation
We can fix these.
Fun Not-Fun
Programming Meetings
Puzzles Mysteries
Collaboration Criticism
Just doing it Process/Ceremony
Learning Repeating
Designing Sizing
Doing Status reporting
Prototyping Hardening
Interactions Interruptions
Making a difference Being a cog
Streamlined
process
Pair
programming
#noestimates
Self-generating
status
Protect peace
MVP
Self-directed
teams
Automation

107. Make it easy for people to find the
information they need to do their job.
Find a good, indexable, solution.
Use it.

108. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna

109. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna

110. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
Get rid of the stuff that stops
us doing what we enjoy.

111. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
Get rid of the stuff that stops
us doing what we enjoy.
“We’re short staffed. You’re going to
need to cancel all my meetings for a
month so I can do programming.”

112. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
Get rid of the stuff that stops
us doing what we enjoy.
“We’re short staffed. You’re going to
need to cancel all my meetings for a
month so I can do programming.”
This worked!

113. Interactions are fun.
Interruptions are not.

114. Interactions are fun.
Interruptions are not.
Martijn promises me this is a hilarious in-joke if you're British.
Apparently.

115. Protect your coding time
from meetings.
“I’m sorry, since I’m pair-
programming, I can’t make
that meeting.”

116. Pair programming

117. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
#noestimates
Estimates are rarely accurate.
Why bother??

118. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
Can adding logging ever be fun?
Prototyping versus hardening

119. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
Can adding logging ever be fun?
Prototyping versus hardening
Making a difference is fun.

120. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
Can adding logging ever be fun?
Prototyping versus hardening
Making a difference is fun.
Having a prototype become real is fun.

121. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
Can adding logging ever be fun?
Prototyping versus hardening
Making a difference is fun.
Having a prototype become real is fun.
Add the logging when you know it actually matters.

122. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
"We don't want to be the
prototyping department.”
-- Head of Innovation, A-Client

123. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
Testing should not be part
of the hardening phase.
TDD is fun.

124. TDD

125. TDD

126. Automation
Computers don’t expect to have fun (yet).
Let them do the tedious tasks.
Bonus: Automating stuff is fun (yay!).

127. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
Status for all to see.

128. @holly_cumminshttp://ibm.biz/bluemixgaragelondon@holly_cummins @karianna
Keep stories small, so
status is self-reporting.
Daily stand-up. Keep it
short.
Status for all to see.

129. We all hate being told what to do.
Usually, because we know it’s wrong.
Let people make their own
decisions.

130. Step 2: Add fun

131. Can I have a volunteer?
... or two?

132. The exercise:
Write down your partner’s father’s name.

133. The exercise:
Write down your partner’s father’s name.

136. Wait, where’s the rigour?

137. Wait, where’s the rigour?

138. Wait, where’s the rigour?
Write down your partner’s father’s name.

139. Wait, where’s the rigour?
Write down your partner’s father’s name.
We need QA on these letters. Show a
draft of each letter to me, first.

140. Wait, where’s the rigour?
Write down your partner’s father’s name.
We need QA on these letters. Show a
draft of each letter to me, first.
Show each letter to the room, so we
know what your progress is like.

141. Wait, where’s the rigour?
Write down your partner’s father’s name.
We need QA on these letters. Show a
draft of each letter to me, first.
Show each letter to the room, so we
know what your progress is like.

142. What have we learned?
• Status reporting and code reviews slow
things down.
• That was on an earlier slide, but we
learned that better through a game :)

143. Children learn through play.
Adults do too.

145. Play
Exploration
Work
Games

146. Play
Exploration
Work
Games
Play: for its own sake
Exploration: investigation
Work: a goal
Games: a goal and rules

150. TDD

152. Build gamification

153. Build gamification
(Strictly speaking, productization of build gamification)

154. Build gamification
can be pretty serious.

156. Play

157. Quirkiness

162. Images: shawcomputing.net, computerhistory.org

163. Images: shawcomputing.net, computerhistory.org

164. Images: shawcomputing.net, computerhistory.org
"Is 'Gullible' in
the Dictionary?"

165. Quirkiness
How do a production-train slack-integration right:

166. _
Failing
at
Fun

167. What if you got paid to do
something other people
would pay to do?

169. No, not the best
job in the world.

172. A layer of fun

173. A layer of fun
… on top of a terrible
workspace …

174. A layer of fun
… on top of a terrible
workspace …
is still terrible.

175. 31% of us dislike team-
building activities.
http://www.successfulmeetings.com/Strategy/Meeting-Strategies/When-Teambuilding-Fails/

176. 31% of Americans dislike
team-building activities.
http://www.successfulmeetings.com/Strategy/Meeting-Strategies/When-Teambuilding-Fails/

177. How to ruin an office party?
Take attendance.

178. _

179. _
Fun is important.
Recap on achieving fun:
1. Get rid of un-fun things
2. Add fun things
Doing 2. without 1. is going to fail.

180. #jspring
Thank you!
@holly_cummins
Please rate this session
in the J-Spring app