<?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[UI / UX Articles - Medium]]></title>
        <description><![CDATA[Articles related to user interface and experience design - Medium]]></description>
        <link>https://medium.com/ui-ux-articles?source=rss----517c655d3868---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*vAz4vcdHz0Yn9xv2.jpeg</url>
            <title>UI / UX Articles - Medium</title>
            <link>https://medium.com/ui-ux-articles?source=rss----517c655d3868---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:14:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/ui-ux-articles" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Explaining app mechanics with animations]]></title>
            <link>https://medium.com/@rudpunk/explaining-app-mechanics-with-animations-c31a5f80575?source=rss----517c655d3868---4</link>
            <guid isPermaLink="false">https://medium.com/p/c31a5f80575</guid>
            <dc:creator><![CDATA[Eugene Rudyy]]></dc:creator>
            <pubDate>Wed, 18 Jun 2014 17:21:05 GMT</pubDate>
            <atom:updated>2014-09-01T13:36:40.996Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q4FFo1zAiiXqQa7e9AU4FQ.jpeg" /></figure><h4>Animations got the power to explain particularities of custom app mechanics. This is how its made in yep! app.</h4><h3>What is Yep!</h3><p>A year ago I started to work with Yep! founders Roman and Alexander who wanted to change the way people meet. Simple service that should allow people meet each other and spend time together doing what they both want to do right now.</p><p>Lets say you want to drink coffee with someone interesting. You see people around who are ready to do the same thing within next hour. Choose anyone, discuss details and go to drink coffee with someone interesting.</p><p>App mechanics feature lots of peculiarities that we are going to test on strength within next months. That will become a matter of future posts about <em>yep!</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/182/1*_T7JmE0uDKvfF93bxUKfeQ.png" /></figure><p><em>yep!</em> is currently available on the <a href="https://itunes.apple.com/app/id727632360?mt=8">Appstore</a> for free.</p><h3>Meaningful Animations</h3><p>Since iOS came out I was impressed with a power of meaningful animations. Animations can build beautiful non-computer paradigms inside users mind. No long text explanations but with showing. Most simple example is an item that jumps inside the trash bucket when its deleted. Computer programs became just apps, as they no longer feel “computer” and non-human. Today as skeuomorphism goes away meaningful animations remain, they are just no longer so much connected to real life objects.</p><p>Check <a href="http://www.ui-transitions.com/#home">Meaningful Transitions</a> site for simple yet understandable transitions.</p><p>As we worked on <em>yep!</em> UX building first wireframes and prototypes we came to a conclusion that app should be visually very clean with interactions showing the mechanics which is not a standard one for meeting or dating app. This approach has two positive sides: 1. Animations explain whats happening right now 2. It brings more life and emotions to the app usage (which is important for a leisure app like <em>yep!</em>). From the development perspective that means code custom animations that are additional time and money. Still we added basic animations to MVP.</p><p>In <em>yep!</em> we got linear flow: choose activity &gt; post request &gt; wait until search ends &gt; see results (matches) or get message that no one is around (search will continue for 1 hour). All stages are different screens but with animations we can show transitions that will make them feel one screen transforming from stage to stage and make user understand what is happening. Its Apple approach that perfectly works for native iOS. But as we have linear scenario we can go with more customised gamification.</p><h3>Choose Activity</h3><p>In <em>yep!</em> activities are shown as coloured circles with icons. Each activity type has its own colour. Regarding to activity colour all action colours (<em>links, buttons)</em> within activity corresponds to this colour.</p><p>As app starts activities appear clockwise. Sport and Events got list of sub activities. Sub activities appear the same way. In this case these animations are more “candy” looking additions to make user feel that app “lives”. <strong>Bringing emotions to a minimal look is essential.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*KGOGQ2mroeFjFYNm3_FVZQ.gif" /><figcaption>Video on Dropbox <a href="https://www.dropbox.com/s/huyor87anxcfxz6/activities%20to%20subactivities.mp4">https://www.dropbox.com/s/huyor87anxcfxz6/activities%20to%20subactivities.mp4</a></figcaption></figure><p>In this animation you see activities appear, than Sport is tapped and sub activities appear.</p><h3>Post Request</h3><p>This is where we start transforming screens to make user flow feel smoother and explain whats happening.</p><p>These are the stages from the animation below:</p><ol><li>Choose activity (meal, coffee, running, movies etc.);</li><li>See your request ready for posting. Optionally add venue and additional description;</li><li>Post request;</li><li>Wait while yep! searches within 50 km radius;</li><li>Get results (<em>not presented in this animation</em>)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*ulZ4m-QzyWNhchrUPmjffg.gif" /><figcaption>Video on Dropbox <a href="https://www.dropbox.com/s/137ps63ydfqwj7t/yep_linear_progress.mp4">https://www.dropbox.com/s/137ps63ydfqwj7t/yep_linear_progress.mp4</a></figcaption></figure><p>On video above user choose Meal activity and activity circle goes up transforming into a map pin. That gives an understanding of location based mechanics and clearly connects activity type with location (ready to have a meal here).</p><p>Next after you tap OK map pin drops into the center of radar, map zooms out to 50 km radius showing user location is in the center of search.</p><p>As a conclusion user see activity element is “traveling” from stage to stage.</p><h4>UX improvements and mistakes.</h4><p>On a previous version of app we got other design for request screen (second stage after you choose activity). Our first approach was to show the request screen with name and photo. Same as how other people requsets look when you browse through matches. Main idea was to show your request as others will see it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*sAg5isacOm7jnzL1cOPGkA.png" /><figcaption>Old version of submit request stage with 67% pass through rate</figcaption></figure><p>Still the screen did not work well. <a href="http://mixpanel.com/">Mixpanel</a> showed people where distracted with their photos, names and profiles. We were loosing to many users on this stage as they did not posted their requests.</p><p>So we cleaned up everything that was not related to request, everything that distracted people.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*wd52Pri23s1Q48M24XW7AA.png" /><figcaption>New version of the same stage now with 83% rate</figcaption></figure><p>Main things here is to review location, optionally choose venue and write additional description. We also added sharing (not yet released).</p><p>That worked and we raised pass-through rate from <strong>67%</strong> to <strong>83%</strong>. We still work on the flow to raise this index.</p><h3>Send Requests</h3><p>Every match got a yep! button below his or her request. Tapping this button means send a request to meet. If user accepts the request the chat starts. Users can both send and get requests.</p><p>I decided to make an animation where yep! bubble appears from bottom and disappears on the top of the screen. <strong>This “push” direction clearly shows “sending” movement FROM user</strong>. Bubble stops in the center with a message that request was sent (this is where you can also withdraw your request), tapping the screen proceeds the movement of bubble.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*uQO7jOQdLqmp2BXcDEpmaw.gif" /><figcaption>Video on Dropbox <a href="https://www.dropbox.com/s/95m2snjm5dy4jzq/yep_sent.mp4">https://www.dropbox.com/s/95m2snjm5dy4jzq/yep_sent.mp4</a></figcaption></figure><h3>Get Requests</h3><p>Getting request (getting yep!) animation is close to how you get chat messages in Facebook app. Its in up right corner with avatar. Users can both tap these notifications or continue browse matches and see these requests within stack of matches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*gkrlZh5fw5I8unQQcEBaDw.gif" /><figcaption>Video on Dropbox <a href="https://www.dropbox.com/s/3du65xyb2461ylv/get%20request.mp4">https://www.dropbox.com/s/3du65xyb2461ylv/get%20request.mp4</a></figcaption></figure><p>Work continues as we have a bunch of improvements coming this summer and fall. There will be an Android version as well. I will keep writing on <em>yep! </em>design and UX evolution and challenges. Please leave your comments and notes.</p><p><em>yep!</em> team: Founders: <a href="http://www.linkedin.com/profile/view?id=431033&amp;authType=OUT_OF_NETWORK&amp;authToken=gfiT&amp;locale=en_US&amp;trk=tyah2&amp;trkInfo=tarId%3A1402410307748%2Ctas%3Aroman%20sido%2Cidx%3A1-1-1">Roman Sidorenko</a> &amp; <a href="http://www.linkedin.com/profile/view?id=3994562&amp;authType=OUT_OF_NETWORK&amp;authToken=fZa1&amp;locale=en_US&amp;trk=tyah2&amp;trkInfo=tarId%3A1402410333820%2Ctas%3Akukhte%2Cidx%3A1-1-1">Alexander Kukhtenko</a>,</p><p>Frontend: <a href="http://www.ipolecat.com/">Polecat</a></p><p>Design &amp; UX: <a href="https://www.behance.net/keepa">Keepa</a> (Eugene Rudyy)</p><p><a href="https://itunes.apple.com/app/id727632360?mt=8"><strong>Check out the app on the Appstore </strong></a>. We will be glad to receive a feedback from you. You can also check the promo site <a href="http://letsyep.com/en/">http://letsyep.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c31a5f80575" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Applying the Three Levels of Design to Building Software Products]]></title>
            <link>https://medium.com/@chakkaradeep/applying-the-three-levels-of-design-to-building-software-products-9885ebef63ce?source=rss----517c655d3868---4</link>
            <guid isPermaLink="false">https://medium.com/p/9885ebef63ce</guid>
            <dc:creator><![CDATA[Chakkaradeep Chandran]]></dc:creator>
            <pubDate>Sun, 24 May 2020 14:56:14 GMT</pubDate>
            <atom:updated>2014-06-12T02:20:24.899Z</atom:updated>
            <content:encoded><![CDATA[<h4>Visceral. Behavioral. Reflective.</h4><p>Don Norman in his book titled <a href="http://www.amazon.com/The-Design-Everyday-Things-Expanded/dp/0465050654/ref=dp_ob_title_bk"><em>The Design of Everyday Things</em></a> talks about three levels of design — <em>Visceral Level</em>, <em>Behavioral Level</em> and <em>Reflective Level</em> — on how they work together and play an important role in determining how people like or dislike the product. In other words, these three levels together determine whether your product is successful or not.</p><p>Though the book refers to designing physical products, I think these levels of design also apply to building great software products.</p><h4>Visceral Level</h4><p>— Visceral level is about <em>first impression</em></p><p><a href="http://en.wikipedia.org/wiki/First_impression_%28psychology%29">First impression is the best impression</a>. Working on building a great on-boarding experience helps you tell your users what your product is all about and make them like your product. It is about telling the story of why users should use your product.</p><p>— Visceral level is about <em>attraction</em></p><p>The more attractive (pretty) your product is the more chances you are going to get users’ immediate attention. Its when you hear users say, “WoW! Look at that!”</p><p>— Visceral level is about <em>immediate</em> <em>emotional impact</em></p><p>Immediate feeling users get looking at your product (color, design etc.,) or touching your product (it feels good…) or feeling the immediate need of the product!</p><h4>Behavioral Level</h4><p>— Behavioral level is about <em>user experience</em></p><p>Bad user experience, no matter how good your product is, can cripple users’ expectations, drive anger &amp; frustration which ultimately results in users not using your product.</p><p>— Behavioral level is about <em>understanding how users use your product</em></p><p>Its not just about building the user experience, it is also about understanding how users use your product, getting the right feedback so you can improve your product’s user experience.</p><p>— Behavioral level is about <em>expectations</em></p><p>It is about what users expect from your product. In other words, the product should deliver what it promises to the users. e.g., Dropbox should allow its users to put stuff in their Dropbox and get to it from their computers, phones, or tablets.</p><h4>Reflective Level</h4><p>— Reflective level is about <em>memories</em></p><p>The joy users get using your product that lasts forever.</p><p>— Reflective level is about <em>the relationship with the product</em></p><p>If users like your product, they are going to be more attached to it. They build a relationship with the product. They are proud to use it.</p><p>If users do not like your product, they are not going to use your product. Period.</p><p>— Reflective level is about the <em>overall impression of the product</em></p><p>The more users like the product, the more they are going to keep using it. Not only use it, but recommend it to others.</p><p>You can follow me in twitter <a href="http://twitter.com/chakkaradeep">@chakkaradeep</a> and my blog at <a href="http://www.chakkaradeep.com/">Chaks’ Corner</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9885ebef63ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hotel Room UX]]></title>
            <link>https://medium.com/@tinkadoic/the-hotel-room-ux-e88af195a34c?source=rss----517c655d3868---4</link>
            <guid isPermaLink="false">https://medium.com/p/e88af195a34c</guid>
            <dc:creator><![CDATA[Tin Kadoic]]></dc:creator>
            <pubDate>Mon, 11 Aug 2014 01:58:16 GMT</pubDate>
            <atom:updated>2014-06-10T15:12:11.882Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HzEJKZKi5Nd19vfLLlWxEg.png" /></figure><h4>A few quick guidelines for the Hospitality industry</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*H7CixzG_R8ZpHCkxpX1eHw.png" /></figure><p>The only two fixed moments in the entire Hotel UX are the check in and the check out. Even the exploring, research and reservation are not obligatory parts of the process (e.g. when travelling through Provence in the summer of 2007, we didn&#39;t have any reservations but rather crashed a different hotel each night).</p><p>In this rant I&#39;m focusing mostly on the <em>business / conference </em>hotel experience, rather than a classical leisure stay.</p><h4>My top three activities</h4><ol><li>Shower</li><li>Sleep</li><li>Work (Email)</li></ol><p>I rarely wish to spend more time than is needed in the room, and focus mostly on exploring the city, having breakfast and (potentially) working in a nice looking café, just around the corner.</p><p>Here are some ideas the hotels would benefit from. They require a minimum of intervention in the planning process</p><h4>1. <strong>Connectivity</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*WJjUlrttFtVz0Z2k7yLlxg.png" /></figure><p>Water, air and internet are the <em>new</em> necessities. Having limited connectivity or charging $20 for a day’s worth of internet is ludicrous in this day in age. It’s just an image of an old school, mastodontic approach to the hospitality business — “Hey, let’s charge everything possible!”. In certain hotel groups, only five-star hotels have wi-fi, while the three-stars charge their guests.</p><h4>2. Charging (your computer)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*zooMzFFzc_nxPslf4VZAQw.png" /></figure><p>Most hotel bathrooms have a <em>shavers only</em> electrical socket. There was obviously a point in time (my guess would be the 50&#39;s) where the architects and interior designers realised that this was a real necessity and planned accordingly.</p><p>The same needs to happen for our digital extensions, portables ranging from cameras, laptops, and mostly — smart phones (or at least to finally make an iOS phone able to make it through the day). I constantly keep finding myself unplugging the hotel TV, bending over benches, pushing the minibar, and replacing the landline plug with my iPhone plug.</p><h4>3. Charging (yourself)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*wNC1Dg5HasyptNVepnLWIQ.png" /></figure><p>The bed cover. Where does it go? What am I supposed to do with it? I usually put in on the floor (and then feel bad when leaving — it’s dirty!). Sometimes I fold it and put in the wardrobe (if they have it). Can we choose to live and sleep without the bed cover? How many of you use the cover in your home? Do you miss it if it’s not in the hotel room?</p><h4>4. Refreshing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*3NuXC8TjhWXJrz__WB5SuA.png" /></figure><p>With many written things regarding the learning process of the shower logics (namely <a href="http://www.amazon.com/Design-Everyday-Things-Donald-Norman/dp/0465067107">Norman’s Design of Everyday Things</a>), I will not repeat this as an issue, but rather build upon it.</p><p>I’m happy when I get the temperature to be <em>just right. </em>I&#39;m not willing to lightly throw away that moment of happiness. That is why, in the soap phase, I do not turn the water off, but rather hurry and try to waste as little water as possible. This opens the question: where does the shower head go? There’s usually no room behind the faucet, so I constantly find myself putting the head on the floor, holding it with my feet, and hoping it’s not gonna turn around and splash me in the face and all over the bathroom.</p><h4>5. <strong>Personalisation</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*bK1nIU_9Vg0girarfdXBRQ.png" /></figure><p>It would be great to add a human, personalised touch to the entire experience. If someone travels in the same brand of hotels, you would imagine the reception would know in what part of the hotel he would like to get a room, what he likes to eat, drink and so on. Maybe you would replace the contents of the entire mini bar with a certain brand of drinks, the kind he always drinks. This, for instance, is a hack that doesn&#39;t cost the hotel anything other than little time to prepare. The drinks are charged by usage anyway, but it’s a nice little touch that goes a long way.</p><p>Examples like this are far and beyond. I would argue that a five minute online search would provide sufficient information to make a little gesture for just about anyone.</p><p><strong>What are your top activities in a hotel room, and what are the accompanying things that annoy you during your stay?</strong></p><p>This entry is the 5th part of <a href="http://twitter.com/tinkadoic">my</a> New Year’s resolution project.<br><a href="http://medium.com/@tinkadoic">Read all of the entries here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e88af195a34c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UI for UI’s Sake]]></title>
            <link>https://coyleandrew.medium.com/ui-for-uis-sake-1266d0f98789?source=rss----517c655d3868---4</link>
            <guid isPermaLink="false">https://medium.com/p/1266d0f98789</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Andrew Coyle]]></dc:creator>
            <pubDate>Mon, 02 Jun 2014 17:12:23 GMT</pubDate>
            <atom:updated>2017-05-21T23:05:05.827Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*sFVHlOqVIm29kdlxkttw4w.jpeg" /></figure><h4>l’art pour l’art’</h4><p>The current theory of UI advocates that the best design is the least amount of design needed to accomplish a user’s tasks and goals. This belief drives a sameness to the aesthetic of interfaces. Spend a few minutes looking at the beautiful UI work on <a href="https://www.behance.net/search?field=132">Behance</a> and <a href="https://dribbble.com/tags/ui">Dribbble</a> and you will realize that everything looks terribly similar. I don’t think this is because people feverishly copy each other, rather they employ UI patterns that have been validated by others. Designers are increasingly defaulting to quick prototyping tools and “designing in the browser” to save time. The problem is that we don’t move past these practices. Also, we often over test and over optimize common design patterns in the name of “lean UX.”</p><p>These methods have made design more and more standardized leaving some asking <a href="http://blog.usabilla.com/ux-death-ux-2/">“What happens once we have discovered all possible solutions?”</a> Could we reach a point where designers are no longer needed because every design challenge has been solved and standardized?</p><p>What would happen if designers stopped trying to resolve the same UI problems and began creating new ways of doing things driven by their intrinsic taste?</p><p>“Art for art’s sake” was an art movement in the early 19th century that held that art doesn’t need to be the product of any moral or utilitarian function, and that art can merely be an expression of self. The movement was a rejection of the industrialization of society and culture during the time. The movement produced many beautiful works that later influenced the same system it sought to repudiate.</p><p>Should UI designers drop their analytical lens and start building for themselves like the artists of the 19th century that sought to undermine the industry’s influence on art? Is it time to add “art” back to the design process?</p><p>Of course any self-respecting designer will base their design choices on some objective standard but maybe we should add a bit of fun to our UI and see what happens. Perhaps we may find a new way of doing things. Perhaps our intrinsic whims and tastes are shared with the “users” we serve.</p><p><strong><em>l’art pour l’art’</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1266d0f98789" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reimagining Calendar App with Cards]]></title>
            <link>https://medium.com/@chakkaradeep/reimagining-calendar-app-with-cards-c9bb9157db0f?source=rss----517c655d3868---4</link>
            <guid isPermaLink="false">https://medium.com/p/c9bb9157db0f</guid>
            <dc:creator><![CDATA[Chakkaradeep Chandran]]></dc:creator>
            <pubDate>Wed, 12 Nov 2014 09:55:23 GMT</pubDate>
            <atom:updated>2014-09-03T04:41:31.762Z</atom:updated>
            <content:encoded><![CDATA[<h4>My experiment of reimagining the calendar app with cards user interface.</h4><p>Recently I wrote about <a href="https://medium.com/ux-ui-design/redefining-mobile-user-interfaces-with-cards-3ba4ed42c965">how cards user interface is slowly becoming the de-facto design for mobile apps</a>.</p><p>I thought why not give this cards design a spin. So, I picked to design a calendar app that used the cards design. The goal is to see whether we could re-imagine calendar app with cards without losing the need for users to easily track their daily schedule or accept invites and be productive managing their day.</p><p><a href="https://medium.com/@chakkaradeep/reimagining-calendar-app-with-cards-layout-1c5f162ac7de">I initially started with Balsamiq mockups</a> and got some good feedback on the design. Overall feedback was not that good — I saw people were not able to get what I was trying to do with the wireframe mockup. So, I decided to build an interactive prototype with good design elements.</p><p>I used <a href="http://bohemiancoding.com/sketch/">Sketch</a> to build the mockups and <a href="http://marvelapp.com/">Marvel App</a> to build the interactive prototype.</p><p>You can try out the <a href="http://marvl.in/206243">prototype here</a> (iPhone recommended for best experience) or watch the demo below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FXDRw1ejr0RA%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DXDRw1ejr0RA&amp;image=http%3A%2F%2Fi1.ytimg.com%2Fvi%2FXDRw1ejr0RA%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d6422b2966788af395b02f19d221ebbd/href">https://medium.com/media/d6422b2966788af395b02f19d221ebbd/href</a></iframe><blockquote><em>While I am a product manager, I am also passionate about UX/UI. While my design skills may not be perfect, I spend considerable amount of time practicing UX/UI. Feel free to leave a comment on what you think about the design and what can be improved to make it better.</em></blockquote><blockquote><em>If you like what you read/see, and interested in taking the next step — building the calendar app — with the same design, please </em><a href="http://twitter.com/chakkaradeep"><em>contact me</em></a><em>. I am more than happy to discuss further.</em></blockquote><p>Without further adieu, below is the design:</p><h4>Today Screen</h4><p>The app starts with letting you know whats next in your schedule.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*E-Ep3xKMfRxHR0t8ams4LA.png" /><figcaption>Today Screen</figcaption></figure><p>As you can see, the design uses cards to represent meetings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*LHlpa0PoRn0zqtmQo5yxZA.png" /><figcaption>Next Immediate Meeting Card</figcaption></figure><p>The next immediate meeting is well highlighted with information such as: <em>subject of the meeting, time, location, attendees, weather information for that particular meeting etc.,</em> — while other meeting cards contain the basic information required.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*bcWXYf_C9FLJTqJb8VIVmw.png" /><figcaption>Meeting Card</figcaption></figure><p>Just like in Google Now cards, the meeting cards also have the vertical hamburger button (Yep, hamburger button!) that will allow you to manipulate any options available, such as:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*FjCLiDsnfQEBtJBd08-YzA.png" /><figcaption>Meeting Options</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*6jVkNQEj65HGRYZGG-Wi1g.png" /><figcaption>Meeting Options</figcaption></figure><p>Actions card lets you perform quick actions such as <em>Email Guests</em> or <em>Navigate</em> or <em>Join the conference call</em> for example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*mqC6GstiXrXzs89kXsH2yQ.png" /><figcaption>Actions Card</figcaption></figure><blockquote>Think of these actions as context aware or meeting aware so they can provide you with the right actions when you need them.</blockquote><h4>Agenda Screen</h4><p>As you scroll up the Today Screen, you will scroll to view your list of other meetings for the day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*VgpZ9IbCnm7eJUJIs9tpMQ.png" /><figcaption>Agenda Screen</figcaption></figure><h4>Month Screen</h4><p>As you swipe down while you are in the calendar, the app will reveal the month screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*mNrCOX3zx8UlTnLdrht6gA.png" /></figure><h4>Meeting Information Screen</h4><p>When you tap on a meeting card, the app will load the meeting information screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*3MCmXtPp01m7ven6yyoV9w.png" /><figcaption>Meeting Information Screen</figcaption></figure><blockquote>The goal is to not just use cards but also make it easier so you can grasp and focus on the information needed as quickly as possible in a glance.</blockquote><h4>Inbox Screen</h4><p>Inbox screen holds all the pending invites in one place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*18UCcv_l-PaCWg38hJmhbg.png" /><figcaption>Inbox Screen</figcaption></figure><p>The meeting invite card gives you the right amount of information required to respond to the meeting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*39xCnBS-WMg0oc9uqKfNjA.png" /><figcaption>Meeting Invite Card</figcaption></figure><p>To respond, just click on <em>Respond</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*HizCOeVn-_CaJlzBxFDQ_Q.png" /><figcaption>Respond to the meeting invite</figcaption></figure><h4>Summary</h4><p>The more I work with cards, the more I love them! I feel the calendar app looks much cleaner with cards interface. My prototype does not cover all the scenarios, but I think it shows how useful cards design can be to represent information to users.</p><p>Don’t forget to let me know what you think about the design!</p><p>You can follow me in twitter <a href="http://twitter.com/chakkaradeep">@chakkaradeep</a> and my blog at <a href="http://www.chakkaradeep.com/">Chaks’ Corner</a>.</p><p><em>*User photos used in the mockups are downloaded from </em><a href="http://www.uifaces.com/authorized"><em>uiFaces website</em></a><em>. These awesome users have given their consent to be used on live websites (not just mockups).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9bb9157db0f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design principles for a payments experience]]></title>
            <link>https://medium.com/@christianpalino/design-principles-for-a-payments-experience-dcfb72053dff?source=rss----517c655d3868---4</link>
            <guid isPermaLink="false">https://medium.com/p/dcfb72053dff</guid>
            <dc:creator><![CDATA[Christian]]></dc:creator>
            <pubDate>Sat, 25 Oct 2014 17:06:41 GMT</pubDate>
            <atom:updated>2014-06-05T03:53:11.977Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p_-LMJTzUYbGpJOM8ZOjZw.png" /></figure><h4>At work at OpenTable</h4><p>Design principles can often take the shape of aspirational qualities or attributes — they sound great and everyone nods their head when they hear them, but they rarely serve the purpose of helping to guide and shape the outcome. The best principles are applicable to what you’re designing and help provide a framework for making decisions (<a href="http://www.uie.com/articles/creating-design-principles/">More on design principles</a>).</p><p>We’ve had lots of design principles at OpenTable, some we’ve written on the walls, others are always present in our conversations about a design (even without writing them down). Here are a few of the principles we’ve actively used as we developed a new experience for paying at a restaurant.</p><h4>Look beyond friction within your product</h4><p><em>Whenever you remove a known convention to reduce steps and make things easier, you will likely create new points of friction, often outside your product.</em></p><p>We removed all the back and forth involved in asking for, receiving and paying for the check by automating much of it with our app. This reduced the number of steps and time in the process, but introduced new issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/384/1*7IZlBmxAj0e1xRnPuGwOlw.jpeg" /></figure><p>Because there are different systems involved, diners have to let their waiter know that they are going to pay with OpenTable. That may seem like a small thing to mention, but remembering to do this and knowing when is the <em>right</em> time creates new burdens.</p><p>Now that the restaurant knows you’re going to pay through OpenTable — sure, people could get up and walk out unannounced — but they usually won’t. There is a general uncertainty about whether they have actually paid or if they need to tell their waiter they are leaving.</p><p>We designed subtle cues that help you know what you need to do without you needing to go look for instructions in the app. However, we also worked with the restaurant staff to identify equally subtle shifts in their interactions with the guests that would influence the perception of the service and how it works.</p><h4>Honor the ceremony</h4><p><em>Don’t eliminate the interactions that are meaningful between people for the perceived convenience of speed or fewer steps.</em></p><p>Asking diners to interact with an app on their phone takes their attention away from the waiter, their meal, and their companions. In addition, automatically delivering the check to your phone eliminates consistent cues that allow the restaurant to time your experience and ensure they deliver all the finishing touches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qvIgqU1BYhdIEHdtduXdzQ.png" /></figure><p>Our team designed an experience that only requires one swipe in the app to pay for your meal, and you can do it whenever you (and your waiter) are ready. While you have immediate access to your check—and control over your tip—you don’t need to look at it for it to work. This enables the final moments at the restaurant to involve fewer transactions.</p><h4>Design for no interaction</h4><p><em>The moments between each tap, swipe or scrub are just as important to your experience.</em></p><p>We didn’t design the payment experience to give you anytime access to your check on the phone (though that’s there if you need it). Our main focus was to help you and the restaurant pay less attention to the transaction of money. To do this, our service has to work in the background. Automating the exchange of something that people are accustomed to doing through a physical exchange can make people nervous.</p><p>Our team spent a lot of time designing the screen diners hopefully won’t be looking at to provide confidence in the service and product experience. We wanted diners to know that the app is working, even at a glance, without needing to tap into something. We made the screen gently “breathe” and fade into the dining environment’s background to achieve this.</p><h4>Win best supporting actor</h4><p><em>We’re in support of an experience, we’re not the featured attraction.</em></p><p>This is one of our core principles and extends beyond our payments experience to everything we do. Our products are in service to the diners and in support of a restaurant’s ability to be hospitable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/384/1*F-OOGFyIz7x7V2eUD2K2Yw.jpeg" /></figure><p>OpenTable’s restaurant listings and reservations are one of our most valuable assets. However, when you’re at a restaurant you’re likely not thinking about other restaurants or booking them (even if we hope you are).</p><p>We completely remove the distraction of our most important revenue driver (reservations) using our knowledge of you and your reservation to know when you’re at a restaurant. We use this to feature what might be useful to you in the moment — and in service to the restaurant.</p><h4>Design with seams</h4><p><em>Don’t remove points of friction that help people have more meaningful interactions.</em></p><p>Know when to stop making it more seamless and simple — essentially, leave in some of the seams of experience. Seams can be felt, they identify a transition, and importantly, offer an expectation for people to know where to look to understand or interact with a transition. It’s much easier to smooth out seams or remove them later than reintroduce them.</p><p>In creating a new payment method we want to make it easier to pay and enable diners to think less about money during their meal. If the diner needs to declare their payment method intentions before their meal has started or ask the waiter for a table number to enter in the app, the diner is forced to think about payment more frequently, not less. On the other hand, if the service makes it possible for the diner to pay and leave so seamlessly the waiter doesn’t know until after it’s happened, the experience the restaurant wants to provide diners has been interrupted.<br>Even though we could make paying with OpenTable so seamless the diner could pay and leave anytime they like, we chose to retain a point of friction, designing the service to enable the waiter to control when they’re ready for the diner to pay and leave.</p><blockquote><em>This raises an important comparison or point of inspiration that commonly surfaced while we developed this product experience — “it should be like Uber!” While the comparison works for establishing a model of having a credit card on file to automate a real-time payment, paying at a restaurant is an entirely different context than in a taxi.<br>While you might chat with your taxi driver, you didn’t come for the conversation, the car seats, or the pine-scented atmosphere. When you get in a taxi your objective, most often, is to get somewhere quickly (which includes getting out of the cab as soon as possible).<br>By contrast, when you go out to a restaurant, especially a reservation-taking restaurant, you’re there to be waited on. It is, most often, not about getting in and out as quickly as possible. You’re there to enjoy the food, the atmosphere and the well-timed interactions with the restaurant. Taking as much in-person interaction as possible out of the approach to the service misses the point and doesn’t serve the needs of the restaurant (to be hospitable!).</em></blockquote><h4><strong>Light the Way</strong></h4><p><em>Don’t trap people, equip them to move effortlessly throughout the system.</em></p><p>Like <em>win best supporting actor</em>, this principle is present in everything we design. We’re committed to making it easy to pivot (i.e. let me change my search, my location, my mind), helping people recover from errors (without blaming them or making them feel stupid) and eradicating dead ends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/384/1*eul33ReZUQBHQfDLsm8MaQ.jpeg" /></figure><p>Menus and nested paths provide structures that can be clearly understood for knowing where to look for things or digging deeper. However, those those conventions won’t do when you’re designing for an in-context experience that is infrequent and time-sensitive.</p><p>We think of every page as a landing page in our payments app by showing people the alternative paths or interactions directly on this screen. The service, not just the screens need to be designed with this in mind to avoid cluttering the screen or bundling options into menus.</p><h4>Open and adaptable</h4><p><em>Recognize that the situation is complicated and may change.</em></p><p>There is no specific anecdote for this. Things will change. Technology will change. People will want new features. Design for the unknown future.</p><p><em>Many thanks to the </em><a href="https://twitter.com/chloepark"><em>@chloepark</em></a><em>, </em><a href="https://twitter.com/meesasun"><em>@meesasun</em></a><em>, </em><a href="https://twitter.com/ladylexy"><em>@ladylexy</em></a><em>, and the </em><a href="https://twitter.com/OpenTableDesign"><em>OpenTable design team</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcfb72053dff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redefining Mobile User Interfaces with Cards]]></title>
            <link>https://medium.com/@chakkaradeep/redefining-mobile-user-interfaces-with-cards-3ba4ed42c965?source=rss----517c655d3868---4</link>
            <guid isPermaLink="false">https://medium.com/p/3ba4ed42c965</guid>
            <dc:creator><![CDATA[Chakkaradeep Chandran]]></dc:creator>
            <pubDate>Sun, 24 May 2020 14:55:47 GMT</pubDate>
            <atom:updated>2014-06-08T01:39:43.965Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/desat/multiply/grey/60/overlay/grey/1*SXmgDUZmxr6z5eqssot5Zg.png" /></figure><h4>Simple. Interactive. Powerful</h4><p>With so many mobile applications releasing everyday, very few catch our attention. Some apps have great visual designs and represent information in a new way while others redefine &amp; reinvent existing layouts. One such existing layout, tried and tested by us several times, that is becoming popular is the Cards layout.</p><h4>Well, what is so special about Cards?</h4><blockquote><em>“It’s not like we’ve invented a new way to organize information,” admits </em><a href="http://www.fastcompany.com/person/matias-duarte"><em>Matias Duarte</em></a><em>, UX director for Android. “We’ve actually tapped into one of the oldest pieces of graphic and information design around–business cards, calling cards, greeting cards, playing cards. They all have the same embodiments because they’re all reflections of a similar set of design problems.” — </em><a href="http://www.fastcodesign.com/1672605/how-google-unified-its-products-with-a-simple-index-card"><em>ARE CARDS GOOD DESIGN, OR A FOREGONE CONCLUSION?</em></a></blockquote><p><strong>Simplicity: </strong>Cards is all about simplicity.</p><p><strong>Being Minimal: </strong>They help us to show the required information that makes it easy for us to digest.</p><p><strong>Provide a Glance: </strong>What is my weather today? When is my next flight? — Well, with cards, answer to these questions can be represented with simple visual cards than complex visual interfaces with many information to digest (especially in weather apps where some apps have animations, visuals, and throw more information etc.,)</p><p><strong>Holds Key to more Information: </strong>If the user wants to know more information, they can very well go ahead and tap/click on the card which would provide more information regarding the selected card.</p><p>I think <a href="https://medium.com/@cezinho">Cezary Pietrzak</a> has done a good job on <a href="https://medium.com/mobile-marketing/ef5d35ab6fc">summarizing why cards are useful</a>.</p><p>Below is a comparison of Google Now weather card and Accuweather app — clearly the information in the Google Now weather card is easy to digest and has the right amount of information that I need to know before I go outing or shopping, whereas there are lots of information in the Accuweather app — of which the current temperature is what matters to me most.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/1*pnbi9guY5zou8u0HRi-sSQ.png" /><figcaption>Accuweather App</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/309/1*VMGrwenhFTxhWitmpe77JQ.png" /><figcaption>Google Now Weather Card</figcaption></figure><p>Google has now adopted the cards design almost in all of their products where applicable, especially in mobile apps like YouTube, Google Now, Google+ and even Google Wallet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/309/1*ZSOD0D0b8o_pzo7YY3tstQ.png" /><figcaption>Google Wallet App</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/309/1*XajTRScg1b9ipEEZ2WOJcQ.png" /><figcaption>Google Now Watch Cards</figcaption></figure><p>I also like how <a href="https://cir.ca/">Circa news app</a> uses the card layout. The app loads the cards into the foreground as you scroll through the news.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/309/1*IpkjJtV5KHH7-yAGWBnkgg.png" /></figure><p>And here is <a href="http://jelly.co/">Jelly app</a> that also uses card layout which makes this app super simple to help users by answering their queries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/309/1*s26ndLKv9gsEA7WlaW_aTw.png" /><figcaption>Jelly App</figcaption></figure><h4>Summary</h4><p>Cards are slowly becoming popular choice for mobile apps, not because they are fancy, but because they can show information to users that are simple to digest.</p><p><strong>Update</strong>: In order to see how cards can be useful, I did an exercise on designing a calendar app with the cards layout. You can read the article <a href="https://medium.com/user-experience-researche/reimagining-calendar-app-with-cards-c9bb9157db0f">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ba4ed42c965" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Never Ask What They Want — 3 Better Questions to Ask in User Interviews]]></title>
            <link>https://chuckliu.medium.com/never-ask-what-they-want-3-better-questions-to-ask-in-user-interviews-aeddd2a2101e?source=rss----517c655d3868---4</link>
            <guid isPermaLink="false">https://medium.com/p/aeddd2a2101e</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Chuck Liu]]></dc:creator>
            <pubDate>Fri, 18 Jul 2014 04:03:59 GMT</pubDate>
            <atom:updated>2017-11-20T22:51:59.724Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/583/1*IBhySzNKhuVvn0Z-raf-5g.jpeg" /></figure><h4>Wouldn’t it be so easy if users just told you what they wanted? Nope.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/1*qOV-WWYcN3gnDV-Z9YM-ng.gif" /></figure><blockquote><em>The first rule of user research: never ask anyone what they want.</em></blockquote><blockquote><em>— Erika Hall, </em>Just Enough Research</blockquote><p>I rave about user interviews. They’re cheap (see: free), potent (you get more than what you ask for), and efficient (<a href="http://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">you only really need to talk to five people</a>).</p><p>But good interviewing takes practice.</p><p>It helps if you’re naturally curious about people, but if you aren’t, you can still <em>fake it till you make it. </em>For example, Michael Margolis of Google Ventures likes to <a href="http://www.gv.com/lib/get-better-data-from-user-studies-16interviewing-tips">get into character</a>.</p><p>Like Erika Hall states above, when you embark on your user interviews, you’ll want to avoid asking what they want. Asking people what they want will lead you to the wrong insights. You will not discover the root cause of a problem, but rather what they envision as their own ideal solution.</p><h3><strong>Don’t Make User Interviews Hard For Yourself</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*U4rFt-246UnyAVcXXJcmjQ.png" /><figcaption>Asking people what they want makes user interviews harder than it should be. And you also can get the wrong insights.</figcaption></figure><p>When you ask a person what they want, you let them think within the realm of possibility. And that makes user research harder than it should be. If you’re trying to create a new product or experience that doesn’t exist yet, you’ll want to know what’s causing people to not be able to do what they want <em>with the tools they currently have. </em>That way, you can design for an entirely new experience or incremental improvement that helps them get the job done.</p><p>At KISSmetrics, I spend a lot my time interviewing people about what they currently use to solve a problem. Here’s what I think are 3 better questions to ask. And I ask these all the time:</p><ul><li>What are you trying to get done? (Gather context)</li><li>How do you currently do this? (Analyze workflow)</li><li>What could be better about how you do this? (Find opportunities)</li></ul><h3><strong>What are you trying to get done? Why?</strong></h3><p>Getting background information about what a person is trying to do is critical to understanding your users. Things like how big their team is and how their role fits into the larger organization helps frame the scale of a job that your product can help do better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/1*I1cQH8rT5K5QD3ezDDv6KA.png" /><figcaption>Finding out the use case and root cause can take multiple instances of “Why?” until you understand your user or customer correctly.</figcaption></figure><p>Imagine that you are a handy man. Wouldn’t you want to know whether you’re fixing a small leak or re-doing a whole room? You’ll need different tools for those jobs and the scale of those jobs are completely different.</p><p>It’s the same with user interviews. You’ll want to gain an understanding of what your users are trying to get done in order to get the necessary information back to your team. Your product and engineering teams will thank you for it.</p><p>Getting down to root cause of a problem requires you to also ask why. <a href="http://en.wikipedia.org/wiki/5_Whys">Use the 5-Why’s model to make this easy</a>. You’ll naturally discover a process or lack thereof by asking “why” a couple of times (you don’t have to exactly ask “why” 5 times). I’ve been able to save our engineering team from working on low-value projects by uncovering customer needs that can be fixed with process or approach rather than developing a new feature.</p><h3><strong>Can you show me how you currently do this?</strong></h3><p><em>Edited based on many comments and suggestions. Big thanks to Jared Spool for sparking a discussion!</em></p><p>After knowing the scale of a problem, I like to find out how a user currently deals with a problem. This lets me step into <em>their </em>shoes and experience how potentially painful it is for them. Sometimes, users come up with alternative/hack methods in order to get what they want. These methods are sometimes pretty easy for us to implement in order to save someone hours a week doing something.</p><p>Here’s an example. I was recently doing research for the product team on a new feature we wanted to build. But we wanted to see how painful this problem was in order to prioritize it accordingly. By interviewing a bunch of customers on how they operate internally, I was able to draw something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*GTGBggxoIO6AS22a3itwcQ.png" /><figcaption>Uncovering workflows and organizational processes will help you identify where you can help.</figcaption></figure><p>Knowing a user’s workflow also lets your team figure out what parts of the workflow you can improve. For example, at KISSmetrics, we’ve recently found out that our customers prefer to work primarily out of email than with the app itself for checking on stats. Given that KISSmetrics is part of their daily workflow and sometimes even the first thing a person works with when they come into the office, we’re now pursuing projects that will deliver better email summaries to our customers.</p><h3><strong>Can you show me what’s frustrating about your current process?</strong></h3><p><em>Edited based on many comments and suggestions. Big thanks to Jared Spool for sparking a discussion!</em></p><p>Most of your research has already been completed before you even get to this question. This question prompts the user to give you some ideas on what areas need the most help. Also, this is when they will help you validate or disprove your team’s hypothesis on building something.</p><p>If you jump to asking users about how they think something can be better from the start, you only get their opinion, not how they actually deal with their current problem.</p><blockquote><em>It’s really hard to design products by focus groups. A lot of times, people don’t know what they want until you show it to them.</em></blockquote><blockquote><em>-Steve Jobs</em></blockquote><p>This is where you’ll find opportunities to improve or where customers will vent about their current solution and what’s missing. Either you find this opportunity big enough to pursue with your team, or you dismiss it as something that’s already solved and move on to another hypothesis.</p><p>This question can also help inform you about a prototype you can build to validate whether you can solve a problem. Note: I’m not saying you should build exactly what they say. The insights you glean from their answers will help steer you to some ideas you can try out. Test the prototypes to see if your designs end up solving their problem. Don’t just make whatever people want.</p><p>Using these 3 main questions, I’ve been able to validate hypotheses for my team with a very quick turnaround so that we’re able to work on things that provide long term value to our customers instead of just a bandaid to hold them over.</p><p>What questions do you like to ask your customers to figure out what to build or develop? I’d love to hear them. Feel free to ask me anything <a href="https://medium.com/u/133bd67c7046">Charles Liu</a> or <a href="https://twitter.com/chuckjliu?lang=en">@chuckjliu</a> on Twitter.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aeddd2a2101e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 ways to add visual hierarchy]]></title>
            <link>https://coyleandrew.medium.com/8-ways-to-add-visual-hierarchy-8820be73218a?source=rss----517c655d3868---4</link>
            <guid isPermaLink="false">https://medium.com/p/8820be73218a</guid>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[art]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Andrew Coyle]]></dc:creator>
            <pubDate>Thu, 29 May 2014 22:09:50 GMT</pubDate>
            <atom:updated>2020-05-16T20:02:19.336Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/968/desat/multiply/yellow/60/overlay/yellow/1*tfgrYbhBT_haTjzYVf-rqQ.jpeg" /></figure><h4>Add direction to your design</h4><p>There are many ways to achieve a visual hierarchy. Below are a few that can add direction to your design.</p><h4>Size</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*8-o8RD77BNkHfN0Dh6fhZg.jpeg" /></figure><h4>Contrast</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*7vz8ExlaRQ1Z2LMgjBLXIw.jpeg" /></figure><h4>Color</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*EHKLIqS53ErF1x20iuCEsQ.jpeg" /></figure><h4>Style</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*zeLHzmoOrZBIKoJag5bncw.jpeg" /></figure><h4>Grouping</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*nGHcwNNziAX_aiYOy0wNKg.jpeg" /></figure><h4>Unity</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*nWCed-KyMJEmFnwzc0INPQ.jpeg" /></figure><h4>Symmetry</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*6B5WT4QAFOQfuYaBgwuIMA.jpeg" /></figure><h4>Similarity</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*pmy3Ey5FUZzR5xDYlEjWaQ.jpeg" /></figure><p>What are some other ways to add visual hierarchy? I would love to hear your thoughts.</p><blockquote><a href="https://andrewcoyle.com/">Find me</a> on <a href="https://twitter.com/CoyleAndrew">Twitter</a>, and <a href="https://dribbble.com/AndrewCoyleDesign">Dribbble</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8820be73218a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Think you have empathy?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://kaizenbarry.medium.com/think-you-have-empathy-dc7c9aade79c?source=rss----517c655d3868---4"><img src="https://cdn-images-1.medium.com/max/1498/1*C_iACB-aK1agdGTxL76mNw.jpeg" width="1498"></a></p><p class="medium-feed-snippet">Your use of distancing language may say otherwise.</p><p class="medium-feed-link"><a href="https://kaizenbarry.medium.com/think-you-have-empathy-dc7c9aade79c?source=rss----517c655d3868---4">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://kaizenbarry.medium.com/think-you-have-empathy-dc7c9aade79c?source=rss----517c655d3868---4</link>
            <guid isPermaLink="false">https://medium.com/p/dc7c9aade79c</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[language]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Barry W. Enderwick]]></dc:creator>
            <pubDate>Fri, 31 Jul 2015 20:04:55 GMT</pubDate>
            <atom:updated>2016-10-30T14:50:24.126Z</atom:updated>
        </item>
    </channel>
</rss>