<?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 Ryan Connaughton on Medium]]></title>
        <description><![CDATA[Stories by Ryan Connaughton on Medium]]></description>
        <link>https://medium.com/@ryanconnaughton?source=rss-a0b35e034a38------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jVn6gTs3sfQ-hvv9IA8lRQ.jpeg</url>
            <title>Stories by Ryan Connaughton on Medium</title>
            <link>https://medium.com/@ryanconnaughton?source=rss-a0b35e034a38------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:14:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ryanconnaughton/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[Task/Reward Experiment: UX Case Study for Findmypast]]></title>
            <link>https://medium.com/@ryanconnaughton/task-reward-experiment-ux-case-study-for-findmypast-152a40c9755e?source=rss-a0b35e034a38------2</link>
            <guid isPermaLink="false">https://medium.com/p/152a40c9755e</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ryan Connaughton]]></dc:creator>
            <pubDate>Sat, 18 Aug 2018 13:26:22 GMT</pubDate>
            <atom:updated>2019-02-27T12:13:36.636Z</atom:updated>
            <content:encoded><![CDATA[<h4><a href="http://www.findmypast.co.uk/">www.findmypast.co.uk</a></h4><h3>Introductory Context</h3><p>Findmypast is a family history web-based product. You can primarily do three things on said website:</p><ol><li>Search a collection of 8 billion+ records for your British &amp; Irish ancestors</li><li>Build your family tree which in turn generates <strong>‘Hints’</strong> of possible ancestor record matches</li><li>Combine 1 &amp; 2 to make discoveries and build a picture of who your ancestors were</li></ol><p>Now, in the case of this experiment, we’ll be focusing on the user journey of number 2, building your family tree. In order to give you better context before going through my approach, here’s what the current journey looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WDa2ZvIqjUpfSIbgeqQ7fQ.jpeg" /><figcaption>Old journey</figcaption></figure><h3>Problem Statement &amp; Goal(s)</h3><p>First things first, we needed to frame the problem and define our goals. In order to do that, I gathered a group of longstanding ‘specialists’ within the business who had appropriate deep-seated knowledge in different areas and disciplines — the outcome of which can be read below:</p><blockquote>Our tree product is intended to acquire new <strong>beginner users within their first session.</strong></blockquote><blockquote>We have observed that our tree product journey is <strong>overly-complex </strong>and is at present largely <strong>suited towards intermediate users.</strong> This, we believe, is causing people less familiar to family history to <strong>drop off in high numbers.</strong></blockquote><blockquote>How might we improve our tree product to better<strong> onboard</strong> and <strong>retain beginner users </strong>resulting in <strong>higher conversion/paid subscriptions?</strong></blockquote><p>Our deadline for this was just two weeks so we had to move quickly.</p><h3>Defining The Users</h3><p>The next step was to bring the appropriate teams up to speed of what it means to be a ‘beginner hobbyist’. Below you can find the pre-defined user profiles that we were working with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5uXrSMOV-6Ck5d_A-52B_Q.jpeg" /><figcaption>Pre-defined User profile Canvas based off of extensive research (user pains/gains etc.)</figcaption></figure><p>It’s worth mentioning also that at this point in time, I had been leading on the UX of the tree journey for some time and had already conducted 30+ user interviews and tests previously. This helped better guide my decision making on this project while also consulting the analytics team regarding any quantitive data questions we had.</p><h3>Solution Ideation Workshop</h3><p>With the scene set, I gathered a mixed-disciplined in-house team to a meeting room where I facilitated a design studio workshop — this is essentially a process to generate and bounce many diverse ideas off of each of the participants extremely quickly while also building shared understanding and acquiring stakeholder ‘buy-in’.</p><p>I made it clear to the group that the goal of this workshop was not necessarily to create a single, final solution. Rather, they are simply helping to refine the overall design direction that will continue to be explored after the design studio workshop is over.</p><h4>Design studio workshop format</h4><p>The format for this was 3 short rounds of sketching and individual presenting/critiquing. Due to quite a large group and a 2 hour window time constraint, I explored the idea of adapting a simplified version of the ‘6 thinking hats’ (<a href="https://en.wikipedia.org/wiki/Six_Thinking_Hats">https://en.wikipedia.org/wiki/Six_Thinking_Hats</a>) — assigning them into 2 groups of either a ‘green hat (the optimist)’ and ‘red hat (the pessimist)’, which meant they had to give their feedback from one of those two ways of thinking. I then had them rotate hats/roles each round.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BNis1fYnByltIaqA91lgRg.png" /><figcaption><strong>Design Studio facilitation </strong>— featuring optimist/pessimist colour coded ‘thinking hats’ and post-its (<strong>Note:</strong> these are not real hats and are superimposed for illustrative purposes only — although that would of made a nice touch, wouldn’t it? :))</figcaption></figure><p>I found this new experimental hat method resulted in the discussions being much more concise which really helped overcome our time constraints.</p><p>In addition to successfully making the rounds much shorter, I was told the hat method helped their thinking be more focused while also making them much more comfortable in giving ‘negative feedback’, which tended to be a problem for participants from previous experiences conducting similar workshops.</p><h4>Outcome</h4><p>Finally, with colour coded feedback post-its scattered on each pinned up design around the room (which gave a visual indication of which were the more like ideas). We finished up by summarising the overall themes which were:</p><ol><li>Task guidance onboarding</li><li>‘X’ free ‘Hint(s)’ <em>(our usual model was to have them subscribe before access)</em></li><li>Bite-sized education</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EjTfcACpnIezp_X4RrEZVg.png" /><figcaption>Following each workshop I conduct, I send out a short 3 question feedback survey for continuous improvement</figcaption></figure><h3>Choosing Which Solutions to Test</h3><p>Next up, having generated themes from the design studio workshop, I gathered a new group together for a whiteboarding session consisting of the product manager, a content strategists and a few of software engineers in our team (this would also allow them to feedback to the other engineers in our team that couldn’t make it) as and when needed who would potentially be building this feature if our hypotheses were validated.</p><p>Even at this early stage in the process, it’s important for me to get a diverse range of inputs in order to maintain as much consistent shared understanding and team accountability as possible, while also gaining valuable insight into technical feasibility.</p><p>Together, after exploring many possible avenues, we settled on testing the following two hypotheses:</p><blockquote><strong>Hypothesis #1 — Task Onboarding<br></strong>We believe beginner hobbyists within their first session(persona)<br>Will be more likely to engage in our tree product (behavioural success)<br>By guiding them with instructional tasks (feature)</blockquote><blockquote><strong>Hypothesis #2 — Free Hint Reward<br></strong>We believe beginner hobbyists within their first session (persona)<br>Will be more likely to complete tasks and experience value (behavioural success)<br>By rewarding them with free use of a hint after completing 3 tasks (feature)</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_tpPnhoUHp5sSnUwhGZP4A.jpeg" /><figcaption><strong>Left :</strong> Key themes from workshop / <strong>Middle:</strong> Prioritised tasks (impact vs. difficulty) / <strong>Right:</strong> Hypotheses</figcaption></figure><h4>Task selection &amp; prioritisation</h4><p>Before we did that though, we needed to flesh those ideas out. We needed to decide on which tasks we should assign to users and in what order.</p><p>First, using post-its, we listed out all the possible tasks that could be carried out on the tree. Then, we mapped out which ones we felt brought the most value to the user followed by how complex each of those tasks was by the number of steps they had to take to complete them. We then ranked them all ‘high’, ‘medium’ or ‘low’ in impact and difficulty which we then used as a guide for prioritising their order.</p><p>Naturally, we thought it best to start with the easiest and most impactful tasks first and work down from there. We decided on having the ‘free hint’ reward after 3 successfully completed tasks.</p><p>It wasn’t perfect, but with such a short deadline at hand, we had no time to dwell. Our thinking was to get something in front of users as soon as possible to test, where we could then quickly iterate accordingly if our decisions were less than optimal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QKAC55WlLDFnQF-TabkWiw.png" /><figcaption>Impact vs. difficulty task prioritisation method</figcaption></figure><h3>Design &amp; Testing (part 1): Low-fidelity</h3><p>Now equipped with the content, clarity on task selection and order, I began sketching out a bunch of wireframes.</p><p>I tested these internally with different colleagues around the business. One of the key iterations made here was the introduction of a permanently viewable step-by-step ‘text instructions’ bar for each task as to not force the user to repetitively minimise and maximise the below tab when interacting with the product (this will become more clear in the next section).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ctSiWgnqF78RELesevGyPQ.png" /><figcaption>Sketches: One of the more successful internally tested wireframes</figcaption></figure><blockquote>“It’s pretty tedious that I have to minimise and maximise these tabs in order to see what my next step is.” — In-house user testing participant</blockquote><h3>Design &amp; Testing (part 2): Mid-fidelity Prototype</h3><p>Following a few iterations on the user tested sketches, I decided to move quickly to a mid-fidelity wireframed prototype. I decided on greyscale at this point in order to focus the discussion and feedback solely on the idea concepts rather than the aesthetics.</p><h4>External user testing</h4><p>Again, due to a looming deadline, we didn’t have adequate time to test both the mobile and the desktop versions. Suffice to say though, a high majority of our users tended to use higher screen resolutions when actually <em>using</em> our tree product (i.e tablets and desktops), albeit mobile is higher in initial ‘sign-ups’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*5qu9C8nddZH70v4-MdF9GQ.png" /><figcaption>Round #1 user testing participants</figcaption></figure><p>With that said, we (a user research specialist and myself) did two rounds of testing — with each round consisting of 5 participants (10 total). Starting with an initial short user interview followed by the test itself. All successfully matched our ideal user profile demographics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fx7zX7Ka_qIJI7PiMazhpw.png" /><figcaption>Card sorting helped us evaluate our participants thinking and how they value each ‘task’ in order of importance</figcaption></figure><h4>Card sorting</h4><p>Towards the latter part of the interview, we had participants do a card sort in two parts. We had them firstly write out on post-its the tasks they would like to see and rank them in importance. Then, we had them rank the tasks we had put together ourselves in order of importance and questioned them on their reasoning for each.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hnT-RywFRDN5iNrzsvERMw.png" /><figcaption>Mid-fidelity prototype #1 (key screens)</figcaption></figure><h4>User testing key learnings</h4><ol><li>The result of the card sort was extremely enlightening. It hit home how different our thinking was in regards to our task selection decision making and descriptive language style. While we were thinking in terms of actions to take on the product itself, our participants were thinking more of the <strong><em>outcomes</em></strong> they wanted to achieve.</li><li>The descriptive word ‘task’ really didn’t resonate with users. They felt it sounded ‘chore-like’.</li><li>It wasn’t clear to users that the ‘4th step’ was actually a reward and at a glance, they assumed it was just another task having not read the content of it at this point (this is where greyscale mid-fidelity wireframes proved to have it’s downfalls — in hindsight, with an interface of this complexity, a lack of visual colour distinction maybe wasn’t the best testing choice to deliver the best learnings).</li><li>Participants were more interested in a free trial rather than a ‘free hint’.</li><li>On the first task, which was to ‘play the introductory video’, participants were extremely unclear on how to take this action. This was because the button icon to take this action was in the form of a question mark which was taken from the live build (this is what the live website was currently displaying).</li></ol><blockquote>“Tasks? I don’t like the sound of that. Sounds like a chore.” — User testing participant</blockquote><h4>Key iterations/actions undergone from the above key learnings</h4><ol><li>We needed to drastically rethink how we presented these ‘tasks’. Making it abundantly clear that completing them will not only give them a reward and help them learn how to use the product but more crucially, potentially help produce the outcomes they wanted (e.g discovering unknown family members).</li><li>Renamed ‘Tasks’ to ‘Achievements’.</li><li>Added a ‘star icon’ to the reward button, giving visual emphasis and distinction from the tasks.</li><li>Changed the reward from ‘free hint’ to ‘free trial’.</li><li>Changed the button icon from a question mark to a play button. In addition, and to further address this kind of problem, we explored the idea of having temporary ‘lighter/darker’ visuals on the area where the current action was to be executed.</li><li>Changed the shape of the task shape from tall/thin to wide/short to give less visual obstruction on user/tree interaction.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K7vKvrBK3hPwJrE1ypboiw.png" /><figcaption>Mid-fidelity prototype #2 (key screens)</figcaption></figure><p><strong>Prototype link:</strong> <a href="https://goo.gl/qA9zHT">https://goo.gl/qA9zHT</a></p><h3>The Outcome</h3><p>Initially, our confidence was high but our assumptions on how our users would react to our ideas were off the mark. We grossly underestimated the sheer complexity of getting this type of experiment right in such a short time frame.</p><p>Overall, although enticed by the idea of a reward, users felt that this feature added an extra unnecessary layer of complexity to the experience — they wanted to be able to explore the product freely without being distracted by a strict task regiment.</p><p>This, we felt, didn’t necessarily mean that a task/reward feature was a complete write-off — only that for now at least, we had seen enough by this point to persuade us to pivot to a different direction where our confidence was higher in both scope and value to the user/business.</p><p>In the end, within just 2 weeks, we had identified/defined a problem, designed, prototyped and tested what would have been a complex and thus expensive feature to implement. Furthermore, we had generated a foundation of ideas and learnings for the backlog to be picked up for potential future experiment exploration — all without writing one line of code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=152a40c9755e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Onboarding Experiment: UX Case Study for Findmypast]]></title>
            <link>https://medium.com/@ryanconnaughton/user-onboarding-experiment-ux-case-study-for-findmypast-7c1495c9f932?source=rss-a0b35e034a38------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c1495c9f932</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Ryan Connaughton]]></dc:creator>
            <pubDate>Wed, 15 Aug 2018 10:27:12 GMT</pubDate>
            <atom:updated>2019-02-27T10:57:06.808Z</atom:updated>
            <content:encoded><![CDATA[<h4><a href="http://www.findmypast.co.uk/family-tree">www.findmypast.co.uk/family-tree</a></h4><h3>Introductory Context</h3><h4>The product</h4><p>Findmypast is a family history web-based product where you can primarily do three things:</p><ol><li>Search a collection of 8 billion+ records for your British &amp; Irish ancestors</li><li>Build your family tree which in turn generates <strong>‘Hints’</strong> of possible ancestor record matches</li><li>Combine 1 &amp; 2 to make discoveries and build a picture of who your ancestors were</li></ol><p>Now, in the case of this experiment, we’ll be focusing on the user journey of number 2, building your family tree. In order to give you better context before going through our approach, here’s what the old journey looked like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WDa2ZvIqjUpfSIbgeqQ7fQ.jpeg" /><figcaption>Old journey</figcaption></figure><h4>The team</h4><p>First off, I’d like to introduce you to the team I worked with on this experiment. We were 1 of 6 total product teams working cross-functionally to achieve overall continuous product improvement. We numbered a total of 8 — consisting of 1 Product Manager, 6 Software Engineers and myself.</p><p>I was charged with leading on the UX, user research and visual design (as well as occasional Product Owner duties).</p><p>The company and its team were working within an <a href="https://en.wikipedia.org/wiki/OKR">OKR</a> framework which was popularised by Google and stands for ‘<strong>O</strong>bjectives &amp; <strong>K</strong>ey <strong>R</strong>esults’. The purpose of which is to define goals and track their outcomes in the context of the wider team and company mission.</p><p>Day to day and within the team itself, we tended to follow many <a href="https://en.wikipedia.org/wiki/Lean_software_development">Lean</a>, <a href="https://en.wikipedia.org/wiki/Agile_software_development">Agile</a> and <a href="https://en.wikipedia.org/wiki/User-centered_design">User-centered Design principles</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AzF4hWPbgyg0ZerbMJVVeg.jpeg" /><figcaption>The dream team (mid-<a href="http://searchsoftwarequality.techtarget.com/definition/Agile-retrospective">retrospective</a> exercise carried out weekly)</figcaption></figure><h3>Defining the Problem(s), Objectives &amp; Key Results</h3><p>It was approaching a new quarter, and as per routine, it was time to define new OKR’s. To do that, we had to decide what the <strong><em>right</em></strong> problem was to solve for our users (user objectives v business objectives), coupled with a viable strategy on how to tackle it and how best to measure our success (key results).</p><p>In order to help us do that and as with all our pre-decision making, we first accumulated all existing previous data we had in our arsenal and/or carried out additional research we thought necessary but unavailable — a few examples of which I’ll be touching on in the following paragraphs.</p><h4>Previous user research</h4><p>Taken from vast amounts of previous user testing, we knew that:</p><ol><li>The tree was a complex product that was suited more towards intermediate users</li><li>Beginner users felt overwhelmed due to high-educational and knowledge barrier to entry</li><li>Beginner users wanted to be ‘hand-held’ throughout the experience</li></ol><h4>Competitor analysis</h4><p>To further guide our decision making, and since such research was at the time non-existing, I thought it useful to get a better understanding of our competitors strengths and weaknesses and what worked for them, or didn&#39;t. I conducted and documented in-depth analysis which I then relayed onto to the rest of the team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/521/1*-CV44BpHc345wNKrXku9aQ.png" /><figcaption>Competitor analysis: matrix (features &amp; business model)</figcaption></figure><p>To begin the process, I spent some time on each competitor product across different platforms and mapped out the experiences in the form of <a href="https://www.google.co.uk/search?q=page+flow&amp;source=lnms&amp;tbm=isch&amp;sa=X&amp;ved=0ahUKEwiZl8j9vefYAhWqIMAKHVQsAFcQ_AUICigB&amp;biw=1807&amp;bih=1030">page flows</a> — weighing up the differences in terms of features and business models along the way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ikJ_qWf6_Hd5PrXw8anHA.jpeg" /><figcaption>Competitor analysis: spider/radar chart (themes and features)</figcaption></figure><p>I then conducted a <a href="https://en.wikipedia.org/wiki/Heuristic_evaluation">heuristic evaluation</a> of each competitor and grouped everything together in the form of several key themes. These were put into a spider/radar chart diagram where I ranked each from 0–5 (0 being non-existent and 5 being excellent).</p><p>It’s not an exact science in all cases and thus some themes can be subject to opinion, but I felt it would be helpful to have this extra layer of qualitative data to hand when we congregated at the decision table.</p><p>Ultimately though, this technique is a quick way to visually distinguish a strong and weak areas of our competitors in comparison to our own as well as identifying patterns and gaps. This could also be built upon and reused going forward for all future experiments.</p><h4>Data science discovery</h4><p>Furthermore, we had been working closely with a data scientist that had made a profound discovery — when users reached the point of adding ‘x’ or more people to their family tree, the likelihood of them signing up for a paid subscription increased dramatically.</p><h4><strong>Technical blockers</strong></h4><p>It’s worth mentioning at this point also, the tree product was built in legacy code — this meant that improvements to the tree itself was at best extremely difficult, expensive and time-consuming and at worst out of the question.</p><p>In addition, work had begun to build a newer version of the tree from the ground up by another in-house team.</p><h4>Outcome</h4><p>With all the above taken into consideration, we concluded that we had strong indication on the direction we should go. The outcome of which can be read below:</p><blockquote><strong><em>Objective: </em></strong><em>Improve the tree onboarding experience for first time session users</em></blockquote><blockquote><strong>Key Result #1:</strong> The Average number of family members added to each tree increases from ‘<strong>X</strong>’ to <strong>‘Y’</strong>or more by new users within their first session<br><strong>Key Result #2: </strong>Achieve a conversion rate increase of ‘<strong>X</strong>’, from ‘<strong>Y</strong>’ to ‘<strong>Z</strong>’<br><strong>Key Result #3: </strong>Achieve an<strong> </strong><a href="https://www.medallia.com/net-promoter-score/">NPS</a> (Net Promoter Score) increase of ‘<strong>X’%,</strong> from ‘<strong>Y%</strong>’ to ‘<strong>Z%</strong>’</blockquote><h3>Defining the Users</h3><p>Before we jumped into ways we could achieve the above objective, It was important to reiterate to the team the types of users whom we would be designing for. Below was one of the pre-defined primary personas/user profiles we were working with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xLC6oCMht5DiN7ArtQNQew.jpeg" /><figcaption>Pre-defined User profile Canvas based off of extensive research (user pains/gains etc.)</figcaption></figure><h4>Experience level capture</h4><p>To help us validate our assumptions and inform us which type of user we should be focusing on when it came to designing solutions, we wanted to know exactly what percentage of our traffic were beginners who were signing up.</p><p>It had been unclear up until this point what the answer to that question was. It had been believed that the majority of users were intermediates.</p><p>In order to clear that question up once and for all, I advised the team we first conduct a quick experiment where we would ask the user(s) if they were a beginner, intermediate, or expert upon signing up which was agreed upon. Since this question alone could produce a subjective answer, we added an additional question which asked: “How long have you been researching your family history?” — this would help us further understand how they defined themselves in comparison to how we would define these 3 labels.</p><p>We later jumbled up these answers and re-tested in order to see if selection bias came into play. It did not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wnGMEDeiagtpmyYt4B_Clg.png" /><figcaption>Experience level capture (<strong>left</strong>: wireframes, <strong>right:</strong> live-build)</figcaption></figure><p>The results showed that in fact, the vast majority of new users classified themselves as a beginner with 0–1 month experience. This experiment was then rolled out to the rest of the product journeys were it was discovered that near identical results persisted.</p><h3>Strategy &amp; Planning</h3><p>As with all our experiments, we created a strategy and planning board which was split into 3 simultaneous workflows represented by different post-it colours (discovery, delivery and cross-functional teams), assigning each item into one of the timeline columns and rows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xb6C2GlNnkPJ6uoCva4PWw.jpeg" /><figcaption>Planning board (<strong>pink</strong>: discovery, <strong>yellow:</strong> delivery, <strong>green</strong>: cross-functional team)</figcaption></figure><h3><strong>Solution Ideation Workshop</strong></h3><p>To begin the solution process, I gathered the team and other appropriate key participants into a meeting room where we conducted an ideation workshop where I had the user journey flows and OKR’s readily pinned up on the wall. Doing this together meant building a shared understanding, gaining buy-in and developing potential solutions from diverse perspectives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qQJ8oFo1jlPjsKzNyBbDVg.jpeg" /><figcaption>User flows with generated ideas on post-its</figcaption></figure><p>Everyone had a good understanding of what we were trying to achieve by this point — but I reminded the group of the types of users we were designing for and the technical blockers/restrictions we had to ensure the discussions were on point and generated ideas were practical.</p><p>The workshop produced many great ideas and discussions which I grouped into themes and later used for inspiration.</p><h3><strong>Design &amp; Testing (part 1): Sketches</strong></h3><p>Following the workshop, I began exploring some of the more popular ideas further by sketching out what they would look like and mapping out how they would fit into the overall user journey.</p><p>One of the better solutions I thought, was to have a visually clear step-by-step process which added family members one at a time before they reached the tree itself. This solved several problems we knew from our research:</p><ol><li>Overcame our technical blockers (the tree product itself was built in legacy code with a separate team working to build a newly-coded version from the ground-up)</li><li>Overcame the lack of clear direction for the user with bite-sized next steps</li><li>Jump started the high learning curve needed to build on and interact with the tree</li><li>When completed, it meant the tree would be readily populated with additional family members, which in turn meant our system would generate more ‘hints’ from the get-go, making them see immediate value when they arrived on the tree</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*TthTtEXJWrrVDNb4e6hq6Q.png" /><figcaption>Early wireframed sketches</figcaption></figure><h4>Internal user testing</h4><p>Having then tested these sketches with a few colleagues, a few of them expressed their scepticism (and rightly so) on this particular direction, as I was informed that a similar experiment had failed previously which looked like the below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wEwWxdydE7dWKLO8Io7zAQ.png" /><figcaption>Previous experiment</figcaption></figure><p>However, I felt strongly that this may not necessarily be down to the concept itself, but rather, the execution. With some healthy debate, we were all onboard to explore this idea further.</p><h3>Design &amp; Testing (part 2) : Mid-Fidelity Prototype</h3><p>I then quickly created a simple greyscale clickable prototype which we (a user research specialist and myself) user tested with 5 external participants that matched our user profiles covered in the beginning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kMZ3aS4LJWx3Xcm5PoDgmg.png" /><figcaption>Mid-fidelity wireframed prototype (key screen)</figcaption></figure><p>We tasked each participant to sign up and to think out loud, prompting questions where necessary to better understand their thought process.</p><p>Overall, the prototype appeared to resonate extremely well with our participants.</p><h4>External user testing key learnings</h4><ol><li>Participants wanted the ability to go back and edit</li><li>It was not clear to participants what the ‘correct’ format of the ‘year of birth’ input was and how that might affect their result. It made them feel uneasy (despite the example text ‘1965’ that displayed the correct format)</li><li>Users were unsure on which parts were compulsory and which parts were not and how that would affect their results going forward (only a single name was needed to move forward)</li></ol><blockquote>“Ah! What if I make a mistake? Can’t I go back and edit it? Would I do that from the browser menu?”— User Testing Participant</blockquote><h4>Key iterations/actions undergone from the above key learnings</h4><ol><li>Introduced a back button (later new learnings meant we had to remove this due to technical constraints)</li><li>Changed the ‘<a href="https://en.wikipedia.org/wiki/Text_box">text entry box/field</a>’ to a selective ‘<a href="https://en.wikipedia.org/wiki/Drop-down_list">drop down list/menu</a>’ to remove any ambiguity</li><li>Added a subtitle that read “Don’t worry if you don’t know everything, just fill in what you can…”</li></ol><h3>Design &amp; Testing (part 3) : High-fidelity prototyping</h3><p>With our confidence growing from positive feedback, I began work on a more in-detail and refined version. I explored several different styles, some of which you can see below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*2o7i-h_WlNcFsi-N43lb2Q.png" /><figcaption>Layout &amp; styling exploration</figcaption></figure><blockquote>“The amount of effort you put into your <a href="https://en.wikipedia.org/wiki/Minimum_viable_product">MVP</a> (Minimal Viable Product) should be proportional to the amount of evidence you have that your idea is a good one” — <a href="https://www.amazon.co.uk/Lean-UX-Applying-Principles-Experience/dp/1449311652">Lean UX</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*muYBbcrNp6nhDRVvv6dk7A.png" /><figcaption>High-fidelity prototype #1 key screens</figcaption></figure><p>As with all my designs, I made sure that I pinned them up at regular intervals for everyone to see. That way I could encourage frequent useful feedback throughout the process as and when colleagues felt ready to give it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M2ew8uh0WIJnz37HY8Y-LA.jpeg" /><figcaption>User flow pin-up (situated just outside of our team seating area)</figcaption></figure><h4>Avatars</h4><p>One piece of useful feedback from the above designs told me that from previous user research, users tended to dislike ‘cutesy’ avatars as family history had a more serious connotation to it. This prompted me to design the below improved faceless avatars:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HEm6t6F_dhMTAWx31nEexA.png" /></figure><p>These I figured could also be used for marketing assets and throughout the rest of the product going forward as and when needed.</p><h4>User testing key learnings</h4><p>We did a further 2 rounds of testing both involving 5 participants each (totalling 15 so far).</p><ol><li>It wasn’t clear enough which family members details they were asking to be filled in on each step</li><li>Mobile: The skip link and call to actions were hidden away on smaller resolutions underneath the <a href="http://www.webvanta.com/post/2014-07-06/responsive-design-above-the-fold">fold</a> (the immediate viewable area without the need for scrolling)</li><li>Participants tended not to read the subtitle we added at the top of the page which read “Don’t worry if you don’t know everything, just fill in what you can…” This again meant users weren’t sure about which fields were mandatory and which were not</li><li>Making the previous decision to introduce the ‘dropdown list/menu’ for the ‘year of birth’ presented it’s own problems — it meant that participants were having to scroll for some time in order to select the right date which they found tedious, particularly when taking into consideration that they were potentially going to do this up to 7 times</li></ol><blockquote>“I don’t know my Grandfathers details. Is it not possible to skip this step?” — Mobile user testing participant</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MvduoWxWGJXgUqWypUhWfA.png" /><figcaption>Prototype #2 keyscreens</figcaption></figure><h4>Key iterations/actions undergone from the above key learnings</h4><ol><li>We experimented with having the avatar boxes ‘slide’ horizontally as to have it always be centred in the middle on the relevant family member (ultimately though this presented some technical challenges so we decided to settle on having a clear bold title within the form accompanied by a mini icon replicating the family members avatar).</li><li>Mobile: Added a permanently visible ‘next/skip’ footer navigation</li><li>We added a clear bold title <strong><em>within</em></strong> the form itself, where users eyes tended to be drawn (as opposed to the top of the page)</li><li>We devised a way to only have possible/relevant date ranges depending on how old the user was— this made scrolling to the right date much more efficiently on all following family member forms</li></ol><h3><strong>Build Execution &amp; Release Plan</strong></h3><p>For storytelling purposes and readability, I thought it best to explain things linearly as structured above. In reality, we had more than enough evidence sometime prior to this point that our idea was good enough to warrant testing this for real in the form of <a href="https://en.wikipedia.org/wiki/A/B_testing">A/B testing</a> (a method used to split user traffic 50%/50% to compare its performance against the current live build).</p><p>This meant we had two separate simultaneous workstreams with discovery and design work being 1–2 weeks ahead of what was being built into the live product.</p><p>This afforded us improved efficiency and two separate sources of continuous learning (qualitative user testing and quantitative metrics from the live website) that we could use to make evidence-based improvements as and when they came in.</p><h4>Release plan</h4><p>Since this wasn’t the only experiment we were testing at the time, we first had to come up with a test/release plan in order to see how this would fit in with the other ongoing work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/898/1*ooGQhj_HTaFzk1QnlyKsIw.jpeg" /><figcaption>Team roadmap</figcaption></figure><p>First, as a team, we estimated each items complexity (using Agile’s ‘<a href="https://www.ca.com/en/blog-highlight/works-agile-estimation-story-sizing.html">t-shirt sizing</a>’ method). We then grouped and prioritised each into ‘release segments’ — containing time until completion estimates and structuring it in a way where we thought we could make the most positive impact to the user and business in the shortest amount of time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cFLuoeMv1Mrh2g2oP54FOw.jpeg" /><figcaption>A <a href="http://searchsoftwarequality.techtarget.com/definition/user-story">user story</a> refinement session with the team — using <a href="https://trello.com/">Trello</a> with a <a href="https://leankit.com/learn/kanban/kanban-board/">kanban</a> structure</figcaption></figure><h4>Shipping it</h4><p>We then began breaking down release #1 into Trello tickets in the form of <a href="https://www.atlassian.com/agile/project-management/epics-stories-themes">epics</a> and <a href="https://www.atlassian.com/agile/project-management/epics-stories-themes">user stories</a> to be built into real code.</p><p>We tracked how our users engaged with our experiment on <a href="https://analytics.google.com/analytics/web/">Google Analytics </a>and the results were promising. This gave us the green light for us to plough on and execute on further iterated releases we had waiting in the pipeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LBZU-_1UmAiyP7-qk8k7mQ.png" /></figure><h3>The Outcome</h3><p>We managed to hit our overall objective and 2 out of 3 of our key result goals. Results showed we had upped user engagement by 150% and increased conversion (paid subscriptions) by 6%.</p><p>Through the remainder of the quarter, we carried out several more related successful experiments which increased engagement a further 150% totalling 300%+, including integrating this experiment into different user journeys throughout the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Yh4rBkZemACBR_izbww3fA.jpeg" /><figcaption>150% increase in user engagement metrics</figcaption></figure><h4>Learnings summary</h4><p>All said and done, we learned that beginner users really liked clear guided bite-sized onboarding steps to help overcome the trees overwhelming nature and usability complexity (to which we were powerless to improve due to technical constraints).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uZenhu1T2TsuDghYVq96rA.png" /></figure><p>This helped kick start their journey and in turn increased the chances of them attaining the outcomes they wanted sooner, without the daunting task of starting from scratch (an empty tree).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h2BpXryVwLM1_1bjUvGdmw.gif" /></figure><p>In closing, the biggest key take away I think, was that there is a fine line between what is minimally viable for the user and what is not — and with that, and although a difficult judgment call, we should always approach with caution when deciding to waive an experiment too early before they have had a chance to be fully fleshed out.</p><p>Although the previous ‘add parents’ experiment had failed, the<strong><em> concept</em></strong> itself turned out to be solid — it just needed a different approach.</p><h4><strong>Live demonstration video</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ME0eOeicuz0-YrhnDsOtMQ.jpeg" /><figcaption>Old journey</figcaption></figure><p><strong>Watch my verbally presented demo on another experiment: </strong><a href="https://vimeo.com/251565658">Click here</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F253118296&amp;dntp=1&amp;url=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F253118296&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F679926088_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1200" frameborder="0" scrolling="no"><a href="https://medium.com/media/f890c97889b32c4364b4cb4e3f2ae663/href">https://medium.com/media/f890c97889b32c4364b4cb4e3f2ae663/href</a></iframe><p><strong>Live link:</strong> <a href="http://findmypast.co.uk/family-tree">http://findmypast.co.uk/family-tree</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c1495c9f932" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>