Download as PDF, PPTX
Uploaded byMelinda Seckington
How and Why We Run Internal Hackdays
The document outlines the organization and execution of hackdays, emphasizing the importance of social learning experiences. It details various hackday themes, participant involvement strategies, and lessons learned from multiple events held at FutureLearn. The aim is to foster creativity, collaboration, and innovative ideas among staff while producing tangible outcomes for the company.
TechnologyâŠ
More Related Content
Similar to How and Why We Run Internal Hackdays
How and Why We Run Internal Hackdays
- 1.
- 2.
- 3.
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 13. To pioneer thebest social learning experiences for everyone, everywhere
- 14.
- 15. learn on your own learnfrom each other learn from the community learn by teaching
- 16. learn on your own learnfrom each other learn from the community learn by teaching
- 17.
- 18.
- 19.
- 20.
- 21. why why are you runningthe hackday?
- 22. why is there aspecific theme?
- 23.
- 24. who is thehackday for? who
- 25.
- 26. if everyone: who how doyou involve everybody? does everyone need to code?
- 27.
- 28. where where are you runningthe hackday?
- 29.
- 30.
- 31. when are you runningthe hackday? when
- 32. how many days? when weekdayvs weekend specific days tricky for certain teams? timing with other events?
- 33.
- 34. how how are you runningthe hackday?
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42. why Highlight talent &creativity among the team Get people working across teams
- 43. why Let people becreative and experiment!
- 44. why How do wemake clear that people can work on what they want?
- 45. What can Iwork on? Whatever you want. Well, as long as it is related to FutureLearn in some way or another. Has there always been one thing you wish FutureLearn did? Got some crazy idea that youâd love to experiment with? Go ahead and build it! Our hacks should showcase what FutureLearn could be, so your ideas can range from features that we could add tomorrow to something completely blue sky. why
- 46.
- 47. Everyone in thecompany who
- 48. How to geteveryone involved? who
- 49. Do I needto know how to code? Nope, you donât! Hacking is all about playing with technology and using it in new and creative ways. For our hackday it means coming up with new ideas for FutureLearn and creating something to showcase that idea, be it in code, in semi- decipherable whiteboard scribbles, or in interpretive song and dance. who
- 50.
- 51.
- 52. How to makesure people donât get distracted by the day-to-day? where
- 53.
- 54.
- 55. Full day 10:00 -17:00 when
- 56.
- 57. Allow people toform their own teams and choose hack ideas how
- 58.
- 59. how What next? 1. Checkoutthe whiteboard, get inspired and add your idea 2. Add +1 to any idea you like, add your name to ones youâre interested in working on 3. Talk to people! Think you need a developer or a designer to pair with during the day? Talk to them beforehand to see if they want to help out 4. Think about which tools you might need to install beforehand 5. Check out the Slack #hackday channel for inspiration
- 60. 3 minute demos 1prize Audience vote how
- 61.
- 62.
- 63. ?what did welearn?
- 64. 1Lots of discussionto form teams, less hacking lessons learnt
- 65. 2Not everyone wassure they should join a team lessons learnt
- 66. 3Lots of greatideas, but only one got rewarded lessons learnt
- 67. 4What happens withthe ideas after the hackday? lessons learnt
- 68.
- 69.
- 70.
- 71. why This hackday wewant to generate as many hacks as possible around how we can grow our number of registered users. We want you to come up with any ideas that can help grow our user base - from small changes on the platform to creative concepts for other corners of the web.
- 72. why How to encouragepeople to come up with diïŹerent and lots of ideas?
- 73. why Prize categories: Most likelyto grow awareness of FutureLearn offline Most likely to grow awareness of FutureLearn online Most likely to increase new registrations Most likely to improve number of shares Most likely to reduce bounce rate Most likely to improve conversion from sign up to active learner Best use of social media Simplest change we can make Best hack inspired by data Best international hack
- 74.
- 75.
- 76.
- 77. 1Lots of discussionto form teams, less hacking lessons learnt how
- 78. 2Not everyone wassure they should join a team lessons learnt how
- 79.
- 80.
- 81.
- 82. ?what did welearn?
- 83. 1Too many hacks! lessonslearnt
- 84. 1Donât promise onething and then do something else lessons learnt
- 85. 2Half day istoo short lessons learnt
- 86. 3Judging took toomuch time lessons learnt
- 87. 4Not everyone feltcomfortable just joining a team lessons learnt
- 88.
- 89.
- 90.
- 91. why This time aroundwe want you all to create something that is full of delight, play or fun for our users.
- 92.
- 93. when The day beforethe Christmas Party
- 94.
- 95. 4Not everyone feltcomfortable just joining a team lessons learnt how
- 96. how How can weencourage everyone to participate?
- 97. how How can weget people working across teams?
- 98.
- 99. how 5 minutes topresent per team
- 100.
- 101. how Challenges: Wear clothes withcolours from the FutureLearn gradient (blue to pink to yellow) Bring a Secret Santa present in the theme of delight & play, for less than ÂŁ8.53 Find the hidden chocolate coins Solve the cryptic riddles Make your own lunch and be creative! Perform a song/poem with FutureLearn as the topic (they can be based on real songs and poems).
- 102.
- 103.
- 104.
- 105. ?what did welearn?
- 106.
- 107. 2Challenges were fun forâthisâ hackday lessons learnt
- 108.
- 109.
- 110.
- 111. why Explore ideas fromand for our partners
- 112. why Show our partnersour team and how we work
- 113.
- 114. who Invite representatives from eachof our partners
- 115.
- 116. when The day after ourPartner Forum
- 117.
- 118. how How can weencourage people to participate?
- 119. how Emails and blogposts explaining what the day was for
- 120. how Pre-assigned teams + GoogleDocs + Slack
- 121.
- 122. stats21 hacks 43 partners 10teams 38 fl-ers
- 123. ?what did welearn?
- 124. 1Developers & designers feltstretched lessons learnt
- 125. 2How to sharewhat eïŹect the hackday had? lessons learnt
- 126.
- 127.
- 128. ?what did welearn?
- 129.
- 130.
- 131.
- 132.