<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Olli Savisaari on Medium]]></title>
        <description><![CDATA[Stories by Olli Savisaari on Medium]]></description>
        <link>https://medium.com/@o.savisaari?source=rss-1b1bb018d7f1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gadb-jSZfSE6gPXHtfcrDw.jpeg</url>
            <title>Stories by Olli Savisaari on Medium</title>
            <link>https://medium.com/@o.savisaari?source=rss-1b1bb018d7f1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:49:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@o.savisaari/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Opening up open innovation!]]></title>
            <link>https://medium.com/@o.savisaari/opening-up-open-innovation-474e3ceeabdf?source=rss-1b1bb018d7f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/474e3ceeabdf</guid>
            <category><![CDATA[open-innovation]]></category>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[problem-solving]]></category>
            <dc:creator><![CDATA[Olli Savisaari]]></dc:creator>
            <pubDate>Mon, 16 Apr 2018 10:57:35 GMT</pubDate>
            <atom:updated>2018-04-17T13:12:13.232Z</atom:updated>
            <content:encoded><![CDATA[<h4>Introducing Open Innovation Meetups to encourage open innovation approach in technology projects</h4><p>The world is full of communities trying to respond to different needs and trying to bring doers and makers together around various topics. But let’s face it, there is no one who invites challenge-driven hackathon enthusiasts, problem solvers and groundbreaking visionaries across the board to share their wisdom with like-minded people.</p><p>Whether you’re oriented in business, software development or design, this community is something you definitely worth checking out. We are putting this together for you.</p><h4><strong>Motives for arranging meetups</strong></h4><p>Our ultimate goal is to make everyone’s work meaningful.</p><p>Developers and designers have caught up on to the fact that it’s hard for industry giants to create new, interesting products. That’s why it’s hard for corporations to hire the best talent. Instead, the most talented individuals seek small, more agile companies where their work really matters.</p><p>We, too, have had enough with the waterfall model and the old way of doing things. Since corporations have the resources and smaller companies have the vision, maybe there is something we could do to make both parties benefit?</p><p>The reason we’re putting together these meetups is simple: we’ve seen open innovation work in practice and now, we would like to convince you that it is the way to go. With a combined experience from hundreds of innovation challenges and dozens of pilot projects, we hope we can share some DO’s and DON’Ts we have learned the hard way, so you won’t have to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uuLmQ4GASuNhHYkyfppwzw.jpeg" /><figcaption>Problem solving in real life. © Daniel Taipale</figcaption></figure><h4><strong>What do participants gain?</strong></h4><p>We encourage you to check your ways of working. How are you promoting the innovative culture at your company? Can you support your client to make better decisions or be more effective?</p><p>We aim to bring you the latest in open innovation: upcoming hacks, practical toolkits as well as newest research in the field.</p><p>This all aims to fulfill our ultimate goal: we want your work to matter. However, people are rarely able to bring this approach to a company all by themselves. And that is where the meetups come in. By meeting like-minded people, sharing thoughts and ideas <em>you</em> can make this community even more meaningful.</p><h4><strong>What are these meetups all about?</strong></h4><p>Open innovation meetups will be organized regularly starting in May 2018, with the next one just around the corner!. The themes and content will be different each time. Want to contribute? Shoot us a message!</p><p>So, this is what we bring to the table:</p><ul><li>Latest publications and case studies behind open innovation</li><li>Best practices and lessons learned from pilot projects based on hackathon concepts</li><li>Practical toolkits and tools for success</li><li>A way to enter hackathons, hear about open innovation challenges and other relevant events</li><li>A network of people to connect and share your ideas with. We believe that ultimately, these encounters are the seeds for real, radical innovation</li></ul><p>To make this all matter, we need your help! After all, no matter how much amazing content we produce, it’s all meaningless unless we have someone to share it with. That’s why we hope that you share this view of working. We warmly welcome you to this community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*na9Rsp9NTc8hGhCzUiJe_A.jpeg" /><figcaption>Part of our community! © Daniel Taipale</figcaption></figure><h4><strong>So, how can I join this fun?</strong></h4><p>Our first meetup will be held on May 15th at Maria 01. It’s open for anyone interested and we would be more than happy to see you there!</p><p>In the first event, we will start with a brief introduction to the topic of open innovation, how it is used to create novel ideas and why it’s so useful. We will then open a case example of how a open innovation supports founding of new companies and lastly, we will hear the takeaways from 30 pilot projects that have sprung from open innovation challenges run by Industryhack in 2017.</p><p>If you have any questions at all, please don’t hesitate to reach out to us!</p><p>See you at the meetup!</p><p>Remember to register for the event:<br><a href="https://open-innovation-meetup-2018-05.eventbrite.com/">https://open-innovation-meetup-2018-05.eventbrite.com</a></p><p>And please, join the fun on Facebook as well:<br><a href="https://www.facebook.com/events/217433269007653/">https://www.facebook.com/events/217433269007653/</a></p><h4>With love,</h4><p>Industryhack &amp; Perfektio</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=474e3ceeabdf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hack report: Kohdataan-hack]]></title>
            <link>https://medium.com/@o.savisaari/hack-report-kohdataan-hack-a127f5f26f8a?source=rss-1b1bb018d7f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a127f5f26f8a</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[mentoring]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Olli Savisaari]]></dc:creator>
            <pubDate>Wed, 24 Jan 2018 18:38:54 GMT</pubDate>
            <atom:updated>2018-01-25T21:27:36.963Z</atom:updated>
            <content:encoded><![CDATA[<h4>Miten hyödyntää hackathon-kokemusta hyvän mentoroinnin peruskivenä?</h4><p>Harva hackathon onnistuu enää yllättämään. Väistämättäkin muodostuu tiettyjä odotuksia aiempien kokemusten perusteella, ja yli kymmenen hackathonin kokemuksella tietää aika hyvin millainen meininki niissä on.</p><p>Mutta ei tällä kertaa.</p><p>Ensimmäinen yllätys <a href="http://kohdataan.fi/hackathon/">Kohdataan-hackissa</a> oli alustuspuheenvuorojen erittäin korkea laatu.</p><p>Monessa hackissa puheenvuoroja pitävät yrittäjät tai tapahtuman järjestäjät, ja jotain kertoo se, että kovinkaan monesta esityksestä ei ole jäänyt mieleen juuri mitään. Yksi syy voi olla se, että odotukset ja todellisuus eivät kohtaa: yleisö tuskin malttaa odottaa pääsevänsä ratkomaan ongelmia samalla, kun esiintyjä pitää myyntipuhetta epäilemättä hienosta tuotteestaan.</p><p>Mutta — ei täällä.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L7qw3jRnyFGAObdnw-u5qA.jpeg" /><figcaption>Tapio Haanperä Kehitysvammaliitosta pitämässä yhtä alustuspuheenvuoroista. Kuvan avulla voit kurkistaa myös kulissien taakse — reunassa näkyy osa kuvausryhmää, jonka avulla yhteiset osuudet streamattiin koko maailmalle Yle Areenan kautta. Kuva: Kaisa Kaatra.</figcaption></figure><p>Puhujien tavoitteena oli tökkiä osallistujien ajatuksia liikkeelle, ja saada heidät ajattelemaan isosti. Ylenkin streamaama kahden tunnin mittainen hackathonin aloitus oli miehitetty erittäin inspiroivilla ja teemaan täydellisesti sopivilla puhujilla, joiden puheenvuorot asettivat hackiin sopivan innostuneen tunnelman ja auttoivat tiimejä pääsemään alkuun ripeästi.</p><p>Aiheet vaihtelivat saavutettavuudesta pelillistämiseen sekä sosiaalisista taidoista tulevaisuuden teknologioihin. Onko motivoivampaa, kuin kuulla esteettömyyden asiantuntijoiden, eli loppukäyttäjien itsensä kokemuksia teknologian kanssa painimisesta? Tämän parempaa starttia puhujaohjelman osalta on vaikea saada.</p><p><a href="https://areena.yle.fi/1-4333300">#Kohdataanhack - Näin suunnittelet saavutettavan somepalvelun</a></p><p>Linkistä voit itse katsoa tapahtuman tallenteen.</p><p>Toinen yllätys oli se, kuinka pienellä porukalla tapahtuma oli tehty. Muutamasta henkilöstä koostuva ydinporukka osoitti todellista ammattitaitoa loihtiessaan tapahtuman kasaan. Osallistujia hemmoteltiin monipuolisten ja terveellisten aterioiden ja snackien avulla koko viikonlopun ajan unohtamatta tietenkään saunomis- ja uintimahdollisuutta!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ElADH-N5tvR5h3GMAZg7aQ.jpeg" /><figcaption>Kohdataan-hackathonin järjestäjät: Tanja Räsänen (vas.), Mia Purho, Ronja Oja ja Pia Rahkola. Kuva: Kaisa Kaatra.</figcaption></figure><p>Sadat post-it laput saivat kyytiä, kun tiimit alkoivat lauantaina kartoittamaan saavutettavuuteen liittyviä ongelmia ja ideoimaan niihin erilaisia ratkaisuja.</p><p>Alku on usein hackathonin vaikein osuus. Pitäisi löytää ongelma, joka on tarpeeksi iso ratkaistavaksi, mutta ei liian iso, jotta ratkaisu on toteutettavissa. Sen takia alan ammattilaiset, eli mentorit, aloittivat oman työnsä heti tiimien jakamisen jälkeen. Tarkoitus oli, että kaikki pääsevät heti kiinni varsinaiseen työskentelyyn ja hahmottelemaan omaa ratkaistavaa ongelmaansa.</p><p>Tiimien päästyä vauhtiin heistä paistoi innokkuus. Lisäksi monia vei eteenpäin monipuolisuus. Yksi oli työskennellyt ikänsä lasten ja nuorten kanssa, kun taas toinen ratkoi päivätyössään vanhusten yksinäisyyteen liittyviä ongelmia. Eri alojen osaajien ja eri taustoista tulevien ihmisten tiedon yhteentuominen on yksi olennaisimmista onnistumisen edellytyksistä.</p><p>Kolmas yllätys oli se, kuinka vähän tiimit lopulta pyysivät apua ja kommentteja mentoreilta, sillä oma työskentely nojaa hyvin vahvasti mentoreiden asiantuntijuuteen ja tietopohjaan. Hyvän mentorin kuuluu kuitenkin lähestyä tiimejä — jopa pyytämättä.</p><p>Kun kysyy oikeita kysymyksiä, jokaiselta tiimiltä löytyy aina epävarmuuden aiheita, ja idean selittäminen muille kirkastaa konseptia sen selittäjälle. Vaikka tiimien ajatukset ja ideat eivät tulleet esille ihan itsestään, lopulta tiimit vastailivat mentoreille mielellään, ja kertoivat innokkaasti omasta konseptistaan.</p><p>Lauantain lähestyessä loppua oli mielenkiintoista huomata miten osallistujien ajatukset alkoivat muotoutua ratkaisuiksi. Alustavista ratkaisuista huomasi, että mentorien viestiä oli kuunneltu tarkasti.</p><p>Mentorit ovat todella tärkeässä roolissa hackathonin onnistumisen kannalta. Kirjoitimme <a href="https://www.perfektio.fi/blogi/how-to-be-a-mentor">hyvän mentorin </a>ominaisuuksista, ja hyvät mentorit onkin helppo tunnistaa.</p><p>Aiempi kokemus konseptoinnista, ja tieto siitä mikä on johtanut omien konseptien kaatumiseen oli erityisen arvokasta ja auttoi tunnistamaan samoja yleisiä ongelmia Kohdataan-hackissa. Silti oli erittäin vaikeaa tunnistaa ja arvioida omaa mentorointa ja sen vaikuttavuutta samoin kriteerein, mitä on muille joskus asettanut.</p><blockquote>“Loppujen lopuksi näihin kysymyksiin on mahdotonta saada täydellistä vastausta.”</blockquote><p>Herää kysymys, mikä on kullekin tiimille hyödyllistä tietoa? Mikä auttaa heitä pääsemään eteenpäin työskentelyssä? Kuinka valmis tiimi on ottamaan vastaan apua ja ideoita? Miten voi varmistua siitä, että mentorointi vie tiimiä oikeaan suuntaan, eikä vahingossa johda väärälle reitille. Niinkin on tapahtunut.</p><p>Useasti.</p><p>Loppujen lopuksi näihin kysymyksiin on mahdotonta saada täydellistä vastausta. Täytyy vain luottaa omaan osaamiseen ja asiantuntijuuteen. Parhaimmillaan mentorointi kasvattaa myös mentoria itseään.</p><p>On helppoa katsoa ratkaisua ulkopuolisena ja tunnistaa siinä piileviä haasteita. On helppo havaita <a href="https://en.wikipedia.org/wiki/Sales_presentation">pitchin</a>* heikkoudet, kun kuuntelee sitä yleisöstä.</p><p>Ei kuitenkaan ole yhtään helppoa muistaa näitä asioita, kun itse muodostaa konseptia hackathonissa.</p><p>Näiden havaintojen tekeminen ja niistä oppiminen on mentorille kenties arvokkainta, mitä hackathon voi antaa.</p><p>Niin myös meille.</p><p><em>Kohdataan-hack oli ensimmäinen hackathon, johon osallistuimme järjestäjinä ja mentoreina. Eikä se jää viimeiseksi.</em></p><h4>About Hack Report</h4><p><em>Hack Report is our way of giving back in the context of hackathons. Hack Reports highlight well crafted hackathons and innovation challenges. They also provide glimpses on how we hack award winning solutions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a127f5f26f8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Perfektio Weekly 5]]></title>
            <link>https://medium.com/@o.savisaari/perfektio-weekly-5-340f6a3ce985?source=rss-1b1bb018d7f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/340f6a3ce985</guid>
            <category><![CDATA[perfektio-weekly]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[techcrunch]]></category>
            <category><![CDATA[user-interface]]></category>
            <dc:creator><![CDATA[Olli Savisaari]]></dc:creator>
            <pubDate>Tue, 05 Dec 2017 07:44:34 GMT</pubDate>
            <atom:updated>2017-12-05T08:27:50.375Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oPG8R_LYIsZ4GAGbIUvXcw.jpeg" /><figcaption>Our team at the TechCrunch Disrupt Berlin Hackathon</figcaption></figure><h4>Making marathons more pleasurable with Cheer My Friend</h4><p>What are we up to this week? What happened last week? Perfektio Weeklies are a light collection of what is happening in our company, what our culture is like, and what types of design and development stuff you should read about this week!</p><h3>🗓 What is Perfektio up to this week?</h3><h4>Fortum hackathon in Sweden</h4><p>We are going to Stockholm for yet another Industryhack, figuring out how the home of the future will be like!</p><p><a href="https://industryhack.com/challenges/ai-comes-home/">AI Comes Home</a></p><h3>✌️ What happened last week?</h3><h4>TechCrunch Disrupt Berlin Hackathon 2017</h4><p>We participated in TechCrunch’s hackathon in Berlin and built Cheer My Friend -app in 20 hours! It allows marathon runners to get voice support from their friends and family to boost motivation. Read more in the TechCrunch blog post and watch the video of Tuomas pitching our idea!</p><p><a href="https://techcrunch.com/2017/12/03/cheer-my-friend-lets-you-motivate-runners-with-voice-messages/">Cheer My Friend lets you motivate runners with voice messages</a></p><h3>⌨️ Newest dev stuff</h3><h4>Learn JavaScript the fun way</h4><p>This great little game teaches you Javascript by making you control a cute little robot. Try it!</p><p><a href="https://lab.reaal.me/jsrobot/">JSRobot</a></p><h4>Performant way to animate layouts</h4><p>Animating anything besides opacity and transform, for example width and height often results in slow and painful animations. This tutorial goes into detail on how to make these animations performant.</p><p><a href="https://css-tricks.com/animating-layouts-with-the-flip-technique/">Animating Layouts with the FLIP Technique | CSS-Tricks</a></p><h3>🖌 Our favorite bits about design</h3><h4>This is why we love great design</h4><p>It’s not only about decoration. Every project comes together as an intricate play between different aspects, and here’s three major categories you need to be thinking about.</p><p><a href="https://uxplanet.org/3c-of-interface-design-color-contrast-content-235b68fbd9a1">3C of Interface Design: Color, Contrast, Content.</a></p><h3>👻 Something completely else</h3><h4>As a bunch of avid problem solvers, we recommend this light read about truly innovative solutions!</h4><p><a href="https://ideas.ted.com/how-to-solve-problems-from-an-inventor-with-200-patents/?utm_campaign=social&amp;utm_medium=referral&amp;utm_source=facebook.com&amp;utm_content=ideas-blog&amp;utm_term=technology">How to solve problems, from an inventor with 200+ patents</a></p><blockquote>Thanks to tuning into this week’s Perfektio Weekly! If you have any questions or suggestions how we could improve these shoot us a message :)</blockquote><blockquote>If you like what you’re seeing, don’t be afraid to give it a clap or two!</blockquote><h4>Follow Perfektio on <a href="https://www.facebook.com/PerfektioOy/">Facebook</a> / <a href="https://twitter.com/perfektio">Twitter</a> / <a href="https://www.instagram.com/weareperfektio/">Instagram</a> 🤖</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=340f6a3ce985" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hack Report: Hack the Law]]></title>
            <link>https://medium.com/@o.savisaari/hack-report-hack-the-law-5edaaf294a64?source=rss-1b1bb018d7f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5edaaf294a64</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[legaltech]]></category>
            <category><![CDATA[legal-services]]></category>
            <dc:creator><![CDATA[Olli Savisaari]]></dc:creator>
            <pubDate>Mon, 13 Nov 2017 11:42:18 GMT</pubDate>
            <atom:updated>2017-11-13T11:57:08.618Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PoseiPae1Il09f6oxutaIA.jpeg" /></figure><h4>Taking legal services to the twenty-first century, building well-performing teams with new members, and having a fun hackathon.</h4><h3>Premise</h3><blockquote>“How to make legal service more approachable?“</blockquote><p>With the right people it is possible to succeed even in impossible situations. We have witnessed this in many hackathons and believe it is the basis for all radical innovation. That is why when we go to hackathons, we are not afraid to include new people into our teams. We know that we can make it work, perform well and bring out everyone’s best capabilities. A good example of how well a collection of hackathon novices and experts can come together and perform excellently (despite lacking the same domain experience), was Hack The Law by Helsinki Legal Tech Lab.</p><p>In this Hack Report I will go through how our team formed, stormed a little, started norming the focus, and performed to win Hack The Law. Like some of you little book worms might have caught on, there is little bit of Tuckman’s theory on group forming in this Hack Report. For the rest of you, who have no idea what I’m talking about: prepare to get educated!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nbpliw_8JYVaRmJsAcif7g.jpeg" /><figcaption>Anna-Maria presenting her initial idea, which sparked our interest.</figcaption></figure><h3>Forming — How not to pitch ideas</h3><blockquote>“Meet your team, us”</blockquote><p>On Friday October 13th me, Felix, and Olli stepped inside the brand new Tiedekulma (Think Corner), which resembles a concrete prison but smells like a lumber mill. We were about to hack the law, together with law students in this weekend-long hackathon. After a long and extensive info session on legal tech, we finally got around to hearing some pre-pitching of ideas and choosing the teams we would want to work with. To be honest, none of the initial ideas sounded that great, so we ended up choosing Anna-Maria, one of the law students, because she was the only one who convinced us with her composure and confidence. After some time our team was also joined by Liis and Katri, who are also studying law. Now, we had a balanced, near perfect team and were ready to start building the best legal service ever.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wlw4qZAc0uE0Wve7H-422Q.jpeg" /><figcaption>Our team name LynxLynx was also the result of a quick storming activity.</figcaption></figure><h3>Storming — Coming up with a lot of bad ideas and, if lucky, even a few good ones</h3><p>The slowest day of hackathons is always Friday. Reaching the correct pace is difficult because you’re unsure of team’s capabilities, hopes, and motivation. To find out what your team is able to achieve and how it wants to do it, you have to storm.</p><p>We started throwing around ideas and different approaches to this broad challenge. When Friday was getting to a close, one of the mentors talked with us and said “you basically have three ideas here. All of them are not going to fly, so choose one.” And so we did.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wOAjZhlh6Ok4xMewZI-TkQ.jpeg" /><figcaption>Post-its, canvases, and broad sheets of paper are the ingredients for effective storming.</figcaption></figure><h3>Norming — The language of co-creation</h3><blockquote>“I understood some of the words like….”</blockquote><p>In order to understand each other and perform, a team has to have norms. This means that it should be clear how you communicate with each other, who does what and so on. In our case, we constantly ran into one slight problem which could have been solved if we had explicitly decided on some norms. This problem was language. At times we would accidentally switch from English to Finnish, and back again once we noticed the problem, which was a bit uncool for one team member.</p><h3>Performing — Pivotal changes before the finish line</h3><blockquote>“I think we just have to be a little bolder”</blockquote><p>If a well-performing team had to described with an object, it would be a clay pot full of cracks and parts glued together. Teams have to run into conflicts in order to refine their ways of working and to build a sustainable way of working. No conflicts means that you’re not challenging each others’ views enough.</p><p>That’s exactly what we did multiple times during the process. About 3 hours before the final presentation, we decided to change one part of the service concept completely, which changed the focus of the the service quite a lot. This decision was not unanimous. It was the result of many questions, convincing arguments, contemplation and a cohesive group effort to create the best service possible.</p><h3>Adjourning — Taking things further</h3><p>Directly after the hack we took a step back and decided to look at the entire field of legal technology a bit better. Will something actually come out of our idea? We don’t know. Legal tech as a field has huge potential but also a lot of work ahead. We will present the service concept again at Reboot Hacks Pitching event in Slush and see where it takes us. Let the adventure begin!</p><h4>About Hack Report</h4><p><em>Hack Report is our way of giving back in the context of hackathons. Hack Reports highlight well crafted hackathons and innovation challenges. They also provide glimpses on how we hack award winning solutions.</em></p><h4>Follow Perfektio on <a href="https://www.facebook.com/PerfektioOy/">Facebook</a> / <a href="https://twitter.com/perfektio">Twitter</a> / <a href="https://www.instagram.com/weareperfektio/">Instagram</a> 👍</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5edaaf294a64" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HOW TO BE THE PERFECT MENTOR AT A HACKATHON?]]></title>
            <link>https://medium.com/@o.savisaari/https-medium-com-perfektio-how-to-be-the-perfect-mentor-at-a-hackathon-709e0ab2d032?source=rss-1b1bb018d7f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/709e0ab2d032</guid>
            <category><![CDATA[mentoring]]></category>
            <category><![CDATA[pitching]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[guide]]></category>
            <dc:creator><![CDATA[Olli Savisaari]]></dc:creator>
            <pubDate>Fri, 20 Oct 2017 05:44:16 GMT</pubDate>
            <atom:updated>2017-10-20T05:44:16.725Z</atom:updated>
            <content:encoded><![CDATA[<h4>A guide to providing meaningful feedback and making the teams work wonders in hackathons.</h4><blockquote><em>It’s Thursday afternoon and you’re sitting at your office, feeling a bit distracted. Your thoughts drift off to the weekend, those two days rest from your otherwise busy life. Except that you’re not getting any rest. You’re going to be working in a whole new environment, with people you’ve never met, on tasks you’ve never seen.</em></blockquote><p>This may be you if you’ve ever been a mentor in a hackathon (or you’re going to be one in the future). Mentoring is the key to achieving the best results from a hackathon — it defines whether you get 10 useless ideas or 10 world changing concepts. Good mentoring is hard but don’t worry, here is (almost) everything you need to be a good mentor!</p><p>I am not going to lay out every single detail in this post. Instead, you will get all the necessary pieces, but at the end of the day, it’s up to you to fill in the blanks. The topics you’re going to see are not rules that you have to follow or else you will fail.</p><p><em>They’re more like guidelines</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wi_CENnzaIo-kkI95V2Qzg.jpeg" /><figcaption>Don’t be afraid to approach hackers. They will tell you if they need privacy.</figcaption></figure><ol><li><strong>Know why you are there</strong></li></ol><p>Many of the most successful projects start with people from different backgrounds. The same applies to hackathons. You need someone who can code and someone who has an eye for the visuals. Too many hackathon teams form around the developers, and sometimes the designers. But, when they start poking at the challenge, there is often a loss of direction and a lack of confidence in the idea. That’s because the most important part of the team is still missing. <em>Every single team should have someone who knows what needs to be built and why.</em></p><p>This is where you come in.</p><p>If the teams don’t have a domain expert from the field, your expertise is required to get the teams on the right track (or pull them back from the wrong one). When you prepare for the hackathon, think about your role in the organisation. What is it that you know better than anyone else? Why were you picked to be one of the mentors? Or, what is it that made you volunteer? Every mentor can give their two cents and each piece of advice is precious to the teams. Remember, usually the teams do not have the required domain knowledge, which is the most important part of a solution. A lot of people can develop stunning products or create beautiful user interfaces, but only few know the challenges and problems of your company.</p><p>So, a hackathon team needs multidisciplinarity. So does the ‘mentoring team’.</p><p><em>Here’s why.</em></p><p>Think back to your role in your organisation. How wide is it? Can you confidently answer detailed questions about technology, business viability, customer segments and sales? These are the topics hackers want to know about, and most often the people in charge of customer service have no expertise in technology, and vice versa. It’s virtually impossible for one or two persons to provide them with a complete understanding of the problem.</p><p>Different viewpoints offer supporting information, but even more importantly, sometimes a single sentence from the right person brings down an entire solution. That’s when learning takes place. That’s why you need a diverse set of mentors.</p><blockquote><em>“To be honest, we could have this done in a backyard shop in Bangladesh.”</em></blockquote><p><strong>2. Be available</strong><br>Since the hackers are going to be working almost 24/7, we expect you to do the same.</p><p>Just kidding.</p><p>But, what is really valuable is the possibility to talk to mentors when problems arise in the development process. That is quite difficult to accomplish, if there are no mentors around. If your company is brave enough to arrange a hackathon, they’re also likely to reserve enough resources and personnel to guarantee the best answers to all kinds of questions (and if they’re not, it’s officially your job now to tell them they should).</p><p><em>What does it mean to be present and how long do should you be there?</em></p><p>There’s no predefined time frame for a good mentor, but most are around from morning-ish until the evening. Whatever your schedule is, it’s a good idea to check in with the teams know before you leave, providing them a chance to ask any questions they may have.</p><p>It’s not enough to be physically in the same environment. A good rule-of-thumb would be to go around the teams one by one at least once a day. Ask what they’re doing, what challenges they might have, and most importantly: how can you help them. Many teams don’t even know what they don’t know, and that’s okay, too. Feel free to challenge their idea, the business model and technology choices they have made. If they’re confident about it, they can justify and explain their choices. If not, at least you have made them rethink, which is incredibly valuable.</p><p>After all, you’re there to help the hackers, and the best way to help them is to make them fail early and often.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1nlDe2avVXr1LV9OJjbVqA.jpeg" /><figcaption>Hackers are sometimes weird. They are not dangerous despite their oddity.</figcaption></figure><p><strong>3. Come in with an open mind</strong><br>Hackathons are all about exploring new products, services and business opportunities. Exploration, by nature, is venturing into the unknown and searching for something new. The only way to successful exploration is by not narrowing down the solution space too much. I mean, if your company already has an existing idea to an existing problem, what do you need a hackathon for? Sometimes the best ideas sound crazy at first, but with a little bit of tweaking they become masterpieces.</p><p>Since you’re going to be mentoring multiple teams, you’re bound to hear a variety of ideas. Your job as a mentor is to bring out the best in all of them and challenge the teams that are not quite there yet. Some teams are focusing on a tiny piece of the problem and others will tell you they are building a spaceship*. In a weekend. You will do both parties a service if you point out the facts early on, when there’s still time to reconsider.</p><p><em>*A figure of speech, unless the hack is all about going to Mars.</em></p><p><strong>4. Have a consensus about what you want from the hackathon</strong><br>There’s nothing quite as challenging as getting mixed signals from different people in the same organization. The teams are leaning on your knowledge and expertise to understand the problem and domain better, so it’s a difficult task to figure out whose opinion weighs more, in case there’s variation.</p><p>In the best scenario, your organization has a clear goal for the hackathon, and both mentors as well as the judges all agree on it. Doesn’t sound like too much to ask? Unfortunately, in too many events this is not the case.</p><p>Hosting a hackathon takes a lot of work. But, there’s a positive side to that as well! The more effort you put into thinking about your organization’s goals and needs for the hackathon, the more value you will gain from the event. If you allow hackers to focus on the right problem, they will give you the right solutions. And that’s where the value comes from.</p><p><strong>5. Place an ‘inside man’<br></strong>I do not mean you should place a spy in each team. What I mean is that when your organization decides who is on the jury, they should consider including one of the mentors.</p><p>A lot happens between the start of a hackathon and the final pitch. Teams form ideas, they pivot ideas, they build mock-ups and some do this multiple times. Although I do believe that good solutions speak for themselves and pitches should be able to stand alone, a mentor can provide a ton of valuable information about the team when it comes to judging.</p><p>As brutal as it sounds, all that matters in hackathons is the final product. But does it? And should it?</p><p>As said, many teams go over multiple iterations of their concept, and sometimes they create a solution at the last minute, throw in some catch phrases and sell it with their killer pitch. The question here is: how thought-out should the solutions be? How bad is it, if there’s no business model? Is it okay if they’re <em>impossible to implement in real life?</em></p><p>I don’t have an answer to these questions, but whoever decides the winner, should. In such cases it’s useful to have someone in the jury who knows what the teams are about and what they’re capable of.</p><p>There is no right or wrong way to be a mentor, as long as you keep this in mind: the purpose of mentors is to expose the underlying hopes, assumptions and knowledge that are not evident to participants.</p><p>The most memorable feedback for me came just moments before our final pitch from one of the mentors, who was also part of the jury. In short, his mindset distinguishes a perfect mentor from the rest:</p><blockquote>“Guys, we really like what you’re doing but, to be honest, we could have this done in a backyard shop in Bangladesh. What is it that makes you unique? That’s what we want to see.”</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=709e0ab2d032" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>