<?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 Vegard Storstad on Medium]]></title>
        <description><![CDATA[Stories by Vegard Storstad on Medium]]></description>
        <link>https://medium.com/@vegardstorstad?source=rss-5a51a42325ee------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CN9GftKSyHEwwpmGJiqx5Q.png</url>
            <title>Stories by Vegard Storstad on Medium</title>
            <link>https://medium.com/@vegardstorstad?source=rss-5a51a42325ee------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:10:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vegardstorstad/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[How FINN made our Tech Strategy]]></title>
            <link>https://medium.com/finn-no/how-finn-made-our-tech-strategy-15a60aaf30f2?source=rss-5a51a42325ee------2</link>
            <guid isPermaLink="false">https://medium.com/p/15a60aaf30f2</guid>
            <category><![CDATA[process]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Vegard Storstad]]></dc:creator>
            <pubDate>Wed, 26 Jun 2019 10:28:09 GMT</pubDate>
            <atom:updated>2019-06-26T20:33:58.461Z</atom:updated>
            <content:encoded><![CDATA[<p>FINN just revamped our plan for how our developers and tech leaders can support the strategic ambitions of Norway’s № 1 and World’s № 20 marketplace company 🔥</p><p>Here we’ll share <strong><em>why</em></strong> we did it, <strong><em>how</em></strong> we included 150+ geeks in the process and <em>the </em><strong><em>final result</em> </strong>we shared within our organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r-DTSlKG-RN5UWiiNy3i9Q.png" /><figcaption>FINN Technology (size illustrated in blue) uses a tech strategy to paint our vision and define common goals. Friends of tech (FINN colleagues, illustrated in yellow) can read the highlights to quickly gain an understanding of how the tech strategy will help FINN achieve our company vision and objectives. Group image from 2018 Chantilly 🇫🇷 kick-off!</figcaption></figure><p>Another strategy, you say? Right, just what the world needs. I’ve worked in businesses that had <strong>no strategy</strong> and I’ve been to places with <strong>too many different strategies</strong> pulling in different directions. FINN is not perfect in this matter, but we’re pretty focused on common goals. And to inspire 400+ colleagues run for shared targets we need a strategy.</p><p>As a developer you hopefully find our current challenges and future visions interesting. As a (tech) manager you should read this piece as one of several approaches to create a strategy.</p><h3>Wait but why?</h3><p>FINN already has a corporate strategy, pointing out compass direction for our business. The FINN Strategy describes our values, social responsibility, growth ambitions, our marketplace verticals, biggest competitors and the relationship to Schibsted. It’s pretty solid, but it doesn’t give many hints to what a strong Norwegian tech organization should do to help.</p><p>With a separate tech strategy we can be more explicit on what we see as our biggest strengths, challenges, vision for the future and which <a href="https://en.wikipedia.org/wiki/Performance_indicator">KPI</a>’s the organization should focus on. We also believe that by going into details on tech and the fact that things change fast, a tech strategy should be revisited 3–4 times a year to give relevant guidance. Is it still valid? <a href="https://www.forbes.com/sites/annlatham/2017/10/29/what-the-heck-is-a-strategy-anyway/">Drink too much company Kool-Aid and you’ll forget that yesterday’s edge is today’s norm and tomorrow’s joke.</a> On the other hand — some choices in tech even outlive corporate strategy turns left and right.</p><p>Last but not least; FINN already had a good tech strategy from 2015. But its goals and visions were pretty much achieved, the description of the surroundings were no longer valid and the ownership and implementation in the organization wasn’t strong enough.</p><h3>The process blueprint</h3><p>Tech management (TLG) decided before summer 2018 to draw up a new tech strategy process and that we wanted a <em>task force</em> approach; getting thoughts from colleagues who wanted to participate. A <em>“TLG back room”</em> approach would be too isolated, and to require every developer to engage in <em>workstreams</em> trickling up and down a hierarchy<em> </em>was also decided against. Some colleagues love a break from building tech, but many also love programming over debating common visions in strategy workshops. We wanted to tap into the mind of the engaged.</p><p>To demystify strategy work and to set expectations for the organization (and ourselves), we shared an ambitious timeline for fall 2018.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A7AThx9Ax3Sj5XpxiqDmrA.png" /><figcaption>Timeline was shared from the beginning. Green marks to show that we were on track, colored dots to connect to already planned meetings, and a sinus showing that we wanted feedback on drafts. Little did we know that Schibsted were to split in two companies in week 38 💣</figcaption></figure><p>Tech management set the scope by brainstorming <strong>13 topics</strong> the tech strategy should deal with:</p><p><em>architecture, legacy, convergence, security &amp; GDPR, infrastructure &amp; scaleability, uptime, innovation, competence, ability to deliver, quality, organization &amp; teams, culture (diversity &amp; behaviour), recruitment &amp; onboarding</em></p><p>Already at this point we challenged developers to spot blank spots, but we found that we were pretty aligned with our organization. We also knew trying to remember 13 topics would end up like <a href="https://en.wikipedia.org/wiki/Kim%27s_Game">Kim’s game</a>, but we trusted the task forces to refine, kill, merge or branch topics through the following weeks. Hopefully to a simpler overall message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CkBs5-Hsx7B_LcAbL7VHrA.png" /><figcaption>Kims game. FINN-version 😇</figcaption></figure><p>13 task forces then dived into their topics, with a few basic principles:</p><ul><li><em>We believe in early distribution and want to </em><strong><em>gather feedback along the way</em></strong></li><li><em>The </em><strong><em>quality of the final delivery</em></strong><em> is crucial to widespread use of the strategy</em></li><li><em>The content must be </em><strong><em>well written</em></strong><em>, </em><strong><em>easy accessible</em></strong><em> and </em><strong><em>look good</em></strong></li><li><em>The strategy must be possible to </em><strong><em>consume from A-Z</em></strong><em>, but we also need to be able to </em><strong><em>refer easily</em></strong><em> to the tech strategy highlights</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DXFH5j6CeS7gspKDdKzx5w.png" /><figcaption>Already from the start, we set format expectations to the final delivery.</figcaption></figure><p>Through the first iteration, we converged 13 topics down to 4 chapters:<em> tech culture, ability to deliver, architecture, infrastructure</em>. A while after a 5th chapter on <em>data</em> was added to emphasize the importance of developing data driven products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-I6aovMmArn2HNCFSWtV-A.png" /></figure><p>During the second iteration we understood the need to cut things even further and establish a simple structure to avoid ambition overload.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uY9MqfIhFbZ1dWFZGNItKg.png" /><figcaption>Each chapter describes current situation (good &amp; bad), draws our vision within the topic, choices to get there (upcoming &amp; taken) and KPI’s where we’ll monitor how we’re on track.</figcaption></figure><h3>The Final Result</h3><p>An eleven pages text document is left forgotten in someone’s Google Drive. But that’s okay, since this mostly served as an internal working document where we gathered what we learned through the strategy process. The document served us well while organizing the input from different streams.</p><p><a href="http://bit.ly/techstrategy-finn">The presentation</a> (38 slides) is now our main tool when presenting FINN Tech Strategy to teams, new hires or to colleagues in other departments trying to figure out what tech is doing to deliver on FINN’s ambitions.</p><p>A single slide (below) is the reference to the main strategy lines, and will hopefully🤞 be used often by colleagues. It anchors FINN’s mission to the 5 top topics where we know tech will play an essential part:</p><p><strong>Increase diversity &amp; fuel engagement</strong> (TECH CULTURE)</p><p><strong>Remove obstacles &amp; collaborate with partners</strong> (ABILITY TO DELIVER)</p><p><strong>Execute on fast changing business using Evolutionary Architecture</strong> (ACHITECTURE)</p><p><strong>Champion tracking &amp; share data</strong> (DATA)</p><p><strong>Move FINN into the cloud</strong> (INFRASTRUCTURE)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DfTtYU6MJ88mnLwfY6_9Cg.png" /><figcaption>The 1-slide version of FINN’s Tech Strategy. To be included in other presentations to remind colleagues on what we’re trying to archive together to help our users. Repeat again and again and again and again ✌️</figcaption></figure><p>By engaging colleagues on one or more of the above, we’ll do just fine. The tech strategy should leave plenty of space for bright talent to figure out <em>what to do</em> and <em>how to do it</em>.</p><h3>Did we succeed?</h3><p>Will the new tech strategy help FINN succeed? It’s hard to validate the value of a strategy, but it points a clear direction on selected topics. Every 6-ish week we’re gathering colleagues’ impression on 4 simple questions on wow we’re doing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-gME7S4Y8W-0dnWwQWtHrw.png" /><figcaption>Launching a new Tech Strategy hopefully helps fellow developers &amp; managers to see where we’re headed, but colleagues also just could have had cake 📈</figcaption></figure><h4>Where did we #fail?</h4><p>I guess it’s not obvious yet, but <a href="https://www.dn.no/kommentar/schibsted/kristin-skogen-lund/kioskvelter-fra-schibsted/2-1-422891">Schibsted splitting out Adevinta</a> was certainly not on the radar when we started. It set us back a few weeks, because TLG had set the split as a №1 priority. It also ment less focus in the strategy on converging with marketplaces outside the Nordics.</p><h3>Now what?</h3><p>The plan going forward is to present our tech strategy to all teams and all new hires. Then it’s all about repeating, reminding and refining the strategy so that it will get traction as the strategic tool it’s meant to be.</p><p>What do you think? What did we neglect in the process or what do you miss from the final result?</p><p>Let us know in the comment section below FINNs mission.</p><blockquote>We help people make smarter choices both for themselves and society. ❤️</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15a60aaf30f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/finn-no/how-finn-made-our-tech-strategy-15a60aaf30f2">How FINN made our Tech Strategy</a> was originally published in <a href="https://medium.com/finn-no">FINN.no Blog – Product, Design, and Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 learnings from Hack Days in FINN]]></title>
            <link>https://medium.com/finn-no/5-learnings-from-hack-days-in-finn-e28e4c78273b?source=rss-5a51a42325ee------2</link>
            <guid isPermaLink="false">https://medium.com/p/e28e4c78273b</guid>
            <category><![CDATA[experimenting]]></category>
            <category><![CDATA[work-culture]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Vegard Storstad]]></dc:creator>
            <pubDate>Thu, 28 Jun 2018 00:00:00 GMT</pubDate>
            <atom:updated>2018-11-28T15:41:02.772Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qLx7v3q4ihpen3T3.jpg" /></figure><p>In <a href="https://www.finn.no/">FINN.no</a>, developers are used to great freedom and great responsibility. Solution design and technology choices are being made on a continuous basis in our teams, and we strive to have all new employees to submit code in production the first day on the job. FINN fills an important role the in Norwegian society, and our passionate developers are every week devoted to build the best marketplace.</p><p>Overall we’re in a pretty good shape, but as a large organization we often see our experts in different domains get dependencies to people, processes or products from different parts of our company. We wanted to see what happened if we made an effort to broaden our horizon and invited everyone to think of sane and insane ideas.</p><p>It worked (obviously, someone would say), so here are 5 learnings from Hack Days in FINN June 7th &amp; 8th 2018 👾</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JxYJkWVb_a2uFr88.jpg" /></figure><h3>Find your Inner Excuse 🧠</h3><p>Taking 150 highly skilled professionals out of daily operation is not necessarily trivial. But it is not very complicated either. In FINN we work to solve high-priority market problems at high speeds, and there is not always room for investigative de-tours with colleagues in other parts of our tech environment.</p><p>This became our excuse:</p><ul><li>Hack Days are about tough ideas, learning, error and breakthroughs</li><li>Hack Days without dependencies let imagination and ambitions run fast, unobstructed and in new lanes</li><li>Hack Days builds stronger team culture</li><li>Hack Days is distributed leadership and responsibility for the individual</li><li>Hack Days gives more innovation than strategy documents</li><li>Hack Days will result in new teams that impresses you</li><li>Hack Days are fun!</li></ul><p>Costly? Possibly. Competence is expensive, but incompetence is more expensive. Besides, we have quite a good conscience since <a href="https://www.digi.no/artikler/dette-er-norges-mest-lonnsomme-it-ansatte/431208">we are profitable</a> (and then so). Did we mention fun?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NVrza2ybfiARc5F1.jpg" /></figure><h3>Create the Best Atmosphere 🤓</h3><p>Hack Days (aka Hackathon, CodeDay, Innovation Days, Challenges) are not new, either in FINN or in other tech companies. In FINN we’ve previously run different concepts, and in recent years different teams have taken local initiatives with great success. The community feeling and the attention it gives internally, however, become much more powerful in a larger format, ergo 150 participants from our tech department.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5b5EU1WvzqN7nZn5.png" /></figure><p>The purpose of the pitch on day 1 is to share with colleagues what you want to achieve, as well as to recruit team members. If you do not have your own idea, hang on to someone else’s plans and make them yours.</p><p>Demo on day 2 is about showing what you’ve achieved, sharing #fails or just telling what you’ve learned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XK4V-QXRsd86a3SX.jpg" /></figure><h3>Make it Something Special ✨</h3><p>Okay, you have people. Management are encouraged to sit on their hands and everyone are excited. We took it up a notch:</p><ul><li>Breakfast in FINN cantine 😍 for all participants</li><li>Inspiration: Thanks to Aslak Borgersrud (journalist, editor, gamer, musician, rapper, etc.) who opened our minds with the talk “<em>Aslak’s complete list of totally useless and too ambitious projects FINN.no should build to secure the future, build The Empire and earn MAD AMOUNTS OF CASH in the years (and decades) ahead</em>”</li><li>Inspiration: Thanks to the Platform &amp; Technology Trends from Schibsted, which contributed to the challenges of AR and developing voice skills for smart speakers</li><li>Black drinks (Coke and coffee from the local café) &amp; snacks</li><li>Dinner in FINN cantine for anyone who can stay past kindergarten and other commitments</li><li>Gadget Budget. We got some Flic.io buttons, 3D-printer filament, Google Homes, Amazon Echos, Philips Hue sets, Arduino &amp; Raspberry Pi starter kits, sensors and misc China merch</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-TY9VOD0m0a7vUPB.jpg" /></figure><h3>Measure the Effect 📈</h3><p>In FINN we are awesome measuring and continuously improving. Understanding the impact of Hack Days, however, is not something that in the short term affects either traffic volume, loyalty of our users, revenue/profit, so the approach this time was (yet another) Google Form.</p><p>We asked 9 questions: Did you attend Hack Days?</p><ul><li>What do you think about the information about Hack Days in advance? 🗣</li><li>What do you think of the lecture by Aslak Borgersrud on Thursday morning? 🎤</li><li>What do you think of the session where the ideas were presented in the form of a pitch from the scene Thursday morning? 📣</li><li>What do you think about the demo Friday afternoon?</li><li>How often should FINN arrange Hack Days? 🗓</li><li>How important are Hack Days to you?</li><li>What’s the most important thing you’re left with from Hack Days?</li><li>What is in your mind ✨The One Thing ✨ that would make Hack Days even better next time?</li></ul><p>67 colleagues answered, and we’ve already applied this feedback in our planning for the next version of Hack Days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cL4UtgL4bxkXG-42.jpg" /></figure><h3>Inspect and Adapt 👟</h3><p>So what are the most obvious learnings?</p><ul><li>An overwhelming overall positive experience 🎉</li><li>Pitch and demo are not in the comfort zone of everyone, but very many liked the way to start and close the event. For keeps.</li><li>Two days go fast! We consider further facilitating that everyone gets even more time to work on their ideas. We can drop inspiration talks (although most people enjoyed the talk), postpone dinner day 1 and maybe push demo a bit.</li><li>The first time (in this format) is always special. That it was an unfamiliar format, unclear what to expect, how shielded one gets to work, and generally the way of things makes it more meaningful to rethink the concept only after some iterations. The format stands.</li><li>Open frames make food planning a little tricky, if you do not have to base on takeaway. With the FINN cantina in the back we are mildly well used, so here we must find better ways to meet the actual need 🌮</li><li>In a company of 450 employees, it is smart to schedule well in advance. Book enough rooms and allow colleagues to make adjustments to other obligations to participate. Hack Days on Thursday &amp; Friday is the perfect end of a week, giving fewer context switches.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8EOqDoSwCIrPw6l-.jpg" /></figure><p>What we built? Here are the ideas that were presented in the demo on Friday, which exploded solidly on time due to high involvement and fast-paced entertainment factor:</p><h3>Top 3 (unpretentious voting with acclamation)</h3><ul><li>Generating 3D room models in VR from 2D architecture plans in real estate classifieds (80 dB)</li><li>“PuseFINN” voice search i Google Home (79,4 dB)</li><li>Jo made a computer game during his work week (79,1 dB)</li></ul><h3>…and some of the other stuff from the demo (not everything was presented on stage)</h3><ul><li>Bombe suitcase game</li><li>Hack on wee-slack</li><li>Voice controlled flight search in FINN Reise</li><li>Arduino ping pong serving</li><li>Reading station for FINN Customer Service</li><li>Augumented Reality-app for FINN Shopping</li><li>FINN orienteering map</li><li>Demoscene programming in C/C++</li><li>How was your day?</li><li>Alexa skill: Route planner in public transport</li><li>Predicate diff between announced price / actual price on real estate ads</li><li>Wi-Fi thermometer</li><li>Raspberry Pi game emulator</li><li>Clojure app for FINN massage booking</li><li>Misc. voice skills for Alexa or Google Home</li><li>NG R&amp;I</li></ul><p>Tags: <a href="http://tech.finn.no/2018/06/28/hack-days-in-finn/tags/">Hack Days</a></p><p><em>Originally published at </em><a href="http://tech.finn.no/2018/06/28/hack-days-in-finn/"><em>tech.finn.no</em></a><em> on June 28, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e28e4c78273b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/finn-no/5-learnings-from-hack-days-in-finn-e28e4c78273b">5 learnings from Hack Days in FINN</a> was originally published in <a href="https://medium.com/finn-no">FINN.no Blog – Product, Design, and Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>