<?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[ice Norge - Medium]]></title>
        <description><![CDATA[ice is a new and upcoming cellular provider that’s set forth to challenge the telecom-duopoly in the Norwegian market. ice has an extreme focus on customers, that’s articulated in a goal of “becoming Norway’s most recommended company”. - Medium]]></description>
        <link>https://medium.com/ice-norge?source=rss----ffe8a1b48a1b---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>ice Norge - Medium</title>
            <link>https://medium.com/ice-norge?source=rss----ffe8a1b48a1b---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:58:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/ice-norge" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Lean analytics with Metric Mondays]]></title>
            <link>https://medium.com/ice-norge/lean-analytics-with-metric-mondays-bcb74ae528a3?source=rss----ffe8a1b48a1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/bcb74ae528a3</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[data-analytics]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Michael Kølleskov Gunnulfsen]]></dc:creator>
            <pubDate>Mon, 26 Apr 2021 06:42:38 GMT</pubDate>
            <atom:updated>2021-04-26T06:42:37.878Z</atom:updated>
            <content:encoded><![CDATA[<h4>Building data-informed product teams</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QxI9Sy7x5a22tOx0" /><figcaption>Photo by <a href="https://unsplash.com/@isaacmsmith?utm_source=medium&amp;utm_medium=referral">Isaac Smith</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In the mobile app team at ice, we aim to work data-informed by making decisions based on data analytics. Every member participates in the decision-making process, and so it’s important that the team is aligned and well-informed on the relevant data. In practice, however, it can be challenging to prioritize time to think about metrics and ideas, when you first and foremost need to work on your dedicated tasks. To improve this we’ve designed a product development process we call “Metric Mondays”. The idea is to have a continuous flow of relevant analytics data fed into the team on a weekly basis and to build and prioritize functionality based on this. By pushing our most important data and metrics into the teams’ Slack channel, the team can align better around our shared goals and purpose. This can lead to improved creativity around ideation, and better focus on what really matters to grow our product. In addition, it is motivating and gives team members a better sense of purpose.</p><h4><strong>Background</strong></h4><p>Our team (called the DCI team) uses the <a href="https://en.wikipedia.org/wiki/OKR">OKR</a> framework to define our business goals. We have decided on some high-level goals and identified the metrics that tell us to what extent we are reaching them. In order to improve our metrics, we need to build better functionality and verify whether the new solutions are affecting our metrics the way we hoped for. Building great functionality can be very difficult, and you are unlikely to be good at it until you’ve gained experience through trial and error. As a product team, it’s important to realize that the <strong>goal is really to learn</strong>, as fast as possible, which ideas stick and what functionality removes the most friction in your customer’s lives. A great way to acquire this learning is through rapid product experimentation.</p><blockquote><em>Product experimentation can be a truly creative process, that involves gathering ideas and running each one as an experiment. This is sometimes referred to as </em><a href="https://growthhackers.com/growth-studies/high-tempo-testing-revives-growthhackers-com-growth"><em>high-tempo testing</em></a><em>, where instead of building one solution per iteration, you build multiple variations and see which ones are more successful.</em></blockquote><p>From the beginning, our goal with the team was to become fully autonomous so that we could reach this level of rapid experimentation. Metrics are essential in this process, as they are the leading indicator for which variation performs better. In addition, the metrics tell us to which degree we are having the impact we aim for in our OKR.</p><p>Lastly, there’s the creative part of working with ideas. We believe that a good way to force positive brainstorming in this context is to be <strong>fed frequently with the results of our experimentation</strong>. A sort of positive reinforcement of our current mission. By getting these metric reminders, we believe each team member will spend more time thinking of new ideas and care more about the success of our product. Seeing the same number on a screen each week should also trigger more growth-minded discussions in the team. Additionally, we see great value in sharing openly our most important metrics with the rest of the company.</p><h4><strong>Metric Mondays</strong></h4><p>The Metric Mondays process can be explained in a single sentence. Each Monday, a specific data report is posted in the teams’ Slack channel with the most important metrics, including the current and previous weeks’ measures, together with our current ongoing experiments. Here’s what it may look like:</p><figure><img alt="Example of a (made up) Metric Mondays report" src="https://cdn-images-1.medium.com/max/1024/1*WY0T6brLvQ7CppNYH6khnQ.png" /></figure><p>Let’s discuss the metrics. The team has identified one primary metric, called our <a href="https://amplitude.com/north-star"><strong>North Star metric</strong></a>. The north star metric alone indicates progress towards the teams’ primary business goal so that everything we decide to build should ultimately impact this metric. We do this by breaking down the north star metric into a set of secondary metrics, called <strong>input metrics</strong>. The north star metric is thus a function of its input metrics, meaning that the inputs should collectively have a substantial impact on the north star. The input metrics are closely tied to functionality in the app, and the team designs experiments to influence them.</p><blockquote>For example, one input metric could be the percentage of users who regularly gift rollover data. In this example, let’s say it’s 16%. We want to increase this metric because we see it as a “positive customer interaction” (our north star). We design and roll out experiments that we believe can increase this metric, and measure the results over time. Once we have enough data to make a statistically significant conclusion, we decide to either change, kill or keep the feature.</blockquote><p>The Metric Monday report shows our current input metrics, north star metric, and current experiments. We believe that being frequently exposed to our metrics this way can give powerful context that help us to better prioritize and ideate when we plan our backlog. The ultimate goal of all this is to learn quickly what actually works, so we can improve our product at a high pace. Many successful tech companies have product teams running similar growth cycles with great results. Here’s a recent tweet from a product owner at a fast-growing mobile-app company:</p><figure><img alt="High tempo testing" src="https://cdn-images-1.medium.com/max/1024/1*6Q7eN_BBZByXMYVt7Yddhw.png" /></figure><h4>Process</h4><p>Each week, we bring the teams’ metrics into a “<a href="https://eleganthack.com/monday-commitments-and-friday-wins/"><em>Monday Commitments</em></a>” meeting. In this meeting, we align on our weekly agenda and look at our current running experiments. We discuss the experiments together with the metric results and decide if we need to make minor adjustments. In addition to the weekly meeting, we hold a “<em>Monthly Metric</em>” meeting once every month. Here, we bring new ideas to the table and prioritize based on what we think will make the biggest impact on our metrics. These ideas are very much shaped/biased by our understanding of the data we get through Metric Mondays.</p><h4>From mercenaries to missionaries</h4><p>It can be interesting to compare this way of working with a traditional conservative siloed organization. In this context, our team would be handed a requirement specification from other parts of the company. Only a year ago, this was to some degree the way we would build our product. Thought leaders in the agile sphere sometimes call the members of <a href="https://svpg.com/missionaries-vs-mercenaries/">such a team “mercenaries</a>”. In the world of Metric Mondays however, every team member is instead in charge of defining that specification based on what they believe is the best way to reach their goals. Using the same lingo, members of such a team are called “<em>missionaries</em>”. We believe that the people sitting closer to a problem, have unique insight, and are more likely to know how to grow the product faster. We also believe that brilliant ideas come from a great understanding of the data and that <strong>knowing which ideas stick is something you learn over time after repeated attempts</strong>. This form of product development is a skill that needs to be trained. Over time, the training is likely to pay off, big time.</p><h4><strong>Learnings and pitfalls</strong></h4><p>There are a few reflections we’ve made around the Metric Mondays process that we think is important to address. Here are some key points:</p><ul><li>Set clear, and measurable goals, early. To be a data-informed team (and run Metric Mondays successfully), it is crucial that the team decides on a single, clear goal. More importantly, this (primary) goal must be <strong>easy to measure</strong> so that the result of building something would be clearly reflected in the metric. Otherwise, we would not be able to know whether building something has a positive or negative impact on our target goal. Once such a goal is clearly defined, the team should come up with a set of smaller input metrics that collectively affects the primary one. This should be done through a team workshop.</li><li><strong>Be aware of false positives/negatives by blindly looking at the Metric Mondays report</strong>. The metrics we post do not tell the whole story, and we need more context to make good decisions. There might be new features from other teams that could impact our numbers, or maybe there have been certain events lately that alter the data, etc. An idea here could be that for the Monthly Metric meeting, one person would be in charge of bringing a report with additional relevant data, to add more context to the Metric Monday numbers.</li><li>Be aware of spending too much time on improving a metric that does not actually affect the global metric (also called local maximums). Sort of, moving the wrong needle. We believe this particularly can become a problem when you are continuously exposed to the same metrics, and can easily get obsessed with local growth.</li><li>Quantitative data alone does not tell the whole story, and we need a deeper qualitative understanding. Optimally, Metric Mondays would include a summary of recent user-research findings discovered through user interviews. We believe there should be a dedicated user-researcher in each user-facing domain, especially when it’s difficult to measure success solely through data.</li></ul><p>We started this journey with the goal of becoming a fully data-informed and autonomous product team. This quickly made us realize the need for a better process around observing and understanding our data. The Metric Mondays process has been a great tool, and just like our product, we’ll continue to iterate on the process itself. Hopefully, some of these learnings can be relevant to others who aim to make their team members data-informed product missionaries.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcb74ae528a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ice-norge/lean-analytics-with-metric-mondays-bcb74ae528a3">Lean analytics with Metric Mondays</a> was originally published in <a href="https://medium.com/ice-norge">ice Norge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Usability Testing from home]]></title>
            <link>https://medium.com/ice-norge/usability-testing-from-home-dfd5cfc79122?source=rss----ffe8a1b48a1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/dfd5cfc79122</guid>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[remote-usability-testing]]></category>
            <dc:creator><![CDATA[Robert Bronkebakken]]></dc:creator>
            <pubDate>Fri, 18 Dec 2020 07:45:11 GMT</pubDate>
            <atom:updated>2020-12-18T07:45:11.153Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to best keep up the Usability Testing working from home?</h4><p><strong>At </strong><a href="http://www.ice.no/"><strong>ice</strong></a><strong>, like most other places, we have found ourselves at our home offices for a prolonged length of time. And despite the pandemic we did more usability testing the last 6 months than we have done in the previous year. What happened?</strong></p><p>Before the pandemic <a href="https://bronkebakken.medium.com/mobile-usability-lab-that-fits-in-a-small-box-f3c609cb1952">we built a brand new Mobile Usability Lab</a>, to be able to use it anywhere according to our way of work. But now, our Mobile Usability Test Lab is collecting dust in a locker back at the office. Like a relic of ancient times, even though it was built just 10 months before all this happened.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fHlZkuxE4QoFh-p3nkF5ow.jpeg" /><figcaption>The ice Mobile Usability Lab</figcaption></figure><p>We buckled up and researched for solutions to deal with the new digital daily life. We found some options we wanted to try. All of them fully digital.</p><h4><strong>Moderated Usability testing</strong></h4><p>This is how we ideally want to conduct our Usability testing, and there were several options we looked at. The one that stood out were the <a href="https://lookback.io/">Lookback</a> solution supported by <a href="https://norstat.no/">Norstat</a>, who also conduct the recruiting of test users for us on a daily basis.</p><figure><img alt="Screenshot from Usability Testing in Lookback" src="https://cdn-images-1.medium.com/max/1024/1*OrTpdg_PqF5GFk8dhAnI6g.jpeg" /><figcaption>Mockup from recorded video in Lookback.</figcaption></figure><p>But that was not where we started off…</p><h4>Unmoderated Usability testing</h4><p>We had a deal with <a href="https://teston.io/no/">Teston</a>, who gave us a free test. We did a trial test of a product we just released. While we were a bit sceptic to this kind of testing, it proved to be a great way to test smaller tasks and flows. Especially testing prototypes, where the test user don’t have to use a lot of test user data, proved to work just perfectly. Keeping in mind we test Mobile first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZDvpqj97GCQs--5oyDpNdQ.jpeg" /><figcaption>Mockup from the recorded videos from Teston.</figcaption></figure><p>The downside is of course that the test user might misunderstand the task given, and we’re not able to correct the user. But that is totally up to the structuring of the questions to make sure the given tasks are crystal clear.</p><h4>So what if I have limited budget?</h4><p>So these two options , <a href="https://lookback.io/">Lookback</a> and <a href="https://teston.io/no/">Teston</a>, were tried and tested, but then we decided that we needed to test a more informal platform to do usability testing on internal newly appointed employees. We were building a quite experimental new way of buying our products, and we wanted to test it on people who were not colored by our way of working yet, and keep the testing in-house and not spill out company secrets.</p><h4>Testing through Teams</h4><p>Yes, it was not streamlined, but i worked fine. We felt we were doing a usability test as much on the Teams structure as we were testing our new product. But we did a lot of interesting findings and found lots to iterate on and improve. It was quite an eyeopening way of structuring our way of testing.</p><h4>Ramp up your user feedback!</h4><p>So if you have a hypotheses then try this out; Trow it first out on your companies newbies. Especially the ones who don’t know the industry.</p><p>Iterate, and then do an unmoderated usability test through <a href="https://teston.io/no/">Teston</a>, <a href="https://maze.design/">Maze</a> or any other platform you could think of, with external testers. What makes <a href="https://teston.io/no/">Teston</a> great is that they also do the recruiting for you, but if you have a base of test users available then <a href="https://maze.design/">Maze</a> might be the way to go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*na_DEdrf35TFC422Aw9KGg.jpeg" /><figcaption>Testing from home has never been easier.</figcaption></figure><p>So two iterations in, you would want to do a moderated standard usability test, right? Get a hold on <a href="https://lookback.io/">Lookback</a>, or talk to your local recruitment partner to see if they have a platform they support.</p><p>Now you get your proper usability test, from your basement, and are able to conduct a proper temperature check on your hypotheses.</p><h4>So the final line is…</h4><p>Don’t settle for doing nothing, there are so many different ways of collecting your user research and testing your hypotheses. So many great digital solutions at hand. It’s all really about your imagination.</p><p>Go get some user insight!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfd5cfc79122" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ice-norge/usability-testing-from-home-dfd5cfc79122">Usability Testing from home</a> was originally published in <a href="https://medium.com/ice-norge">ice Norge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile Usability Lab that fits in a small box]]></title>
            <link>https://medium.com/ice-norge/mobile-usability-lab-that-fits-in-a-small-box-f3c609cb1952?source=rss----ffe8a1b48a1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/f3c609cb1952</guid>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Robert Bronkebakken]]></dc:creator>
            <pubDate>Fri, 18 Dec 2020 07:44:54 GMT</pubDate>
            <atom:updated>2020-12-18T07:44:54.031Z</atom:updated>
            <content:encoded><![CDATA[<h4>Usability Testing within an Activity-based Workplace</h4><p><strong><em>ice</em></strong><em> is a new and upcoming cellular provider that’s set forth to challenge the telecom-duopoly in the Norwegian market through higher efficiency and better quality-of-service by utilizing no-legacy technology, digital customer journeys and with an extreme focus on customers, that’s articulated in a goal of “becoming Norway’s most recommended company”</em></p><figure><img alt="The Usability Testing Lab at ice in a Tool Box." src="https://cdn-images-1.medium.com/max/1024/1*fHlZkuxE4QoFh-p3nkF5ow.jpeg" /><figcaption>The Usability Testing Lab at ice in a Tool Box — ready to go!</figcaption></figure><h4>What is Activity-based Working?</h4><p>Ice absorbed <a href="https://www.wework.com/ideas/worklife/essential-guide-activity-based-working/"><strong><em>Activity-based working</em></strong></a><em> (</em><strong><em>ABW</em></strong><em>)</em> as a way of working in 2017 when moving into new office spaces at Nydalen in Oslo. The office space was designed with the philosophy of “Water Circles”; concentric circles from noisy social areas in the heart of the office to strictly silent zones around the edges.</p><h3>How do you set up a test lab where there is no such thing as a permanent set-up?</h3><p>So how can we make sure that all the stakeholders are able to observe the usability testing within their own time schedule and keep the momentum going? What if there is no observation room available, or the meeting rooms are booked in a way that you are not able to have the same set-up for the entire day?</p><h4>The solution is simpler than you think! (Getting started)</h4><p>As a newcomer to ice and the work culture, one of my first tasks was to set up a usability lab. I collaborated with the other UX designers at ice, and sounded out what they could recommend equipment wise. Just to make sure I didn’t have any equipment biases. I was also watching the culture, the way the communication stream was set up, and just how everyone was extremely busy every day.</p><figure><img alt="Usability Lab equipment used at ice Communication AS, Norway." src="https://cdn-images-1.medium.com/max/1024/1*QE5_Mcam5_4cj0zu2moH2A.jpeg" /><figcaption>The Huddly IQ, a USB-C hub and Mr. Tappy on display.</figcaption></figure><h4>Streaming</h4><p>There is no way around it. A no-brainer, really. And the tool was just there in front of me. Workplace — the Facebook at-work offering. Everyone had access, and the stream is automatically stored if you miss the live stream. The only minor negative with streaming through Workplace is the slight delay in the live stream.</p><p>Also protecting the recorded material in the summary phase of the usability testing was easy to manage with restricted observation groups. Having a set time for the captured material to be available before deleting the recorded stream.</p><figure><img alt="The OBS studio dashboard with connected video and audio devices." src="https://cdn-images-1.medium.com/max/1024/1*kVYY9sZoiIx4dH2yD_RN0g.jpeg" /><figcaption>The OBS studio Dashboard with devices connected.</figcaption></figure><h4>Managing the streaming with OBS studio</h4><p><a href="https://obsproject.com/">OBS studio</a> is a tool I had never used, but which kept popping up during my research. I wanted to give it a try, and it turned out to be quite the tool! Free to use for Mac, Windows and Linux. You can store different set-ups allowing you to switch testing between desktop, mobile or whatever your chosen device is within the session. It’s just a blessed set-up.</p><h4>Capturing the usability testing</h4><p>First of all we need to test on mobile, being a mobile operator and all, and as we work with a mobile first approach. Secondly, we wanted flexibility in regards to serving the user, and making sure that she would be able to complete the tasks she wanted to complete on a desktop computer if that is what she wanted to do. So that meant several devices in play to serve our needs.</p><h4>Capturing the mobile screen</h4><p><a href="https://www.mrtappy.com/">Mr. Tappy</a> was one of the first devices for testing on mobile that came up in the UX stream of conciseness for usability testing. We sought out other solutions as well, but that’s where we ended up. It works quite well, even though the focus is not perfect. But the point is to capture the interaction itself and we can back it up by screen capture as well.</p><figure><img alt="Capturing different screens and the user in OBS studio through Workplace." src="https://cdn-images-1.medium.com/max/1024/1*8Dg0IKSscxxXU6mLd6wUWg.jpeg" /><figcaption>Capturing different screens and the user in OBS studio through Workplace.</figcaption></figure><h4>Capturing the user</h4><p><a href="https://www.huddly.com/conference-cameras/iq/">Huddly IQ</a> was another device we chose for capturing facial expressions of the user and the interaction with the test lead. A quite small camera working wide lens to capture the room and interactions. It enabled us to see the user but also the interaction with the test-lead.</p><p>Tying these two devices in with screen capture and PC-camera, we had a wide range of available angles to wrap up and record the usability testing.</p><h4>What about sound capture?</h4><p>The beauty with Mr. Tappy and the Huddly IQ through OBS studio is that both have internal mics, and can be changed during the session as well. Each room is different, and each user is different, so to be able to optimize the sound through different sources is just top notch.</p><h4>Communicating with the observation room</h4><p><a href="https://slack.com/">Slack</a> is king. It allows us to keep in touch when needed, and get answers to questions that might arise during the process, in case the usability testing crew are not able to answer them.</p><p>This channel is also good for popping in follow-up questions to the conversation happening with the user, whether you are located in the observation room or are elsewhere following the live stream.</p><figure><img alt="Usability Lab technical set-up, from the test itself recorded and streamed to the Observation room and to Workplace." src="https://cdn-images-1.medium.com/max/1024/1*b-5m4ZuRq2G9WmoQw_EFZw.jpeg" /><figcaption>From the Usability Lab the stream goes to all the stakeholders.</figcaption></figure><h3>What did we learn?</h3><h4>Key take-aways from the first test</h4><p>With some tuning and minor trial and error, we sat out to do our first proper usability test with this new setup. Ice had just recently launched a freemium-type subscription for kids, and wanted to test the order process and the self-service handling on the parents. We were able to easily swap between mobile and desktop, but had some issues with the desktop version since we used the same laptop for capturing the test and doing the usability testing. Not ideal.</p><p>We also registered that some users would rather use the desktop than the mobile when having the choice. In hindsight we needed to be more strict and true to the mobile first strategy.</p><p>Having a test-lead to do all the interaction with the user, and a second person in the room to observe, take notes and do all the tech tasks and interaction with the observation room, is very important in test phase of the lab. It allows the Researcher to focus on the user only.</p><h4>Overall take-aways from our set-up</h4><p>So what are our recommendations to you if you are in a similar situation and are looking into setting up a usability lab?</p><p>OBS studio as a base for capturing video and audio is an absolute winner. This set-up gives you loads of alternatives for both what kind of sources you want to capture, but also for where you want to take your stream. Did I mention that you can both stream and record at the same time? And that it’s free?</p><p>Secondly — think economy. You don’t need an expensive camera to catch the user. The Huddly IQ is a great camera, but also expensive. You could probably save lots on you usability lab budget by trying out a much cheeper solution.</p><p>For capturing the interaction with the mobile screen, there are other solutions than Mr. Tappy out there, but we found it to be a reasonably priced solution for our needs. As I mentioned the focus isn’t perfect, but you would want to back it up with screen capture anyway. And if you’re really handy you could actually make your own!</p><p>Having several devices you can swap around for capturing the audio is also a great addition to a flexible set-up. Make sure your chosen video capture devices are able to capture audio as well. Alternatively you could buy a separate audio capture device to place and adjust around the room.</p><p>Last but not least, the equipment is really easy to set up and get ready for usability testing within minutes. It has proved to be really easy to just grab the lab gear and run over to the next booked meeting room, where we’re up and running in no time.</p><p>And when you really know the lab equipment after several tests — you could actually run the usability testing by yourself! We have done that with great success even though it is a bit more stressful caring for both the user AND the set-up. In a high tempo environment where everyone is caught up in tasks, this is a very handy alternative.</p><figure><img alt="The usability lab fits in a small box." src="https://cdn-images-1.medium.com/max/1024/1*fHlZkuxE4QoFh-p3nkF5ow.jpeg" /><figcaption>Usability test lab on the go!</figcaption></figure><h4>…and it all fits in a small box!</h4><p>Our mobile usability lab is really easy to store in our small lockers. Just get your hands on a little tool box and you are all set.</p><p>Good luck :)</p><h3>References</h3><ul><li><a href="https://uxdesign.cc/the-ultimate-guide-to-recording-mobile-user-tests-a-ux-epic-b84dd6d3b16f">The ultimate guide to recording mobile user tests — a UX epic</a></li><li><a href="https://medium.com/deep-work-studio/the-no-bullshit-setup-for-design-sprint-user-interviews-e07cf0815aeb">The No Bullshit setup for Design Sprint User Interviews</a></li><li><a href="https://www.facebook.com/workplace/resources/tech/it-configuration/live-video">Workplace | IT Configuration: Networking</a></li><li><a href="https://www.wework.com/ideas/worklife/essential-guide-activity-based-working/">The essential guide to activity-based working</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3c609cb1952" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ice-norge/mobile-usability-lab-that-fits-in-a-small-box-f3c609cb1952">Mobile Usability Lab that fits in a small box</a> was originally published in <a href="https://medium.com/ice-norge">ice Norge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Helping users choose stronger passwords with known data breaches]]></title>
            <link>https://medium.com/ice-norge/helping-users-choose-stronger-passwords-with-known-data-breaches-9bb36b6c8ea5?source=rss----ffe8a1b48a1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/9bb36b6c8ea5</guid>
            <category><![CDATA[passwords]]></category>
            <category><![CDATA[telecom]]></category>
            <category><![CDATA[haveibeenpwned]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Lars Smeby]]></dc:creator>
            <pubDate>Fri, 03 Apr 2020 06:25:49 GMT</pubDate>
            <atom:updated>2020-04-03T06:25:49.718Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-Y6wa5LXIzuzDOmG" /><figcaption>Photo by <a href="https://unsplash.com/@shaneavery?utm_source=medium&amp;utm_medium=referral">Shane Avery</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong><em>ice</em></strong><em> is a new and upcoming cellular provider that’s set forth to challenge the telecom-duopoly in the Norwegian market through higher efficiency and better quality-of-service by utilizing no-legacy technology, digital customer journeys and with an extreme focus on customers, that’s articulated in a goal of “becoming Norway’s most recommended company”.</em></p><p>Telecom companies are attractive targets for attackers. We have a lot of data about our customers, some of it very sensitive. We’re also targets for <a href="https://en.wikipedia.org/wiki/SIM_swap_scam">SIM swap scams</a>, an attack where a victim’s phone number is transferred to the attacker’s SIM card. It’s needless to say that it’s critical that we protect our customers.</p><h4>The easiest solution</h4><p>When you create a self-service account at ice, either through the ice app or on the web, you’re asked to create a password. Choosing a strong password can be hard, and users tend to go for the easiest solution that passes the password requirements, usually the same password as they use other places. It’s of course recommended to use a <a href="https://en.wikipedia.org/wiki/Password_manager">password manager</a>, but let’s face it, most users don’t. By making the password requirements stricter, “password” becomes “Password”, then “Passw0rd”, and eventually “P@ssw0rd!”. Even though the entropy of the last example is much higher than the first, it’s still easy to guess for both humans and computers. And as of today, it has been seen <em>681 times</em> in known data breaches!</p><p>A <a href="https://digitalguardian.com/blog/uncovering-password-habits-are-users-password-security-habits-improving-infographic">Dashlane analysis</a> from 2015 found that the average user has 90 online accounts. Five years later, it’s probably more. As users tend to reuse their passwords on multiple sites, a data breach on one site will give valid credentials to other sites. Attackers use these lists of valid username and password combinations for what’s called credential stuffing attacks. They run all the combinations against a site’s login and see if they manage to log in with some of them. They usually do.</p><h4>Have I Been Pwned</h4><p>Troy Hunt runs a service called <a href="https://haveibeenpwned.com/">Have I Been Pwned</a> that lets you search for your e-mail address in known data breaches. As of today, the service contains close to <em>10 billion compromised accounts</em>. Most people have probably gotten their account compromised without even knowing it. Have I Been Pwned also lets you <a href="https://haveibeenpwned.com/Passwords">search for a password</a> to see if it has been used in any of the compromised accounts. This service, which contains more than 555 million unique real-world passwords, is what we’ve started using to help users choose better passwords for self-service accounts at ice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-JEPDB_37n_0OCtLH48fGA.png" /><figcaption>Password search at haveibeenpwned.com</figcaption></figure><h4>Looking up the user’s password</h4><p>When a user registers a new account or changes his or her password, we use the API from Have I Been Pwned to look up the password. If the password has been breached, we show a warning, urging the user to choose a different password. We also encourage the user to change the password on other sites if it has been reused. The warning reads:</p><blockquote>“The password you have chosen has previously been leaked in a data breach on a different website and is considered unsafe. We recommend that you choose a different password.”</blockquote><p>There’s also a link, “How do we know?”, that shows more info about data breaches and how we use the API at Have I Been Pwned. To proceed with a breached password, the user must confirm that he or she understands the risk by checking a checkbox.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*17gMg-4dRfYIO1liwenu-w.png" /><figcaption>Registering a new user in the ice app</figcaption></figure><h4>So, you send my password to an external site?</h4><p>No! The API at Have I Been Pwned implements a <a href="https://en.wikipedia.org/wiki/K-anonymity">k-anonymity model</a> that lets us search for a password without the password itself leaving our servers. This works by hashing the password with SHA-1, and then sending the first five characters of the hash to the API. Since changing a single character in the password would create a totally different hash, the first five characters won’t give away any clues about what the entered password might be, if intercepted. The API responds with all password hashes starting with these characters, usually a couple of hundred. If we find the full hash of the password amongst the returned hashes, we show the warning to the user.</p><h4>Educating the users</h4><p>As mentioned earlier, enforcing a strict password policy doesn’t necessary lead to stronger passwords, as users tend to choose predictable passwords that barely meet the requirements. What it definitively leads to, however, is annoyed users. By instead educating the users, trying to explain in a friendly way why their chosen password is insecure, we let the users themselves make the decision of creating a strong password. And does it work? By collecting anonymous statistics on the number of warnings displayed and what the users choose to do, we see that <em>80% of the users that get the warning change their password to something else.</em> That’s a significant share of users!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9bb36b6c8ea5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ice-norge/helping-users-choose-stronger-passwords-with-known-data-breaches-9bb36b6c8ea5">Helping users choose stronger passwords with known data breaches</a> was originally published in <a href="https://medium.com/ice-norge">ice Norge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One emoji that aborted our app-launch; The power of the feedback-loop]]></title>
            <link>https://medium.com/ice-norge/one-emoji-that-aborted-our-app-launch-the-power-of-the-feedback-loop-e2afe69b8b44?source=rss----ffe8a1b48a1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/e2afe69b8b44</guid>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[emoji]]></category>
            <category><![CDATA[user-testing]]></category>
            <dc:creator><![CDATA[Henrik Lexow]]></dc:creator>
            <pubDate>Mon, 18 Nov 2019 18:07:34 GMT</pubDate>
            <atom:updated>2019-11-18T17:55:35.431Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>ice</em></strong><em> is a new and upcoming cellular provider that’s set forth to challenge the telecom-duopoly in the Norwegian market through higher efficiency and better quality-of-service by utilizing no-legacy technology, digital customer journeys and with an extreme focus on customers, that’s articulated in a goal of “becoming Norway’s most recommended company”</em></p><p>Before launching the ice app, we encountered a problem we had not foreseen. Had we not had a feedback-loop, our reputation could have taken a serious hit</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QCFs6QdZyrB4SxuGaUH0TQ.png" /><figcaption>Beta version of the app — here showing the feedback-button</figcaption></figure><p>The ice-app project was initiated after summer 2017 and we prepared to go public around x-mas, with alpha and beta-stages leading up to launch. We decided to incorporate a prominent, “in-app” feedback mechanism to get insight and confidence in our app before launching. The setup was extremely simple; a button with the caption “Your App feedback” that linked to a google-form (ok, so not entirely in-app) which again was hooked up to an IFTTT that piped responses into a slack-channel. Development overhead as low as you can get it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wK2K_bhPuuZnFz1vLIoVaQ.png" /><figcaption>Feedback through Google forms</figcaption></figure><h3>The emoji</h3><p>As a “carrier app” for a carrier that focuses on families, we found it essential that the app functionality not only reflected families’ needs, but was essentially built around ice’s core values of sharing and trust. For this we found that instead of logging into the carrier app with your mobile number, we would have our users register as “self-service” users and through that display the relevant subscriptions. I.e a mother who administers her whole family’s telco-life would after logging in not just see her own subscription, but all subscriptions in her family</p><p>This again posted a problem; how to visually separate the different subscriptions?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGYyd_soBlJ-Q8H1cpvZzA.png" /><figcaption>Not a great visual representation when all the subscriptions look the same</figcaption></figure><p>This was a topic of both Design Sprints and user testing, and we found that the best way was to “stamp” each subscription with a different emoji.</p><p>Which again posted a new problem. Older versions of Android had an extremely limited set of emojis compared to modern OS’, so we decided that we would need a proprietary implementation that would be backwards compatible to Android 4.3.</p><p>Our mentality was always to get the 1.0.0 version out the door as quickly as possible, so we decided that we would leave the proprietary emoji implementation on the back-burner, and move forward with the final beta to prepare for launch. Instead, we decided that we (the app) would select emojis from a “safe” set for each of the subscription the user would see.</p><p>To keep some consistence and to avoid very similar looking emojis, we opted to have the app choose randomly from “animal-emojis”. A fast implementation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_5OvjCllv2m617Dqye1_OA.png" /><figcaption>The ice app today has an emoji selector — here with the animal emojis</figcaption></figure><h3>Alpha and Beta</h3><p>Our alpha testing pool was ice employees, their family and friends. About 60 signed up. We got useful feedback, and no-one mentioned the emojis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oQWOzVKi8rZGaUkvN6MnTQ.png" /><figcaption>Alpha ice app logo</figcaption></figure><p>Our beta testing pool was recruited from ice’s Facebook page, and we had approx 280 live testers. This is where we started to get a broad enough base to actually uncover the issue that would abort our launch</p><h3>Feedback streaming in</h3><p>The feedback-loop worked flawlessly, and we were prioritizing changes that needed to be fixed before launch realtime. The beauty of having the feedback piped to Slack, was that we 1) would get notified and see the feedback live as we were updating and launching new beta versions and 2) could discuss the respective feedback posted directly in the same environment the team members normally would be present and collaborate in</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jLn37-iy_z1U6XyHUKZhFg.png" /><figcaption>In Norwegian; discussions go viral as feedback comes in</figcaption></figure><h3>Abort launch</h3><p>Then, in the mists of packing up for App/Play store releases, this one feedback came in:</p><blockquote>It would be good to remove the pig that is in front of my name. Someone would probably take issue with that<br>- Muhammad</blockquote><p>The whole team went into panic mode. We felt extremely stupid. Ignorant. How could we not have thought about the fact that animals have different meanings for different cultures, even if just as iconography?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eWWOQF5LTwD0rHrNafVzEA.png" /><figcaption>Not always so cute</figcaption></figure><p>After a quick summon of the team, we decided that whatever set of emojis we would try to pivot to, we could not ensure that every emoji in the selected set would be non-offensive to everyone. So we decided to pull the task of implementing the proprietary emoji-selector to the top of the todo-list, halt the launch and get that in.</p><h3>Disaster avoided</h3><p>There is a significant and growing muslim population in Norway, and making a mistake like this could have scarred ice for years to come.</p><p>Luckily, thanks to our customers that were willing to part-take in beta testing coupled with the feedback-loop, we did uncover this potential serious embarrassment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DHK7Ustz6BDTWXWckj0zSg.png" /><figcaption>Emojis help distinguish between different subscriptions</figcaption></figure><p>We did launch a few weeks later than we thought we would prior to pig-emoji. But the launch went great, and nobody complained about pigs.</p><h3>Always ask for user feedback</h3><p>The initial plan was to remove the feedback from the app prior to App/Play store release. Already in the Alpha testing-stage we agreed that we can’t remove it… maybe we could move the feedback-button somewhere less prominent? Though,</p><blockquote>After the pig-incident, the whole team was 100% aligned; the feedback-button stays exactly where it is!</blockquote><p>This feedback-loop has been extremely valuable to ice since the launch of the app; we have gotten a lot of valuable feedback on everything from the UX of the app, to the structure of ice, and has helped us prioritize high-level decisions way outside of the scope of the app.</p><p>The feedback-system has been continuously improved and is no longer a Google form, it’s now very much integrated — and with an opt-in to leave your contact details (GDPR-compliance and all)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8TjBKrtG-1XvyC5SveB5iw.png" /><figcaption>The feedback-form presented to the user is truly in-app today</figcaption></figure><h3>Sunglasses emoji. That’s the one</h3><p>Ok, so you might have wandered which emojis people are actually picking (since we have had the feature of picking emoji since launch). So here is the official ice-emoji-top-20 list as of November 2019:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/1*-pQYphvwzL3t9OFPo_OFvQ.png" /><figcaption>Not one animal in sight!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2afe69b8b44" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ice-norge/one-emoji-that-aborted-our-app-launch-the-power-of-the-feedback-loop-e2afe69b8b44">One emoji that aborted our app-launch; The power of the feedback-loop</a> was originally published in <a href="https://medium.com/ice-norge">ice Norge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How ice incorporated kids in a Design Sprint]]></title>
            <link>https://medium.com/ice-norge/how-ice-incorporated-kids-in-a-design-sprint-4954f1b5d4ce?source=rss----ffe8a1b48a1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/4954f1b5d4ce</guid>
            <category><![CDATA[design-sprint]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[kids]]></category>
            <dc:creator><![CDATA[Henrik Lexow]]></dc:creator>
            <pubDate>Fri, 26 Apr 2019 08:14:46 GMT</pubDate>
            <atom:updated>2019-04-26T08:14:46.524Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>ice</em></strong><em> is a new and upcoming cellular provider that’s set forth to challenge the telecom-duopoly in the Norwegian market through higher efficiency and better quality-of-service by utilizing no-legacy technology, digital customer journeys and with an extreme focus on customers, that’s articulated in a goal of “becoming Norway’s most recommended company”</em></p><p>In Norway, Junior High-students will take part in work-experience projects for a full “work-week” during their senior year to gain experience and understanding of what actual work means (I assume). In <em>ice</em>, we quite often get requests for facilitating student’s “work-weeks”, and I, as the “app-guy”, am ever so often forwarded these requests; “if there is something they can test in the app… or anything else, really…”. The problem has, until now, been that I’ve gotten these requests just days ahead of students arriving, and what could have been an interesting and efficient week for both the student and ice, typically ends up with them playing in our social-room, clean the dish-washer, sit awkwardly looking round the room in a meeting they don’t understand, test the app for about 30 minutes and do other rudimentary tasks. This, I feel, is in itself a problem; is this the way we want to portray how it is to work for such a cool company as ice?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*HWqMGIVAnpC6sY1WirU_OA.png" /><figcaption>The ice-app as it looks today</figcaption></figure><p>As these requests came in, I started thinking about “what if we could plan for proper user-testing focused on students?” or “what if we could do proper interviews to gain deeper insight about what youngsters need from our app?”. If only I could get a notice well ahead of time…</p><p>At the same time, I had realized that we’d been missing important age segments in previous Design Sprints and user tests:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M9WK9t5xvplA40ZGciqxwg.jpeg" /></figure><p>In fact, the youngest to test our app (in a user test) prior to this Sprint, was 20 years old. Do teenagers actually like our app? What could be improved? Which problems can we help them solve? Are teenagers’ problems different than adults’? A lot of questions. I therefore had a clear goal of digging into these questions further, I just didn’t know exactly how — yet</p><h3>Planets aligned</h3><p>I aired my frustration around these challenges with some of my colleagues, and not many weeks later, a message on our message-board ticked in;</p><blockquote>“My 14 y.o. brother-in-law is coming to ice for his ‘work-week’ in a month. Anyone has some useful tasks or ideas for what he can work on?”</blockquote><p>Perfect. I jumped on it, checked my calendar, and to my surprise, it was almost empty for that week. Nothing that couldn’t be shifted around. Planets were aligned, and I replied back: “I’ll make a program for him for the whole week”.</p><p>I immediately started planning for user-testing, different employees who should interview him, and other tasks i thought could be insightful and interesting. As this planning progressed, the week started to more and more take shape of something… something more than just testing and interviews. It started looking like… a Sprint.</p><p>Now checking other relevant peoples’ calendars, I realized that it actually would be possible to do a full-week Design Sprint.</p><blockquote>How cool wouldn’t that be? A Design Sprint with a Sprint-challenge focused at kids, with an expert-kid in the room — for the whole week?</blockquote><p>I went back to my colleague whose 14 y.o brother-in-law was coming in just 4 weeks, whose also been participating in Design Sprints earlier, and asked him if he thought the kid was up for it. I angled my question several ways and repeated it. In Norway, Junior High students typically have 5-hour-ish school days with lots of different activities, both physical and theoretical. What we were talking about here was to bring a kid into one room for a whole week — one of the more intensive types of weeks we have, and expect him to be productive, give insights, learn things, and gain an impression of how cool ice is as a company. Could this be done in a good way, or would it be a dramatic fail?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7kZZpsWTnxdzkcDd13FxAw.jpeg" /><figcaption>Jake Knapp in Oslo October 2018, explaining the different emotions of the week</figcaption></figure><p>Having participated in Jake Knapp’s one-day workshop on Design Sprint facilitation in Oslo last year, combined with having had several different roles in Design Sprints prior, I had acquired enough understanding of how and where to shorten the week. The potential Sprint team members I’d been looking at were all but one experienced in Design Sprints. That helps in shortening. So, I made a plan that didn’t require full days in the Sprint-room everyday. On Monday, before our student had said hi to people we started with a a user-test of him, a task I gave to the app’s PO to complete. Then after lunch, we started the Sprint at noon. Tuesday was also compressed, while Wednesday became a full day (though with some tweaks). Thursday was more intensive for other team members, and Friday we started first interview at 10 a.m.</p><p>For me, the major idea behind Design Sprints, is that we have an inescapable deadline: testers will come on Friday, and we have to have a prototype ready. I figured that, with the setting of having 1) a focus on youth and 2) a youth expert in the room, we should further the “inescapableness” by limiting the people to test on on Friday to… teenagers. Though,</p><blockquote>most teenagers actually go to school on Fridays (!)</blockquote><p>So, I started planning for how to be able to gather a group of five students distributed over a full Friday. And, realizing we had to gather consent form their parents, how to get a guardian’s signature into the flow. Full disclosure; the plan totally blew up (details later), but with part luck, part cleverness and some extra effort, we managed to gather a very good pool of testers in the end. Pewh!</p><h3>Introducing Emil</h3><p>I was mistaken; Emil is not 14 years old, he’s actually “almost 15”. Emil at first glance appears like any typical Norwegian teenager; slender, busty hair, curious, engaged, has a love-hate-relationship with school and can’t sit still. Emil likes to play games, he likes hanging out with friends, he is an avid phone user (which teenager isn’t?), and loves unscrewing things like old computers. At the end of his very first task, the interview mentioned above, my colleague and Emil ended up discussing signaling technology and advantages of packed-switching(!). Yet, Emil does not appear to be something that many Norwegians (teenagers and adults alike) are; he’s not shy and not afraid to speak up and share his thoughts and ideas. Now, that’s a very good start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1cDute5jt9QZPy74wT11hg.jpeg" /><figcaption>Wednesday afternoon: Emil engaged in a discussion on what to storyboard</figcaption></figure><p>My plan prior to Monday, was to have Emil as an expert (like the once you typically would interview on Monday afternoon) in the room throughout the week, while ice-employees were the “real” members. Looking back, I can’t believe my prejudice and my need for this limitation. Emil very quickly became much more than an expert. Actually, he was always a Sprint team member. Luckily, it took me but a few minutes to realize my shortcomings, and the week progressed with Emil as a regular team member.</p><p>One thing I didn’t reveal to Emil though, was that the Sprint was arranged around him having a “work-week” at ice. This, I felt, could have been received as pressure, and I really didn’t want him to feel any stress over this arrangement.</p><h3>Focus at the elbow</h3><p>Last year when participating in Jake’s Design Sprint workshop, I was amazed about his timing (Jake brought no less than three Time-Timers). A one-day workshop where we’re set forth to rush through Monday thru mid-day Wednesday of a Design Sprint — with time for introduction, commentary, questions and “facilitators’ tips and tricks”. Jake spent about 10 minutes of this precious time discussing how to do high-fives.</p><blockquote>“I’ve learned that when doing high-fives, the best result is achieved when both high-fivers are looking at (though, not aiming at) each other elbows” — Jake Knapp</blockquote><p>“Now, go ahead and try it”. “That didn’t sound like real high-fives, come on, lean in a little bit and focus! Give it some thought”. “There’s a very low bar for high-fives today. We shall do them often, and not just only when I remind you”. “Think about when you should do high-fives. Remind each other”. Ok, I’m paraphrasing from memory here, but I was really impressed. It actually worked. I proudly “stole” Jake’s high-five technique and have incorporated it in many different settings. This Design Sprint was no exception. And again, it worked. Yeah, it’s awkward, but think about it; the whole Design Sprint-week is! Doing something little silly, little rewarding, little awkward like this, really can help the energy in the room. And Emil seemed to enjoy it… maybe after a few rounds. By the end of the week, we were all high-five masters, and we apparently needed mastery for Friday!</p><h3>Reward, reward, reward</h3><p>Since we already had locked down the age-range by limiting this in the Sprint challenge, I started one week before the Spint kicked off to recruit youngsters we could use as testers for Friday. As mentioned, most school-aged children apparently go to school on Fridays. This posted a problem; if we could only test after school, we’d probably start 2 pm, earliest. Instead, my plan was to engage with the very nearby High School where we expected that schedules are less compacted, and that there probably would be students that would be available in the morning, and maybe lunch break. In fact, each class’ week-plan is publicly available online, and we could confirm that it would be possible to either get pupils in the morning, or even in the one-hour lunch-break. But High School students only represents the higher end of the range we wanted to test on, so I also engaged with the closest Junior High School, about 1/2 mile down the street. In Norway, Craigslist is not at all used, and any of the similar services are not used by (junior) High School students. Targeted, digital marketing towards children is regulated in Norway, and we wanted to stay clear of any gray zones. So, I needed another approach. For each school, I created a poster looking about like this (translated, localized and cropped for the purpose of this blog-post) and blew it up to A3 (double size of Letter, whatever that is in non-standardized-U.S.-formats) and hanged them on info-boards on both schools:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6S33nJdCclVlGwWAaeY8hg.jpeg" /><figcaption>Fail. Students didn’t get it</figcaption></figure><p>Ok, so a couple points here. First, we chose the equivalent of US $30 because we felt pretty strongly that parents potentially could get upset over a too high reward (i.e $100) for one-hour work for such young people. $30 seems like a pretty decent reward. Second, by Tuesday afternoon, the posters had been up for three school-days, though not yielded any responses from the High School, and only three responses from the Junior High. Was the reward too low, or was there something else?</p><p>We therefore decided to take a break on Wednesday at exactly 11:40 am to walk a few hundred feet due north to intercept the High School students passing out of the school gates aimed at the local shopping center in their lunch break (being neighbors, we’d observed this swarm of students during lunch break often before). We brought A4 (letter)-sized printouts of the same poster and passed them out. The kids didn’t respond to that either, they thought we were selling them something. We changed gear and started crying out “Thirty dollars reward, join us for app-testing”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q2LYY5PBAeMwc8x4V-kPYQ.jpeg" /></figure><p>That helped. A lot. We easily got rid of our 80 copies of the poster this way. It took about 25 minutes. During the Sprint-lunch, I checked the responses, and suddenly we had eight. By mid-day Thursday it had grown to 14. Focus on the reward did help a lot, and $30 was plentiful to get students interested. It was just that they hadn’t gotten the message. Looking back, the poster should probably have looked more like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_QF5bq4-ub7xPMWsiMNw6w.jpeg" /><figcaption>Better. Will try this (if there ever is a) next time</figcaption></figure><p>If I was to do this again, I would have done the exercise of standing outside the school gates, but doing it the week before the Sprint, both outside the High School, and the Junior High School, and hand out copies to students and their parents.</p><h3>Who has a working printer at home these days?</h3><p><em>Not many</em>, I guess</p><p>Working with people under 18 (and specially when video-transmission is involved) requires consent from their parents. In my plan for recruiting teenagers, I’d prepared an info-email and a consent form for parents or guardians to print, fill out and sign. ice’s legal team felt that an email-only consent from parents would not be sufficient, so we went with the approach: Print out, sign and scan or take picture and return to this email address (being mine). All but one of the parents replied that they didn’t have a printer at home, so I asked if the kids could print out at school and bring the paper home for them to sign. This resolved most of the cases, but for now, let’s just say I did put on some miles on my car Thursday night to acquire signatures.</p><h3>What?? Her name is … Paul?</h3><p>As was already evident, my brilliant idea about starting early with recruiting kids for Friday’s test went poof. For many raesons. Another example came from the applicants’ online form to fill in. There were many boys and just a few girls responding. Wanting to have a balance between girls and boys, I tried to secure the few, relevant girls first. <em>Pauline</em> was just outside our main target range in terms of age, but was available in the moring. So, I sent out a text as soon as I had finished laying out the schedule. This was Wednesday evening, and I addressed her properly by her name, Pauline. No response that night. Maybe she’s an early sleeper? Repeated text Thursday morning. Well, she’s at school, right, so she’s probably not engaged with her phone..? Then Thursday afternoon, patience ran out and I called her. I don’t know who was more confused, me or <em>him</em>, but whomever I talked to was definitely not a Pauline. The boy in the other end sounded confused and his manly voice was cracking up in laughter. Further investigation revealed that <em>Paul’s</em> friends had played a prank and submitted the form unbeknownst to him, with most of his data correct, except for the gender and name. Duh, what was I thinking? Kids are kids, and this stuff was bound to happen. <em>ice</em>, being a telco provider, could easily have incorporated a text message verification mechanism or something to that effect, without too much effort. Note taken.</p><p><em>(actual names changed for privacy reasons)</em></p><h3>A bit of luck</h3><p>On Thursday afternoon after the team already had headed home to get a well-deserved rest, I was sitting by the coffee machine with my head in my hands. I didn’t want to let the Sprint-team know the actual status of tomorrow’s pool of user testers, and I was pondering on how to resolve this. In addition to losing the only girl in the pool, another boy had last-minute withdrawn his participation and we were left with only four testers. All boys. I felt this was a fail on my part and, through this screwup, was jeopardizing the whole Sprint. We need <em>five </em>testers the Book says. As I was scrambling through the responses from the posters and hand-outs and checking the available spots to see if I somehow could re-arrange something last minute, a colleague (non Sprint part-taker) from the “App-team” approached me and wandered how the user test recruiting was going. I was baffled at the relevance of the question. She explained that she had a daughter, aged 12, that she assumed would love to join testing. I was very grateful for her approaching me and told her that normally I’d prefer kids that are not children of employees to avoid bias, but since I was left with no girls at this point, I was very happy to take her. Her daughter couldn’t join in the morning hours, so I explained that she’ll have to come in last, which was the only after-school-available spot. She scratched her head and asked, “so, you need more girls? In the morning?” Yes. Please! She said she would check and get back to me. Not an hour later she had not just confirmed her own daughter, she had found a High School student, girl, aged 16, a not-too-close neighbor that was available at 10 am. Thank you! I immediately contacted the girl’s mother, and everything seemed fine, except she didn’t have a printer (!). The damn consent form again. My motivation was at this point extremely high, and (duh, I don’t have a printer at home either) I had to drive to office, print out the form, drive to the girl’s home and get the signature from her mother.</p><p>For those who are keeping tabs; yes, we did end up with six testers (one more than recommended). Given all the uncertainty and the effort to gather a representative pool, I’m quite happy with that, and Friday went along just fine — only a few breaks were shortened a bit.</p><p>At lunchtime Friday, as we were relieved about how things were going and laughing about all the recruitment screwups, a suggestion for a future improvement came up:</p><blockquote>Print the damn consent form on the back of the flyer!</blockquote><p>Yes. Noted.</p><h3>The inescapable deadline</h3><p>Apart from the Thursday deadline to complete a prototype, I had effectively limited the scope of the Sprint by clearly announcing that the testers on Friday will all be teenagers. In normal settings, this limitation is not a good idea, but given that we had secured Emil, and that the logistics of acquiring youth testers for Friday is much more complex and needs more planning than the Sprint allows for, I decided to do it anyway.</p><p>The week progressed pretty much to my (altered) schedule, and except for the chaos surrounding user testing recruitment, I as facilitator did not need to be too strict and remind people about the deadline. We were a team of mostly experienced Design Sprinters, after all.</p><p>I was probably most curious about how Emil would receive the instructions, and if he was willing to follow the methodology. Design Sprits are about learning, and learning is Emil’s primary job, so that came easy to him. Norwegian schools uses a lot of different methodology in the education, not just teachers lecturing, and adoption of new methodology is part of his school day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j8C9yIrNP1lQp-t06E-gwA.jpeg" /><figcaption>Monday afternoon: Expert meet expert. Villen (in red) came in as an expert on Digital Sales and Engagement</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*huhwEdykAES_OAOlAwt5Yg.jpeg" /><figcaption>Crazy 8s. Emil reverted to paleontology when he ran out of ideas</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kJuWxb5NTuCEEy0VCA4bDg.jpeg" /><figcaption>Straw poll: Emil, together with the decision maker, each got two dot-stickers. Difficult choice?</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LBax9FI9gJfIby3gypMnug.jpeg" /><figcaption>Wednesday afternoon: Emil as storyboard artist</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sp2Ho-KKKg5763EKiNbuIA.jpeg" /><figcaption>Thursday: Intensive prototyping</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ax4P3ajm-Q2Pqd9u2ENbuA.jpeg" /><figcaption>Emil acting as tester during the 3 pm Thursday trial run. Will the mocked AR work?</figcaption></figure><h3>High-fives all around</h3><p>Friday 10 am, first tester. Anxiety and excitement in the room as the test was about to start. 10 minutes later, smacks of palms meeting each other were echoing in the room, and relieved laughter was heard. There were a lot high-fives that day. And, as post-it-notes flew up on the white-board, a team-member noted; “I’ve never seen so much green on the board [on a Sprint-Friday] before”. Agreed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UgeAWaXo2VAn7tMuEPQPGA.jpeg" /><figcaption>The team intensely focused on the user test. Will he get it?</figcaption></figure><p>Apart from the fact that the prototype performed extremely well, the open-ended interview-section was time-and-time again super interesting, probably because kids are filter-less, unafraid and typically very open. And it was interesting to see where the different kids put their focus on the open-ended questions. For example, one kid really delved deep into ice’s Business Rules for the various products and how this prototype would affect them(!). Absolutely on the money. We got, what feels like (even though only six youngsters were interviewed), very deep insights into what matters for this age segment, insights ice can utilize in bettering the customer experience way outside of the scope of the prototype, the “long-term goal” and the Sprint questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ThQ-jPpt4lFft0D68SZFlg.jpeg" /><figcaption>The funniest and most insightful things can come out of open-ended questions to kids</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HXUNK0zLuOGCReSVmoYijg.jpeg" /><figcaption>Youngest tester in ice’s history; Valdemar, 11</figcaption></figure><p>By the time the last tester had finished, we’d given ourselves so many high-fives and had shared so much laughter that our palms were sore and we were mentally exhausted. Yet, seeing the results was, as always, extremely gratifying.</p><h3>“We did this Sprint because you were coming”</h3><p>Friday 5 pm. “Was this week different than what you expected it would be?”, I asked Emil. Yes, extremely different. Emil had never heard of, or seen anything like this, and thought it was very cool and a maybe little bit tiring. Check, check and … noted.</p><p>I’ll probably never forget Emil’s expression when I told him that the whole week was designed around him. By this time, he must have realized the amount of man-hours being put into this strange way of working. The surprise on his face was evident. Yet, probably as he thought about the results we just had summed up, a slim, almost insecure smile emerged.</p><p>So, <strong>Emil</strong>; Thanks a lot for <em>your</em> time, for being an integral part of the Sprint-team, and for helping ice’s younger customers to get a better user experience. We really couldn’t have done it without you. We’re gonna miss you here, big guy! I’m really looking forward to telling you about the working product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S9RJDCCpqvccv09wGfOhcw.jpeg" /><figcaption>Thanks!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4954f1b5d4ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ice-norge/how-ice-incorporated-kids-in-a-design-sprint-4954f1b5d4ce">How ice incorporated kids in a Design Sprint</a> was originally published in <a href="https://medium.com/ice-norge">ice Norge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>