Hackathons

What's a hackathon?

• Crowd-sourced innovation
• Process-lite outcome creation
• Take thinking beyond previous dares
• Inclusive, levelling, participative
• Pacy, Energising, Purposeful

What makes a good hackathon?

• A critical issue or new opportunity
• Energised, creative, collaborative people
• A conducive environment
• Belief in the process
• Holding nerve, being bold, determination to succeed

hackathons

Sprint 1: what's some of the ways to describe our ideal situation? What will we see, feel, know and do for this to be a truly resolved issue or perfect situation?

Sprint 2: what gets in the way of our progress now and potential barriers in the future?

Sprint 3: Our mini-hacks; ideas; suggestions - how can we get started on creating solutions, better ways and activities to change our situation?

Sprint 4: Clustering our hacks: how can build on mini-hacks to aggregate our thinking and create feasible, energetic, creative ways forward?

Sprints timetable

• 40 minutes: Capture headline thoughts on ASPIRED STATE to flipchart
• 30 minutes: Capture BARRIERS to flipchart. 30 minutes - Break and review our work - walk the walls
• 120 minutes+ : Mini-Hacks - post its / flipchart. Cluster/link mini-hacks . Produce hacks "hypotheses". Lunch & re-group
• 110+ Form Hack Squads. Take Mini-Hacks to full Hack. Use Canvas. Break. Produce and deliver short "playback pitch" of Hacks for group

Untitled Slide

Our Hack hypothesis:
We believe for through will then we will know

hackathons: Sprint Summary

• 40 minutes: High level aspired state
• 30 minutes: Barriers
• 120+ minutes: Mini-Hacks
• 110+ minutes: Hacks and Pitches