<?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 Abigail Rumsey on Medium]]></title>
        <description><![CDATA[Stories by Abigail Rumsey on Medium]]></description>
        <link>https://medium.com/@abbie2020?source=rss-44cdf82052f8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*aLvW_pEjmvWwTMjHhAEv_g.jpeg</url>
            <title>Stories by Abigail Rumsey on Medium</title>
            <link>https://medium.com/@abbie2020?source=rss-44cdf82052f8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 17:40:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abbie2020/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[Are you using science in your user testing? Here’s how you can start]]></title>
            <link>https://medium.com/waitrose-partners-digital/are-you-using-science-in-your-user-testing-heres-how-you-can-start-29a0b34cf545?source=rss-44cdf82052f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/29a0b34cf545</guid>
            <category><![CDATA[user-experience-research]]></category>
            <category><![CDATA[quantitative-ux-research]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[statistical-analysis]]></category>
            <dc:creator><![CDATA[Abigail Rumsey]]></dc:creator>
            <pubDate>Mon, 04 Apr 2022 14:02:45 GMT</pubDate>
            <atom:updated>2022-04-11T09:23:42.486Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_Vj-6uKYQmwxFYbc" /><figcaption>Photo by <a href="https://unsplash.com/@tsvetoslav?utm_source=medium&amp;utm_medium=referral">Tsvetoslav Hristov</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><em>As user researchers, our ‘quick and dirty’ methodologies sometimes don’t leave the time for doing a scientific analysis and we’re just looking for a ‘good enough’ answer. However, I want to show that it doesn’t always take too much additional effort to get an answer that is more scientifically robust. In this article I will be showcasing how I used a few spreadsheet formulas to analyse the task completion times from two first click tests done in Usability Hub. Let’s head into the world of </em><strong><em>quantitative user experience research</em></strong><em> (or Quant UXR if you’re in a hurry) and see if we can be quick, dirty AND extra nerdy!</em></p><p>Statistics in research is all about <strong>probability</strong> — how likely it is or isn’t that something happened completely randomly. As researchers it is helpful, and sometimes critical, for us to say that our results are not just a coincidence but highly likely to mean something. You might have done first click tests before and said something like “Users took, on average, 7 seconds longer to complete the task using Design B”. However, this doesn’t say whether it was just down to chance that a few users did the task quicker with Design A. A statistical test will tell you how likely it is that the difference between the average times was actually different and not just due to chance.</p><p><strong>First click tests</strong> are an easy place to dive into statistical methods because they are quick to do and you don’t have to do much processing to get the numbers you need out. I often use a first click test to compare how long it takes for users to perform a task between two (or more) designs. I like to use Usability Hub to run first click tests because they make it super easy to recruit participants and you can export the results with one click.</p><p>The type of statistical test that you need to do to compare two separate first click tests is a <strong>two-sample t-test</strong>. This assumes that you have used different participants to test the two different designs. If it was the same participants testing the two designs you would use a <strong>paired t-test</strong>.</p><p>Heads up: further down the page it may start to look complicated but don’t worry it mostly comes down to a couple of formulas that you stick in a spreadsheet, and I’ve shared mine so you can copy them.</p><h3>How to analyse your first click test results</h3><p>First things first, you need the raw data. On Usability Hub that means clicking the ‘Export X results to CSV’ button. Open the CSV file in a spreadsheet and you will see that you have a column showing the task duration for each participant in milliseconds.</p><p>Just a note that you will only want to be measuring the participants who completed the task correctly, i.e. clicked in the right place. If you used Usability Hub and ran a <strong>navigation test</strong> where you created hotspots to show where the right place to click was then the spreadsheet should have ‘hit’ columns that say TRUE for a correct click. If you ran a <strong>first click test</strong>, you have to do extra work to find out which participants clicked in the right place. Hopefully Usability Hub will fix this gaping hole in the data some time soon. In the meantime, <a href="https://bootcamp.uxdesign.cc/how-to-do-detailed-first-click-analysis-on-usabilityhub-data-d72e84304913">a helpful guy called Shane has written all about how you would check whether a click was in the right place or not</a>.</p><p>Back to our statistical analysis… Grab the task duration data for the correct participants from each test and stick it in another sheet. Keep it in milliseconds for now. You are going to be comparing the average time taken to complete the task between the two designs so you will need to work out the average or, to be scientific about it, the mean. The top brains of Quant UXR, Sauro and Lewis, recommend taking something called the <strong>geometric mean</strong> due to time data being skewed (basically humans will never complete a task in the fastest time possible, and some can be extremely slow). I’m sure there’s a formula we can use to calculate the geometric mean but let’s just use the MeasuringU calculator. Paste in your task duration data for each test separately and it will tell you the geometric mean: <a href="https://measuringu.com/calculators/time_intervals/">https://measuringu.com/calculators/time_intervals/</a></p><p>You should now have two geometric means. Count the number of correct participants for each test. Now you can start doing proper statistics!</p><h3>Doing the calculations</h3><p>The formula for a <strong>two sample t-test</strong>, i.e. finding out if there is a significant difference between two averages (where there are two separate groups of participants), is this:</p><figure><img alt="Mathematical formula: t equals open parenthesis x1 minus x2 close parenthesis divided by square root of open parenthesis s1 power 2 divided by n1 close parenthesis plus open parenthesis s2 power 2 divided by n2 close parenthesis" src="https://cdn-images-1.medium.com/max/319/1*vTHdKngDghYO7TTw1zJPNw.png" /></figure><p>where x1 and x2 are <strong>means</strong> from samples 1 and 2, s1 and s2 are <strong>standard deviations</strong> from samples 1 and 2, n1 and n2 are the <strong>sample size</strong> from samples 1 and 2, and t is the <strong>test statistic</strong>.</p><p>This formula just needs to be translated into a spreadsheet formula, which will provide your <strong>t statistic</strong>. My formula in Google Sheets looked like this:</p><p>=(B20-C20)/SQRT((POWER(STDEV(B2:B18), 2)/B22)+(POWER(STDEV(C2:C14), 2)/C22))</p><p>And here’s a Google Sheet that shows it in action so that you can replicate it:</p><p><a href="https://docs.google.com/spreadsheets/d/19YEWQKDlG41wlFW53qAoR9hNi2cGiKuYB4Z51krltL4/edit?usp=sharing">https://docs.google.com/spreadsheets/d/19YEWQKDlG41wlFW53qAoR9hNi2cGiKuYB4Z51krltL4/edit?usp=sharing</a></p><p>Once you’ve got your t statistic you need a <strong>p value</strong> (I know, this is too many letters now). The p value is the most important part as it gives you the probability that the difference between your two tests was due to chance. You want this to be as low as possible but usually below 0.10, or below 0.05 if you want to be more sure. A p value below 0.10 means that there is only a 10% likelihood that the difference between the tests is due to chance, so conversely there is a 90% likelihood that the difference is not due to chance.</p><p>Luckily, there’s a spreadsheet function (TDIST) that you can use to calculate the p value, which is the same in both Google Sheets and Excel. TDIST requires the t statistic, degrees of freedom (the simple version is to add the number of participants in both tests together and take away 2) and tails (for this type of test this is 2).</p><p>This is what it looked like in my sheet:</p><p>=TDIST(B26,(B22+C22–2),2)</p><h3>Reporting the results</h3><p>In my example I got a p value of 0.15, which meant that I could be 15% sure that the difference between my tests was due to chance. In other words it meant that I could only be 85% sure that it was quicker to complete the task using the new design. This is less than the 90% certainty I was aiming for. If I wanted to be more certain I would need to test with more people and run the t test again.</p><p>So, how do we report this?</p><p>In my report, I said:</p><p>“A two-sample t test was used to test whether the difference in time to complete the task between the two designs was statistically significant.</p><p>The t test found that <strong>we can be about 85% sure that it is quicker to complete the task using Version A</strong>. This isn’t a significant difference between Version A and the control because statistical tests usually require at least a 90% confidence.</p><p>Recommended next step: <strong>A/B test the two designs on the live site to gather further data on ease of completing this task</strong>”</p><p>Have a go at following this method the next time that you are comparing first click tests. It may take some time the first time that you’re working it out but soon you’ll be doing stats like a pro! Let me know how you get on in the comments.</p><p>If you are interested in learning more about how you can use statistics to more accurately report on quantitative user data, I highly recommend the book <strong>Quantifying the User Experience</strong> by Jeff Sauro and James R. Lewis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29a0b34cf545" width="1" height="1" alt=""><hr><p><a href="https://medium.com/waitrose-partners-digital/are-you-using-science-in-your-user-testing-heres-how-you-can-start-29a0b34cf545">Are you using science in your user testing? Here’s how you can start</a> was originally published in <a href="https://medium.com/waitrose-partners-digital">Waitrose &amp; Partners Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Running wild with ideas]]></title>
            <link>https://medium.com/waitrose-partners-digital/running-wild-with-ideas-7602f7af32ea?source=rss-44cdf82052f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/7602f7af32ea</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[card-sorting]]></category>
            <category><![CDATA[user-testing]]></category>
            <dc:creator><![CDATA[Abigail Rumsey]]></dc:creator>
            <pubDate>Tue, 31 Aug 2021 09:24:56 GMT</pubDate>
            <atom:updated>2021-08-31T09:24:56.299Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to maximize customer insight using wildcards</h4><figure><img alt="Zebra running on dry ground" src="https://cdn-images-1.medium.com/max/1024/1*U2MDBj1NOyYx7IktpfZZ5A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@studiofabelhaft?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Wilmy van Ulft</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>A vital part of good product design is speaking to real customers to understand what they need from your website or app. At Waitrose we’re lucky to have access to a range of tools that we can use to get insights from our customers. Since the start of the pandemic, our customer research has gone almost fully online and we’ve been using tools such as <a href="https://www.usertesting.com/">UserTesting</a> and <a href="https://www.optimalworkshop.com/">Optimal Workshop</a> to set tasks for our user research panel, which they complete in their own time.</p><p>Our latest research has been determining which features customers would want on the home screen of the <a href="https://apps.apple.com/gb/app/waitrose-partners/id1346064128">Waitrose app</a>. To find out their priorities we carried out a <a href="https://www.optimalworkshop.com/learn/101s/card-sorting/">card sort</a> where participants were instructed to put each card that contained the name of a feature into one of several columns. The columns were labelled from ‘I need this on the home screen’ to ‘I don’t want this on the home screen’.</p><p>In addition to having cards with existing features we also included several wildcards that described features that we could build but don’t currently have in the app. We recorded participants doing this activity so we could hear their thoughts on the cards.</p><p>A wildcard could be reacted to in one of three ways:</p><p>“I LOVE that idea!”,</p><p>“Meh, I’m not bothered either way”,</p><p>or “I HATE that idea!”.</p><p>If lots of customers say they love the idea we’ll do some more research into the best way to create that idea in our app, including producing sketches or prototypes of the idea and testing these with customers. For features that get a “meh” reaction we might do some more research, particularly if we’re confident that it’s a good idea and if we think we could get a better reaction from customers if they see it in practice.</p><blockquote>It’s actually really valuable to get a strong “I HATE that” reaction. As an app designer you learn not to be precious about your ideas and not to take feedback personally! Such a reaction is a good signpost that shows the direction you shouldn’t be taking.</blockquote><p>One of our wildcards was an idea we had that we could show Waitrose Stories like you see at the top of the screen on Instagram (and Twitter for a brief time). We thought this could be a neat way of displaying Waitrose content like recipes and new products. This kind of frequently refreshed content could encourage users to open the app more regularly too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P50OzlpU6vY7NthIkbvFEw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UGID0D2m10BI_Ud5i1rP_A.jpeg" /><figcaption>Instagram has a ‘Stories’ feature that users can share regularly changing content on. Twitter trialled a similar feature called ‘Fleets’ but has since removed this.</figcaption></figure><p>Here are some of the comments that users made when they saw our idea for ‘Stories (like on Instagram)’:</p><blockquote><strong>Non-Waitrose app shopper, aged 47, male: </strong>Stories like on Instagram. Crikey, don’t want that sort of stuff. I’m trying to do a shop, I’m not coming there to read other people’s stories. It’s food shopping, it’s not a film I’m going to watch. I don’t want it to be like social media.</blockquote><blockquote><strong>Waitrose in store customer, aged 48, male:</strong> Stories like on Instagram… I think… boring. Don’t want that.</blockquote><blockquote><strong>Waitrose in store customer, aged 37, female:</strong> Stories like on Instagram? No! I don’t need that while I shop!</blockquote><blockquote><strong>Waitrose in store customer, aged 27, female:</strong> Stories like on Instagram… No, probably don’t want that on there. That seems a bit excessive.</blockquote><blockquote><strong>Waitrose in store customer, aged 31, male:</strong> I don’t want that on the home screen. I don’t want Stories like on Instagram. It seems a bit pointless.</blockquote><blockquote><strong>Waitrose in store customer, aged 25, male:</strong> Stories like on Instagram — definitely not on the home screen. I don’t know why that would be appropriate to have on the Waitrose app. Seems ridiculous for Waitrose to have Stories.</blockquote><blockquote><strong>Waitrose app customer, aged 33, male: </strong>Stories like on Instagram? [scoffs] No! No, no, no, no, no, no, no. A million times no.</blockquote><p>I wasn’t expecting to get such a strong reaction to this suggested feature. I thought participants might say things like “I guess you could have that”. Instead, we found almost all participants in the card sorting activity reacted extremely negatively to the idea.</p><p>Even though the results of this wildcard test were surprising, it was valuable to find this out at such an early stage. It is the kind of feature that could sound attractive to our colleagues: a great opportunity to showcase our high quality content in a new and exciting way. No other supermarkets have anything like it in their apps!</p><p>If we had spent time designing a prototype or, much worse, got our developers to start coding this new feature, we would have wasted a lot of time and money on something that our users do not want. It turns out there’s a reason why no other supermarkets have anything like it!</p><p><strong>Follow us on Medium for updates on what our UX Research team has been up to and what new insights we’ve gained from Waitrose customers.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7602f7af32ea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/waitrose-partners-digital/running-wild-with-ideas-7602f7af32ea">Running wild with ideas</a> was originally published in <a href="https://medium.com/waitrose-partners-digital">Waitrose &amp; Partners Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Innovation is key to winning new union members]]></title>
            <link>https://medium.com/@abbie2020/innovation-is-key-to-winning-new-union-members-75c574d98c0a?source=rss-44cdf82052f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/75c574d98c0a</guid>
            <category><![CDATA[trade-unions]]></category>
            <category><![CDATA[unions]]></category>
            <category><![CDATA[labor]]></category>
            <category><![CDATA[future-of-work]]></category>
            <dc:creator><![CDATA[Abigail Rumsey]]></dc:creator>
            <pubDate>Mon, 03 Apr 2017 14:13:07 GMT</pubDate>
            <atom:updated>2017-04-03T14:13:07.378Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xDKg7sK23Zr3ZguOQ_ZRGA.jpeg" /><figcaption>Young scientists and public sector workers brainstorming at the Prospect YPN Forum</figcaption></figure><p><em>This article was originally posted on the </em><a href="https://www.prospect.org.uk/blog/index/2017/March/28/Innovation-is-key-winning-young-union-members"><em>Prospect blog</em></a><em> following the 2017 TUC Young Workers’ Conference.</em></p><p>The second day of the young workers’ conference in London this weekend was opened by <a href="https://medium.com/u/ed878a0a588d">Antonia Bance</a>, head of campaigns and communications at the TUC. She has been tasked with working out how to make unions relevant to <a href="https://www.tuc.org.uk/LivingForTheWeekend">Britain’s young core workers</a>.</p><p>The TUC, along with an organisation called <a href="http://www.goodinnovation.co.uk/">Good Innovation</a>, has been conducting user research of the type usually associated with developing a new app or website, to find out what young workers need from a union. They used WhatsApp diaries and conducted interviews and found that, despite working in horrendous conditions — including physical fights for work, 24-hour shifts and unflexible rotas — these workers still had not considered the relevance of unions to them.</p><h3>Gareth Hathway on Twitter</h3><p>Many of Wales&#39; workers have no idea about their basic rights https://t.co/1v1DPepbjU</p><h3>Gareth Hathway on Twitter</h3><p>This is reflected in TUC research on young workers. Many young workers are exploited but don&#39;t realise that fact https://t.co/xszMlH9qsc</p><p><a href="https://twitter.com/prospect_ypn">Prospect’s young professionals</a> will be keeping a close eye on the outcomes of this research but I don’t think we should be waiting around until this project has finished.</p><p><a href="https://www.prospect.org.uk/">Prospect</a> represents workers in areas different from the core fields of hospitality, social care and retail that the TUC is looking at and, while we may find common ground, it is possible that we will require a much different strategy to engage young people in our work areas.</p><p>It is clear that innovation is the only way that we will be able to push our trade unions into the 21st century. Yes, we’ve already had 17 years to do this but I don’t think the processes we currently have in place have progressed much from those used in the 1990s.</p><h3>Tom Loosemore on Twitter</h3><p>Digital: Applying the culture, practices, processes &amp;amp; technologies of the Internet-era to respond to people&#39;s raised expectations.</p><p>The use of digital to engage with customers, which is perhaps how we should start to view potential union members, is now something that society expects. We will need to approach this innovation task with open-mindedness — the union of the future may look completely different to the union of the past century that we have grown attached to. We will need to embrace technology, not just with an electronic survey here and there, but in every part of our organising strategy.</p><p>The regular woman on the street is attached to her smartphone and does so much on it: banking; shopping; socialising; reporting crime; navigating the world on public transport, by car or by foot. Unions need to be right in there, too.</p><p>I will be going to <a href="http://2017.render-conf.com//">an IT developers’ conference in Oxford</a> with some of my Prospect colleagues to find out what people working in the IT sector require from a union. These people very much represent what the future of work may look like — remote working, job transience, high technological integration. We will be looking for new ideas for how to connect with this workforce and how we might innovate our union.</p><p><em>Let me know your thoughts on how we can innovate today’s trade unions in the comments below.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75c574d98c0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>