Loading...
Community presentation
Title — THE 36-HOUR LIVING HACKATHON 36 Hours. Real Problems. Unknown Challenges. One Community. A radically different hackathon experience Concept proposal Visual: dark, energe…
Create your own version
Use this visual direction as inspiration for a new Presenton deck.
Use this designCreator prompt
Title — THE 36-HOUR LIVING HACKATHON 36 Hours. Real Problems. Unknown Challenges. One Community. A radically different hackathon experience Concept proposal Visual: dark, energetic hackathon environment with teams building, playing and collaborating 2. The Problem With Traditional Hackathons Teams arrive with their own ideas Most projects follow the same “AI + App + Dashboard” formula Participants spend 36 hours continuously coding Interaction between teams is limited Winning often depends heavily on presentation The experience becomes predictable Question: What if the hackathon itself became part of the challenge? 3. Our Big Idea “You Don’t Choose What to Build. You Discover It.” Participants don't enter with a fixed project Every team receives a randomly assigned real-world problem Problems are unique and carefully curated Challenges evolve throughout the 36 hours Teams must adapt, collaborate, compete and solve 4. The 36-Hour Journey Show the hackathon as an evolving journey: Hour 0: Enter Hour 1: Draw your problem Hour 2–12: Understand & Build Hour 12: Mystery Box Hour 12–24: Adapt & Collaborate Hour 24–30: User Testing & Boss Challenges Hour 30–35: Final Build & Submission Hour 35–36: Judging & Finale 5. The Problem Box — 300 Unique Problems 300 teams / participants receive unique problem chits No repeated final problem Problems are based on real-world situations Every problem is designed to be solvable within 36 hours Problems focus on people, systems and communities — not just technology Each chit contains: Problem User Context Current workaround Constraint Success condition 6. The Three-Draw Rule Three chances. One final mission. Team leader receives three draws Draw #1 → Can accept or reject Draw #2 → Can accept or reject Draw #3 → Final and locked Once locked, the problem cannot be exchanged Creates suspense, strategy and ownership Every team begins with uncertainty 7. Real-World Problem Universe Show the categories as a visual ecosystem: 🏙️ Smart Cities & Public Infrastructure 🎓 Education 🏥 Healthcare Systems ♿ Accessibility & Inclusion 🌱 Environment & Sustainability 🧑💼 MSMEs & Businesses 👷 Informal Economy 🚨 Emergency Response 🧠 Human Behaviour 📱 Digital Life 🚌 Transportation 🏫 Campus & Community Problems 8. The Mystery Box — Hour 12 At Hour 12, everything changes. Every team receives a mystery box/card Teams don't know what they will receive The card introduces a new challenge, opportunity or constraint Teams must adapt their project Some cards help Some cards disrupt Some cards force teams to rethink their solution 9. Wildcard Cards Four types: TWIST Change the target user Change an important assumption BOOST Get access to an expert Receive hardware/data/resources CHAOS No AI for 60 minutes Build offline Remove a major feature OPPORTUNITY Talk to a real user Access new data Get an industry connection Key idea: The best teams aren't just builders — they're adapters. 10. THE HACKBOARD A live digital/physical board visible to everyone. Two major sections: LEADERBOARD Team rankings Hack Points Challenge wins Community contribution HELP BOARD Teams can publicly post what they need They reveal only the problem area, not their project Example: TEAM 01 🔴 UI/UX Help Needed ⏱️ 30 minutes 🎯 Reward: +100 points Another team can volunteer to help. 11. The Help Challenge System Help someone. Earn points. Take a risk. Challenge levels: Quick Fix: 5–15 min → +50 Skill Help: 15–30 min → +100 Serious Problem: 30–60 min → +200 Boss Challenge: 60–90 min → +400/500 Rules: Requesting team gets no penalty Helping team earns points if successful Helping team loses a smaller amount if unsuccessful Clear time limit Both teams confirm the outcome Anti-farming limits keep the system fair 12. The “I'M STUCK” Moment Introduce a physical/digital I'M STUCK button. When a team is stuck: They activate the request Their help request appears on the Hackboard Other teams can see it Anyone with the required skill can volunteer Teams can become heroes by solving someone else's problem Philosophy: “You came here to build your project. You might leave remembered for helping someone build theirs.” 13. The Corridor Playground The hackathon isn't only about coding. Create mini-games throughout the venue: Reaction-time challenge Mini basketball Table tennis Speed chess Puzzle wall Ring toss LEGO rapid build Console gaming Blind drawing Mini escape challenge Meme/caption challenge Karaoke Participants can: Take breaks Meet other teams Win small prizes Earn Hack Points Reset mentally 14. Real-User Validation Don't build for imaginary users. Create a dedicated User Room. Teams can: Talk to real users Test prototypes Collect feedback Observe actual behaviour Demonstrate their solution Record validation evidence Judges evaluate: Did the team actually understand the person experiencing the problem? 15. Multiple Ways to Win Not everyone needs to win the main prize. Awards can include: 🏆 Overall Winner — The Problem Solver 💡 Best Innovation ❤️ Best Human-Centered Solution 🌍 Best Impact ⚙️ Best Execution 🎯 Best User Validation 🔥 Best Unexpected Solution 🤝 Community MVP 🧠 Most Valuable Individual 🎲 Best Risk Taker 🚀 Best Comeback 🌙 3 AM Madness Award 16. The Hack Points Economy Hack Points are earned through: Help Challenges Boss Challenges Corridor Games Mystery Challenges Community contributions Special missions Points can unlock: Mentor access Expert consultation Hardware Data access User interviews Special resources Mystery opportunities Important: Hack Points enhance the experience but do not simply replace project judging. 17. The Venue Becomes a Game Divide the venue into experience zones: THE DRAW Problem discovery THE ARENA Main building area THE HACKBOARD Help + leaderboard THE PLAYGROUND Games & challenges THE MENTOR LOUNGE Experts & guidance THE USER ROOM Real-world validation THE STAGE Final pitches & awards Make the entire venue feel like a live game world, not a classroom. 18. How Teams Are Judged Suggested scoring: Problem Understanding — 25% Impact / Usefulness — 20% Innovation — 20% Execution / Working Prototype — 20% User Experience — 10% Storytelling / Pitch — 5% Judges should ask: Did they solve the right problem? not simply: Did they build something technically impressive? 19. Why This Hackathon Is Different Create a strong comparison: Traditional Hackathon Living Hackathon Choose your idea Discover your problem Build continuously Build + adapt Fixed challenge Mystery challenge Teams work separately Teams help each other Coding-focused Problem-solving focused Breaks feel like downtime Breaks become games Imaginary users Real users One winner Multiple ways to win Pitch-focused Experience-focused Bottom line: We're not changing the hackathon project. We're changing the hackathon itself. 20. Closing — THE EXPERIENCE Large closing statement: 36 HOURS. 300 PROBLEMS. UNKNOWN CHALLENGES. ONE COMMUNITY. Then: You don't choose what to build. You discover it. And finally: Build. Adapt. Help. Play. Solve. Welcome to the Living Hackathon. Follow Design: {"palette":["Raw cardboard kraft #E8DCC4 — physical problem chit background","Blueprint navy #0D1F3C — dominant text, container borders, and blueprint grids","Stamp vermilion #EB3B2D — draw status, wildcard stamps, and penalty alerts","Chalkboard off-white #F8F6F0 — clean content paper cards","Industrial graphite #24292F — body copy and structural diagrams"],"fonts":{"Archivo Black":"https://fonts.googleapis.com/css2?family=Archivo+Black&display=swap","Work Sans":"https://fonts.googleapis.com/css2?family=Work+Sans:ital,wght@0,100..900;1,100..900&display=swap"},"type":"Archivo Black in uppercase for heavy tactile display headers, category badges, and challenge titles; Work Sans in regular and medium with generous line height for rules, mechanics, and scenario briefs.","layout":"A six-column physical game-board layout mirroring box inserts and tactical field manuals, using partitioned rectangular zones, heavy border rules, and numbered step registers aligned strictly to the left edge.","framework_treatment":"Perforated tear-off chit outlines with dashed borders, circular rubber-stamp completion marks, tactile cardboard surface textures, physical token icon markers, and side-by-side comparative ledger tables for judging frameworks.","feels_like":"An unboxed premium strategy board game paired with an expedition survival field manual"}
Presentation overview
This community presentation was shared by FAROOQ MD as a complete 20-slide example. Title — THE 36-HOUR LIVING HACKATHON 36 Hours. Real Problems. Unknown Challenges. One Community. A radically different hackathon experience Concept proposal Visual: dark, energe… The preview lets you review the full sequence in order, rather than judging the design from a single cover image.
Use it as a reference for planning your own deck: notice how the amount of information changes from slide to slide, where visual emphasis appears, and how repeated design choices help the presentation feel connected. Community examples are inspiration, not locked templates, so you can keep the ideas that fit your audience and replace anything that does not.
Learn from the example
Look at the job each slide performs. Identify where the deck introduces its subject, develops the main points, adds evidence or examples, and moves toward a conclusion.
Notice which element attracts attention first and how headings, supporting text, images, and data are separated. Strong hierarchy makes the intended reading order obvious.
Compare spacing, typography, color, and repeated components across the slides. Consistent rules help varied content feel like one presentation instead of unrelated screens.
Make it your own
Begin with your audience and the decision, lesson, or action the presentation should support. Replace the topic, examples, evidence, and visuals with material you can verify, then edit every slide for one clear takeaway. You can borrow the visual direction without copying the creator's wording or message. Presenton will use this community deck as a design reference while you develop content for your own purpose.
