<?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 Chris Callaghan on Medium]]></title>
        <description><![CDATA[Stories by Chris Callaghan on Medium]]></description>
        <link>https://medium.com/@CallaghanDesign?source=rss-53b411b5eb3a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*e8lFtFK6ZI7k-kKx.jpeg</url>
            <title>Stories by Chris Callaghan on Medium</title>
            <link>https://medium.com/@CallaghanDesign?source=rss-53b411b5eb3a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:33:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@CallaghanDesign/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[Design Sprints for Kids: Unlocking the next generation’s creativity]]></title>
            <link>https://medium.com/sprint-stories/sprints-for-kids-unlocking-the-next-generations-creativity-775bd28892af?source=rss-53b411b5eb3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/775bd28892af</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Chris Callaghan]]></dc:creator>
            <pubDate>Mon, 11 Mar 2019 13:31:13 GMT</pubDate>
            <atom:updated>2021-04-27T16:08:50.024Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is a story about my wonderful 7 year old daughter and how she used a GV style design sprint to achieve her Brownies Inventor badge.</em></p><p><em>If you’ve never heard of a GV design sprint, you can learn more about it </em><a href="http://gv.com/sprint"><em>here</em></a><em> or </em><a href="http://amzn.to/1rz0uiv"><em>read the book</em></a><em>.</em></p><p>My daughter Matilda was tasked with completing a Brownie interest badge over her school holidays. With dozens of topics to choose from, I was thrilled when she decided to pursue the Inventor badge — the only problem was, she didn’t know what to invent.</p><p>However, with a little guidance, I knew she could solve her problem.</p><p>Enter the design sprint…</p><h3><strong>Who was on the sprint team?</strong></h3><p>We kept the sprint team light…</p><ul><li>Facilitator — Me; an NN/g &amp; HFI certified UX Director.</li><li>Designer — Matilda; a 7 year old Brownie.</li><li>Test participant — Jack; Matilda’s 18 month old baby brother who was oblivious to the whole thing.</li></ul><h3><strong>What question did you want to answer in your sprint?</strong></h3><p>Inventors are usually pictured as people with pens, pencils, rulers and set-squares. So its no surprise that if you ask a 7 year old to invent something, their first action is likely to grab a pen and start drawing.</p><p>However, without stimulus or prompts, they will very quickly ask <em>“what shall I invent?” —</em> and this is what happened with Matilda. She wanted to invent something, but didn’t know where to start.</p><p>This immediately got me thinking about the design sprint.</p><ol><li>Firstly, I knew we could use the Empathy and Define stages of Design Thinking to create a springboard for an area to investigate.</li><li>Secondly, as Matilda was eager to start designing and making, I needed to maintain her interest, not impose too much theory, and get to the fun ideation stage as quickly as possible.</li></ol><p>The approach I took was to explain…</p><blockquote>There are some steps we can take to help us come up with ideas for inventions.</blockquote><p>Rather than explain the whole design sprint process, I simply told Matilda there were 5 steps and I’d explain each one as we worked through them.</p><h3>1. Starting with empathy</h3><p>We started with a single piece of A4 paper.</p><p>The reason for this is that a single piece of paper provides focus and scope. Focus on the stage at hand, and scope in the sense that only one-piece-of-paper’s worth of effort was required.</p><p>I asked Matilda to take a coloured pen and write the word ‘empathise’ at the top in large letters.</p><p>The first lesson was how to spell ‘empathise’ while the second was to understand what it meant.</p><blockquote>Empathy is when we can understand what it might be like for other people. If we empathise with someone it means we understand how they think and feel about something.</blockquote><p>There are lots of debates about how to define empathy, but for a 7 year old, the above definition worked just fine.</p><p>So I asked Matilda if there’s anything that came to mind and her immediate response related to her 18 month old baby brother who she absolutely adores.</p><p>Matilda wanted to know what it felt like for my wife and I to look after her baby brother Jack.</p><p><em>“That’s perfect”</em> I said, <em>“write it down!”</em></p><p>If we empathise with a 7 year old, we can understand that introducing the concept of a design process is enough to take on, never mind new words, spellings and meanings. So rather than introduce the empathy mapping technique, I simply asked Matilda to think about how my wife and I might think and feel about looking after Jack.</p><p>I asked her to write down some of the words that came to mind, just as we would do on an empathy map.</p><p>While in the empathy phase, I wanted to impart some knowledge about the importance of research. If we were going to design properly, we needed some empirical data.</p><p>I asked Matilda to think about the words she wrote down and to think about what she sees my wife and I do. Recalling this observational data, I asked her to write down <em>why</em> she selected those words.</p><p>It turns out we’re tired and exhausted because we run around the house chasing our little boy to make sure he doesn’t hurt himself… sounds about right!</p><p>The final thing I suggested Matilda do was to conduct a brief interview with the people she was designing for.</p><blockquote>As well as watching people, its also really helpful to talk to people about how they think and feel.</blockquote><p>This was as simple as having Matilda ask my wife what she thinks about Jack running off around the house. My wife’s response being: “I worry when I don’t know where Jack is.”</p><p>And there it was — the start of a problem statement…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VFYAFKXbzPd_mj4o" /></figure><h3>2. Defining the problem</h3><p>Being mindful that Matilda hadn’t drawn or invented anything yet, but had written a whole side of A4, I wanted to keep the next step as light as possible.</p><p>As before, Matilda took a single piece of paper and wrote the heading at the top. Again, we learnt the spelling and meaning before starting the activity.</p><p>I always find the problem definition stage tough, but Matilda had this great insight that my wife and I were tired from running around after Jack and were also worried when he ran out of the room.</p><p>I briefly explained how flipping the problem into a question can help us come up with ideas.</p><p>This step required a leap of faith on Matilda’s part and some conversation to craft the HMW statement. Its this phase where I helped the most with content, but they were all Matilda’s own thoughts and words.</p><p>On reflection, I think a <em>goal</em> &gt; <em>context</em> &gt; <em>benefit</em> model would have helped me communicate. A learning point for next time.</p><p>However, Matilda arrived at her springboard question…</p><blockquote>How might we know where Jack is when he runs around the house so that we don’t have to worry?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*C1yLiPjkbIPc9oD8" /></figure><h3>3. Coming up with ideas</h3><p>Again, we started with a new piece of paper and wrote the word “ideas” at the top.</p><p>As she entered the ideation stage of the design sprint, Matilda now knew what she wanted to invent.</p><p>She wanted to invent something that would let us know where Jack was in the house so that we didn’t have to worry about him.</p><p>As before, I didn’t want to introduce too many methods so avoided ideation techniques. I didn’t want to put any time pressure on Matilda either, so I avoided Crazy8s and similar activities, but instead suggested she come up with 6 different ideas, one per post-it.<strong></strong></p><p>Here’s what she came up with…</p><ol><li>Stop Jack from running off in the first place with an Alexa enabled door. We could tell Alexa to close the door out of the room as Jack headed towards it. (We’ve recently introduced Amazon Echos and Hive lighting into the house, so voice activated things are front of mind which is where I guess this came from)</li><li>If Jack was free to leave the room, we could have a camera in every room which would be connected to our phones so we could see where he was.</li><li>Developing the idea above, Matilda suggested that rather than having a camera in every room, we could put a camera on Jack — using our phones.</li><li>Similar to attaching a phone to Jack, Matilda thought about putting bells on his shoes. That way he’d make a noise when he walked and we’d know where he was.</li><li>Trying to build on the previous idea I said; “that’s interesting, what else could you do with noise?” to which Matilda had the idea of putting bells on a hat rather than shoes.</li><li>Trying to push further, I asked; “what if it wasn’t Jack that made the noise? Could you use noise in another way to know where Jack was?” to which Matilda suggested triggers on each door which would play a different sound so we’d know which room he’d entered.</li></ol><p>Once the post-it notes were created, we talked through them in detail.</p><p>We avoided any critiquing and instead talked about all the fun elements of the ideas, the bits we liked, and how they might work.</p><p>I explained to Matilda that when you work in a group, people will like different ideas.</p><blockquote>One of the things you can do to choose which idea to make, is to have everyone in the group vote for the idea they think is best. This means everyone gets a fair say.</blockquote><p>Matilda and I took a silent vote and both selected the idea where we attach a camera to Jack so we could see where he was.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TSAkSF5A48H6aYx_" /></figure><h3>4. Making a prototype</h3><p>Matilda took another piece of paper, learnt how to spell ‘prototype’, and talked about what it meant before starting the activity.</p><p>We started by talking about the critical elements of the prototype and arrived at the following components.</p><ul><li>The phone that would be strapped to Jack</li><li>A separate phone that we would watch from</li><li>A safe and secure method for attaching the phone to Jack, so he could move freely around the house.</li></ul><p>We had the phones, but Matilda needed to explore ideas for the method by which the phone would be attached to Jack — this was critical for the prototype to be testable.</p><ol><li><strong>String </strong>— Matilda’s first idea was to make a string harness that would go over Jack’s shoulders, around his waist and also around the phone. But this was rejected on the basis of safety and the fact that no one could pin the 18 month old down long enough to be able to strap him up!</li><li><strong>Tape</strong> — Matilda’s next idea was to use masking tape. She thought this would be a faster method to get the phone onto Jack, by sticking the phone directly to his T-shirt. But an early attempt proved this wasn’t feasible.</li><li><strong>A pouch </strong>— Matilda looked back at her ideas board and returned to her original drawing which had a pouch or case that the phone could sit in.</li></ol><p>It was at this point I intervened…</p><blockquote>A prototype is just a way to test an idea, so it doesn’t have to be perfect or look like the final thing. And you don’t have to build everything from scratch either — its ok to take shortcuts.</blockquote><p>This led onto the final idea where Matilda would make a pouch to hold the phone, but use an existing method to attach it to Jack.</p><p>We talked about how some sort of belt would be helpful and Matilda immediately thought of Jack’s backpack.</p><p>A cardboard box, some tape, and a little help with scissors saw Matilda arrive at the prototype.</p><p><em>This method also led to a happier little boy who now didn’t notice what was going on as he concentrated on cooking LEGO in the toy kitchen!</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1QZyJnlm-4TSk6YT" /></figure><h3>5. Testing the prototype</h3><p>The moment of truth.</p><p>As before. We started with a new piece of paper and wrote the word “test” at the top with space to write the results.</p><p>My wife’s phone was put in the holder Matilda made, and it was threaded onto the backpack’s belt. We initiated FaceTime and then put the backpack on Jack.</p><p>In the end we opted for the receiver to be an iPad so that we had a larger view as well as allowing me to take photos on my phone.</p><p>Everything was ready, and off Jack went!!</p><p>Although I enjoyed every minute I spent with Matilda in the 1 hour Design Sprint, this was by far the most rewarding stage.</p><p>I got to see my little girl in fits of laughter, with huge proud smiles of achievement on her face and giggling as she herself ran around the house with the iPad shrieking…</p><p>“Jack’s in the playroom, playing with the kitchen!”…</p><p>“Now he’s got his lightsaber!”… “Daddy, Jack’s got the lightsaber!”</p><p>“Now he’s spotted a bird outside!”… “I can hear him saying hello birdie!”</p><p>“Mummy, mummy, don’t worry, Jack’s in the playroom. He’s near the chalkboard now!”</p><p><strong>In my eyes, thats a massive win!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Aa30kutJTbeYn2lY" /></figure><h3>Things that worked well</h3><p>For a first run at a design sprint for kids, most of the approach and methods seemed to work well.</p><p>In particular…</p><ul><li>The use of single sheet of A4 paper helped to constrain effort and time as well as setup the activity. I also felt that if Matilda got bored or didn’t like a stage, she knew it would only be 10 minutes of work before we moved on.</li><li>Tackling the project in one go as a loose one hour design sprint worked well and front loading the first 15 minutes with writing to make way for drawing and making was the correct thing to do too.</li><li>During the ideation stage, the little prompts I gave seemed to encourage and help rather than give answers, so the activity definitely needs facilitating.</li></ul><h3>Things I’d change</h3><p>There’d be a few things I’d change next time.</p><ol><li>I’d like to see less writing and more kinaesthetic learning in the empathy phase. Eagerness to capture my daughter’s attention and dive straight into the sprint meant I failed to think about how we could build out proper observational and interview activities for that first phase.</li><li>I had to intervene a few times during the ideation phase to help Matilda develop her ideas. Similar to the empathy phase, I think there’s some light touch methods that could be used here. I’d remove the time pressure but perhaps think about random input, stimulus or storyboarding. It might have been nice to have Matilda generate a name for each of her ideas too.</li><li>I think the Define stage needs some thought as it very much centred around a conversation. What I needed was a simple technique to get us to the problem statement; something around <em>goal</em>-<em>context</em>-<em>benefit</em> perhaps.</li></ol><h3>Call to action</h3><p>If there’s a call to action to this post then it’s this…</p><p>Please, please, please try running a design sprint with your children. Run them with your young nephews and nieces, with the classes you teach, in the after school clubs you support. Try using design sprints for homework, school competitions and more.</p><p>I genuinely believe design thinking can unlock our children’s imagination and prepare them for their future world which will demand critical thinking, collaboration and creativity.</p><p>And please let me know how you get on! (Contact details below)</p><h3>Final note</h3><p>If you decide to post or re-share this please credit my wonderful Matilda and her very patient little brother Jack — it was all their work!</p><p><strong>Chris Callaghan</strong> is a UX and Optimisation specialist based in Manchester UK, nearing two decades of experience across user research, usability, testing and persuasive design. Chris is one of the few people in the world to be certified by both Nielsen Norman Group (UX Master) and Human Factors International (CUA). <a href="https://www.linkedin.com/in/chriscallaghan/">Connect with Chris on LinkedIn</a> or follow him on Twitter <a href="https://twitter.com/CallaghanDesign">@CallaghanDesign</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=775bd28892af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sprint-stories/sprints-for-kids-unlocking-the-next-generations-creativity-775bd28892af">Design Sprints for Kids: Unlocking the next generation’s creativity</a> was originally published in <a href="https://medium.com/sprint-stories">Sprint Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Heatmaps: 5 ways you could be screwing them up]]></title>
            <link>https://uxdesign.cc/heatmaps-5-ways-you-could-be-screwing-them-up-9fb645d6ecf0?source=rss-53b411b5eb3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fb645d6ecf0</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[heatmap]]></category>
            <category><![CDATA[conversion-optimization]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Chris Callaghan]]></dc:creator>
            <pubDate>Sun, 12 Aug 2018 21:11:10 GMT</pubDate>
            <atom:updated>2021-04-27T16:09:24.503Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YHM8bm9QvfCEAwrzDUymnQ.png" /></figure><p>Click maps, scroll maps, move maps… these are quick and easy methods for understanding on-page user behaviour. All you need to do is select from one of the many tools available, drop a tag onto your website, set-up which pages to record and then watch the colourful heatmaps generate. So simple, you can’t get it wrong… or can you?</p><p>Here’s 5 things you need to consider when using such tools.</p><h3>1. Sample size</h3><p>The whole point of a heatmap is to take away the noise of numerical data and provide a simple-to-understand visual.</p><p>However, many people are blinded by the pretty rainbow like blobs and fail to remember that once the numerical data is taken away or hidden, the heatmap no longer communicates the size of the data set, and therefore the context or validity of the information presented. This can be particularly dangerous when analysing, distributing or communicating results — does the blob represent 500 of the 100,000 visitors to the page that month, or 50,000 of the page visitors that month? Who can tell?</p><p>The point here is to not be swayed by the pretty visual and to treat data collection in a similar way to other behavioural quantitative data. Make it representative.</p><blockquote><a href="https://ctt.ac/tIcr1">Use a representative sample size when heatmapping a page — don’t just default to your bucket of 2,000 credits.</a></blockquote><p>Some tools have smaller pre-defined buckets while other tools will let you crank up the size of the sample. One gotcha here though. If you’re planning on viewing clicks as a confetti map (x-y points) and not just a heatmap (blobs), be mindful that a large number of plotted data points can make a confetti map difficult to interpret.</p><h3>2. Sample period</h3><p>In addition to sample size, the sample period is definitely worth considering.</p><p>Many tools operate by collecting a sample of the first 1,000 or 2,000 visits and then stop once they’ve hit the target.</p><p>Think about this; if you start your data collection on Monday morning and you hit your 1,000 target by the end of the day or even by the Friday, will the heatmap represent weekday/weekend trends and month-start/month-end trends? Quick answer; No, it won’t.</p><p>You may have payday visitors who interact differently at the end of the month compared to the start of the month, or you may have a B2B business where Monday activity is completely different to Friday activity. Your sample period needs to consider this.</p><blockquote><a href="https://ctt.ac/2c6x3">Consider your data collection period when heatmapping — don’t just stop once your first 2,000 credits have been used up.</a></blockquote><p>Some tools will just use up credits in sequence while other tools will collect from every other or every N+5 visitor for example. Start by looking at your web page analytics to determine the size of the sample required, and how you’ll cut it during the sample period. Or consider multiple recordings, perhaps a weekdays recording and a weekend recording if appropriate for your business.</p><h3>3. IP blocking</h3><p>One thing I regularly see with organisations who are new to all-in-one analytics tools and the heatmaps they generate is that they like to peek. And they like to peek early and often. They also like to infer early and often. And this is a problem.</p><p>Peeking can be particularly problematic when you’re recording a low traffic page, are unaware of the sample size issues detailed above, and you have a number of highly curious colleagues who like to check in.</p><p>I’ve seen a number of cases before where someone is wanting rationale for why a blob appeared on a particular element, only for me to find out that the click recording had only been running for a couple of days, and most of the clicks were made by the person requesting the insight, and their colleagues.</p><blockquote><a href="https://ctt.ac/99PvY">When heatmapping, make sure the relevant IPs are blocked from the recording tool so that you, your colleagues, and any third party agencies aren’t polluting the data sample.</a></blockquote><p>The lesson here is to make sure all necessary IPs are blocked from the recording tool so that the sample isn’t polluted by people checking in on the page in question — this is particularly common when people are wanting to see surveys or polls in the live environment on a page which is also recording clicks.</p><h3>4. Traffic type</h3><p>Most tools will allow you to target a device, but also consider whether your heatmap will allow you to view data by new or returning visitor.</p><p>When looking at accounts, profiles, sign-ins, sign-ups, special offer banners, seasonal campaigns etc, it may be important to know how different visitors interact. Depending on whether they are a new visitor or perhaps more familiar returning visitor, the heatmap may give you different insight.</p><p>It might be that new visitors favour one type of information, but returning visitors come back to the site for a different type of information. How would you be able to tell?</p><p>Here’s an example. A B2B website might show some low heat on an account sign-in element suggesting little usage, but if you segmented the heatmap by new and returning visitors, you might find that the heat increases significantly for returning visitors who tend to sign-in to view their accounts and order tracking. It could actually be their number one feature which was made to look unused by the greater percentage of new visitors incorporated into the heatmap.</p><blockquote><a href="https://ctt.ac/Wcfx5">Be careful grouping new and returning visitors into the same heatmap — if segmented, the heatmap may show very different results</a></blockquote><p>Some heatmapping tools allow you to segment by new and returning visitors while others will not. By using advanced segments in Google Analytics you may be able to determine whether behaviour is different enough to warrant a dedicated heatmapping tool over an all-in-one analytics tool.</p><h3>5. Traffic source</h3><p>Finally, are you considering the source and therefore the quality and intent of the traffic represented in your heatmap?</p><p>Visitors arriving directly might have different needs to visitors who arrive via organic or paid search. Similarly, visitors arriving from a social campaign will have different motivations and may demonstrate on-page behaviour unique to that source.</p><p>It’s worth thinking about. Are your heatmaps giving you this segmented view of the data or are they just lumping all visitors together into a pretty visual of the average visitor? Remember, designing for everyone is designing for no one.</p><blockquote><a href="https://ctt.ac/cfNdK">Understand that your heatmap may show the average visitor, and not visitors segmented by source or intent — that might mean you miss a whole bunch of insight and make some wrong decisions</a></blockquote><p><strong>Chris Callaghan</strong> is a UX and Optimisation specialist based in Manchester UK, nearing two decades of experience across user research, usability, testing and persuasive design. Chris is one of the few people in the world to be certified by both Nielsen Norman Group (UX Master) and Human Factors International (CUA). <a href="https://www.linkedin.com/in/chriscallaghan/">Connect with Chris on LinkedIn</a> or follow him on Twitter <a href="https://twitter.com/CallaghanDesign">@CallaghanDesign</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fb645d6ecf0" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/heatmaps-5-ways-you-could-be-screwing-them-up-9fb645d6ecf0">Heatmaps: 5 ways you could be screwing them up</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Left or Right?]]></title>
            <link>https://medium.com/@CallaghanDesign/left-or-right-824aee5f96c9?source=rss-53b411b5eb3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/824aee5f96c9</guid>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Chris Callaghan]]></dc:creator>
            <pubDate>Thu, 07 Nov 2013 18:43:09 GMT</pubDate>
            <atom:updated>2015-10-08T12:17:36.895Z</atom:updated>
            <content:encoded><![CDATA[<h4>Using the Gutenberg principle to decide layout and increase conversion</h4><p>I was recently asked to spend a couple of hours providing a top line review of one of our clients’ websites to identify any ‘quick wins’. Without access to analytics or time and budget for testing, this was very much an ‘Expert Review’ based on best practice i.e. “what does the UXer think about this?”</p><p>During the review, I believe I discovered an opportunity to increase the conversion of a sign up page through layout alone.</p><p>The page in question was extremely lightweight, simply containing an emotive image, a basic form consisting of a few fields, and a submit button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/409/1*f-ATAqLIuvezB47CELJTJg.png" /><figcaption>The page in question, with navigation, header and footer. The page layout consists of a simple form to the left of the screen and an emotive image on the right.</figcaption></figure><p>After correcting a few usability issues in the form, I was left with the question as to whether the layout was correct; should the form appear on the left and the image on the right (as it currently does), or should the image be on the left and the form on the right?</p><p>Now, if I wasn&#39;t a User Experience Designer, I imagine I may simply have a subjective opinion of which <em>looks </em>best. As a creative or web designer with years of experience, I may have a gut feeling or instinct as to which <em>feels </em>best; I may even turn to PhotoShop to explore what the design looks like if the two elements (form and image) were reversed. If I were a web developer, I guess I’d just alter a few lines of code and make the <em>decision in the browser — </em>but that’s a blog post for another day.</p><p>However, as a User Experience designer interested in psychology, neuroscience, and human-computer interaction, I am able to turn to the science of how we read screens to make an informed decision about layout — and this is why I love UX.</p><p>In this particular scenario, I believe we can use the Gutenberg principle to understand the reading gravity of the page and ultimately determine that a reversed layout is likely to be more effective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/409/1*eIFSD6ZjgzI84yuCc9-XNQ.png" /><figcaption>The revised layout with the emotive image on the left and the form on the right.</figcaption></figure><p>The Gutenberg principle tells us that we scan <em>evenly distributed homogeneous information</em> through four quadrants, starting top left in the primary optical area, moving to the top right (the strong fallow area), to the bottom left (the weak fallow area) and finally to the bottom right — the terminal area.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/409/1*prv8HIQs4WRIp4PMTJux7w.png" /></figure><p>This principle was brought about from the way in which we read columns of <em>evenly distributed </em>text from the days of newspapers. But the layout of the page in question clearly isn&#39;t a block of evenly distributed text.</p><blockquote>However, whilst the emotive image, visual hierarchy, and colour are all effecting the reading pattern, I still believe the underlying principle of reading gravity from top left to bottom right is still applicable.</blockquote><p>On a neuroscience note (why not?) the primitive part of our brain that deals with the easier and faster system one thinking, really favours emotive imagery over complex system two thinking stuff (such as reading and working out.) This means we can make an educated guess that the user will focus on the image first, which we know is true from numerous heat mapping studies.</p><p>It just so happens that in my revised design, the emotive region of the screen (the image) now appears in the primary optical area of the Gutenberg quadrant. This means we are now gently guiding users into the page, where they are most likely to be looking, and appealing to the emotive part of the brain <em>before </em>asking them to exert effort and switch over to system two thinking to read and operate the form.</p><p>I propose that in the current design, due to the Gutenberg principle, it will be more uncomfortable for the user (and more difficult) to get their attention away from the emotive image on the right, back to the form on the left — it is for this reason, that I believe the revised layout will be more effective.</p><blockquote><a href="https://twitter.com/intent/tweet?text=%22We%20first%20prime%20the%20emotive%20part%20of%20the%20brain%20%26%20then%20deliver%20the%20CTA%20in%20the%20terminal%20area%22%20-%20%40CallaghanDesign%20http%3A%2F%2Fbit.ly%2F1QalCSN&amp;source=clicktotweet&amp;related=clicktotweet">Using the image on the left and the form on the right, we can first prime the emotive part of the brain, and then deliver the call to action in the terminal area.</a></blockquote><p>Found this useful?</p><p>Please ❤ <strong>Recommend </strong>for others to see.</p><p>Thank you : )</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=824aee5f96c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Higher or Lower?]]></title>
            <link>https://medium.com/@CallaghanDesign/higher-or-lower-32be0a299d32?source=rss-53b411b5eb3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/32be0a299d32</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Chris Callaghan]]></dc:creator>
            <pubDate>Wed, 30 Oct 2013 00:17:41 GMT</pubDate>
            <atom:updated>2016-11-08T21:52:52.961Z</atom:updated>
            <content:encoded><![CDATA[<h4>Making sense of usability findings with criteria based severity ratings</h4><p>Having completed a number of broad usability labs over the last couple of months, I&#39;ve had the opportunity to refine many of my processes, one of which is the logging and analysis of <strong>lots</strong> of usability issues.</p><p>Back in the day when I first started out usability testing, it quickly dawned on me that simply spotting a user having difficulty, logging it as an issue, and then later rating it as <em>high</em>, <em>medium</em> or <em>low</em> just wasn&#39;t good enough.</p><p>From the outset, the rating mechanism was completely subjective, and while the difference between <em>high</em> and <em>low</em> wasn&#39;t that debatable, why an issue was classed as <em>medium</em> and not <em>high</em> or <em>low</em> was.</p><p>As I received my usability lab training from the Nielsen Norman Group, I turned to Nielsen for his approach to <a href="http://www.nngroup.com/articles/how-to-rate-the-severity-of-usability-problems/">severity ratings for usability problems</a>.</p><h4>Nielsen’s severity rating scale</h4><p>“In order to facilitate prioritizing and decision making”, Nielsen suggests the following rating scale to classify usability findings:</p><ol><li>Not a usability issue</li><li><strong>Cosmetic issue:</strong> <em>the fix being</em> a <em>nice to have</em></li><li><strong>Minor usability issue:</strong><em> low priority fix</em></li><li><strong>Major usability issue:</strong> <em>high priority fix</em></li><li><strong>Usability catastrophe:</strong><em> imperative to fix before system release</em></li></ol><p>On reflection, this scale didn&#39;t offer anything beyond the original <em>high</em>, <em>medium</em> and <em>low</em> scale I was trying to replace. Points 1 and 2 were essentially a don’t bother option, <em>catastrophe</em> became my new <em>high</em> and <em>major </em>became my new <em>medium</em>.</p><p>I wanted to confidently report why I had classified an issue as <em>medium</em> and not as <em>high</em> or <em>low</em>, so I dug a little deeper.</p><h4>Nielsen’s definition of a usability issue</h4><p>Turning back to Nielsen, I knew that he defined a usability issue as being a combination of three factors.</p><ol><li>The frequency with which the problem occurs</li><li>The impact of the problem if it occurs</li><li>The persistence of the problem</li></ol><p>I was already recording frequency and impact in my Heuristic Evaluations, so adding a persistence column and updating my final score formula wasn&#39;t going to be any trouble.</p><p>The problem was, I was still going to use a <em>low</em>, <em>medium </em>and <em>high</em> rating for each of the three components. I was still facing the same problem, but making it more complicated.</p><h4>Discovering a criteria based approach</h4><p>After some further research I discovered an article by <a href="https://twitter.com/baekdal">@baekdal</a> who shared the same concerns, but proposed an alternative method to <a href="http://www.baekdal.com/insights/usability-severity-rating">usability severity rating</a> developed on the back of software testers’ rating scales.</p><p>What I liked about Baekdal’s severity rating scale was that it had a clear criteria based approach which significantly reduced the amount of subjectivity (and time) involved in rating an issue. A third party could essentially review the usability log and understand why an issue was rated in a particular way.</p><ol><li>Not an issue</li><li><strong>Minor: </strong><em>Cosmetic issues, spelling issues, non-critical workflow issues</em></li><li><strong>Serious:</strong> <em>Normal status for an issue</em></li><li><strong>Major:</strong> <em>Loss of functionality, problematic impact on a person’s workflow</em></li><li><strong>Critical:</strong> <em>System crashes, workflow breakdown, complete loss of focus for a specific task, loss of information</em></li><li><strong>Fatal:</strong> <em>Blocker, issue prevents further use</em></li></ol><h3>My approach to severity rating</h3><p>Whilst I can’t take any credit for Baekdal’s approach which I did adopt, I can add a number of enhancements that I&#39;ve implemented based on years of using it in the field.</p><h4>Customise the criteria to your system</h4><p>Firstly, ensure you build on the criteria, personalising it to the domain in which the system in question operates.</p><p>For example, when testing a medical software application, it would make sense to add the criterion “incorrect information is presented” to the <em>fatal </em>rating if it has the possibility to impact human life. However, incorrect information for a financial application might be <em>critical</em>, and for hobbyist supplier website might only be <em>major</em>.</p><p>In some instances, you may want to further remove subjectivity. For example, if the system crashes and prevents further use, is that <em>critical </em>or <em>fatal</em>?</p><p>If you’re testing a website which crashes, yet the user can recover by reloading the site, will you <em>ever </em>be able to reach a fatal classification?</p><p>However, for a kiosk software application where the user is unable to perform a software or hardware reboot, fatal is pretty much fatal.</p><p>You may even want to tie in moderator assistance to some of the criteria to help with your classification. <em>Major </em>might include “requires some assistance from the moderator” and <em>critical </em>might include “cannot continue without assistance from the moderator.”</p><p>The key is to define and agree your criteria before starting the severity rating process and make it work for you.</p><blockquote>Aim to arrive at a clear checklist where there’s no debate… “if <strong>this</strong><em> </em>happened, then the issue has to be classed as <strong>that</strong>.”</blockquote><h4>Be client friendly</h4><p>If you decide to agree and define criteria without your client, it would be advisable to consider the terminology used for the five shortcuts (<em>minor</em>, <em>serious</em>, <em>major</em>, <em>critical </em>and <em>fatal</em>) and whether they are suitable.</p><p>For example, reporting back that you encountered two “fatal” issues could be alarming for some clients or a bit melodramatic for others.</p><h4>Make everything serious first</h4><p>One micro-process I have is to first classify everything as <em>serious;</em> this being the normal status for an issue. I then check against the criteria, finding reasons to classify it as something else.</p><h4>Record frequency</h4><p>When recording the severity rating, ensure you record the frequency with which issues occur across the lab.</p><p>For example, if I’m analysing a lab of say five participants, I will create a spreadsheet for each participant and chronologically line item the individual issues. I time-stamp when they occurred in the session and assign the issue a severity rating based on my domain specific criteria.</p><p>When done, I create a master spreadsheet which pulls in all the findings from the individual participant spreadsheets. I remove duplicates, each time adding a +1 to the frequency column.</p><p>This way, I arrive at a single log of all usability issues from the day, with visibility of their frequency, and an appropriate severity rating for each.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*e4qWBgZCRB-kiIKfMvnWIw.jpeg" /><figcaption>Master log combining issues from multiple participant sessions</figcaption></figure><h4>Quick analysis</h4><p>Finally, from the master spreadsheet, I order the data by the frequency column from highest to lowest. I then secondary sort the data by the severity rating, again, highest to lowest.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*rTIYBh0Lrr-uH-d3HXvZEw.jpeg" /><figcaption>Master log ordered by frequency of most severe issues. The top half of the list shows recurring issues, while the bottom half shows edge cases by severity</figcaption></figure><p>At this point you will be presented with line items in the order of the most frequently occurring highest rated issues —<strong> these are the guys you’ll want to have a look at first. </strong>The single instance, but high severity issues may be your edge cases and should be investigated further.</p><h4>That’s all folks</h4><p>This concludes my tips and experiences of severity rating in a bid to stop playing “higher or lower” — a guessing game which shouldn&#39;t really have a place in usability test analysis.</p><p>If there’s one take-away…</p><blockquote><em>Define specific and mutually exclusive domain-related criteria to arrive at an unambiguous and quick to use rating system</em>.</blockquote><p>Found this useful?</p><p>Please ❤ <strong>Recommend</strong> for others to see.</p><p>Thank you : )</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32be0a299d32" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>