<?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 Pantelis Korovilas on Medium]]></title>
        <description><![CDATA[Stories by Pantelis Korovilas on Medium]]></description>
        <link>https://medium.com/@pantelisak?source=rss-6a0b0c1e0c3d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FRtWF-XmRO1xzaZAG6C6kQ.jpeg</url>
            <title>Stories by Pantelis Korovilas on Medium</title>
            <link>https://medium.com/@pantelisak?source=rss-6a0b0c1e0c3d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:50:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pantelisak/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[The Case for Solving Core Problems]]></title>
            <link>https://medium.com/@pantelisak/the-case-for-solving-core-problems-bcb58678470f?source=rss-6a0b0c1e0c3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcb58678470f</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[checkout]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Pantelis Korovilas]]></dc:creator>
            <pubDate>Wed, 23 Sep 2020 15:02:12 GMT</pubDate>
            <atom:updated>2020-09-23T15:02:12.542Z</atom:updated>
            <content:encoded><![CDATA[<p>If you don’t already, you should know <a href="http://fast.co/">Fast</a>. Fast solves a core problem with the internet that you likely deal with all the time. In fact, I recently left a promising role and a great team as Senior Director of Product Design at Turo, the Airbnb of cars, to join them.</p><p>People often ask me why I left. I was happy there. And Fast is a Series A startup, so I’m choosing a higher risk opportunity, to be sure. But let me tell you why I believe it is also a higher reward one, why you should be as excited as I am about Fast, and why the desire to solve core problems, rather than symptoms, is at the center of it all.</p><h3>Symptom One: Hopper</h3><p>For this to make sense, I have to go all the way back to the summer of 2015, when I was working on a new product called <a href="http://www.hopper.com/">Hopper</a>.</p><p>Hopper was using big data to predict the future price of airfare, so you could book plane tickets at just the right time. This could save you money and provide the confidence that you scored the best deal. It was pretty cool, and our customers loved it. As a mobile-only product, one reason for our success had to do with the state of buying a flight on your mobile phone at the time:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JRMAZsLkWtNGJpdQRtyxgQ.png" /><figcaption>Booking a flight online required you to go through a lot of steps, and see a lot of information.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-OdAhmp2eH0L3QuNhgVSJA.png" /><figcaption>Sometimes airline websites weren’t mobile friendly, so you had to pinch and zoom to find what to do.</figcaption></figure><p>You’ve probably been here yourself at one point. The process of buying a flight online was long and drawn-out. There were a ton of form fields to fill out. The airlines each wanted to “own” the relationship with the flyer, so it felt like you were always filling in the same information time after time with each one — name, email, phone, etc. The consumer doesn’t care if the airline wants to own the relationship. They want the best flight for them, in as few steps as possible. But, airlines had no incentive to share this information with each other, and the customer was the one that suffered.</p><p>Back then, working at Hopper, we didn’t think that made sense, and so we built this: QuickTap booking, where you could book a flight in 4 taps on your phone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ida2ABXVB_a6QcdCgNxseg.png" /><figcaption>Hopper’s QuickTap Booking</figcaption></figure><p>And when you came back, if you wanted to fly a different airline because you found a better departure time or price, you could do it again in 4 taps, without repeating any of your information. Hopper created the Amazon experience for repeat purchasing of flights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xnSfnd0hZSND4AT7vIsImA.png" /><figcaption>You could buy a flight with 4 taps using Hopper’s QuickTap Booking.</figcaption></figure><p>How? Well, first we allowed you to use the same information regardless of what airline you booked with. But, another thing we realized early on was that so many of the fields the airlines are asking you to fill out are not made with you in mind — they are made for the airlines. Airlines want to collect more of your data. They want to use it for remarketing and to convince you to only book with their airline going forward. If you remove those self-indulgent asks, what was really required for you to legally buy a flight was far less.</p><p>The Airline’s incentives were misaligned with yours, however. This is where Hopper comes in. As a neutral third party, Hopper can think beyond the individual motivations of any one airline and build something that just makes it easier to book flights generally. What we created was pretty neat, and it allowed you to quickly snag those great deals that Hopper was helping you find, regardless of where they came from. I wrote about it <a href="https://medium.com/@pantelisak/butt-booking-7b1e7f79fe84">here</a> — and people really liked what we were building.</p><p>But, what I didn’t yet realize, is that I should have been building Fast.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lSRLpDoP18woGLw9NWmuXQ.png" /><figcaption>Fast replaces a lot of steps products try to build themselves, and allows customers to re-use this information on other products.</figcaption></figure><p>It was clear I didn’t realize this because I would go on again to try and solve the same problem for another individual product and vertical. This time it was for Turo, the Airbnb of cars.</p><h3>Symptom Two: Turo</h3><p>As Senior Director of Product Design, I led the Guest team at <a href="http://www.turo.com/">Turo</a>. The guest team designed all the products associated with people who wanted to borrow cars from others, our hosts, on the platform. I was passionate about solving many things at Turo, but reducing the many steps in our checkout flow was a major one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tyvthRS1kGnegny4wdTZaw.png" /><figcaption>www.turo.com</figcaption></figure><p>Renting a car is risky, and fraud and insurance complicate the user experience requirements to maintain a safe platform. This, along with marketing requirements, a low bar from the competition, and no one owning the end-to-end experience of checkout, led to a bloated user experience.</p><p>There were upwards of 20 steps to book a Turo. You had to verify your ID, enter lots of information, and add the same information multiple times, among other user experience offenses. Why? It was in many ways a symptom of how we built at the time: compromising a cohesive experience for individual team goals.</p><p>Let me give you an example. Turo’s Insurance teams have the incentive to want friction during the checkout process to ensure your identity is safely verified before giving you the keys. However, this made you more likely to leave the app before finishing booking. That, in turn, would naturally make marketing worried this would cause a drop-off in the funnel before they could capture your email for remarketing. This tension made a booking on Turo feel fragmented. It felt like two separate teams building two independent solutions and only sticking them together at the end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ovMdIx1CW7bJdpHPmeVO3Q.png" /><figcaption>Turo’s sign up and booking funnel required Guests to enter their first and last name twice, and asked for your email, only to reconfirm and verify it later in the flow, after you thought you were done with it.</figcaption></figure><p>The consumer doesn’t care if Turo wants your email for marketing. They want the best car for them, in as few steps as possible. Our design team was convinced it could have been simpler, however. So, our talented Guest team explored how to do just that, designing solutions that would reduce steps and make everything feel more unified and cohesive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5keRmTvrtg_gxyNEpvWoMA.png" /><figcaption>Reducing steps in Turo’s booking flow.</figcaption></figure><p>We made some inroads on solving this problem for Turo. But, again, what I really should have been doing was building Fast.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*npMLxiiExrW0gYlU0LZOcg.png" /><figcaption>Fast replaces a lot of steps products try to build themselves, and allows customers to re-use this information on other products.</figcaption></figure><p>Why? Well, a theme was starting to emerge for me: incentives were often misaligned for individual companies to solve the more general problem of complicated checkout funnels.</p><h3>The Core Problem</h3><p>Companies had incentives to offer you great products and services but, when it came to you giving them your money for it, other goals got in the way of them making that easy for you:</p><ul><li>Departmental silos satisfied individual team goals but at the expense of a unified and efficient overall user experience</li><li>The desire to capture unnecessary data, that only served the business, made steps longer for the consumer</li><li>The desire to “own” the customer relationship resulted in companies not sharing your information with competitors or other, unrelated product and service categories, creating duplicate steps across sites and stores</li></ul><p>In other words, no one is solving the core problem of how to share your information safely, across multiple products, services, and sites. No one is solving how to do so quickly and efficiently, while only taking what it needs to make the transaction. We are all solving the downstream symptoms: how to buy and re-buy an American or United Airlines flight; how to buy and re-buy any flight on Hopper; how to book and re-book cars on Turo. This is resulting in worrying trends in e-commerce user experience.</p><p>Customers often have to complete over 12 fields to complete the average e-commerce funnel [1], despite tests showing reducing form fields from 11 to 4, for example, can result in a 120% increase in conversion [2]. As a result, e-commerce sites convince only about 3 percent of visitors on average to complete checkout [3]. Passwords are forgotten, reset, forgotten again. Emails, credit cards, names, are all typed, re-typed, and typed again, time after time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QBc84tIO8nzVFT8kY870Hw.png" /><figcaption>Websites ask for a lot of the same information: email, first and last name, address details, card details, delivery preferences, etc.</figcaption></figure><p>No wonder it has become so much easier to book on Amazon. At least they know my name; my address; my shipping preferences. Why set up a new account on some site I have only been to once, when I can instead look on Amazon and enter none of those everyday pieces of information? But the problem that this creates is it leaves out all the other small businesses, or retailers, who don’t put their merchandise on Amazon. That limits our options as consumers. So, where does that leave us in all this? Who is going to solve <em>our</em> problems?</p><h3>The Fast Solution</h3><p>Fast forward (pun intended) to the summer of 2020 when I met Fast’s two founders Domm and Allison, and when I realized people were trying to solve this exact problem. People were trying to solve this as a core issue for the internet, not just via the numerous and narrow symptoms. And they were talented, experienced people too: from Uber, Visa and HotelTonight, to name a few. A recent funding round led by the payments giant Stripe [4] also added to their industry expertise.</p><p>Domm and Allison were building one-click login and check out for the entire internet, and they aptly called it Fast. <a href="http://fast.co/">Fast</a>, now live to the public, allows you to carry your identity with you across the internet, wherever you want to log in or buy something. This reduces the need to input the same information, specify the same preferences, and create the same account with the same name, each time you want to do something online.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bSs8wM0llXLF-Se1EXk-gA.png" /><figcaption>Fast goes straight from pressing the button to checking out, making the booking experience truly one-click, while allowing you to make changes after booking after, if you need to.</figcaption></figure><p>By solving this problem directly, Fast makes the internet easier, and, well, faster. Not just to log in or check out, but to do all sorts of other stuff it enables, like tracking packages from multiple online stores all in one place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BjOekaMFXoK6W6ZPxu6zHA.png" /><figcaption>You can track delivery for all your orders made across different websites in one place: Fast.co</figcaption></figure><p>It enables you to change and use your address, credit card, or phone number in just one place while using it with hundreds of online stores across the internet too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I-WHq7U-9B0E2QQ9RFwTvQ.png" /><figcaption>Information you often repeat can be shared, securely, across multiple products and sellers, so you can only enter it one time.</figcaption></figure><p>Or it enables you to re-purchase products from different websites in one place, without needing to go back to the individual sites you bought them on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZlzICo1ci0uxTSSW4ZO2Og.png" /><figcaption>Fast Reorder allows you to re-purchase directly from Fast, instead of needing to remember the website or to log back in with another forgotten password.</figcaption></figure><p>And that is just scratching the surface. The possibilities are nearly endless. One-click government forms. One-click flights. One-click event registrations. One click movie steaming. One-click dinner.</p><p>When I heard the vision, it clicked. I realized that Fast can think more freely about new ways to solve the problem precisely by focusing on the core issue, not the symptoms. Others limit their thinking from the start by solving the problem only to support existing businesses: like buying flights, or cars. In this way, Fast can make e-commerce better for everyone, not just one product, service, or vertical.</p><p>This is why I am so excited to join the team at Fast. And why what we’re building is going to be worth keeping your eyes on. So, buckle up, we’re in for an exciting ride, and I want to take you with us. How? There are few ways for you to join us on this journey:</p><ul><li>Sign up at<a href="http://fast.co/"> fast.co</a> and start logging in or buying in one-click wherever you see a Fast Checkout button!</li><li>Follow our Design team on <a href="https://dribbble.com/fast">Dribbble</a>, where we will be sharing our design journey building the product</li><li>Follow <a href="https://twitter.com/fast">Fast</a>, <a href="https://twitter.com/domm">Domm</a>, <a href="https://twitter.com/abarrallen">Allison</a>, and the gang on Twitter</li><li>Look for jobs at <a href="http://fast.co/careers">fast.co/careers</a> if you want to be a part of the fun! We’re hiring Designers, Engineers, PMs and more!</li></ul><p>It’s 2020; check out should be faster, safer, and easier. We’re ready to go Fast. Are you?</p><p>—Pantelis (PK) from Fast, on twitter at <a href="https://twitter.com/pantelisak">pantelisak</a></p><p><strong>Sources:</strong></p><ol><li><a href="https://baymard.com/blog/checkout-optimization-from-16-fields-to-8">https://baymard.com/blog/checkout-optimization-from-16-fields-to-8</a></li><li><a href="https://unbounce.com/conversion-rate-optimization/how-to-optimize-contact-forms/">https://unbounce.com/conversion-rate-optimization/how-to-optimize-contact-forms/</a></li><li><a href="https://www.crazyegg.com/blog/ecommerce-conversion-funnel/">https://www.crazyegg.com/blog/ecommerce-conversion-funnel/</a></li><li><a href="https://techcrunch.com/2020/03/26/stripe-leads-20m-series-a-into-fast-which-is-building-a-universal-checkout-service-for-e-commerce/">https://techcrunch.com/2020/03/26/stripe-leads-20m-series-a-into-fast-which-is-building-a-universal-checkout-service-for-e-commerce/</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcb58678470f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Users Don’t Want Filters, They Want Better Content]]></title>
            <link>https://medium.com/sketch-app-sources/users-dont-want-filters-they-want-better-content-80f2958a2a96?source=rss-6a0b0c1e0c3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/80f2958a2a96</guid>
            <category><![CDATA[content]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Pantelis Korovilas]]></dc:creator>
            <pubDate>Sun, 18 Nov 2018 19:05:37 GMT</pubDate>
            <atom:updated>2018-11-18T19:05:37.822Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ux_jPBlGNJ1XITB-yVi_Zw.jpeg" /></figure><p><strong><em>This article was </em></strong><a href="https://medium.com/@hopper_travel/users-dont-want-filters-they-want-better-content-3146f650b8f6"><strong><em>originally posted</em></strong></a><strong><em> on Hopper’s Medium account.</em></strong></p><p>I thought I understood this comment — by User Experience veteran Don Norman — until a recent project I designed taught me otherwise.</p><blockquote><em>“[…] never solve the problem I am asked to solve. […] Because, invariably, the problem I am asked to solve is not the real, fundamental, root problem.” — Don Norman in </em><a href="http://www.amazon.com/Design-Everyday-Things-Donald-Norman/dp/1452654123"><em>The Design of Everyday Things</em></a></blockquote><p>The ability to narrow down flight search results by hiding undesirable flights was one of the most asked for features on the Hopper app for much of the product’s first year of existence. Preoccupied with product/market fit and validating our core business, we made no progress that first year. But filters were always in the back of our minds.</p><p>When we finally shipped the feature, however, we realized that filters weren’t what users wanted at all. They wanted something much more basic: content that was relevant to their unique situation, with the minimal number of steps required to get it. Giving our users what they wanted taught us this lesson the hard way.</p><h3>Give The Users What They Want</h3><p>The <a href="http://www.hopper.com/">Hopper</a> app analyzes billions of flight prices every day to predict when to fly and when to buy plane tickets to score the lowest fare.</p><p>The app can predict — insanely accurately — if you should buy your tickets now or if you should wait. It does this based on historical prices. If you should wait, you can press a “watch” button and the app will literally watch the flight prices for you. When the price hits its expected “good deal” range, the app will send you a push notification to buy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jomgAWp6k9-XpdF6ksdUyg.jpeg" /></figure><p>Since the early days of Hopper, users wanted more control over what we notified them about. And they were not shy about telling us:</p><h3>Ben Dalziel on Twitter</h3><p>@hopper is there a way to watch a flight with a maximum number if stops? flying with kids makes that a deal breaker</p><h3>Cooper Marcus on Twitter</h3><p>@hopper please allow me to filter results to those X hours longer (or Y% longer? Or Z $/hour longer?!) than the shortest flight option</p><h3>Peter Wu on Twitter</h3><p>@hopper there should be a feature that allows you to block certain airlines from results - otherwise prices can be misleading</p><p>At the time, our price notifications only informed users about the lowest available price. Sometimes, that price could be the result of a low-cost carrier or a bare fare, with lots of added fees. Sometimes, it was because a flight had very long layovers (upwards of 18 hours, at times) or several unnecessary stops.</p><p>If a user didn’t want to book these kinds of flights, we were sending them content that was less relevant to them. For example, we could notify a user about a price dropping to $125 for a flight with a long layover. At the same time, the cheapest flight with short layovers could be $250. How disappointing to receive that notification, only to find out the price is $100 more for the kind of trip you’re willing to take.</p><p>But the situation is even more complicated. After an analysis by our Data Science team, we learned that the prediction we provide could also vary. For example, we could predict you should wait to buy a flight from Chicago to Las Vegas with stops. But, if you exclude stops, we may tell you to buy now, because these are at a good price range and are going to rise soon.</p><p>Regardless, less relevant content meant more noise for our users, less value from our solution, and lower conversion rates. We couldn’t ignore this problem any longer. We had to give the users what they wanted.</p><h3>Focused Filters</h3><p>Filters are not a new concept. There are countless examples of this in travel and e-commerce.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IDtEVEsCW40zw4cDJDq7gw.jpeg" /><figcaption>The filters menus of various flight search apps: Kayak, SkyScanner, and Hipmunk</figcaption></figure><p>We decided not to re-invent the wheel and planned for a simple “filters” button in the app. This button would trigger a filters list, where users could apply what they wanted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7uoxRR2RCHxtKVgPtAwmew.jpeg" /></figure><p>Given that our app predicts prices, new filters could have an effect on our data coverage and prediction accuracy. So, we had to be very careful in our implementation.</p><p>Some digging taught us that over 80% of filter requests would be addressed with only 3 filters:</p><ol><li>Remove Basic or “Bare” fares from low-cost carriers</li><li>Remove Stops</li><li>Remove long layovers</li></ol><p>By focusing on these three filters only, we could provide the same level of prediction accuracy as without filters. This also allowed for a simpler and more focused filter set, which fit our app’s goal of a concise and mobile-first user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QvWY_AoOAPjVOl_hrus5AQ.jpeg" /></figure><h3>Ship It!</h3><p>We were happy to build something that felt “Hopper” in its simplicity, and to fulfill a major user request. Once we released filters, we sat back, waiting for the love and praise to pour in. <a href="https://news.fastcompany.com/hoppers-new-filters-make-it-easier-to-book-the-cheapest-most-optimal-flight-4020508">Fast Company even wrote about it</a>, using the flattering headline: “Hopper’s new filters make it easier to book the cheapest, most optimal flight.”</p><p>To our surprise, what followed was a bit anticlimactic. After letting the dust settle, we found a dismal 2.6% of our total watches had filters applied.</p><p>We were a bit confused and disheartened. Were we mislead about the importance of this feature by a small and vocal minority of users? Was our implementation not discoverable enough? We had a large button earlier in the flow, but maybe users expected to apply filters later, on the flight list. We had reduced the size of the CTA on these screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LiSg10fzKdx-BE5NmJlmdQ.jpeg" /></figure><p>But, we also had another data point. We found out that filtered watches had higher conversion rates than unfiltered ones. This was the motivation we needed for another go; this time, to increase adoption.</p><h3>I Get By With A Little Help From My App</h3><p>To make sure users weren’t missing the feature completely, we knew we could make the button larger and more prominent in the interface. There was also an opportunity to add custom onboarding for the new feature. But, a more interesting approach came from one of our Product Managers. Instead of making the button to filters easier to find, could we make the filters themselves easier to find?</p><p>Hopper is already known for providing tips and suggestions, not just a list of options. Could we make filters a tip and a more integrated part of the interface? To do so, we placed a new card on the prediction screen to suggest filters based off of the user’s unique route. We would use dynamic copy to help them weigh the financial trade-offs of applying the filters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EhGApYe3Jit1YD0DxX6B5A.jpeg" /></figure><p>To apply the suggested filter, the user simply tapped a button, right in thumb’s reach. Instead of going to the filters screen, we automatically applied the filter on tap. If there was another filter worth suggesting, we would display that one next. Tapping it would then apply the new filter too. Every time a filter was applied, we updated the user’s watch with the new settings. No need to enter a menu, no need to scan a list of options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pkKWao_Htn84vrqSMmRZYQ.jpeg" /></figure><p>After releasing the new format, we saw the number of watches with filters go from 2.6% to over 23%! The change resulted in a nearly 10x increase in our conversion rate. That was more like it.</p><h3>Give The Users What They [Don’t Know They] Want</h3><p>In product design jargon, one might conclude that what happened here was simple. We improved the discoverability of filters by exposing them, one by one, via a new, hard-to-miss card. We improved the value of filters by showing that nonstop flights or short layover flights were not always more expensive. And, we reduced friction by not forcing users into a new screen, with several more taps to apply filters, but rather by applying them in a single tap.</p><p>This is definitely a good product design explanation, with a lot of truth. What we created the second time was simply a better solution.</p><p>There is, however, also a more human explanation: People don’t want filters. They don’t want a list of even more options to sort through. People want better, more relevant content and help making difficult trade-offs, in as few steps as possible. Can you blame them?</p><p><em>-Pantelis Korovilas (</em><a href="https://twitter.com/pantelisak"><em>@pantelisak</em></a><em>), Head of Design at Hopper</em></p><p><em>You can find</em> <a href="http://www.hopper.com/"><em>Hopper</em></a> <em>for iOS on</em> <a href="https://itunes.apple.com/us/app/hopper-airfare-predictions/id904052407?mt=8"><em>the App Store</em></a><em>.</em></p><p><em>Interested in becoming part of the Hopper team?</em> <a href="http://www.hopper.com/corp/jobs.html"><em>Click on our Jobs page</em></a> <em>for more information and to apply.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80f2958a2a96" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sketch-app-sources/users-dont-want-filters-they-want-better-content-80f2958a2a96">Users Don’t Want Filters, They Want Better Content</a> was originally published in <a href="https://medium.com/sketch-app-sources">Design + Sketch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing Goal-Oriented User Onboarding in 4 Steps]]></title>
            <link>https://medium.com/@pantelisak/designing-goal-oriented-user-onboarding-in-4-steps-8b076a38a837?source=rss-6a0b0c1e0c3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b076a38a837</guid>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Pantelis Korovilas]]></dc:creator>
            <pubDate>Mon, 02 Jan 2017 20:51:58 GMT</pubDate>
            <atom:updated>2017-01-02T20:51:58.092Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*N5F5OUlelU3EJ67E.jpg" /></figure><p><strong><em>This article was </em></strong><a href="http://www.appcues.com/blog/designing-goal-oriented-user-onboarding"><strong><em>originally posted</em></strong></a><strong><em> on the </em></strong><a href="http://www.appcues.com/blog"><strong><em>AppCues Blog</em></strong></a><strong><em> on Nov 22, 2016</em></strong></p><p>We product designers have been seduced by trends. The prevalence of welcome messages and product tutorial screens in user onboarding has created the illusion that they are the best means of getting users to your Aha! moment, but they are just one approach of many.</p><p>Choose the right approach and actively show users that your product or service is a must-have experience. Choose the wrong approach and create friction just as they are deciding whether or not to make your product a part of their lives. Given that the average app can <a href="http://www.appcues.com/blog/3-cringeworthy-stats-on-customer-retention/">lose up to 86% of its users</a> in the first use, the stakes are high.</p><p>Thankfully, thinking through the lens of “Goal-Oriented Onboarding” can help you identify the right actions to build your onboarding around and pick the right approach, all in the name of driving users to your core value as efficiently as possible.</p><h3>Avoiding the Tutorial Trap</h3><p>Google “app onboarding” and you’ll see endless pictures of attractive welcome or tutorial screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*NCILZM03IaZzHVqd.png" /></figure><p>There’s a lot to admire in a good welcome screen — they’re often beautifully designed, with nice use of color, imagery, and concise text. Since they are added at the beginning of your app’s experience, designing tutorials can offer a lot of creative freedom for designers and can be implemented with minimum disruption to your core interface or user flows.</p><p>But the tutorial screen’s popularity and often beautiful execution can give the wrong impression: onboarding isn’t a particular type of screen, but the <strong>strategy you employ to get your users to discover your app’s core value quickly and efficiently.</strong>User onboarding helps you convert new users into regular users before losing them for good. And tutorial screens are not always the most effective tool for the job.</p><p>Many teams discover that users just swipe “through the tutorial without reading any of the copy,” <a href="http://apptimize.com/blog/2015/10/vevos-app-defies-user-onboarding-best-practices-heres-why/">as Vevo found</a> through user testing. A participant for a RetailMeNot user test <a href="https://www.smashingmagazine.com/2014/04/rethinking-mobile-tutorials-which-patterns-really-work/">once said</a> “I just want to get in the app and start exploring.”</p><p>I’ve received similar user feedback at <a href="http://www.hopper.com/">Hopper</a>. If users are not engaging with the content but just swiping through your onboarding screens, you are adding friction and risk undermining your product’s true value.</p><p>I call this the Tutorial Trap: any instance in which we apply an onboarding UI pattern without clear goals in mind and without an understanding of their effectiveness. The trap is that it focuses on the means over the ends with potentially tragic results.</p><p>Goal-Oriented Onboarding, or GOO for short, can help you avoid the Tutorial Trap. GOO has four key steps:</p><ol><li>Drive users towards specific, key actions</li><li>Focus your product around onboarding first</li><li>Add new UI where it’s most needed</li><li>Analyze, adjust, and repeat</li></ol><p>Focusing on GOO will help you design a user onboarding experience that not only looks beautiful, but will also drive results for your business.</p><h3>1) Drive Users Towards Specific, Key Actions</h3><p>A <a href="http://www.appcues.com/user-onboarding-academy">good onboarding experience</a> makes it as easy as possible for new users to take meaningful actions. For actions to be considered meaningful, you should have an opinion (or a best guess) as to what steps are most impactful for user activation and eventually your business.</p><p>You’ll want to combine whatever qualitative and quantitative data you have to identify these steps, with the aim of further validating or invalidating your understanding of what drives user success.</p><p>Don’t go too far down the funnel to find your key actions. The steps you want to drive users towards in onboarding aren’t necessarily your main conversion metrics. You’ll want <a href="http://andrewchen.co/the-next-feature-fallacy-the-fallacy-that-the-next-new-feature-will-suddenly-make-people-use-your-product/">“day one” actions</a> that are low-effort, high-value.</p><p>At <a href="http://www.hopper.com/">Hopper</a>, booking a flight is our ultimate conversion, but is too high of a commitment to expect from a first-time user. Booking also isn’t really a good expression of our value prop either, which is predicting when users should fly or buy their plane tickets to get the lowest fares. Our airfare predictions often recommend waiting to book to take advantage of a price drop later.</p><p>The ability to make good on the promise of a future cheap fare, and help users save money, is our real Aha! moment. Buying on first use might obscure this, despite being one of our core success metrics in the user lifecycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*s1l2AWCSAsvJJyLo.png" /></figure><p>Instead, our onboarding action is what we call “watching”, where users decide to follow prices so that they’ll be notified when prices hit the predicted low. It is a much lower commitment and we can drive users to it in just a few steps. It also gives us permission to contact them about something they are interested in later, ensuring future value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*sArTZgFp8wmQgUtq.png" /></figure><p>Your most effective actions might not be what you initially expect, so you may have to experiment a few times before getting it right.</p><h3>2) Focus Your Product Around Onboarding First</h3><p>Once you have identified a potential action to focus on, don’t start adding onboarding UI patterns just yet. First, make sure your product is as supportive of your onboarding journey as it can be.</p><p>I like to start by making an onboarding list of the steps users currently have to take to perform these key actions. Once I have a list, I analyze where it is too long, or too complicated, and see if there is room to remove steps or make the intended actions clearer or more compelling along the way.</p><p>A good range to aim for is anywhere between 3–7 steps as suggested in the concept of “<a href="https://www.nngroup.com/articles/chunking/">chunking</a>”, for easy cognitive processing and memorization. While there are certainly exceptions to this rule, having too many steps will overwhelm users or obfuscate your main point.</p><p>For Hopper, we got our list down to only three steps users needed to do to perform our key action:</p><ol><li>search for an origin and destination</li><li>select travel dates</li><li>press the watch button on the prediction screen</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*M8XkZNgS7KDwWbpN.png" /></figure><p>For this to happen, we had to ensure that the search screen was the first one users saw on install, the search action was obvious to perform, it was really clear how to select dates, and the watch button was the most prominent on the prediction screen. This required altering our existing screen’s layouts, interfaces, and interactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*soo0qMR8Muugcopn.png" /></figure><p>You’ll have to weigh trade-offs in making such core app decisions, but, if you can, doing it up front will help both your onboarding <em>and</em> overall app experience.</p><h3>3) Add New UI Where It’s Most Needed</h3><p>When you feel your app is doing the best it can to help drive first-time users to ideal behavior, test it. Put it in front of people and see where they get distracted or confused.</p><p>Whatever you did in the previous step is still likely too subtle, and testing it at this stage will help surface how you can reinforce it. This doesn’t need to be incredibly time consuming; you’ll likely pick up on key trends pretty quickly, <a href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">in as few as 5 users</a> for some.</p><p>Take what you learn and use it to fill in the onboarding gaps left in your product with new UI patterns specifically for first-time users. There are plenty of <a href="http://www.appcues.com/blog/we-categorized-327-user-onboarding-experiences-into-9-ui-patterns/">interface patterns</a> to chose from — aim for the methods that best communicate your value and drive users to your key actions.</p><p>For Hopper, we found action-driven tooltips were just the thing we needed. These UI elements lay on top of the app interface, with an arrow pointing to a key element, and prompt a desired action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*DVxM_PSg8xH2xf9Z.png" /></figure><p>We used one tooltip for each of the three steps in our onboarding flow, pointing out the one action that would move them to the next screen.</p><h3>4) Analyze, Adjust, and Repeat</h3><p>Building your onboarding flow isn’t enough. Make sure to have a plan for <a href="http://www.appcues.com/user-onboarding-academy/what-to-measure/">event tracking and analytics</a>. This insight will help you know if you did in fact build your onboarding around the right action(s) in step 1, or if you should refine your flow further in steps 2 or 3.</p><p>Onboarding is not that different than building a product more broadly; you should be prepared to hypothesize, iterate, test, and adapt quickly based off of what you learn.</p><h3>Focus On Ends Over Means</h3><p>Welcome screens are the means, not the end of user onboarding. They are one tactic of many to drive users to high-value actions that keep them coming back for more. Goal-Oriented Onboarding is a simple way to think about how to approach user onboarding to achieve tangible goals and choose only the right tools for the job.</p><p>If you focus on getting users to perform low-effort, high-value actions right away, you will have a higher chance of getting them to make bigger commitments later as they engage deeper in the product.</p><p>There is no one-size fits all scheme for onboarding, so this will likely need some care and iteration, but doing so will put you a step ahead of much of your competition. Design with intention; design with goals in mind.</p><p>— <a href="https://medium.com/u/6a0b0c1e0c3d">Pantelis Korovilas</a> (<a href="http://www.pakdsgn.com/">pakdsgn.com</a>), Lead Product Designer at Hopper</p><p><a href="http://www.hopper.com/"><em>Hopper</em></a><em> is an award-winning mobile app that offers airfare prediction to help you buy your plane tickets at the best times.</em></p><p><em>We’re hiring a Mobile Product Designer to join me at Hopper! </em><a href="http://www.hopper.com/corp/jobs.html"><em>Click on our Jobs page</em></a><em> to apply and for more information.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b076a38a837" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Butt-Booking]]></title>
            <link>https://medium.com/@pantelisak/butt-booking-7b1e7f79fe84?source=rss-6a0b0c1e0c3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b1e7f79fe84</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Pantelis Korovilas]]></dc:creator>
            <pubDate>Thu, 08 Dec 2016 16:49:13 GMT</pubDate>
            <atom:updated>2016-12-08T16:49:13.448Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Or, How to Accidentally Sell Things on Mobile</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jwrFBN9RZ3fwxvmvClpEUw.jpeg" /></figure><p><strong><em>This article was </em></strong><a href="https://medium.com/@hopper_travel/butt-booking-2e035113bc3#.16t58qa1v"><strong><em>originally posted</em></strong></a><strong><em> on Hopper’s Medium account on Oct 30, 2015</em></strong></p><p>The <a href="http://www.hopper.com/">Hopper</a> app analyzes billions of flight prices daily to predict how they are going to change and when are the best times to fly, and “watches” flights to notify you when to buy your tickets.</p><p>As outlined in <a href="https://medium.com/@hopper_travel/the-notification-problem-50267cbabad2#.yqaxq55in">The Notification Problem</a>, “watching” is a central part of Hopper’s product strategy. Watching a trip is a really useful tool for savvy travelers: It means they can go on living their lives while we do the heavy lifting of keeping an eye on their trips’ prices and notifying them when prices drop to our predicted low (as well as alerting them about good deals and flash sales). And for us, the feature has important engagement hooks, as users who watch a flight are much more likely to return to the app than those who do not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Y2F5-63oHHK2T3MreaN2A.jpeg" /></figure><p>But what is the ultimate point of watching and engaging with the app? Users watch trips so that they can get a good deal or the lowest price on airfare, meaning that they (usually) intend to book the flights they watch. Focusing our energy on improving the front of the flow — i.e., watching — helped <a href="http://appcues.com/academy/wow-tactics/">reduce “our time to WOW</a>,” driving up short-term engagement and retention metrics. But these efforts only served half of our app’s use cases. Addressing the back of the flow and how users “lock in” their good prices will in time decide our long-term usefulness, retention, and “completeness” on mobile. So we set out to improve our booking handoff, or how we transition the user from shopping to buying.</p><h3>The Importance of Handoffs</h3><p>As we mentioned in “<a href="https://medium.com/@hopper_travel/waiting-is-the-hardest-thing-b340626ff123#.dnpevbp6o">Waiting is the Hardest Thing</a>,” good flight prices are often found as a result of volatility and can change from hour to hour. This means that when Hopper sends users push notifications about prices reaching their predicted lows, they have a short and often unknown window until those prices fluctuate again. Users can lose out on a great deal if they do not act quickly, and, in a worse case scenario, pay more than if they would have just bought that flight earlier. Anything that limits the ability of the user to act decreases the chance of them locking in the prices we predict.</p><p>A user not getting a good price or paying more than when they started watching a trip risks the user’s overall experience buying flights. Even if this isn’t a result of the quality of our prediction and notifications — our core app features — the user is still likely to associate our product with the negative feelings of that experience. Limiting that risk became a priority, and our existing handoff limited the user’s ability to act and lock in a good deal.</p><h3>The Problem with Handoffs</h3><p>Not unlike Kayak or Hipmunk, for example, our existing handoff linked users to a web view of the site where the prices were found (often the airline or an online travel agency). From there, the user would fill in the forms and complete the booking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8m_phaQFVottHx67m0iegQ.jpeg" /><figcaption>The Kayak iOS app’s booking handoff.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZzsYHqwJBxSXtYEoYyjhEA.jpeg" /><figcaption>The Hipmunk iOS app’s booking handoff.</figcaption></figure><p>The problem with loading a web view was that the process was often slow, and by “exiting” the user from the app into the web, we lost control of the quality of the user experience on all fronts. Many airline’s websites are not optimized for mobile and are extremely frustrating to use; they increase the amount of time it takes to book on mobile (vs. on the web) and they ultimately hurt our conversion numbers, as users abandon Hopper and either never book at all or book later (on mobile or on a desktop computer) at a higher price. As a mobile-only company, the idea of users needing to leave the app and re-search for the flights on their desktops or laptops stung. Moreover, the thought of missing a deal eroded our value prop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iAyE_3fPGSf42mUko68dVQ.jpeg" /><figcaption>The Skyscanner iOS app’s booking handoff.</figcaption></figure><p>Taking the user from the app and into the web also meant we lost out on important conversion data, such as how many users complete the process post-exiting as well as what parts of the booking funnel had higher or lower friction than others. This data could then help us create a better experience for the user overall. We were not only sending users into an unknown universe, but we were flying blind after we sent them.</p><h3>Amazon’s 1-Click Ordering</h3><p>The more we came to understand the problem we were trying to solve, the more we realized it was not just about how we build a booking engine. <strong>Rather, it was about whether or not we could ultimately build a better way to book flights on mobile</strong>. Could we actually <em>improve</em> the buying experience in the process? It was a lofty and intimidating goal for us.</p><p>We looked for other examples in airfare but were often disappointed in the mobile experience, with online travel agencies doing the very same thing from which we were seeking to distance ourselves. Booking with the airlines directly on mobile surfaced text-dense forms and content-dense screens that lacked focus and often failed to meet many best practices for usability and simplicity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YUX9ra8R776BeNODwADAtA.jpeg" /><figcaption>Booking from the American Airlines iOS app.</figcaption></figure><p>There were, however, interesting examples <em>ad nauseam</em> outside of airfare, with companies such as Airbnb, Uber, and Amazon creating successful and relatively painless e-commerce funnels. This led us to think, what if we could bring the simplicity of, say, Uber or Amazon to booking flights? Amazon has<a href="http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&amp;Sect2=HITOFF&amp;d=PALL&amp;p=1&amp;u=%2Fnetahtml%2FPTO%2Fsrchnum.htm&amp;r=1&amp;f=G&amp;l=50&amp;s1=5960411.PN.&amp;OS=PN/5960411&amp;RS=PN/5960411"> patented</a> the process of what they call “<a href="http://www.amazon.com/gp/help/customer/display.html?nodeId=468482">1-Click Ordering</a>,” which makes it easy to bypass the shopping-cart flow and buy an item immediately based off of payment and shipping information previously selected by the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tg9xQKXzuBE-Un8bYjCG8A.jpeg" /><figcaption>Amazon’s patented 1-Click Ordering.</figcaption></figure><p>We asked ourselves: What is our equivalent to 1-Click Ordering?</p><h3>Hopper’s QuickTap Booking</h3><p>After racking our brains over the question, we came to an answer that was so simple, so obvious, that it seemed almost silly: strip down the booking flow to its bare essentials.</p><p>The question that followed was, what are the essentials? We realized many fields or selectors in flight-booking flows were used for upselling, there to gain data for marketing or sales, or were carried over, seemingly blindly, from precedent. Much was superfluous. We figured, if we could pare booking down to its core elements, we would reduce friction and improve on the ease of use.</p><p>What we came to was simpler than we thought we could achieve, with two to three main steps: initial signup, choose travelers, and choose payment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ND7_8_GrZuU3471CMsQ3w.jpeg" /><figcaption>The core screens of the Hopper QuickTap Booking flow.</figcaption></figure><p>What this basic architecture did was allow us to make use of the principle of progressive disclosure, or<a href="http://www.nngroup.com/articles/progressive-disclosure/"> as the Nielsen Norman Group defines</a> it, deferring “advanced or rarely used features to a secondary screen, making applications easier to learn and less error-prone.” We were able to make the selection screens for the two core parts of the booking process refreshingly simple, with more info only when you need to add or edit your traveler or payment method.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0zRzpX21IRF1Nnu529JD2g.jpeg" /><figcaption>The Choose Traveler &amp; Payment screens, &amp; their associated edit views.</figcaption></figure><p>Entering your information is unavoidably more complex — even after doing our due diligence by removing extraneous fields — so we gave these screens a lot of white space to lighten them up. After entering this information once, users returning to the app could book again in less than a minute (or as fast as 15 seconds) without the need to re-enter or even see those form fields. The range depended on how prepared the user was when going through the flow, but one could easily go straight from their flight details to their confirmation screen in four taps!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aMElbopd6sFJCYWvJ_BuwA.jpeg" /><figcaption>QuickTap Booking allowed you to book flights in as low as 4 taps.</figcaption></figure><p>We called it QuickTap Booking, and we were really excited for how simple and lightweight it felt.</p><h3>Butt-Booking</h3><p>User and beta testing for this new flow confirmed our hopes, with user comments like “I LOVE the booking experience” and “It rules.” We didn’t anticipate, however, that it was possible to build a flow that was too easy when it was out in the wild.</p><p>Somehow, we achieved just that.</p><p>It was so easy, in fact, that despite language of “Pay Securely Now” on the button of the final screen, people actually booking flights expected another step in the process and would press the “Pay” button assuming there must be another screen after.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mpye83ptREwoVYsNngKsTg.jpeg" /><figcaption>Pressing “Pay Securely Now” booked the flight and charged the user.</figcaption></figure><p>Or, in a few instances, users would press the “Pay” button accidentally; we called this phenomenon butt-booking, just like the problem once reserved for dialing recent callers from the pocket of your pants. I even experienced this myself the first week of our release, and I designed it! Our Director of Communications, Brianna, did something similar, in which she left the payment screen up on her phone, had put her phone in her bag, and something pressed and triggered the “Pay” button. We were initially pleased, and then frightened, at how easy this process was.</p><p>We determined the combination of expectations set by other flight-booking engines for length and level of complexity, the lack of a significant differentiator for the blue “Pay” button from the buttons on screens immediately preceding it, and the ease of triggering its final state made our booking flow far easier than we expected … to a fault.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sQxnfYWy6X-Sx5zdcVMHAQ.jpeg" /><figcaption>The primary CTA buttons in the booking flow were treated the same, and didn’t visually express the significance of the “Pay Securely Now” action.</figcaption></figure><h3>Context, Security, and Friction</h3><p>Through the process of analyzing behavioral data, we also learned that we didn’t balance the bare essentials required to book a flight with the necessary level of information that would make people comfortable enough to book. We saw a lot of users jumping back and forth in the funnel, going from payment selection back to traveler information, back to trip summary, and forward again. This behavior suggested that users were going back to see information about their itineraries that they had forgotten in the process, likely fearful of losing their data when they returned. Some users dropped off the funnel completely before finishing. An unknown number of those users likely intended to book before they lost confidence and swiped back.</p><p>To address both the dangerous ease of conversion and the confidence issue, we opted to make an additional screen right after the payment step, in which a user could review all of the details of his or her flight.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8HmaXJwtjJYHtJ2QBEXQ8w.jpeg" /><figcaption>The Hopper Review Details screen.</figcaption></figure><p>Here we colored the payment button green to differentiate it visually from the blue buttons previously seen in the flow, to warn the user that they were going to take a more significant action than on previous screens. We also made it a swipe, rather than tap, interaction to decrease the number of accidental taps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KVlHVV36tetxGBnjGvX9jw.jpeg" /><figcaption>The “Swipe to Pay” button was given unique visual treatment to signal importance.</figcaption></figure><p>A lock icon replaced the words “securely” on the button so we could make room for the extra words associated with the swipe interaction. To set us up for the new screen, we relabeled the blue button on the prior screen to “Review Details.”</p><h3>Better Booking</h3><p>We were nervous that this added screen and friction would lead to a 10%+ decrease in conversion, but we were pleasantly surprised to see it comfortably below that margin, with a notable decrease in the amount of back and forth we were seeing before. We’ve also started to see a lower percentage of support resources tied up on accidental bookings. Put in the context of week-over-week growth in bookings, we are super excited about what we created with QuickTap Booking in iOS and are working hard to add it to Android soon.</p><p>This process made it clear that with determination, initiative and the right team, it <em>is</em> possible to build better e-commerce flows in mobile categories that are often neglected; for us, that was flights. In today’s mobile landscape, users reward it, so aim high, friends, aim high.</p><p>— <a href="https://medium.com/u/6a0b0c1e0c3d">Pantelis Korovilas</a> (<a href="http://www.pakdsgn.com/">pakdsgn.com</a>), Lead Product Designer at Hopper</p><p><a href="http://www.hopper.com/"><em>Hopper</em></a><em> is an award-winning mobile app that offers airfare prediction to help you buy your plane tickets at the best times.</em></p><p><em>We’re hiring a Mobile Product Designer to join me at Hopper! </em><a href="http://www.hopper.com/corp/jobs.html"><em>Click on our Jobs page</em></a><em> to apply and for more information.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b1e7f79fe84" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Notification Problem]]></title>
            <link>https://medium.com/@pantelisak/the-notification-problem-15267e968e38?source=rss-6a0b0c1e0c3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/15267e968e38</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Pantelis Korovilas]]></dc:creator>
            <pubDate>Mon, 28 Nov 2016 14:46:54 GMT</pubDate>
            <atom:updated>2016-11-28T14:46:54.331Z</atom:updated>
            <content:encoded><![CDATA[<p>To “allow” or not to “allow,” that is the question.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j_jQBvHA2rM4FwDdP_D-Pg.jpeg" /></figure><p><strong><em>This article was </em></strong><a href="https://medium.com/@hopper_travel/the-notification-problem-50267cbabad2#.w40hm9gdu"><strong><em>originally posted</em></strong></a><strong><em> on Hopper’s Medium account on Aug 17, 2015.</em></strong></p><p>The <a href="http://www.hopper.com/">Hopper</a> app analyzes billions of flight prices daily to predict how prices will change, and tells you when to buy your tickets.</p><p>The app can predict — insanely accurately — if you should buy your tickets now or if you should wait, based on future price predictions. If you should wait, you can press “watch” and the app will literally watch the flight prices until it hits its expected “good deal” range (a historically great price), before your departure date, and then it will send you a push notification to buy. Whoa.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r47ULlYR_mxwNYYvgfItZw.jpeg" /></figure><p>Our product team wanted more users to discover and understand the “watch” feature, and in turn, use it more. We were sure our numbers for conversion on this metric had not reached their peak and understanding users’ willingness to watch is an integral part of our product strategy. Given that the watch feature has important engagement hooks — i.e., a user who watches trips is more likely (by a significant multiplier) to return to the app and engage with it and other features — we wanted to make sure their first visit is set up properly and that they understood the value. We set out to improve our onboarding flow.</p><h3>The Notification Problem</h3><p>Notifications are really important to this “watch” concept. If the user doesn’t allow notifications for the app, they can’t receive our message that the price is at its expected low, completely undermining the power of the feature. Apple requires that you get permission from the user to send them push notifications, and restricts the firing of an iOS alert request to one time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2iSh8WFE0RYC1UEceRvF7g.jpeg" /></figure><p>If the user presses “Allow,” all is well. If not, it is really difficult for a user to change course — they must exit the app, go into settings, find notifications, find the app in a long list of apps, and then set their desired level of notification.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yBHw1VLJOCsLmEYBL5-1iw.jpeg" /></figure><p>No notifications means we could lose the user forever, so we needed to be really careful when triggering this one-time-use modal. Any “improvements” would need to take this into account.</p><h3>Existing Flow</h3><p>The current flow started with three educational screens in an “app tour” format to try and sell the value prop and functionality of the app; after, it sent the user off into the wild to use the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HXAsHocjFgCQJGks3Jwxpg.jpeg" /></figure><p>The problem with this was that reality had proven to us that most users didn’t want to sit and read even three short blurbs about the app — they wanted to get straight to doing. The content of these types of onboarding screens is often very general and detached from the actual places and interactions the user would be in or have with the user interface (UI).</p><p>One of these screens included our pitch for the Watch feature, but it said very little about the feature’s UI or notifications explicitly, nor their relationship to each other and iOS alerts. If users weren’t reading these messages, because there were too many and/or it wasn’t useful or timely information, that user would likely also not understand the Watch feature properly and its relationship to notifications, and thus not allow the notifications when prompted.</p><h3>Onboarding = Notifications</h3><p>We decided we would cut back on the initial tour screens, landing on two more practical messages: The first as a welcome and context to the overall app, and the second to focus on the value of notifications. Before the user lost interest, we would then let them into the wild of the app, contextualizing the rest of the content into small tool tips during the actual use, to improve its timeliness and usefulness.</p><p>I iterated quickly by sketching, with the top series of screens in the sketches below reflecting our initial solution:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Boq4LeSt-CKnIV3ycaL3FQ.jpeg" /></figure><p>Translated to our app’s UI, it looked like the below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NTO_7d0_4dAczPN9GvFz3w.jpeg" /></figure><p>For the notifications screen, we decided to test only one path forward: pressing the “Allow Push Notifications” button, triggering the iOS notification alert.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AQnJ_G6bQPO5ROAeL-tCgQ.jpeg" /></figure><p>Our hypothesis was that even though this was an aggressive gate to progression, that the button would (1) put more pressure on the user to read the tour copy before progressing, i.e., “What am I agreeing too?”, which may (2) increase awareness of the relationship between notifications, watching in the app, and saving money on Hopper — but even more importantly, we were curious if it would (3) lead to increased “allows,” despite letting potentially fewer users past onboarding. The ultimate result: a larger proportion of qualified users (users who have allowed notifications, thus benefiting from this powerful app feature) on the app.</p><h3>Lesson Learned</h3><p>This proved to be too heavy-handed. Further down the funnel, conversion metrics greatly improved — a much greater percentage of users were getting all the way though onboarding successfully and watching trips — likely attributed to the in-context tool tips later in the flow. But fewer people were actually getting to that point, as they either (1) dropped off right away on the notifications onboarding screen, or (2) pressed “don’t allow” on the iOS alert, even after pressing “yes” on our custom button for allowing notifications, then finding out they couldn’t watch a trip without visiting their settings outside the app. The net of this in our analytics was that we hadn’t lost any qualified users, but we also hadn’t gained any — we hadn’t improved the numbers, we just changed how we were achieving them.</p><h3>The Fork</h3><p>The simple lessons for us were that our users would not significantly read the onboarding screens, or even if they did and understood the content, they were not afraid to wait to “allow” us notification access until they had gotten a feel for the app first. For a user to press “allow,” they have to trust us not to abuse our newly granted power and understand the value of how we will use that power. Like our tool tips, we hypothesized that triggering the notification alert in context would increase those willing to do it, but we also didn’t want to restrict it until that moment in the app, further down the funnel.</p><p>We decided to keep the notifications screen but to instead add an “opt-out” button, forking the app to either (1) the users who don’t yet trust us and want to get a look around first, having read the copy or not and not triggering the iOS alert — allowing us to trigger it in context later — and (2) the user who were highly likely to press “allow,” triggering the modal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EEkk4qX8UmkrbR3_RYv4EQ.jpeg" /></figure><p>Within the existing flow, it looked something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PcQThrqSn8Sf9RwRjlYXgg.jpeg" /></figure><h3>Natural Onboarding</h3><p>This greatly increased the number of users who continued through to the rest of the onboarding process, while maintaining the higher back-of-flow numbers we achieved through the addition of in-context tool tips. Success.</p><p>I came away with resounding support for user onboarding that feels as natural as possible, to not feel as if it is a secondary part of the experience but as if it is part of the very fabric of the app. Our tool tips helped bring us closer to that goal, with positive effects on our user engagement. And trust, well, it takes time. Our willingness to allow users to take a look around, before being forced into deciding whether to do so or not, helped establish just enough of it.</p><p>— <a href="https://medium.com/u/6a0b0c1e0c3d">Pantelis Korovilas</a> (<a href="http://www.pakdsgn.com/">pakdsgn.com</a>), Lead Product Designer at Hopper</p><p><a href="http://www.hopper.com/"><em>Hopper</em></a><em> is an award-winning mobile app that offers airfare prediction to help you buy your plane tickets at the best times.</em></p><p><em>We’re hiring a Mobile Product Designer to join me at Hopper! </em><a href="http://www.hopper.com/corp/jobs.html"><em>Click on our Jobs page</em></a><em> to apply and for more information.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15267e968e38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for Business]]></title>
            <link>https://medium.com/life-tips/designing-for-business-c74a0e563e82?source=rss-6a0b0c1e0c3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c74a0e563e82</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Pantelis Korovilas]]></dc:creator>
            <pubDate>Tue, 12 Jan 2016 14:39:37 GMT</pubDate>
            <atom:updated>2016-01-14T02:54:46.642Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Proper Context for Product Designers</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d0zuqN3QuOTxrGh-DlRE5g.jpeg" /></figure><p>The role of <a href="http://get.invisionapp.com/chapter-1-of-making-a-product-designer?ecid=ACsprvteoCn-r2_Z9EOtpWXw6Eg9iL_avTUFmT_wxz9GAd197qPf30VvROFh8WtxpYSN_MNTFuJJ&amp;utm_campaign=e-course-1-1&amp;utm_source=hs_automation&amp;utm_medium=email&amp;utm_content=21578194&amp;_hsenc=p2ANqtz-8jRnVq6hyAz_WydX7ou1ABKoCf3N5NC5QAMuCYjT5-y1W7ulah2PFXI8ZwgP6JFJnPUPBb2IsCiXiWFvFiPZtaGLII_Q&amp;_hsmi=21578196">Product Designer</a> in tech has never been more appealing as a career path. Whether you started as a visual, user interface, or experience designer to get there, the reason you create seamless user journeys and polished product experiences is ultimately business—and that’s a good thing. Understanding this and how to support it will make you a better designer and a better leader.</p><h3>Designers Are Business Leaders</h3><p>Not too long ago, designers were a lot lower on the organizational chart. I remember those years and experienced the frustration first hand. But the growth of software and mobile has ushered in a new era for the design community. Today, Product Designers <em>are</em> business leaders and many of us don’t even realize it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9b-cL-e92JDyWN7tNz_G_A.jpeg" /></figure><p>As designers increasingly sit at the table and work side-by-side with CEOs, CTOs, VCs, and a host of other business leaders (the volume at which this is happening is huge if you compare it with pre-mobile) this point is only more pertinent. We are increasingly relied upon to help steer product concept, direction, and roadmaps. As our voice as designers gets louder, the bigger our responsibility is to understand the businesses we are designing for.</p><h3>Business Models Are User Experiences</h3><p>Tech startups are often changing the means in which we interact with products and services, and sometimes the related laws, but ultimately they are working under the same pressures, tensions, and environments as traditional businesses in their industry. Business is still business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fddbs934exqVn6GnNSFStQ.jpeg" /></figure><p>The economics of the industry and the business model of the company decide what we designers build, how we build it, and if we are successful. Without sound business metrics, our products and companies will not live long enough to make a lasting impact on people and the world around us. It is ultimately the best user experience to have a strong business model.</p><p>So, get to know your industry and business as best as you can. Understanding this will allow you to make better recommendations and judgements regarding the regular tradeoffs that arise. When you are in a small team with limited resources, how you respond to these tradeoffs can be the difference between success or failure.</p><h3>Design to Grow, Retain, and Convert</h3><p>Designing for business means creating a product that is self-supportive of its business goals. It means designing to facilitate <strong>growth</strong>, <strong>retention</strong>, and <strong>conversion</strong>.<strong> </strong>While there are whole books and countless articles written on these topics, a few basic principles are worth mentioning.</p><h4><strong>Growth</strong></h4><p>Designing for growth means designing a system that supports, if not outright facilitates, the acquisitions of new users at no cost, i.e. organically. For many under-funded and early-stage products, <a href="https://growthhackers.com/growth-studies/airbnb">organic growth is an important component of initial traction and take-off</a> and a way to ensure you survive to the next round of funding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CudJXiJnseoQKp2cfHI9Hg.jpeg" /></figure><p>Put simply, build mechanisms in your app for content or social sharing. But, don’t get carried away. Plastering share buttons on every screen or list item is an easy way to condition users to ignore them. Kamo Asatryan — who <a href="http://firstround.com/review/this-is-how-you-design-your-app-for-maximum-growth/">was recently covered in a great article</a> on how to design for growth — rightly points out that you should prioritize moments of <em>natural</em> sharing and socializing. Try to put them in high-impact places where content is already being shared by existing users via screen captures, texts, or other means.</p><p>If your product doesn’t have these natural moments, Asatryan recommends trying to make sharing worth it for the user by offering financial or in-app incentives, e.g. a certain dollar or percentage off for both those sharing and those you acquire as a result. While a shareable and social structure won’t save a product that can’t find a market, it can increase the chances of a good fit taking off without a massive budget.</p><h4><strong>Retention</strong></h4><p>Getting new users to the app is pointless and an unsustainable feat if they don’t stick around. Long-term relationships and high engagement are the goals of designing for retention. And, as it turns out, they also help you in designing for growth.</p><p>The more users come back to your app, the more engaged they are. Those who are engaged are far more likely to support your product, tell their friends, create content on your app, and spend money. <a href="http://andrewchen.co/why-consumer-product-metrics-are-all-terrible/">As Andrew Chen points out</a>, most consumer app metrics are horrendous — it’s not uncommon to see 90% of users unengaged on a daily basis. In the face of these odds, doing the small things right will go a long way in keeping users interested.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ELviAC8EKuzUc_4ycg5HkA.jpeg" /></figure><p>Designing for retention starts by working with your CEO and product managers to define and maintain a strong product concept throughout the life of the app. Solving a real user pain point can save the designer from the awkward situation of being asked to compensate for lack of engagement by “making it pretty.” The idea that visual design can save a useless product concept is a fallacy. It never lasts. And users will be a lot more forgiving of early-stage missteps and shortcomings if you are relieving a real discomfort. So, make sure you understand the problem and create something that really adds value.</p><p>If you have a strong concept, you want your users to realize as quickly as possible what benefit it can bring to their lives. This means creating a user onboarding experience that is concise and sets the user up for ideal behavior. Prioritize learning through doing, not reading. The Appcues <a href="http://appcues.com/academy/">User Onboarding Academy</a> is filled with useful tips on how to reduce the amount of time it takes for people to realize your app’s value.</p><p>After the first use, you want to keep the user coming back, so make sure your onboarding experience includes hooks for repeat usage. The user’s journey starts outside your app, so set yourself up to be welcomed into that space. Incorporate external prompts—like push notifications, badges, or trigger emails—that point to real rewards for the user, be it the chance to meet a hot date, get a discount on that dream vacation, or provide a solid cure for boredom. Set these up as quickly as possible for first-time users.</p><p>But be careful, if you don’t provide real value in these triggers, user tolerance can be pretty low with <a href="http://andrewchen.co/why-people-are-turning-off-push/">over 60% of users opting out of push notifications in some product categories</a>. Make sure your push notifications say something meaningful either in and of themselves (due to the content and timeliness of the message) or for the reward they offer when the user enters the app. Using what you learn about the user to provide tailored triggers will only increase your success rate for relevancy.</p><p>Once users return to the app, make sure to minimize the physical and mental steps required for them to experience the rewards that brought them in. Ensure they once again realize your value while creating further hooks for repeat engagement.</p><p>If you have to prioritize, design for retention over growth. High retention will ensure growth initiatives, organic or paid, really take off and make maximum use of their resources.</p><h4><strong>Conversion</strong></h4><p>Lastly, getting new users to come back to the app or existing users to return is only useful if it gets them to convert on the metrics that drive your business. If this is hotels, it’s booking; if it’s event tickets, its buying. Without this, your business won’t be able to sustain itself over the long run, and the wonderful experience you are designing will have a short shelf-life.</p><p>Conversion doesn’t always have to be buying or paying for something. For many apps—in particular early-stage, investor-funded products—this might be hitting certain growth or retention metrics, spending a certain amount of time on a particular screen, clicking through or viewing ads a certain amount of times, or pressing a certain button regularly. While these key performance indicators are usually defined at high levels within the company, or with board members, designers can play a key role in figuring out how to make them tangible and forming the structure of the app around them early on. At a minimum, designers need to be aware of what these metrics are and how each design decision will effect key funnels that lead to conversion. This is what it means to grasp the constraints of our work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3S155rNF7ntoBPGr3JWvSQ.jpeg" /></figure><p>Many of the similar tactics described above help us get to this point, with frictionless flows tailored to the user’s interests naturally leading to better conversions. If we have them engaged and motivated via designing for retention, one of the most important things we can do for conversion is get out of the way.</p><p>Remove anything that doesn’t need to be there and allow the user to “convert” in as few steps as possible. Asatryan recommends designing “every dominant call to action to move users forward consistently with all previous calls to action they chose beforehand. All of these CTAs should look and feel the same in terms of superficial traits like color, font, wording, placement.”</p><p>You would be surprised by how little is required in a design, <a href="https://medium.com/@hopper_travel/butt-booking-2e035113bc3#.siku0b9np">as we at Hopper learned building a booking flow for airfare</a>. But make sure to balance this with the right types of content to build trust and allow users to feel confident in converting. Making it easy and providing proper motivation will get you where you need to go.</p><h3>Design Methodologies Are The Means</h3><p>Ultimately, we must solve real problems in real markets, if we are truly designing for business. Then, getting people to find and use the products we design at minimal cost to us, come back regularly to interact with them, and convert on our key success metrics will determine whether or not our designs last long enough to provide <em>real</em> value.</p><p>The ways we traditionally think about design and the importance we place on users are still incredibly important and striking the right balance between creativity, product experience, and business priorities can feel like walking on a tightrope sometimes. It is the role of the Product Designer, however, to be sympathetic to all sides. Difficult or not, our success will be defined in the end by our balance, not our stubborn insistence on one over the other.</p><p>User experience, interface, and visual design are the methodologies we use to solve these key business problems effectively. They are the means, not the end. Leveraging the tactics we use to deliver engaging product experiences to support growth, retention, and conversion will make us better and more effective leaders at a time when our guidance is more valuable than ever.</p><p><em>—Pantelis Korovilas (</em><a href="https://twitter.com/pantelisak"><em>@pantelisak</em></a><em>), Lead Product Designer at Hopper</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c74a0e563e82" width="1" height="1" alt=""><hr><p><a href="https://medium.com/life-tips/designing-for-business-c74a0e563e82">Designing for Business</a> was originally published in <a href="https://medium.com/life-tips">Be Yourself</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>