<?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 Callum O&#39;Connor on Medium]]></title>
        <description><![CDATA[Stories by Callum O&#39;Connor on Medium]]></description>
        <link>https://medium.com/@callumoconnorUX?source=rss-ce295c7f9944------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*e8x2Yu7b-M8KM-FGMShjtw.png</url>
            <title>Stories by Callum O&amp;#39;Connor on Medium</title>
            <link>https://medium.com/@callumoconnorUX?source=rss-ce295c7f9944------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:19:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@callumoconnorUX/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[Service Blueprinting]]></title>
            <link>https://medium.com/@callumoconnorUX/service-blueprinting-5974b59e4610?source=rss-ce295c7f9944------2</link>
            <guid isPermaLink="false">https://medium.com/p/5974b59e4610</guid>
            <dc:creator><![CDATA[Callum O'Connor]]></dc:creator>
            <pubDate>Thu, 30 Jan 2020 00:03:47 GMT</pubDate>
            <atom:updated>2020-01-30T17:48:05.512Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>The challenge</strong></h3><p>We were asked by Formula 1 winning team, Mercedes AMG, to <br>map out key internal customer experiences and teach the internal <br>Change Management team about the design thinking process and <br>some of the key methodologies. The internal customer experiences <br>were how employees at race events abroad submit travel expenses <br>and the internal car leasing rewards scheme.</p><p><strong>The Kickoff</strong><br> <br>We began with a full-day workshop, facilitated by myself and my <br>agency’s Chief Strategy Officer. I selected and worked to prepare <br>all workshop activities which included persona co-creation, <br>customer journey mapping, the underlying backstage actions, <br>empathy mapping and a project prioritisation activity which aligned <br>all stakeholders around the project scope and expected outcomes.</p><p>The overall aims of the workshops were to:</p><ul><li>Understand the end-to-end ‘internal’ customer journey with each step clearly mapped out</li><li>Develop a deeper understanding of the type of user and their <br>current pain points and emotions at each step</li><li>Teach the internal Change Management team how to run such a workshop</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/549/1*NuxJf7dThbciWGOvYnfOBw.png" /></figure><p>We used the journey mapping session to map all the <br>steps in the user journey and used the empathy mapping activity to draw out what types of things Mercedes F1 employees were thinking, saying <br>about these internal customer experiences, both publicly and <br>privately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*KZB9rvCyjKfjope6dbPt8w.png" /></figure><h3><strong>In-depth interviews</strong></h3><p>Following on from the workshop we digitised all the workshop artefacts and sent them back to the client for review. We then revisited the Mercedes F1 head office to conduct in-depth interviews to add the detail we missed in the initial workshop sessions. Here we were able to speak individually to both internal ‘customers’ such as a Marketing Executive or Engineer who travels to Formula 1 races abroad with Mercedes and the Finance and Payroll staff who manage the whole experience.</p><p>I conducted all in-depth one-to-one interviews and noted key pain points in the internal customer journeys for both the internal end-users and the backstage actors:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/567/1*K2YEUL2MYW_35i9riV2RRw.png" /><figcaption>The first iteration of the travel expenses user journey and backstage actions</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*on8mr6NsdsOe4FXSjrx-JQ.png" /><figcaption>Car-sharing scheme user journey</figcaption></figure><p><strong>Car Scheme — User pain points</strong></p><p>• Lack of engaging, rigorous onboarding process which ultimately leads to confusion around how the scheme will work, how much it will cost the user and ultimately whether it is a worthwhile reward.</p><p>• Lack of cars available is another major frustration for the user, this should be better managed by the Reward Manager with live updates and notifications in place to ensure that the user gets to drive the cars they want to.</p><p>• The ‘Ready Reckoner’, while relatively simple, is very manual and does not provide the information required in a clear and intuitive way — a digital solution closer to a dashboard would be more suitable.</p><p><strong>Travel Expenses — User pain points</strong></p><p>• The initial itinerary sent out is vague and often fails to detail how much each employee is entitled to on their upcoming trip, this begins the chain of confusion.</p><p>• Users have to physically sign a sheet to confirm their expenses, often the users are out of the country for a number of weeks and will forget to keep a log, making physically signing off their expenses difficult.</p><ul><li>The monthly payslip does not provide a detailed breakdown of expenses leaving users confused at the end of the journey and chasing Payroll to find out if they have been paid properly.</li></ul><p><strong>Car Sharing — backstage actors pain points</strong></p><p>• Users ask colleagues about the car-sharing scheme which spreads misinformation about the scheme and leaves users with misconceptions.</p><p>• Chasing and filling in miles accumulated is a very manual process carried out over Excel and leaves much room for human error.</p><ul><li>There is no sign-off process meaning that a lot of information goes without formal checking or scrutiny.</li></ul><p><strong>Travel Expenses — backstage actors pain points</strong></p><p>• Users are often not back between races in the calendar leaving a huge backlog and knock-on effect for monthly expenses payroll.</p><p>• A lot of the process is done manually and could be made easier with an all-encompassing online dashboard or system.</p><ul><li>The who process is managed on one huge Excel file, leaving room for human error and versioning issues.</li></ul><p>Finally, I designed and created the ‘hybrid’ customer experience/service blueprint artefact which was specifically produced to meet the client’s particular requirements (below). Included on this hybrid map were a number of opportunities for innovation for the Change Management team at Mercedes to take forward, test and implement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/581/1*hKlXEwbKu8SZtCV61EzJHQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/839/1*2C7jevh7qN8Kdz7NUoOTkQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5974b59e4610" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Tailored Experience: A New Product Proposition for Paysafe]]></title>
            <link>https://medium.com/@callumoconnorUX/a-tailored-experience-a-new-product-proposition-for-paysafe-59c42081f4bc?source=rss-ce295c7f9944------2</link>
            <guid isPermaLink="false">https://medium.com/p/59c42081f4bc</guid>
            <dc:creator><![CDATA[Callum O'Connor]]></dc:creator>
            <pubDate>Wed, 29 Jan 2020 23:48:54 GMT</pubDate>
            <atom:updated>2020-03-10T13:20:03.941Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>The Approach</strong></h3><p>Working with leading FTSE250 global payments company, Paysafe, I worked as part of a team to research, validate, de-risk and design a brand new iGaming platform for the emerging US online gambling market.</p><h3><strong>The Challenge</strong></h3><p>As gambling regulation slowly begins to ease in the US, Paysafe asked us to create a brand new product proposition that they could take to gambling operators and software companies in order to win new business and become the payment provider of choice in this growing market.</p><h3><strong>1. Research: Survey</strong></h3><p>We began by surveying the key players in this space; gambling operators, software companies (who license their software to the operators) and the end consumers. We used the survey results to build a picture of our proto-personas and some of their key pain points and frustrations that we could help alleviate. We organised follow up in-depth 1–1 interviews with some of the respondents who interested us with their answers.</p><h3><strong>2. Research: In-depth interviews</strong></h3><p>A number of 1–1 interviews were organised with our key proto-personas to help us fill out the full persona profiles and better understand the US gambling market. I wrote the interview scripts and conducted many of the sessions. We focussed on the day-to-day working lives of our personas, what their KPIs were and what was currently helping/hindering them achieve their professional goals. Reporting back to the client at this point, we summarised our findings (below) by outlining the main problems each persona faces, how Paysafe’s new proposition could potentially address these problems, what this enables the persona to do post-launch and how we will know it has worked. The most pertinent pain points identified at this stage were players not being able to deposit funds and the number of integrations operators had to make in order to manage their operations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*sbt_7nIA3CZ4GBP6Y40lYw.png" /></figure><h3><strong>3. Analysis: Personas</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/1*ut8YVAExkQqYXNAEBMXjHw.png" /></figure><p>As well as synthesising our findings to produce consolidated problem statements, we also completed our working proto-personas, adding insight from the in-depth user interviews. We created multiple personas for operators, software companies and consumers encompassing all potential key stakeholders from different areas of the business such as Finance, Operations, and Risk. The key elements of the personas were goals and current frustrations, and this formed the basis of the next phase of the project, designing a tailored experience.</p><h3><strong>4 Analysis: User journeys</strong></h3><p>Our next step was to map out the key user journeys we unpacked during our research phase. We chose a number of journeys particularly important for the operators such as large numbers of consumers deposits failing, a VIP customer struggling with a large transaction, etc. We then ran workshops with the client to map out a new ideal journey (below) allowing us to discuss potential solutions to some of the key blockers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*BCr0NB8u9Tm_zjdkgNOAqg.png" /><figcaption>The ideal path</figcaption></figure><h3><strong>5. Design: Wireframes</strong></h3><p>From the new, ideal user journey we began sketching potential solutions to the pain points identified in the research phase. The overall solution would be an all-encompassing platform for operators to access all key data &amp; reports, monitor any alarming stats and respond in a timely manner.</p><p>You can see from the initial wireframes below that one of the key features of the platform was giving operators the chance to monitor failed deposits and isolate individual transaction failures. Another key feature that you can see in the UI version of the dashboard was the player conversion funnel, allowing operators to identify where players are dropping off in the deposit process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*GwvjrTLu1C0LR-inCNl7xw.png" /><figcaption>Initial wireframes of the operator’s dashboard</figcaption></figure><h3>5. Design: Iterations and UI</h3><p>In order to validate our new customer journeys and wireframes, we arranged second in-depth interviews with the same operators we had spoken to in the research phase and used the insights to iterate our designs. One key finding was that it would be useful to see some of the features we had proposed by region in the US, given the disparity in regulation and consumer behavior between the different states. You can see this additional feature incorporated in the UI version of the dashboard below.</p><h3>6 Deliver: Final outcome</h3><p>The final design, which has now been implemented by Paysafe, is perfectly tailored to gaming operators providing them with one easy to use dashboard housing all their reports, data and tools.</p><p>The most pertinent pain points identified in the research phase were players not being able to deposit funds and the number of integrations operators had to make in order to manage their operations. Our solution provided operators with a single API integration to a centralised platform (below, right), from here they can access a comprehensive dashboard displaying all key player and financial metrics (below, left), ultimately giving the operators the chance to provide the optimum customer experience for their players (below, centre).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*hmu1ByCi7SXINHHZmyOwwg.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*HQuHDk8IYc6hKG8l4A17Vw.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*11SMGKacHSXd7FJyhVslAA.gif" /><figcaption>Our designs in full working order</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*icix4jhYPeGMW7veFguStQ.png" /><figcaption>UI Outcome</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59c42081f4bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Optimising Onboarding]]></title>
            <link>https://medium.com/@callumoconnorUX/optimising-onboarding-7b8654203199?source=rss-ce295c7f9944------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b8654203199</guid>
            <dc:creator><![CDATA[Callum O'Connor]]></dc:creator>
            <pubDate>Wed, 29 Jan 2020 23:36:51 GMT</pubDate>
            <atom:updated>2020-01-30T17:43:05.269Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W1BE-vX6T8thqXHJnjZkug.png" /></figure><h3>The Approach</h3><p>I worked in a team of three UX designers in a 2.5-week sprint using a combination of agile, double diamond and Kanban frameworks. As a team, we worked cross-functionally, with all team members contributing to the user research and prototyping phases of the project. My core responsibility was user research and mapping out the end-to-end user flows, this involved producing user interview and usability test scripts and creating the rainbow spreadsheet where we recorded our key user insights.</p><h3>The Challenge</h3><p>Pilcro is a brand asset management (BAM) tool available as both a web app and a native desktop app. The main objective of the project was to optimise conversion rates from the site’s onboarding so that a higher number of website visitors download the native app.</p><h3>1. Discover — User research</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/1*6NsZa68oWL2VP27_5fKvuQ.png" /></figure><p>We began the discover phase of our sprint by carrying out a number of user interviews to discover what users consider important when it comes to brand asset management. We also conducted contextual inquiries to identify the issues and blockers that users encounter with Pilcro’s current onboarding flow, this involved asking users to create a Pilcro account for the first time and recording their experience. The goal of this research was to unearth a ‘golden moment’, a moment of realisation where the user instantly understands the benefit of the native app and is therefore compelled to download it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/1*0p6WO71L4aKQsYAcX4FdSw.png" /></figure><h3>2. Discover — Competitive analysis</h3><p>Through our competitive analysis of three similar BAM tools we identified;</p><p><strong>What other tools do well:</strong></p><ul><li>Contextual onboarding</li><li>Clear Call-to-Action on home page</li></ul><p><strong>What sets Pilcro apart?</strong></p><ul><li>Pilcro tool is not gated</li><li>Pilcro is the only tool available as a desktop app</li></ul><h3>3. Discover — Affinity mapping</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/1*qNEkCP0n8rTEjxCfWgDW5A.png" /></figure><p>Collating all of our user insights from both the contextual inquiries and user interviews using an affinity map we were able to identify trends and recurring user pain points.</p><p>The most significant of these included:</p><ul><li>The onboarding tutorial failed to properly communicate the benefit of the desktop app and the majority of users were not even aware of its existence. As a result, none of the users we tested felt compelled to download it.</li><li>Users found the onboarding tutorial useful however most commented that they would prefer to be able to explore the tool and revisit the tutorial if necessary.</li></ul><h3>4. Define — Persona &amp; Scenario</h3><p>We used our affinity map to create a persona and scenario, these would help guide us in the develop phase and ensure that we were focusing on solving a specific issue for Pilcro’s core user base.</p><p>The scenario we used for our persona Alexandra (below) was:</p><p><em>Alexandra is a Marketing Manager for a small tech start-up, the team is growing and several new employees are having trouble locating brand assets.</em></p><p><em>New starters are wasting her and the sole designer in the team’s time by constantly asking for assets. As a result, she wants to find the best way to manage the company’s brand assets.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/579/1*F2hVAwvXfWXYuGq8UZR_Mg.png" /></figure><h3>5. Develop — Design studio</h3><p>Taking the persona and scenario into the ideation phase, we began sketching initial ideas in a design studio session which my team and I ran with the client. This session involved rapid ideation and allowed us to take the strongest elements of various outlandish ideas and combine them into a more coherent solution.</p><p>We were able to prioritise a number of key features that we all agreed should be included in the final solution. These included:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/455/1*iuR22TaXlNiXyqRREof70A.png" /></figure><ul><li><strong>a contextual onboarding tutorial</strong></li><li><strong>a tooltip highlighting the desktop app download button</strong></li><li><strong>a profile completion ‘progress indicator’</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/455/1*j7roF_w1ClXWBHLMr-6bYQ.png" /><figcaption>Design studio in action</figcaption></figure><h3>6. Develop — prototyping &amp; iterations</h3><p>Below are the iterations of the prototypes we created for two of our most important features (the progress indicator and the tooltip highlighting the desktop app). Our user research highlighted that the majority of users did not notice the desktop app download button or understand the user benefits. By incorporating the tooltip which highlights the donwload button with an image preview and succinct copy describing how the app will live in the top menubar, close to 90% of users tested said they would now download the desktop app — great results!</p><p>You can see from the iterations of the progress bar that this is something we struggled to get right (third image of paper and low-fi prototypes, below). Initially, users did not intuitively understand the icon and we then had issues with users not realising that the progress bar was clickable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*e72p9w1Q3sX7b7nr.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9apbobfjMK8mVWvm.png" /></figure><p>Our final solution was a neat drop down from the existing profile icon with clear CTA buttons and a percentage indicator, we found users understood and liked this feature, plus it further compelled users to complete their profile and download the desktop app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/387/0*2_Dpw3ESYorr83uc.png" /></figure><p>Other user feedback included:</p><ul><li>Users did not understand straight away that it was a tutorial so we streamlined the copy</li><li>The <strong>profile completion feature </strong>required further explaining and users were not aware that there were CTA’s.</li><li>Users had no visual confirmation when an artboard is <strong>saved</strong> or information about its location.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Qdqo44BEbf-Nd9Wz.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*avWCrtcUCOxeRK5I" /></figure><p>The final step of the tutorial which provided information about the desktop app, was one of the main new ideas introduced from the start. It started as an intrusive pop-up ‘advert’, as one of our users said, and became a contextual message highlighting the download button, which as you’ll remember was not originally recognised in the initial user tests. Other issues raised in our research phase that we addreessed in our design included:</p><ul><li><strong>Contextual onboarding</strong> was included to allow users to explore the tool</li><li>The tutorial can be revisited through the progress bar</li></ul><h4>8 Deliver — Final solution vs solution implement by the client</h4><p>As you can see from the below, elements of our final recommended solution were implemented by the client. One of these implemented recommendations was the progress feature which was developed from our research finding that users wanted to revisit the onboarding in order to complete the profile once they have explored the tool.</p><p>Our final solution was able to address the main objective by effectively communicating the native app’s key benefit earlier in the onboarding process. The client has since implemented a number of our key design recommendations and conversion rates from website visitor to product user doubled from 26% to 56% in the week after deploying the new user onboarding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bI4oFL-3ZPDil3Cj" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TwaZbSPfJ4Qao5Wg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MZVe1cXvENgdAiK5zGZ-kA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b8654203199" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From blog to bettor: improving player conversion on mobile]]></title>
            <link>https://medium.com/@callumoconnorUX/from-blog-to-bettor-improving-player-conversion-on-mobile-1254cc1c56aa?source=rss-ce295c7f9944------2</link>
            <guid isPermaLink="false">https://medium.com/p/1254cc1c56aa</guid>
            <dc:creator><![CDATA[Callum O'Connor]]></dc:creator>
            <pubDate>Wed, 29 Jan 2020 20:54:11 GMT</pubDate>
            <atom:updated>2020-01-30T10:57:43.267Z</atom:updated>
            <content:encoded><![CDATA[<p>The <a href="http://blog.betway.com/">Betway Insider</a> blog, Betway’s tipping and news site for sports fans, performs relatively well with close to 100,000 monthly users and 170,000+ monthly page views. Despite these impressive <em>(some would say vanity)</em> metrics, the site could be performing better commercially. I’m leading a project to redesign the Betway Insider mobile site with a view to increasing the amount of time users spend on the site and improve the conversion rate from article read to bet placed on the primary Betway sports site. The overarching ambition is to increase the blog’s financial value.</p><h3><strong>1. Kick-off Workshop: Objectives, requirements and scope</strong></h3><p>The first stage of the project was to gather all of the key project goals and requirements from the various stakeholders. I curated and facilitated a workshop which included 3 key activities:</p><ol><li><strong>What does success look like for this project in 12 months time?</strong></li></ol><p><strong>Why?</strong></p><p><em>Create a unified vision for the project and highlight key success metrics.</em></p><p><strong>How?</strong></p><p><em>1.</em><strong><em>Write individually (5 mins)</em></strong></p><p><em>We asked participants to imagine 12 months from the project finish date and asked them to write down an outcome that has meant the project has been a success.</em></p><p><strong><em>2. Group (5 mins)</em></strong></p><p><em>All together, participants grouped the duplicate/similar post-it notes.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lZIVnOdIDTWxv2VxcgTAfA.png" /><figcaption>What does success look like for this project?</figcaption></figure><p><strong><em>3. Prioritise (5 mins)</em></strong></p><p><em>As a group, the ‘top 3’ outcomes were prioritised and relevant KPIs for each outcome were brainstormed and noted down. These would now form the key success metrics for the project.</em></p><p><strong>2. Assumptions activity</strong></p><p><strong>Why?</strong></p><p><em>If someone works long enough on a product, they start to develop unproven beliefs about users, things they like or assume the user likes. Without research, we may treat these beliefs as facts.</em></p><p><strong>How?</strong></p><p><em>1.</em><strong><em>Write individually (5 mins)</em></strong></p><p><em>Participants were asked to write down statements they hold as true about the business, the product and its users.</em></p><p><strong><em>2. Present post-its (2 minutes per person)</em></strong></p><p><em>Each participant then had three minutes to talk briefly about their post-its and put them on the wall.</em></p><p><strong><em>3. Put post-its on the matrix (10 minutes)</em></strong></p><p><em>Drawing a matrix with two dimensions: a vertical line from low-risk to high-risk and horizontal line from known to unknown we mapped the post-its and identified the key assumptions we wanted to test during the upcoming research phase.</em></p><p>These were: <strong>Users find the journey from tipping article to placing a bet easy </strong>and<strong> that users can easily find more articles to read once they finish an article</strong>. These would form the basis of the next phase of the project: research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/394/1*KAuHjy_2RQK0T-bmBejyTg.png" /><figcaption>Assumptions can lead to scary design decisions</figcaption></figure><p>The third and final activity was a proto-persona activity:</p><p><strong>Why?</strong></p><p><em>Proto-persona helps the whole group put themselves in the mind of the end-user and gives all stakeholderss a lens through which they can look at design iterations throughout the project.</em></p><p><strong>How?</strong></p><ol><li><strong>Group Brainstorming</strong></li></ol><p><em>I asked each group to brainstorm who the Betway Insider users are and why they use the product as well as some key goals &amp; current pain points.</em></p><p><strong><em>2. Present &amp; voting</em></strong></p><p><em>Each group presented back and once similar personas were grouped, the participants voted on the personas they saw as most likely to use the blog.</em></p><p>From this, I led the final part of the workshop to complete the persona template, online, in the room. You can see one of the final results below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/667/1*r-JOs4l8nvRkJiF8IPG4NQ.png" /></figure><p>The key learnings from this activity were that the motivation behind Tim’s betting activity was primarily social so he’d likely be using the blog and the main site out when with friends. From this, I know that the site information needs to be easy to retrieve and easy to share.</p><h3><strong>2. Putting assumptions to the test: usability testing on the current site</strong></h3><p>After a UX review of the site, I designed and set-up a number of online, unmoderated user tests to test the key project assumptions established in step 1. One of the key tasks in the test was to ask users to place a bet on the Betway site from an article on the blog. The tests revealed a number of interesting learnings:</p><ul><li>Users did not always realise that the live odds button was clickable and therefore were likely to miss it</li><li>When users do click the odds 8 out of 12 users did not notice that the bet slip had been updated on the main Betway site and were, therefore, not able to complete placing the bet (see the journey below)</li></ul><p>You can see from the images below that the small badge on the second image in the top right-hand corner is very small and easy to miss. Most users did not notice this at all and wondered where their selection had gone.</p><blockquote><strong><em>One user commented: </em></strong><br>‘I wasn’t sure exactly where to click at first. And then when I’d clicked on the odds it only took me to the Betway homepage rather than the specific page to enter my stake to bet on that golfer.’</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W-C0QHT-hFv7gJqjASg_mA.png" /><figcaption>The current user flow — screen 2 shows the small badge that users were missing</figcaption></figure><p>These findings helped us invalidate the assumption that most users can successfully place a bet from the blog site, definitely something to focus on in the redesign.</p><p>Another task we asked users to complete was to find an article relating to their favourite sport. As a lot of the more niché sports were buried behind the burger menu, underneath the most popular sports, many users struggled to find what they were looking for and gave up.<em> </em>Other test feedback included users being left confused between which tab was the selected state; latest stories or most read (see below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/317/1*wi0YYhRmOa0_6p4ffnshCg.png" /></figure><h3>3. Synthesis, ‘How Might We’ &amp; ideation</h3><p>I presented the user testing results to the stakeholders and led an ideation session where we could generate solutions to the main issues.</p><p>Part of my role at Betway is to help educate the wider business about Design Thinking methodologies and practices. In order to get the stakeholders thinking this way, I kicked the session off with a How Might We.</p><blockquote>How might we make it easier and more intuitive for users to place a bet on the Betway site from the blog?</blockquote><p>I used this technique to frame the ideation and introduce the most pertinent challenge of the project in a way that does not hint at any potential solution.</p><p>We brainstormed a number of solutions including placing a bet directly from the blog but the solution we landed on was a number of new CTAs with clearer deep links to the Betway site. This made the user journey clearer and more intuitive.</p><p>In our proposed solution, users could now select the ‘Place Bet’ CTA. This would take them straight to the related market and outcome where all they would have to do is enter the stake and place the bet, as you can see below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*fZ1RsjP9LC4Rx1DADdGmHg.png" /></figure><p>New CTAs such as ‘View Market’ and ‘Add to Betslip’ would accommodate for different users’ mental models and present these users with alternative ways to place a bet from the blog. Users who may want to look at the event before choosing a selection can select ‘View market’ whereas users who want to add all of the tips in the blog article could select ‘Add to Betslip’.</p><h3>4. Further testing and iterations</h3><p>The next stage was taking the initial ideas and wireframes and running through a series of build, test, learn iterations. Below you can see that we addressed some of the key issues mentioned in Section 2 above:</p><ul><li><em>As a lot of more niché sports were buried behind the burger menu, underneath the most popular sports, many users struggled to find what they were looking for and gave up.</em> — I introduced a horizontal scroll navigation menu to bring all of the sports that were buried under the burger menu into view, meaning those who wanted to read about NFL or UFC, for example, could easily find it with a simple swipe. In a later round of usability testing, the number of users who could find an article relating to their favorite sport increased by 30% to 100%.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*V_Uu7fWjCoCFAKtqOjuiAA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*p82shz16WEWQ6KTuJq4yew.png" /><figcaption>V1.2 and V1.5 of the blog redesign</figcaption></figure><p>Further testing showed that the ‘Place Bet’ CTA was a little too ambiguous so we introduced the live odds button. In V1.2 of the design, users were slightly overwhelmed with where to click. After consulting the stakeholders we decided to make ‘View Market’ the primary CTA and make all other buttons secondary, this introduced some clearer visual hierarchy and helps guide the user along the preferred path to viewing the relevant market.</p><p>Currently, the blog redesign is still an ongoing project. As mentioned, the latest round of testing showed that 100% of users (15/15) can find articles relating to their favouite sport (up 30%) and close to 90% of users can now successfully complete the journey from reading an article to placing a bet on the site.</p><p>On our current path we’re on course to achieve the goals we set out to — making it easier for users to find and read the sports articles they enjoy reading, and making it easier for users to place a bet on a tip they feel confident about.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1254cc1c56aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reimagining the mobile dating app market]]></title>
            <link>https://medium.com/@callumoconnorUX/reimagining-the-mobile-dating-app-market-f4498fd3043d?source=rss-ce295c7f9944------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4498fd3043d</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Callum O'Connor]]></dc:creator>
            <pubDate>Wed, 18 Jul 2018 14:50:53 GMT</pubDate>
            <atom:updated>2020-01-28T13:53:56.597Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>The challenge</strong></h4><p>In a world where<strong> 26 million matches</strong> occur on Tinder every day, the fact that males only follow a match with a message <strong>7% </strong>of the time (females a better 21%) may surprise you (or not depending on your past experience with dating apps.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/0*H6bSGwN0OPuJioYM." /><figcaption>Modern daters are being left in the dark</figcaption></figure><p>It was clear from these figures and from the number of users I spoke to that the dating apps currently available are failing to meet users’ needs. People looking for meaningful relationships are being put off by others who are simply addicted to swiping, on the hunt for their next ego boost. This all leads to modern, millennial phenomena such as ‘ghosting’, ‘bread crumbing’ and everybody’s favourite … unsolicited dick pics.</p><h4>User research</h4><p><em>“The whole point of the app is to meet people.”</em></p><p>I conducted a number of user interviews and used an affinity map to identify the key trends and the most pertinent user pain points. The most common frustrations were the amount of “random time wasters” and the lack of interesting things to do with a blind, first date apart.</p><blockquote>“She demanded we do something besides drinking alcohol.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QAbAtB10mFQDRzHd." /><figcaption>The affinity map</figcaption></figure><p>I decided to focus on the first date issue as none of the apps currently available help users overcome this particular frustration. I decided to come up with a <strong>‘How Might We’</strong> statement that I would take in to a design studio with my team. This method helps frame the problem and fosters an environment conducive with producing a number of innovative, novel solutions as the statement focuses solely on the problem and doesn’t mention any possible solutions. My how might we statement:</p><blockquote>How might we make the transition from the online dating experience to the offline initial meeting more fun, interesting and less awkward?</blockquote><h4>Further understanding the user</h4><p>I wanted to better understand my app’s core persona before I moved on to the ideation phase of the process. Based on user research I concluded that the core user would be aged between 21–35, of average income between £20k — £45k and the key motivators would be meeting a romantic partner with similar interests and want to experience what London has to offer culturally. Pain points would be time wasters on Tinder and boring dates (as above).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5nZqgB8cSvWciWJhzANMdw.png" /><figcaption>Experience mapping</figcaption></figure><p>I produced an experience map in order to visualise the task’s necessary for a user to go on a date and further explore our core persona’s pain points. You can see above that the user experiences real frustration when it comes to thinking of a place to go with a blind, first date. This was the pain point I focussed on in ideation and prototyping.</p><h4>Ideation &amp; prototyping</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4OCD3drCZ955id06M_ZJ3w.png" /><figcaption>Ideation: the design studio</figcaption></figure><p>The initial idea borne out of our design studio was centred around people posting spare gig tickets and our users applying to be matched wit potential dates, combining traditional dating apps with gig posting and ticket swap sites. I took this idea and created the initial sketches and paper prototype of the app (below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bRIFVygGq2B_P4rHu8Bk4g.png" /><figcaption>Paper prototype</figcaption></figure><p>Following a number of usability tests with potential users that matched the core persona I was able to identify a number of issues with my initial prototype.</p><ul><li>The flow was not properly thought out with users struggling to navigate back to previous screesn</li><li>There was an issue around the question if multiple people post tickets to the same event</li><li>Ultimately this version of the prototype was almost completely rejected by user</li></ul><p>Time for further iterations and more testing …</p><h4>Wireframes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*NXeAoZPB0B0WviXnRNidrw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/818/1*2WMe-kble-npmDYzQiUlnw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*YyNwDK-sWBEPrvYIQudDsg.png" /></figure><p>As I carried on the prototyping process, moving up in fidelity at each stage, I conducted usability tests and made further iterations. As you can see from the images below, I introduced a ‘chat now’ feature which simplified the user flow by removing the ‘apply’ function. This gave users the freedom to chat to potential matches and removed the unnecessary, complex step of applying for tickets. Further usability tests proved that this new flow made the user experience more seamless and fulfilling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kneUuscwr6efUy-TxfueSQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rYl2jW7WuK86xA2tTEZGxQ.png" /><figcaption>Mood boarding and colour psychology</figcaption></figure><h4>Visual Design</h4><p>Visual design was a signifiant part of the project and involved me creating a style guide for the app which included the colour palette, logo, and typeface. For the colour palette I created a mood board and looked at colour psychology, I also looked at competitor’s key colours and decided that orange was both unique enough and captured appropriate emotions such as warmth and fun. The logo I created incorporated the app’s analogous colour scheme and used two arrows pointing outwards but close enough to one another to symbolise both romance and adventure.</p><h4>The Solution</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vd71APtYkgUAOFL3eOf8DQ.png" /></figure><h4>The New Experience map</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6K5nMIxmiIDDXMORZF3F0Q.png" /></figure><h4>Next Steps</h4><ul><li>User generated dates — think through the user flow of uploading an event</li><li>Recommend friend flow — how could we incorporate friend recommendations (event &amp; date)</li><li>Map out the onboarding/sign up process</li></ul><p>To find out more about me and to get in touch, check out my <a href="https://www.linkedin.com/in/callum-o-connor-ux/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4498fd3043d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first UX project: an e-commerce website with a social twist]]></title>
            <link>https://uxdesign.cc/my-first-ux-project-b7282cd3289c?source=rss-ce295c7f9944------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7282cd3289c</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Callum O'Connor]]></dc:creator>
            <pubDate>Wed, 20 Jun 2018 11:26:57 GMT</pubDate>
            <atom:updated>2018-07-03T12:31:34.376Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZRzNyt7TuBkv6aWO." /></figure><h3>1. The challenge</h3><p>I was tasked with designing a new e-commerce website for a hypothetical homeware store who were seeking to develop their web presence while maintaining their reputable brand image.</p><p>The store, Splendid Housewares, serve small businesses and customers in the local area and prioritise face-to-face interactions with their customers. They can accommodate store collections for their local customer base and would like for this to be reflected on the site.</p><h3><strong>2. Discovery</strong></h3><h4>2.1 User Research</h4><p>The first step of the discovery stage of the process was to conduct a number of user interviews. During these face-to-face interviews I was hoping to better the understand the thought process of people who shop for homeware products online, in particular their context, the process they follow and any particular pain points they have that I could seek to address in my design.</p><p><strong>My findings:</strong></p><p><strong>Context:</strong> Shoppers go online to buy specific products for their home or for a special occasion (dinner party, Christmas etc.).</p><p>Unlike people who shop online for clothes, for example, homeware shoppers often have a clear idea in mind of the product they need and rarely casually browse for items for their home.</p><p><strong>Process: </strong>They<strong> </strong>Look for inspiration for the product they want (social media, catalogue, search engine etc) then go direct to the site to buy the item or search for cheapest place to buy the product using Google’s shopping feature.</p><p><strong>Pain points: </strong>I used affinity mapping to identify two recurring pain points for online homeware shoppers: <strong>product information </strong>and<strong> delivery.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mDlCkatbmZnNMnSX." /><figcaption>A snapshot of my affinity map identifying user’s pain points</figcaption></figure><p>Users often struggle to imagine how the <strong>product</strong> will look in their home, in particular when it comes to the size of the item and how it will look in their home.</p><blockquote>“Item was unexpectedly too big for our home when it was delivered.”</blockquote><p><strong>Delivery</strong> is often not communicated clearly enough and packaging often inadequate.</p><blockquote>“Finding a delivery time slot can be hardest part of the process.”</blockquote><p><strong>Primary Persona</strong></p><p>My primary persona was Valentina who shares many of the frustrations of the users I interviewed, namely a busy lifestyle that makes collecting deliveries a struggle and an uncertainty when it comes to buying products for her home.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*avnyVl6YcIGcjj1aVOJ5pg.png" /></figure><p><strong>Key insights:</strong></p><ul><li>Can doubt her purchases and wants to feel confident in her choices</li><li>She wants to get easy to come by information in order to make a good purchasing decision on a budget</li><li>Supports local businesses</li></ul><h4><strong>2.2 Competitor research</strong></h4><p>The next stage of the design process was competitor research, I analysed a number of direct and indirect competitors to identify a number of key features for my e-commerce website. The feature comparison of smaller, local competitors and larger stores gave me an idea of the key features our users would expect from a homeware store.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JFz9smzSmuBnyKz3." /><figcaption>Competition analysis: feature comparison</figcaption></figure><p><strong>Opportunity</strong></p><p>After identifying our site’s ‘must-have’ features I wanted to look at what the competition weren’t doing so well — what space of the market could Splendid Housewares seize? My analysis identified 3 areas:</p><p><strong>Social</strong><br>All sites lack a community feel which is key to our brand</p><p><strong>Product page</strong><br>Only a few of the competitors show multiple images</p><p><strong>Collection</strong><br>Only one of the sites offer a collect option, could we do the same?</p><p>You can see from the matrix below that none of the smaller, local houseware stores have product pages with multiple images. As one of the key user pain points identified in the user research is the lack of product information I decided to develop this feature to tackle this problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yJQomjUuU0Ddf5gF." /></figure><h4><strong>2.3 Information Architecture</strong></h4><p>Information architecture and taxonomy were the next step of the process. With such a varied product assortment, ensuring the user is able to easily and intuitively navigate the site is vitally important.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aIx3mFKy8r-RRh14." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nDBPdVANRA25DCao." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*r7V1fCtWd6bBdTAi." /><figcaption>Open and closed card sorting</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F14hsyRv6pFylUkC." /><figcaption>Splendid Houseware site map</figcaption></figure><p>My closed card sort showed that the majority of the store’s products fell under the Kitchen category, to tackle this I conducted another closed card with kitchen subcategories. The end result was a more coherent, cleaner site map (left) that meant the users could intuitively navigate the site.</p><h3>3. Define</h3><h4>3.1 Core persona, scenario and frustrations</h4><p>After the discovery phase it was time to hone in on the core persona, pain points and scenario I was to focus on in the next phase of the project (develop).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2TPBQVpwpLHHZ0-GNpT7-Q.png" /><figcaption>Defining the core user problems</figcaption></figure><h4>3.2 Storyboard</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9PjQdSvJ916uJi2J." /></figure><p>I was then able to map my persona’s scenario into a storyboard where I can clearly communicate where the Splendid Houseware brand and e- commerce site could help our target persona with her particular issue, in this case finding glass and dinnerware for an upcoming dinner party in her new flat.</p><h3>4. Develop</h3><p>I then moved on to develop phase where I would begin sketching ideas for solutions to solve our user’s pain points around lack of product information for homeware products.</p><h4>4.1 Design studio</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tnSZCOIvvgqYV1be." /><figcaption>Rapid ideation in progress</figcaption></figure><p>I began the develop phase by running a design studio, rapid, time-boxed ideation with a team to produce a range of varying ideas to tackle the problem.</p><p>I introduced the issue we were addressing to the team:</p><p><em>“How can we help people make better purchase decisions by helping them </em><strong><em>imagine</em></strong><em> how the product will look in their home before they buy it.”</em></p><p>After a range of different ideas, varying from AR to user generated images, we combined the best elements of the various ideas and formulated a final solution.</p><p><strong>The Solution: </strong>Give our users from the local community the chance to upload images of our products in their homes directly through Instagram.</p><p>This will give our users who are considering buying the same product the chance to imagine how it will look in their home.</p><h4>4.2 Paper prototype</h4><p>To communicate and test this solution with the target audience I created a paper prototype of the site’s key screens (below). You can see from the middle image how our site’s product page will look with an image upload button for users to upload an image of the store’s product in their home and an image carousel for users to view these images and feel inspired. I also wanted to test the collect from store feature as this was the solution to our user’s other key pain point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pucnQEBru7upiNA5oFoiTA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X5G2RR2khD6oqfxnYp2mxg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IMvU4O4qLqcGRcsSBJNtCg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rzEsaAXzuFmhUgcP." /><figcaption>Testing the low fidelity paper prototype</figcaption></figure><p>Testing the paper prototype gave me a number of key insights that I was able to take in to the next stage of prototyping:</p><p>Visual confirmation when date of collection is selected is required.</p><p>‘Go to pay’ and ‘basket’ confused users and delayed the checkout process.</p><h4>4.3 Digital Prototype</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kpxXwrBTjoQHQPxT." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RMeiJTndBl9lF-eQ." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oCDK_8f1GJKveHue." /><figcaption>Mid-fidelity screen mock ups created on Sketch</figcaption></figure><p>Taking user feedback from the paper prototype in to consideration I then iterated on the website screens using Sketch. You can see from the image on the right above that visual confirmation of the collection has been added which should make the check out process smoother.</p><p>It was also key to test these screens with users and using a prototyping tool called InVision I was able watch users navigate through the site and complete tasks relating to the user scenario. From there I could identify bottlenecks or areas of confusion and take these in to the next round of iteration.</p><h4>4.4 Proposed next steps for this project</h4><p><strong>A/B Test ‘Buy Now’ button: </strong>users were not fully convinced of the current Buy Now button on the product page</p><p><strong>Map out upload image user flow: </strong>think about how user would upload images of products from Instagram</p><p><strong>Rework Checkout flow: </strong>change ‘buy now’ to ‘proceed to checkout’ and add status bar and include email follow up</p><p><a href="https://invis.io/BGGSSH0YRJ4">Link to InVision Prototype</a></p><p><a href="https://docs.google.com/presentation/d/1sPMjn6MscoXKIIGdLBoDvtViJQybonWsJKXxR5pOPRA/edit?usp=sharing">Link to project presentation</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=b7282cd3289c" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/my-first-ux-project-b7282cd3289c">My first UX project: an e-commerce website with a social twist</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[How to test whether that really brilliant business idea of yours is actually worth pursuing ……]]></title>
            <link>https://medium.com/@callumoconnorUX/how-to-test-whether-that-really-brilliant-business-idea-of-yours-is-actually-worth-pursuing-8771bf668e43?source=rss-ce295c7f9944------2</link>
            <guid isPermaLink="false">https://medium.com/p/8771bf668e43</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[prototype]]></category>
            <dc:creator><![CDATA[Callum O'Connor]]></dc:creator>
            <pubDate>Tue, 03 Apr 2018 10:00:47 GMT</pubDate>
            <atom:updated>2018-04-03T10:00:47.055Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to test whether that really brilliant business idea of yours is actually worth pursuing … PRETOTYPE IT!</h3><p>I’m guessing that you’ve probably been sitting on that fantastic business idea of yours for quite a while now. Maybe it’s a revolutionary new way to get your all-important fresh coffee delivered or a mobile app which would allow you to manage your seemingly endless list of free trials. If only you had the financial backing and the courage to quit your job, you’d be well on your way to changing the world right now, right?</p><p><strong>It seems that we all harbour dreams of becoming the next Elon Musk but how can we test whether our idea really has any potential?</strong></p><p>One of the most important things I’ve learnt from my short time working in an entrepreneurial world is that the reason most new products fail is not because they are poorly designed or put together but because they never really ‘scratched an itch,’ that is to say they don’t solve a real customer problem. Another key lesson is that people rarely know what they want, often they’ll tell you a product or idea is great but in reality they would never actually make it part of their daily routine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/423/1*ZYnpsk9535MNVcW8NpGmtQ.jpeg" /><figcaption>Pretotype It book</figcaption></figure><p>This is where pretotyping comes in, a way to launch an innovation without having to build anything, a way to determine whether there is any real market demand for your idea. There are countless tales of entrepreneurs building great products only to discover that their target audience wanted something a little different. They may have carried out extensive user research and conducted a number of fruitful interviews but never actually tested whether people really would attempt to purchase the product if it hit the market.</p><p><strong>Our pretotyping experiment</strong></p><p>Here at Fuse, as a mobile venture, we encounter this problem a lot. Is there any real demand for the mobile apps we want to build? To test our latest idea we’ve decided to go for the ‘fake door’ pretotype. To see whether anyone would sign up to our recurring grocery delivery service we’ve created a basic webpage explaining the core functionality of the app and incorporated a ‘sign up now’ button. With a few social media ads we should be able to gauge whether enough people really would use our product by the number of sign up now clicks we receive. These clicks will tell us whether our idea is worth building and give us some data around cost of acquisition — far more useful than somebody telling us they would <em>definitely </em>use the app over a cup of coffee.</p><p>Why not you think of ways you could test the market demand for your revolutionary idea. <strong>Next week </strong>we’ll write about the different types of pretotyping including the Pinocchio, the mechanical turk, the one night stand and the impersonator. Stay tuned!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8771bf668e43" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>