<?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 Aoife Johnston on Medium]]></title>
        <description><![CDATA[Stories by Aoife Johnston on Medium]]></description>
        <link>https://medium.com/@aoifej?source=rss-b0d9d46146ce------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sZFbyundu-a4qpQQLzHygg.jpeg</url>
            <title>Stories by Aoife Johnston on Medium</title>
            <link>https://medium.com/@aoifej?source=rss-b0d9d46146ce------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:45:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aoifej/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[Ethical Product Design: Should We Make the Unconscious Conscious?]]></title>
            <link>https://medium.com/seek-blog/ethical-product-design-should-we-make-the-unconscious-conscious-40d46a29efb6?source=rss-b0d9d46146ce------2</link>
            <guid isPermaLink="false">https://medium.com/p/40d46a29efb6</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[cognitive-bias]]></category>
            <dc:creator><![CDATA[Aoife Johnston]]></dc:creator>
            <pubDate>Fri, 20 Apr 2018 04:59:16 GMT</pubDate>
            <atom:updated>2018-12-17T01:31:23.077Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PB7hvgnqjo_7eV6JiAaeOg.png" /></figure><blockquote>“Until you make the unconscious conscious, it will direct your life and you will call it fate.” — Carl Jung</blockquote><p>A lot has been written and discussed about unconscious bias in decision making. There is a <a href="https://www.fastcompany.com/3045899/the-growing-business-of-detecting-unconscious-bias">growing awareness</a> of the biases and mental shortcuts that exist in all of us to enable rapid decision making. These shortcuts reduce the overload of information we process daily into manageable chunks.</p><p>We couldn’t live our lives without our unconscious biases. While they are useful in many aspects of life — such as fast reactions to danger — they are problematic when making hiring decisions. The tendency to see patterns and rely on previous knowledge and stereotypes can result in unconscious bias — mental shortcuts where we make quick judgements and assessments about certain groups of people outside of our own conscious awareness. These biases are shaped by our experiences and by cultural norms, and allow us to filter information and make quick decisions.</p><h4>How unconscious bias hurts recruitment</h4><p>As Australia’s leading employment marketplace, <a href="https://www.seek.com.au/">SEEK</a> helps both candidates to find jobs, and hirers to recruit candidates. Hirers find candidates on SEEK via two main sourcing channels; by applications to their job ads, or by proactively connecting with candidates on SEEK’s <a href="https://talent.seek.com.au/products/talentsearch">Talent Search</a> platform.</p><blockquote>When assessing these candidates, many hirers are time poor and juggling multiple other tasks in addition to recruitment. Modes of thinking and cognitive biases can accelerate but cloud their decision making processes. Instead of slowly and deliberately assessing each candidate, they may spend only a few moments scanning a resume, glancing at details such as name, role title and location.</blockquote><p>In this rapid assessment, they are using what psychologist Daniel Kahneman, winner of the Nobel Prize in behavioural economics called ‘fast thinking.’ While this unconscious ‘fast thinking’ mode is rapid, it is also automatic, irrational and vulnerable to biases — causing errors in judgement. In his book ‘<a href="http://us.macmillan.com/thinkingfastandslow/danielkahneman">Thinking Fast and Slow</a>’, he explores the psychology of judgment and decision-making, exposing the faults and biases of fast thinking, and reveals the pervasive influence of intuitive impressions on our thoughts and behaviour. By contrast, he argues that slow thinking is more conscious — rational, logical and deliberate, and generally leads to better decision making.</p><p>As they use their ‘fast thinking’ mode to assess the list of candidates to determine their suitability for the role, hirers can be vulnerable to similarity bias — the human tendency to perceive people similar to themselves more positively than those who are different. Similarity bias can greatly influence the ability to evaluate candidates effectively. Rather than focusing on the candidate’s merit and capability to do the job, hirers may make unconscious evaluations based on factors such as their gender, ethnicity, age, socio-economic background, educational pedigree etc. They may hire the person they <em>like</em> the best, not necessarily the best person for the job. Left unchecked, similarity bias can lead to the creation of homogenous teams, and perpetuate existing power imbalances, rather than fostering diversity in our companies and teams — which is a <a href="https://hbr.org/2016/11/why-diverse-teams-are-smarter">proven competitive advantage</a>, improving team engagement and <a href="https://www.washingtonpost.com/blogs/she-the-people/wp/2014/11/26/diversity-is-good-why-doesnt-everyone-agree/?utm_term=.ae4eba275353">performance</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yeY3SvvxuU7vOk6w2Ruq7w.jpeg" /></figure><h4><strong>So unconscious bias happens in hiring, but what can we do about it?</strong></h4><blockquote>Many <a href="https://www.weforum.org/agenda/2017/05/job-applications-resume-cv-name-descrimination/">international</a> and <a href="https://economics.com.au/2009/06/17/discrimination-study/">Australian</a> jobseeker studies have shown the impact that a person’s name can make to their success when applying for jobs, as employers can infer both gender and ethnicity from their name — thus opening the door to potential unconscious bias. These studies have shown that despite having equivalent qualifications and experience, job seekers with female or non-anglicised names are significantly less successful than applicants with male or anglicised names.</blockquote><p>The Australian study showed statistically significant differences in callback rates for Jobseekers based on the ethnicity of their name. To get the same number of interviews as an applicant with an Anglo-Saxon name, a Chinese applicant must submit 68% more applications, a Middle Eastern applicant must submit 64% more, an Indigenous applicant must submit 35% more, and an Italian applicant must submit 12% more.</p><p>The simple act of anonymising candidate profiles on SEEK could help reduce this bias, empower hirers to evaluate applicants based on merit rather than fall victim to their unconscious bias implicit in a name, and lead to more opportunities for all jobseekers to have a fair go — regardless of their gender or ethnicity. This technique is called <strong>blind hiring</strong> as it “blinds” demographic-related information about a candidate from the hirer that can lead to bias.</p><p>As experience designers of technology platforms that connect people, we are now faced with a philosophical question and an ethical challenge. Should we optimise the user experience flow, enable ‘fast thinking’ for our hirers, merely make their intended behaviour easier, more efficient and streamlined, without any judgement or interference? Or should we design our platforms for ‘slow thinking’ to encourage more conscious, better decision making by introducing friction to human behaviour which may be harmful or biased in some way? And as Australia’s leading employment marketplace, is it our responsibility to drive equality, fairness, and societal change by combatting these biases, or to non-judgmentally help our users optimise their task— even if that task may be an unconsciously discriminatory hiring process?</p><h4><strong>So, what did we ship?</strong></h4><p>What originated as a hackathon project to ‘shield’ hirers from bias developed into the new ‘Hide Names’ feature in SEEK’s <a href="https://talent.seek.com.au/products/talentsearch">Talent Search</a> platform. This is a simple checkbox that hirers can select to hide candidate names in the search results, helping them focus on merit-based assessment, without unconscious bias clouding their decisions.We decided to focus on the initial reviewing and shortlisting stage of the recruitment process, which is where the majority of unconscious bias occurs — when hirers scan lists of candidates, rapidly evaluating their ability to do the job. We aimed to foster awareness of bias at this stage of the screening process, to educate and empower hirers to overcome their biases via this small but powerful feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YjYicBYIl7EOcNhmkat9XQ.png" /><figcaption>Guard against unconscious bias with SEEK’s ‘hide names’ feature</figcaption></figure><h4>We made 3 important design decisions on the implementation of the feature:</h4><ol><li>We placed the checkbox in a prominent position in the centre of the user flow to achieve optimum visibility.</li><li>We implemented the feature as optional, with user control to switch it on or off (hide or reveal names), in order to balance encouragement of thoughtful behaviour and deliberate decision making with the need for user control.</li><li>We provided user on-boarding and education on the purpose and benefits of using the feature via in-product info, sales training for our customer-facing teams, and further supporting marketing material.</li></ol><p>By de-identifying the candidates, we aimed to encourage hirers to embrace slow thinking — to articulate upfront exactly what’s important to do the job well, and focus their evaluation on these merits, rather than unconsciously assessing the candidates on their gender or ethnicity. We released this feature last week, and 53% of hirers have so far engaged with the ‘Hide Names’ checkbox to try it out. This is an encouraging first step in creating curiosity and growing awareness around unconscious bias in hiring. The feature and supporting material have also sparked conversations and training sessions between SEEK’s sales team and agency recruiters around how they can elevate their sourcing strategies with this tool, and explain diversity benefits to their clients in turn.</p><h4><strong>No silver bullet to bias</strong></h4><p>It’s important to note that both overcoming unconscious bias and improving diversity take a lot of effort, time, and commitment. There is no silver bullet to this multi-faceted and nuanced societal issue. But as SEEK’s product, design and delivery teams, we can consciously make ethical and inclusive product design decisions to balance the interests of both candidates and hirers in SEEK’s employment marketplace. This technology will have increasing influence over our users’ perception, behaviour, and interactions in society.</p><p>For more information on <a href="https://insightsresources.seek.com.au/index.php?action=sitesearch&amp;q=talent+search">Talent Search</a>, and tips on <a href="https://insightsresources.seek.com.au/index.php?action=blogs&amp;form_name=search&amp;searchline=diversity">diversity</a>, <a href="https://insightsresources.seek.com.au/index.php?action=blogs&amp;form_name=search&amp;searchline=unconscious+bias">unconscious bias</a> and <a href="https://insightsresources.seek.com.au/hiring-process">optimising your hiring processes</a>, check out the SEEK <a href="https://insightsresources.seek.com.au/">Insights and resources blog</a>, or contact nlaver@seek.com.au to enquire about SEEK’s unconscious bias training to improve Diversity and Inclusion in your workplace.</p><p>Thanks to <a href="https://medium.com/u/4cabdfb91f84">Evelyn Balfe</a>, Abby Crook, Tim Crook, Michael Isgro and <a href="https://medium.com/u/bc1bb304f93b">Maz penguino</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40d46a29efb6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/seek-blog/ethical-product-design-should-we-make-the-unconscious-conscious-40d46a29efb6">Ethical Product Design: Should We Make the Unconscious Conscious?</a> was originally published in <a href="https://medium.com/seek-blog">SEEK blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 UX Tips To Make Your Site Feel Faster]]></title>
            <link>https://medium.com/seek-blog/3-ux-tips-to-make-your-site-feel-faster-99fe4100c7bd?source=rss-b0d9d46146ce------2</link>
            <guid isPermaLink="false">https://medium.com/p/99fe4100c7bd</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[Aoife Johnston]]></dc:creator>
            <pubDate>Tue, 08 Mar 2016 23:34:36 GMT</pubDate>
            <atom:updated>2021-02-25T01:04:03.571Z</atom:updated>
            <content:encoded><![CDATA[<p>Waiting feels long. Waiting for 1 minute for a web page to load feels a lot longer than a 1-minute snooze after your alarm clock has gone off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*hjY4N7yDJSB43G7Jfa3RGw.png" /></figure><p>Speed and performance are essential parts of the user experience of a digital product. If users perceive a site to be slow or to run sluggishly, they have a <a href="https://www.nngroup.com/articles/website-response-times/">negative experience</a>. Even a small delay in page load can result in a loss of conversions, higher abandonment rates and a negative perception of the site. Speed matters.</p><h4>The problem</h4><p>Here at <a href="https://www.seek.com.au/work-for-seek">seek.com.au</a>, we were trying to improve the speed of SEEK Talent Search, which is a product that allows hirers to search across our database of over 4.5 million profiles to find and connect with candidates and offer them potential employment opportunities. This search product is continually growing in size and complexity, with features like resume parsing and profile enrichment, and a database growing to the tune of 160,000 new profiles every month.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iel34VRL1_ruI4F48BTzfQ.png" /><figcaption>The spinner of death</figcaption></figure><p>This growth however, came at a price. Things were becoming slow. We began hearing complaints about site speed from our users. They weren’t happy. We were hearing their frustrations from our customer service teams, our sales teams, through user research and from internal users of the site.</p><p>Their pain ranged from ‘this <strong>feels</strong> a bit slow, has my search worked? Is this still loading?’ to the more extreme ‘is anything ever going to happen? Will this spinner of death ever end?!’</p><h4>The approach</h4><p>Our goal was to improve <strong>both the</strong> <strong>actual and perceived speed of the site</strong>. While our search engineers worked in the background to improve the actual speed by optimising servers and reducing API query speeds, our UX designers and UI developers tackled the perceived speed on the front end. We wanted to ensure that we improved <strong>our users’ perception of the performance</strong>, because that’s who we’re building for.</p><p>We needed to make the site ‘feel’ faster. We approached improving the perceived performance of the site through UX in 3 different ways, keeping in mind the <a href="https://www.nngroup.com/articles/response-times-3-important-limits/">long-standing HCI research on response time limits from Jakob Nielsen</a>, which are determined by human perceptual abilities.</p><h4>1. Staggered loading</h4><p>Instead of displaying a loading spinner until <em>all</em> elements of the page had loaded (which was taking up to 5 seconds), we implemented <strong>staggered loading</strong> of content on site load. This meant we progressively displayed visual elements of the site sooner for users to focus on while loading was processing in the background — the blurb on what you could do on this page, and the search boxes you could use to do so. This provided distraction and prompted them with a task to cognitively prepare for, so loading didn’t <strong>feel</strong> so long to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*I_wVG6BfvaJxTRjhEDRiuw.png" /><figcaption>Staggered loading order of site elements</figcaption></figure><p>Speed Index (the average time at which visible parts of the page are displayed in the browser window) is the <a href="https://sites.google.com/a/webpagetest.org/docs/using-webpagetest/metrics/speed-index">universally accepted measure of site performance</a>. Under 1 second is the aim, 2 seconds is the point at which user experience is negatively impacted, as users’ attention starts to wander and the perception of dealing with the current task is broken.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*verf1TYl12i-_HAQjySmSw.png" /><figcaption>Comparing loading: New staggered above, old total load below</figcaption></figure><p>By reducing the time taken to provide meaningful visual content to users from 5 to 0.5 seconds, we improved the perceived performance of our site.</p><h4>2. Loading dummy content</h4><p>As users interact with a site, they expect immediate responses to their actions. Clicking a button or running a search should have an immediate response.</p><blockquote><strong>“</strong>0.1 second is about the limit for having the user feel that the system is <strong>reacting instantaneously</strong>, meaning that no special feedback is necessary except to display the result.” Jakob Nielsen</blockquote><p>When a user runs a search on our site, ideally we should show the search results immediately. However, if it’s going to take some time to retrieve these results, we need to give the user immediate feedback that their search has worked, and is progressing. Otherwise, if there is no immediate response, we effectively ‘leave them hanging,’ wondering if the click worked, if the action is happening at all, or if they need to click again.</p><p>As retrieving matching profiles for a search in Talent Search can take over a second, we instantly display placeholder dummy content to the user while waiting for the real profile content to load. This sets user expectation of where the content will appear, and distracts them with something else to look at (more of that cognitive distraction). Animating this content also provided reassuring feedback to users indicating that content is continuing to load in the background.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*_fq07NIA7KEV1bj5twBuaA.png" /><figcaption>Loading dummy content</figcaption></figure><p>By providing this visual response that the search has worked in under 0.1 seconds, we improved another aspect of the site’s perceived performance for our users.</p><h4>3. Asynchronous and optimistic actions</h4><p>When a user clicks on a button to complete an action, we can generally understand their intent. They want this action to happen!</p><p>As often happens on complex sites, all sorts of technical tasks must be completed in the background in order for this task to be completed, which can cause delays. However, the user does not need to know, or care about this. <strong>They just want it to work</strong>. This is a system issue, not a user issue, so we shouldn’t push the problem back onto the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*SDWJr5XV-TpSS4KlVstzyw.jpeg" /></figure><p>Instead of waiting for all tasks to complete before we responded to the user, we redesigned the interaction to give the user immediate positive feedback in the UI that their action has worked. So before we even know if the action has worked, we tell the user that it has. For example, when a user shortlists a candidate profile in Talent Search, rather than waiting for the supporting background tasks to complete, we immediately light up the star icon in the UI, indicating the profile has successfully been shortlisted. Then we keep trying to do it in the background until it <em>really</em> has worked. This is an asynchronous and optimistic action, that assumes a positive outcome.</p><p>In rare cases, the action cannot be completed even after we try numerous times to fix it. In this case, we display an error to the user that their action has not been completed. However, this edge case should not hinder the experience for the majority of users whose actions are completed successfully.</p><p>By giving immediate responses to our users’ actions, rather than forcing them to wait for all background tasks to complete, we further improved the perceived performance of Talent Search.</p><h4>Future performance</h4><p>Following our performance improvements in Talent Search, we have now set a performance baseline and can monitor this carefully to ensure that new features, filters and profiles do not negatively affect this level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r0GqA0v_49HWdxJF_4En2A.png" /></figure><p>Visualising our progress as a team is also key to keeping a user-centred approach to site performance. We are using <a href="http://www.webpagetest.org/">WebPageTest</a><em> </em>to display the daily performance metrics to the team.<em> </em>This visibility creates greater awareness and a shared responsibility amongst the team around performance improvements. Moving forward, we have a shared understanding that collaboration between designers and developers is essential throughout the design process to identify any future potential performance concerns in proposed concepts and wireframes.</p><h4>Conclusion</h4><p>Users don’t like waiting. By making some changes to how your site loads, responds and handles actions, you can help make users perceive that loading times are shorter than they really are, leading them to have a more positive experience on your site.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99fe4100c7bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/seek-blog/3-ux-tips-to-make-your-site-feel-faster-99fe4100c7bd">3 UX Tips To Make Your Site Feel Faster</a> was originally published in <a href="https://medium.com/seek-blog">SEEK blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>