<?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 Tawni Fus on Medium]]></title>
        <description><![CDATA[Stories by Tawni Fus on Medium]]></description>
        <link>https://medium.com/@tawnifus?source=rss-d9d73ffa7de------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*E6Ay1z-4wel_t87IAHDDbg.jpeg</url>
            <title>Stories by Tawni Fus on Medium</title>
            <link>https://medium.com/@tawnifus?source=rss-d9d73ffa7de------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:42:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tawnifus/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[A deep dive into Bootstrap]]></title>
            <link>https://uxdesign.cc/why-bootstrap-doesnt-suck-39c024a728bd?source=rss-d9d73ffa7de------2</link>
            <guid isPermaLink="false">https://medium.com/p/39c024a728bd</guid>
            <category><![CDATA[bootstrap]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Tawni Fus]]></dc:creator>
            <pubDate>Fri, 26 Mar 2021 19:09:55 GMT</pubDate>
            <atom:updated>2021-03-26T19:11:30.154Z</atom:updated>
            <content:encoded><![CDATA[<h4>Sometimes to change your opinion, you have to force yourself to look at things differently, and research.</h4><figure><img alt="Bootstrap logo image from version 5 beta release blog." src="https://cdn-images-1.medium.com/max/1024/0*CeeTkeAonousIrSm.png" /><figcaption>Image sourced from: <a href="https://blog.getbootstrap.com/2020/06/16/bootstrap-5-alpha/">https://blog.getbootstrap.com/2020/06/16/bootstrap-5-alpha/</a> All copyright belongs to Bootstrap and its applicable team.</figcaption></figure><p>I’m going to be the first to admit it: I do not personally like Bootstrap. I dislike their UI elements, the aesthetic, and everything to do with working with a developer who wants it because of the above. I find the design to be incredibly outdated, and when a site uses Bootstrap, I feel like you can tell immediately. Even though I may not like it, I am but a small voice. It certainly has no impact on their progress — they’ve just released their <a href="https://getbootstrap.com/">version 5 beta</a>, which already does seem more interesting than the previous versions.</p><p>I recognize that this is a shallow bias, but I’ve never had a good experience using it in the past, and I’ve challenged myself to see the good in the framework because biases are insidious. Come join me on my research adventure into the positives of Bootstrap.</p><h3>1. If you like Material Design, Bootstrap still has you covered</h3><figure><img alt="Material Design logo." src="https://cdn-images-1.medium.com/max/220/0*QXHk2r6sFcJO9Cba.png" /><figcaption>Material Design logo. Image sourced from Google Images — copyright belongs to Material Design. <a href="https://material.io/">https://material.io/</a></figcaption></figure><p>I must admit, every time I see that you can use <a href="http://material.io/">Material Design</a> with <a href="https://mdbootstrap.com/docs/standard/">Bootstrap</a>, I’m surprised. I continually forget that you can, because initially, I think that it doesn’t make sense to wrap another design style on a design style. Then I remember that there’s a lot more that goes into a framework than simple UI elements — it’s how they function with each other in the code as well, and a lot more technical stuff that I don’t feel qualified to describe.</p><p>As far as I understand it, because Material Design is open-source, it means that other frameworks, developers, and companies can create templates, functionality, and other such features based on Material Design. MDB isn’t just a direct copy of Material Design with Bootstrap underneath, the design is still unique. It just follows patterns and guidelines of Material Design. Things like:</p><ul><li>Capitalized buttons</li><li>Shadows and elevation</li><li>Ripple animations</li><li>Form field animation</li><li>Tabs and other grouped elements</li></ul><p>Just because the framework is well established, it doesn’t mean that you have to compromise on more modern design techniques. I like this because I have templates that I use that are based on Material Design, and with a few small tweaks, I can make it Bootstrap-friendly. In addition to that, both I and the developers can have clear expectations of what the design is supposed to look like in development.</p><h3>2. Bootstrap works with vanilla JS, Angular, Vue, and React</h3><figure><img alt="JavaScript, Vue, Angular, and React logos in a row." src="https://cdn-images-1.medium.com/max/1000/1*nVhao5GPpHDIdeUqZ0gzIg.png" /><figcaption>Logos copyright of their respective owners. Logos are shown for illustrative purposes only.</figcaption></figure><p>Because Bootstrap works with a lot of different variations of JS, it isn’t limited to just one skillset. If you prefer to work in Vue or React because it’s what you feel most comfortable in, you don’t suddenly have to get used to vanilla JavaScript again. Because Bootstrap became open-source so long ago, there are a bunch of different resources where the framework was rewritten to be compatible with all of these other methodologies.</p><ul><li><a href="https://getbootstrap.com/">Default Bootstrap</a></li><li><a href="https://ng-bootstrap.github.io/#/home">ng-bootstrap</a></li><li><a href="https://react-bootstrap.github.io/">react-bootstrap</a></li><li><a href="https://bootstrap-vue.org/">bootstrap-vue</a></li></ul><p>The one flaw that is unfortunately very difficult to plan for is which version the rewrites support — in the case of react-bootstrap, it supports Bootstrap 4.6, despite version 5 being released this past February. This isn’t the biggest drawback, as just because a new version has been released, it doesn’t mean that the older versions have immediately become deprecated. It just means there happens to be a newer version to work with. Unless a rewrite has become deprecated, it’s still likely that it too will receive an update for the newer version.</p><p>This is less of a plus as a designer and more of a plus for developers, because as I stated above, if you’re used to working in a particular style, Bootstrap is still accessible to you. As a designer, the one positive of this is that all of the <a href="https://getbootstrap.com/docs/4.6/getting-started/introduction/">older documentation</a> is still available to you.</p><h3>3. There a lot of predesigned elements already available for designers</h3><figure><img alt="Designing in Sketch on a Macbook Pro" src="https://cdn-images-1.medium.com/max/1000/0*WqbL3oWcDc3XYDcy" /><figcaption>Photo by <a href="https://unsplash.com/@pathdigital?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">path digital</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>It can be hard switching between different frameworks — it seems like each one has a different shadow style, different button requirements, and don’t even get me started on the margin between elements in the navbars. Despite how complicated it can get, there are a bunch of resources out there — and a lot of them for Bootstrap, too. If you’re like me who’s created their own style guides and design libraries based on Material Design, switching to a new style can be difficult and it can be hard to change all of what you’ve learned. I did a quick search to see what was out there for Bootstrap design resources, and I found quite a bit right off the bat:</p><ul><li><a href="https://getbootstrap.com/docs/5.0/getting-started/introduction/">Bootstrap documentation</a></li><li><a href="https://xdresources.co/resources/bootstrap-4-ui">Bootstrap 4 resources for XD</a></li><li><a href="https://www.xdguru.com/adobe-xd-bootstrap-5-ui-kit/">Bootstrap 5 resources for XD</a></li><li><a href="https://www.figma.com/community/file/876022745968684318">Bootstrap for Figma</a></li><li><a href="https://www.figmaresources.com/resources/cjcf8oodrfuhpfyls">Bootstrap 4 for Figma</a></li><li><a href="http://bootstrap-sketch.com/">bootstrap-sketch</a> (v4)</li></ul><p>While customizability is still going to be required, as a starting point, you can use a design resource file so you don’t have to create everything from scratch, and then use the framework’s documentation to understand how you can customize it more as needed. Another plus is that if you’re like me and have created your own design resources, it is still possible that these can be easily modified to suit the styles of Bootstrap.</p><h3>4. The documentation provides a lot of options for breakpoints, containers, and columns</h3><figure><img alt="A stack of multiple phones and tablets" src="https://cdn-images-1.medium.com/max/1000/0*OKjPnABEaG3Uj7c-" /><figcaption>Of the 9 phones pictured above, chances are there are at least 3 separate viewports between them. Photo by <a href="https://unsplash.com/@halacious?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">HalGatewood.com</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>From mobile up and to large desktop sizes, <a href="https://getbootstrap.com/docs/5.0/layout/breakpoints/">Bootstrap</a> provides you with many breakpoints to work with. Not only that, but they’re also customizable using the Sass files in the event that you know you need to modify them.</p><p>The documentation clearly outlines how the size of different containers works depending on the modifier they’re given, which is helpful not just for the developer, but for me as a designer. To have that granular of details is incredible because it means I can reference the documentation, label my elements similar to the <a href="https://getbootstrap.com/docs/5.0/layout/containers/">documentation</a>, give my prototype to the developer, and there’s a lot less confusion of what they’re supposed to do with this awkwardly sized container.</p><p>Bootstrap works on a 12-column layout, which is similar to <a href="https://material.io/design/layout/responsive-layout-grid.html#breakpoints">Material Design</a> making it easier to work with mentally. There isn’t a lot of confusion between working with the columns between one design system and another, this way. The one really interesting thing that Bootstrap seems to have that I haven’t experienced personally in Material Design is the ability to describe, using classes, how the <a href="https://getbootstrap.com/docs/5.0/layout/columns/">columns are to react depending on the screen size</a>. As a basic example, this means that with the addition of these classes, you can describe that you want the column to extend 100% of the width on mobile, but only 50% on desktop.</p><h3>5. Overall, the documentation is well written</h3><p>I’m a sucker for good documentation. Working examples, a lot of description, charts, tables and images are all the key to my heart when it comes to documentation. And I’ve got to give it to the creators of Bootstrap, they did a good job of breaking up their documentation into manageable pieces.</p><p>What I find really interesting that I can’t remember seeing in other documentation is that they have a specific section on <a href="https://getbootstrap.com/docs/5.0/helpers/clearfix/">helpers</a> and <a href="https://getbootstrap.com/docs/5.0/utilities/api/">utilities</a>. I find this really interesting because I personally don’t have a lot of experience working with them — I find that a lot of times I don’t need to, so I don’t go out of my way to look for it. The fact that they have it easily accessible tells me they thought it through and made a dedicated effort to provide as much information as possible. It also means that if I get a chance to read through it, in the future I may be able to help my team to recommend using one of these utilities or helpers if they aren’t sure what to use to solve a particular problem.</p><p>I think, in conclusion, there’s a lot of good to Bootstrap, even if I don’t like the overall aesthetic of it. There are enough ways to customize the design to make it look unique if you take the time and effort to do so, as long as you work within the functional constraints. I don’t think Bootstrap will ever be my go-to, but doing this deep dive has helped me to see the value that Bootstrap provides. If nothing else, this should prove that doing your research is probably the most important thing you can do. You can’t be unbiased without being armed with knowledge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*H-p37Z9KVjfezn4q" /><figcaption>The UX Collective donates US$1 for each article published on our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39c024a728bd" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/why-bootstrap-doesnt-suck-39c024a728bd">A deep dive into Bootstrap</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Being a designer sucks, but we can make it suck less]]></title>
            <link>https://uxdesign.cc/design-sucks-but-we-can-make-it-suck-less-998e0ad35a0?source=rss-d9d73ffa7de------2</link>
            <guid isPermaLink="false">https://medium.com/p/998e0ad35a0</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Tawni Fus]]></dc:creator>
            <pubDate>Thu, 26 Nov 2020 16:20:41 GMT</pubDate>
            <atom:updated>2020-11-27T13:34:48.036Z</atom:updated>
            <content:encoded><![CDATA[<h4>Taking pride in your work as a designer.</h4><p>As designers, we do a lot. Design thinking, especially, is never truly done, and it’s something we’re implementing consciously or subconsciously through the entire project. We’re constantly learning new things, adding new things, or making modifications as new requirements come to light. We’re doing our best to understand what our users need and want, and are building prototypes often with interactions because the user’s needs and wants must inform those interactions, and cannot be left undetermined. These interactions — often referred to as <a href="https://uxdesign.cc/why-micro-interactions-matter-318e1409a6b2">microinteractions</a> — are some of the major pieces that bring a design to feeling as cohesive as <a href="https://medium.com/@shingo2000/microinteractions-in-instagram-9800542e7874">Instagram</a>, <a href="https://medium.com/@shingo2000/microinteractions-in-twitter-e8affd76d0f1">Twitter</a> or even <a href="https://www.userzoom.com/ux-library/best-google-microinteractions-and-easter-eggs/">Google</a>.</p><figure><img alt="Design thinking graph from Neilsen Norman Group." src="https://cdn-images-1.medium.com/max/1024/0*mKft48h_7MuN_mHC.png" /><figcaption>Design is a cycle — we’re never truly done, we’re always ideating, learning and implementing. Credit/<a href="https://www.nngroup.com/articles/design-thinking/">NNGroup</a></figcaption></figure><p>We research and analyze data, we make style guides, we make mobile, tablet and desktop variations of design, we review the design, we talk to users, we talk to stakeholders, we talk to developers. We do all of that, but we never do tend to get recognition for those designs. At least, not very often, and not very explicitly. And that’s a fact we have to accept — but not in a self-deprecating or negative way. We need to accept this in a constructive way — a way that reminds us to look at the bright side, that it doesn’t mean we still can’t take pride in what we did. We do a lot to be <a href="https://patdryburgh.com/blog/take-pride-in-your-craft/">proud</a> of.</p><blockquote>We took those grey blobs signifying buttons and made them clickable and colourful, dammit.</blockquote><p>I don’t mean this in the way of “Well I guess I’ll just roll over and never expect to get credit.” I mean this in a way of we need to remind ourselves that while we may not get written credit a lot of the time, it is our design that draws users in. It is our design that was informed, and what we made into something usable. We took those grey blobs signifying buttons and made them clickable and colourful, dammit. We put the bulk of the time, effort and care to understand what our clients and their customers would need, and would like. The developer may have given it life, but we were able to give them a visual guide of what should be implemented because that is what we do, and what we are <a href="https://blog.prototypr.io/what-makes-ux-design-your-passion-31a6fcf0da4f">passionate</a> about.</p><figure><img alt="UX Designer feeding UI Designer feeding Developer feeding User meme." src="https://cdn-images-1.medium.com/max/1024/0*T-zmfVAJ8LuY1dmU.jpg" /><figcaption>Sometimes, no matter how hard you try, your developer and users just don’t always get it. Credit/<a href="https://twitter.com/uxdesignmemes">Twitter</a></figcaption></figure><p>I’ve had a few experiences working with developers where I give them a design AND a style guide, giving them very clear interaction states for a bunch of elements, only to review the website at a later time and discover they just…ignored it. Or changed something in the design that wasn’t intended to be changed, <a href="https://www.smashingmagazine.com/2018/04/working-together-designers-developers/">without actual consultation of the designer</a>, in the entire review process. And it’s frustrating, trust me. Despite it happening many times on different projects, it still frustrates me to this day. But the best thing to do is remember you gave them what they needed, you already put the thought and effort into those designs, and the best thing to do is <a href="https://www.themuse.com/advice/6-ways-to-correct-a-coworker-without-coming-off-as-a-condescending-knowitall">calmly and politely</a> guide them to what you provided.</p><blockquote>We need to remind ourselves that the work we do is enough.</blockquote><p>Even while having to wade through team and client feedback, developer review and bug discoveries, at the end of the day, we as designers need to remember to take pride in the designs we create. We can let ourselves be demoralized by a seemingly constant barrage of other team members getting credit for what began as our hard work, or from hearing just an individual piece of negative feedback. There is <a href="https://medium.com/quackingtips/5-ways-to-stay-positive-as-a-designer-f1bfadca894b">positivity in design</a>, we just need to remind ourselves that the work we do is enough and that the positive comments we do get on our designs mean much more than what feels like an endless silence of no recognition.</p><p>We need to remind ourselves that we can even put a positive twist on that silence: no commentary is a relatively good indicator that our design is doing what it is supposed to. Users can access the data that they need. Users are being delighted by those small little animations we pushed to add because we knew that it would delight someone. We can still use these projects and sites as examples of a working portfolio in the future if need be, with the right permissions from any companies we worked with.</p><figure><img alt="Group project meme highlighting what it’s like when one person does all of the work." src="https://cdn-images-1.medium.com/max/700/0*glbwn9vwvcTTPVPN.jpg" /><figcaption>The importance of having your name with what you did — you don’t want to be branded the team member who did nothing. Credit/<a href="http://www.newcollege.utoronto.ca/student-blog/the-group-project-scapegoat/">University of Toronto</a></figcaption></figure><p>At the end of the day, we still have a lot to be proud of as designers. The recognition is nice, and through school, we’re almost trained to expect it, especially if you were in a design-centric program where if you didn’t have your name on the project for specific tasks you were likely failing. We live in a world where recognition is king. Without it, it’s harder to prove to ourselves that the work we do is worth it. But we still learn so much going through our research processes. We hone our design skills every time we open our computer to work on a project, learning to choose colours, fonts, button border radii.</p><blockquote>It’s your design that users will see, time and time again. Take pride in that.</blockquote><p>All of this helps us become better designers than we were the day before. We need to let ourselves be happy with our designs and not get caught up on being frustrated or feeling unappreciated when we don’t get specific credit on a project. At the end of the day, it’s nice to get that recognition, but we can’t expect it. We know the work we did was good and meaningful. Even if they don’t say anything, the project team knows that it was your design. The client should know, on some level, who was in charge of the initial design. It’s your design that users will see, time and time again. Take pride in that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*2ru_0odxmEBcRVhB" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=998e0ad35a0" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/design-sucks-but-we-can-make-it-suck-less-998e0ad35a0">Being a designer sucks, but we can make it suck less</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A collection of thanks to those who have supported me.]]></title>
            <link>https://medium.com/afwp/a-collection-of-thanks-to-those-who-have-supported-me-f90841a789a9?source=rss-d9d73ffa7de------2</link>
            <guid isPermaLink="false">https://medium.com/p/f90841a789a9</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[love]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[inspiration]]></category>
            <dc:creator><![CDATA[Tawni Fus]]></dc:creator>
            <pubDate>Tue, 20 Oct 2020 15:33:25 GMT</pubDate>
            <atom:updated>2020-10-20T15:33:25.358Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*u-JRfCREx2ELhf-R" /><figcaption>Photo by <a href="https://unsplash.com/@alexiby?utm_source=medium&amp;utm_medium=referral">Alex Iby</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Thank you for every time you help me when I’m breaking down and can’t handle things anymore.</p><p>Thank you for helping me to put me first.</p><p>Thank you for your unconditional love and support.</p><p>Thank you for every moment we spend together that brings joy and sunshine to my life when the storm clouds are rolling in.</p><p>Thank you for supporting the decisions I make and letting me learn and grow through my own experiences.</p><p>Thank you for keeping me on track to meet goals when you know they mean a lot to me.</p><p>Thank you for helping to fill the silences with just comfort, love, and fun. No sound necessary.</p><p>Thank you for understanding when I’m looking for solutions, and when I’m looking for a shoulder to lean on.</p><p>Thank you for dealing with me when I’m frustrated, even if it means I’m taking it out on you who doesn’t deserve it.</p><p>Thank you for being my sounding board, even if I don’t need your input. Just being able to talk out loud to another presence can be enough.</p><p>Life can be difficult. Life can be fun. But it’s finding those who help you when you’re down and struggling that can make all the difference. Whether it’s a phone call with a stranger, or an in-person family member with a relative, friend or partner, there is someone out there willing to help.</p><blockquote>When you’re ready, we’re ready to listen to you.</blockquote><p>Telehealth Ontario: 1–866–797–0000</p><p>Find your CMHA: <a href="https://cmha.ca/find-your-cmha">https://cmha.ca/find-your-cmha</a></p><p>Mind Your Mind: <a href="https://mindyourmind.ca/help/where-call">https://mindyourmind.ca/help/where-call</a></p><p>CheckPoint: <a href="https://checkpointorg.com/global/">https://checkpointorg.com/global/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f90841a789a9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/afwp/a-collection-of-thanks-to-those-who-have-supported-me-f90841a789a9">A collection of thanks to those who have supported me.</a> was originally published in <a href="https://medium.com/afwp">a Few Words</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning how to listen]]></title>
            <link>https://uxdesign.cc/learning-how-to-listen-5ddf5d1e7468?source=rss-d9d73ffa7de------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ddf5d1e7468</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[Tawni Fus]]></dc:creator>
            <pubDate>Thu, 15 Oct 2020 11:35:12 GMT</pubDate>
            <atom:updated>2020-10-16T23:29:22.194Z</atom:updated>
            <content:encoded><![CDATA[<p>As designers, we may fall victim to the assumption that we are always correct. Or at least, I know I’ve fallen victim to this. The idea of thinking that because at this particular moment I have all the information I think I need, that the design I create is the be-all and end-all of everything, is a very toxic mindset. Not just to myself, but those around me too. So instead, I welcome you to learn with me about how to change your mindset and instead ask questions, as well as learning how to go along with the flow. Sometimes the end result is much better than you could have ever imagined.</p><p>So, let’s get started on what I feel are the most important things you need to start or continue on your journey of learning how to listen. Have something to add? Please feel free to comment away, I’m always looking to learn from others with different experiences.</p><h3>A growth mindset</h3><p>First and most importantly, you need to <em>want</em> to get better. The drive to continually improve, to always grow, and to keep an open mind. This is often referred to as a <a href="https://www.brainpickings.org/2014/01/29/carol-dweck-mindset/">growth mindset</a> — the idea that you’re never done growing, learning, or improving yourself in both your personal and professional lives.</p><figure><img alt="Small pile of self-growth books. Focused emphasis on Influence, The Psychology of Persuasion." src="https://cdn-images-1.medium.com/max/1024/0*3fzVoRcpccJ7Jvuq" /><figcaption>Photo by <a href="https://unsplash.com/@bannon15?utm_source=medium&amp;utm_medium=referral">Bannon Morrissy</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If you’re already in a growth mindset, then great. But it isn’t always easy to pinpoint exactly what this means. It isn’t looking to increase the value of your assets or stocks, and it also isn’t looking to increase your muscle mass. A growth mindset is an openness and willingness towards constant learning. It’s not just knowing, but accepting that you’re never going to be done learning that’s the important piece. It’s looking for ways to constantly improve yourself, even if it’s something as small as eating one more piece of fruit per month. It’s not looking at problems as obstacles, but rather the building blocks of improving. It’s <a href="https://www.succeedonpurpose.com/post/fail-forward">failing forward</a>.</p><h3>Active listening skills</h3><p>The next thing you need is to understand what it means to <strong>actively listen</strong>. This goes further than listening to someone speak and is something that I’ve learned a lot about from my coworkers. The term “active listening” was coined <a href="https://www.tandfonline.com/doi/pdf/10.1080/10904010903466311">around the 50s</a> and refers to how an individual fully comprehends, understands, and responds to input from another individual. To me, this means that when you listen to someone explaining their reasoning, <a href="https://www.forbes.com/sites/womensmedia/2012/11/09/10-steps-to-effective-listening/#4ac125c83891">you aren’t listening for the sake of having an argument</a>. You aren’t honing in on one part of their sentence, and calling them out for having a different perspective. You aren’t <em>attacking</em> the other person for having a unique opinion.</p><h4>So what is “active listening”?</h4><p><a href="https://www.indeed.com/career-advice/career-development/active-listening-skills">Active listening</a> means taking in what the other party is saying and asking questions. Understanding. Taking the time to see things from their perspective, and asking them to clarify if necessary. It’s actively working towards a compromise or resolution to the conversation that leaves both parties as satisfied as possible.</p><figure><img alt="Man and woman smiling, sitting at a desk during a meeting." src="https://cdn-images-1.medium.com/max/1024/0*j6Im8ybCZYmRttWr" /><figcaption>Photo by <a href="https://unsplash.com/@amyhirschi?utm_source=medium&amp;utm_medium=referral">Amy Hirschi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Active listening is using <a href="https://www.forbes.com/sites/nickmorgan/2011/09/08/body-language-quick-takes-how-to-spot-openness/#4e75455e5b14">open body language</a>. Keeping your arms uncrossed, a neutral to positive facial expression, and making eye contact are all important. When you cross your arms during a conversation, it can come off as if you’re now closed off to the other person, especially when paired with crossed legs. This means that you’re now portraying defensiveness — that you’re no longer open to listening to what the other party is saying.</p><p>Something as little as your <a href="https://myalcomy.com/body-language-blog/feet-direction">foot positioning</a> can impact how you portray yourself, too — if you’re in a scenario where you’re conversing with one stakeholder, there may be an opportunity for another to join in the discussion, and changing your standing angle to include the newcomer can portray that you welcome their presence and are therefore more likely to listen to them.</p><h3>Letting things go</h3><p>The last thing you need — equally as important as those above — is an openness to <a href="https://www.tlnt.com/how-to-gracefully-admit-youre-wrong/">admitting when you’re wrong</a> and letting things go so that you aren’t fighting a battle not worth fighting for. This isn’t just saying “I’m sorry”, this is also learning to recognize when you need to let someone else take the spotlight, or when someone else’s idea is the one that does make more sense in the current situation, or even when the way you’re describing something isn’t getting across as intended. Just because a design you create is amazing and satisfies the design brief, the development time and capabilities may not be aligned. <a href="https://uxdesign.cc/i-am-the-user-i-am-not-the-user-40c75dcffdce">What you interpreted as the goal for the users may not be what the actual users think or know their goal to be.</a></p><p>If you find yourself running around in circles in a key meeting, without anyone actually coming to a resolution or conclusion, then chances are someone, whether it’s you or not, isn’t willing to let go of their opinion — or just plain <a href="https://www.themuse.com/advice/how-to-stop-a-conversation-from-going-in-circles">has the wrong assumptions in their mind</a>. Don’t get me wrong — sometimes this can lead to a positive outcome. If someone with key information is describing that something isn’t possible because the software or website will not be technically able to handle the feature, but the stakeholder is really pushing for the feature, the developer is probably correct. What should happen in this scenario is a shift in the tone of the conversation.</p><p>The developer needs to find a <a href="https://www.quickbase.com/blog/how-to-explain-technical-information-to-non-techies">new way to communicate</a> why the feature isn’t possible — <em>using the language of the stakeholder</em>. From the other side, the stakeholder needs to actively listen to what the developer is saying, and take the time to understand why it isn’t possible. Both sides need to be willing to ask questions and be open in their non-understanding.</p><p>A lot of times in development, and even design, just because a <em>specific </em>feature isn’t possible, it doesn’t mean it’s wholly <em>im</em>possible. It just means that this particular implementation isn’t possible. But if no one is actively listening, no one is going to feel comfortable bringing up new suggestions, because it’s more likely that the new suggestion is also going to be turned down.</p><h3>How do you actually get better?</h3><p>It’s grossly overused, but truly the best way to improve at this is to keep trying. Self-improvement is a mountain at the end of the day, it isn’t something you’re going to see happen overnight.</p><p>In my opinion, good listening skills are something that we can only hone by putting ourselves in situations where we need to listen. As designers, this means meetings with developers, stakeholders, team members, users, and anyone integral to the design process. If you have someone in your company, friend group or even family, you can also simulate these scenarios by telling them that you want to work on your listening skills. You can read books, listen to talks, listen to podcasts and attend events related to improving yourself and learning skills — there’s an overwhelming number of options.</p><blockquote>You just need to want to improve.</blockquote><p><strong>Disclaimer</strong>: <em>I am not an expert in the field of UI or UX. I am someone who has been working in the field for 5+ years, who strives to learn more about the field and share with others my knowledge. I hope that this article finds you well, and you’re able to take it and the information it provides with you into your career and also feel just that little bit more confident in your designs and decisions.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*RkDryK8i_ra4PW3B" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ddf5d1e7468" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/learning-how-to-listen-5ddf5d1e7468">Learning how to listen</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Colour contrast in UX]]></title>
            <link>https://uxdesign.cc/colour-contrast-in-ux-design-477011020095?source=rss-d9d73ffa7de------2</link>
            <guid isPermaLink="false">https://medium.com/p/477011020095</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[visual-design]]></category>
            <dc:creator><![CDATA[Tawni Fus]]></dc:creator>
            <pubDate>Mon, 05 Oct 2020 11:44:36 GMT</pubDate>
            <atom:updated>2020-10-05T22:33:43.278Z</atom:updated>
            <content:encoded><![CDATA[<h4>What does it mean to design for accessibility?</h4><p>Accessibility has been a hot topic for what feels like forever, and honestly, I couldn’t be happier. Back in 2016 was the first time I worked on a project where accessibility was a thought, and even then, we answered a grand total of seven questions and made a plan based on the answers to them. Since then, I personally have grown to learn more and more about accessibility in design, and how to incorporate it even if accessibility isn’t the number one concern of the project. For this article, we’re going to focus on colour contrast — both how to plan for an accessible palette and how to meet the standards.</p><figure><img alt="Examples of good (6.2:1) and bad (2.9:1) colour contrast. Both visually appear to be legible, but 2.9:1 does not pass." src="https://cdn-images-1.medium.com/max/1000/1*s1kSlaJmvH1N0Z0iPJr-3A.png" /><figcaption>Examples of good (6.2:1) and bad (2.9:1) colour contrast. Both visually appear to be legible, but by accessibility standards, the text on the right does not pass.</figcaption></figure><h3>What makes colour contrast a part of UX?</h3><p>The user’s experience is shaped by what they see on the screen, and how they’re able to go about what they need to, to get to what they want. If a user is visiting a site and can’t see a link or read a button because the colours are too light, then they aren’t going to be able to complete the task they set out to do. If a user with any form of colour blindness or visual impairment visits your site, they may not be able to see the elements properly, if at all. In all of the above scenarios, the user may experience frustration, or an inability to do what they need to which causes them to leave the site.</p><figure><img alt="Examples of colour blindness — normal vision, deuteranomaly, protanopia, and tritanopia." src="https://cdn-images-1.medium.com/max/880/1*ZwdDcM9V3HMBFlM1km0Zhw.jpeg" /><figcaption>The image above outlines some examples of what users with different types of colorblidness would see. This article, <a href="https://www.boredpanda.com/different-types-color-blindness-photos/">https://www.boredpanda.com/different-types-color-blindness-photos/</a>, has a lot of visual examples for those who want to see more examples.</figcaption></figure><p>This also goes past what we typically define as a visual disability: this also means that users with poor vision who require a higher zoom level or who in general can’t see as well may also have frustrating experiences. In this case, I’m referring to an older audience, but that doesn’t mean they’re the only users who experience poor vision. Someone who is browsing your site with their glasses off and a higher prescription would still fall into this category.</p><p>Even users with good vision, colour or otherwise, can still struggle to view your site if you don’t take colour contrast into account. If you’ve ever struggled to read text on a site and you don’t have any form of visual disability, then chances are a user with one or more would have an even more frustrating experience. This goes back to why testing with different users is important — each user is unique, and they may notice different things or have different experiences that give you insight into improvements to be made. If you’re not able to test with actual users in the initial phases of design, using tools like <a href="https://www.getstark.co/">Stark</a>, <a href="http://color.review/">color.review</a> or <a href="http://abc.useallfive.com/">abc.useallfive.com</a> can all help to test how accessible your colours are, giving you the opportunity to make tweaks.</p><h4>How to plan your palettes</h4><p>One of the first things I do when I get a design prompt is to figure out if we have access to brand colours. If we do, then one of my favourite tools is <a href="https://abc.useallfive.com/">this accessible colour palette tool</a> by Use All Five. You can add in a bunch of colours from your brand and see how accessible they are with each other. I like to include a white and a black in this palette so that I can better understand how I can design my interactive elements.</p><figure><img alt="A screenshot of the abc.useallfive.com website." src="https://cdn-images-1.medium.com/max/1024/1*8n__rr-Hru3dOCnK_gpPVA.png" /><figcaption>A screenshot of the <a href="http://abc.useallfive.com/">abc.useallfive.com</a> website, where you can begin adding in your colours right away.</figcaption></figure><p>If we don’t have access to brand colours, my first step is to go to their current site and start pulling colours. After I&#39;ve pulled them all, I’ll go back to the palette tool by Use All Five and go through the same steps, but usually, I’ll throw in some additional colours if I find any missing or lacking. I like to brief the client on whether we’ll be making these changes, and provide them with an example of what this would look like and why it’s important. I’ve yet to have a client come back and tell me that these changes can’t be made, especially when we’ve been able to accurately describe the importance of accessibility.</p><p>If I have none of the above to work with, then I like to go to <a href="https://coolors.co/">coolors.co</a> and begin generating a palette. I find this tool nice because, with recent updates, I can now test to see the colours through the lens of different colour blindness variations. I love this feature because now if I have two really similar colours that are going to be nearby each other but serve two wildly different functions and I need the colour to help communicate their differences, then I can choose different colours to use.</p><figure><img alt="The different colour blindness viewing options from coolors.co." src="https://cdn-images-1.medium.com/max/1024/1*vo8P3L0M30ALAwopUJyhaQ.png" /><figcaption>The different colour blindness viewing options from <a href="http://coolors.co/">coolors.co</a>.</figcaption></figure><h4>But wait…what exactly is colour contrast?</h4><p>In the simplest terms, colour contrast refers to the calculated difference in luminance between two colours, indicating how visually similar they are. A ratio is typically generated when it comes to colour contrast, something you may have seen, like 4.5:1 or 7:1. For those familiar with <a href="https://www.w3.org/TR/WCAG20/">WCAG 2.0</a> or <a href="https://www.w3.org/WAI/standards-guidelines/wcag/glance/">WCAG 2.1</a>, you’ll know that depending on different situations, you need to meet a minimum contrast ratio for text to meet accessibility standards.</p><p>For AA standards, <strong>regular text and images</strong> of text must meet a minimum contrast ratio of <strong>4.5:1</strong>. For text sized 18pt, text sized 14pt <strong>and</strong> bolded, or iconography, text must meet a minimum contrast ratio of <strong>3:1</strong>. AAA standards increase these two ratios to <strong>7:1</strong> and <strong>4.5:1</strong> respectively.</p><p><a href="https://webaim.org/articles/contrast/#sc143">It is important to note that colour contrast ratios <strong>do not round</strong></a>. This means that if your contrast ratio is 4.49:1, this <strong>does not pass</strong> AA standards. As designers, we walk a fine line of seeing the contrast, testing it, and seeing that it does pass other visual tests, but I urge us all to not fall victim to these assumptions. It is a better habit to always try to choose colours that meet accessibility standards, then to have to go back and make modifications later.</p><p>In Ontario, with AODA, <a href="https://www.ontario.ca/page/how-make-websites-accessible#section-1">all websites must meet AA accessibility standards by January 1, 2021</a>. At this point, that’s less than 3 months away, and a lot of websites still aren’t likely meeting these requirements. AODA and WCAG both extend past just colour contrast — they also help to ensure compliance with a site’s hierarchy and structure, code compliance in terms of screen reader compatibility, and even captions for videos.</p><blockquote>It’s never too late to get started, so let’s work together to make more of the web accessible.</blockquote><p>The more we as designers continue to educate ourselves, the more accessible websites we can design for the future.</p><p><strong>Disclaimer</strong>: <em>I am not an expert in the field of UI or UX. I am someone who has been working in the field for 5+ years, who started when UI and UX were still questionable fields, even if it had been around long enough that some people knew what it was. I’ve seen it grow. I’ve found more and more resources over time. I’ve second-guessed every design decision. I’ve had internal stakeholders question my designs, only to go back to the original design after more vigorous feedback rounds. I’ve had designs that shifted from something I enjoyed, to something the client was happy with.</em></p><p><em>There are so many ups, downs, and confusion in this field, but every time I find new articles, I feel just that little bit more confident in the decisions that I’m making. I hope that this article finds you well, and you’re able to take it and the information it provides with you into your career and also feel just that little bit more confident in your designs and decisions.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*ikdvZbRAj1vmNClk" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=477011020095" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/colour-contrast-in-ux-design-477011020095">Colour contrast in UX</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Principles & UX — Part 3]]></title>
            <link>https://uxdesign.cc/design-principles-ux-part-3-421a61affc68?source=rss-d9d73ffa7de------2</link>
            <guid isPermaLink="false">https://medium.com/p/421a61affc68</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Tawni Fus]]></dc:creator>
            <pubDate>Mon, 28 Sep 2020 12:21:11 GMT</pubDate>
            <atom:updated>2020-09-28T16:51:44.002Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design Principles &amp; UX — Part 3</h3><h4>What are Design Principles?</h4><p>While these articles are numbered, they are by no means sequential. If this is your first time diving in, here’s a quick intro:</p><p>The principles that exist in the world of design are all outlined to help you create a design that is usable, aesthetically pleasing, and accessible.</p><p>There are a lot of resources out there that help outline these things, with many opinions, lists, and other related teachings that are all useful in their own rights. I wanted to share in multiple releases, some of the principles and techniques that I’ve learned of and follow as a UI/UX designer.</p><p>Today, we’re going to focus on the following:</p><p><strong>System communication<br></strong>The system should inform the user of what is happening.</p><p><strong>System confirmation</strong><br>The system should allow the user to cancel their action(s).</p><p><strong>System consistency</strong><br>The system acts the same across sub-pages and tasks.</p><h3># System communication</h3><p><em>The system should inform the user of what is happening.</em></p><p>If you’ve ever been confused after pressing a button or completing an action because nothing seems to be happening, then you’ve experienced the system not communicating to you properly.</p><p>The system can communicate in many ways:</p><ul><li>By showing a push notification.</li><li>By showing a notification requiring user action.</li><li>By showing a loading icon or state.</li><li>By disabling a feature while it’s doing something.</li><li>By playing a sound or showing something on the screen indicating something has changed or is in progress.</li></ul><p>These are just the first 5 things that come to mind, but the list is truly extensive. It comes down to <strong>notifying the user when the system is doing something</strong>, whether it’s at the result of user action or not. If a system is updating or reloading something automatically, there should be a loading state. If a user presses a button to submit something like a payment, then the system should load while it verifies the payment, and show a success or failure notification to the user.</p><figure><img alt="User on Facebook Messenger sends a message, receives a GIF in response." src="https://cdn-images-1.medium.com/max/450/1*eWy9Hb6usphiscDfdL6Ieg.gif" /><figcaption>This GIF outlines, without sound, the visual notice the system gives the user when the other person has read the message. Source: <a href="https://about.fb.com/wp-content/uploads/2017/06/messenger-gif-1.gif">https://about.fb.com/wp-content/uploads/2017/06/messenger-gif-1.gif</a></figcaption></figure><p>Sounds, in particular, have been of great interest to me lately, and I found a very thorough and well-put article on <a href="https://uxplanet.org/the-role-of-sounds-in-ux-47adb8f82b38">The Role of Sounds in UX</a> that I highly recommend if you aren’t too familiar with sound design. Obviously, sound has its own drawbacks as if the user has their chosen device muted or has an auditory disability, they won’t receive any system feedback. Overall, though, the most important thing to keep in mind is to not overdo it. Not every individual piece needs to have a feedback sound to it and not every action completed by a user needs a sound effect. It’s up to your discretion, but typically <a href="https://www.toptal.com/designers/ux/ux-sounds-guide#:~:text=Mind%20the%20Repetitive%20Tolerance%20in%20UX%20Sound%20Design">less is more with sound</a>.</p><h4>## Tips</h4><ul><li>Tell the user when they succeed or fail after completing an action. Tell the user when the system is doing something that directly impacts what they are trying to get done.</li><li>Remember when adding in any sort of animation, to be careful not to trigger <a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/Seizure_disorders#:~:text=Content%20that%20flickers%2C%20flashes%2C%20or,or%20other%20incapacitating%20physical%20reactions.">epilepsy in your users</a>. I am not an expert in planning for this, but <a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/Seizure_disorders#:~:text=Reduce%20contrast&amp;text=Users%20with%20low%20vision%20are,animated%20content%20will%20cause%20seizures.">this article released by MDN</a> gives some advice for helping reduce the chances of causing a seizure.</li><li>Try and plan for multiple forms of system feedback to the user. Not all users will notice a loading icon changing to success, just as not all users will hear a success sound. If you have both, while there is still a chance of the change being missed, there are at least more opportunities for the user to be informed.</li></ul><h3># System confirmation</h3><p><em>The system should allow the user to cancel their action(s).</em></p><p>Have you ever forgotten to add a subject line or finish writing an email but pressed “send”, and been unable to undo your action? Or, even worse, have you ever been working on a document, and either closed it or refreshed the page and gone back and all of your changes were missing? All of these are examples of actions that would have benefitted from the system confirming that the action the user was taking was the one they wanted to take. As annoying as pop-up windows are, they do serve a practical use in most cases — helping the user to not make errors.</p><figure><img alt="Tumblr post outlining mistaken email sent reading “Hi Jeffrey, I am afraid”." src="https://cdn-images-1.medium.com/max/529/1*Ecq7RGqvsDZaXSVOXBnnOw.png" /><figcaption>The first thing I thought of was this post — a perfect example of pressing send before intended. Source: <a href="https://imgur.com/gallery/5MoCRje">https://imgur.com/gallery/5MoCRje</a></figcaption></figure><p>Error messages, meaning that you’re telling the user where the issue is, is just as important as error prevention itself. Error prevention helps stop users from actually making the error, to begin with — giving the user the opportunity to undo the action if it wasn’t intentional. I find that talking with the developers about what undo features will be available is incredibly insightful. I recently had a discussion with the developers I work with about an undo feature I had included in a design, which wasn’t going to be possible. Instead, I added in text in the prior confirmation step, informing the user that their action would be final. This way, the user knows that their action will be irreversible, but they still have the opportunity to back out.</p><h4>## Tips</h4><ul><li>Talk with your developers about what undo features will be available, and try to do this during ideation before you get into the designs themselves.</li><li>Add in undo and back features where it makes sense. I tend to add more in the designs initially and then make the decision to remove them later on, as I find it easier to remove and then realign things than it is to have to add a feature in later on.</li><li>Use humanizing language. Try to avoid overusing sarcasm and negativity, but don’t be so friendly that it comes across as overbearing. It’s a fine line to walk, but at the end of the day, your goal should be to clearly and effectively communicate what the user needs to do, what the system will do, or any other expectations that the user needs to be aware of.</li></ul><h3>System consistency</h3><p><em>The system acts the same across sub-pages and tasks.</em></p><p>Typically, when you visit a website, you expect all of the subpages to look similar enough to at least make it seem like they came from the same URL. Sometimes this doesn’t happen and it can be jarring, even increasing the chance of the user leaving because they feel they’ve been redirected to a random site. This is on the largest scale, and with the influx of sites being built with tools like <a href="https://www.squarespace.com/">Squarespace</a> and <a href="https://wordpress.com/">WordPress</a>, it gets a lot harder to find sites where entire pages are different.</p><p>What I do see, a lot of the time, are small issues. Things such as inconsistent button styles across pages, or things like a weird button hover state. I was recently scrolling through a site looking for a new small appliance, and I experienced the visual button inconsistency on just the homepage!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/352/1*u7YxAy7giCXwqGK3tsza1Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*GLuwdaWQUbTyLQWLnPyNSQ.png" /><figcaption>Left: A rounded, sentence case button. Right: A rounded square, all-caps button. Both screenshots are of buttons from the same site — the site will remain anonymous.</figcaption></figure><p>In the example above, the thing I dislike the most is the fact that the button styles are so different at the most basic level. Colours and button size all change depending on the context in which the buttons are needed, which I understand and don’t find personally jarring. But when the style changes on the buttons — like the border-radius difference between a fully rounded button and a rounded square button or the font style— I find that I usually find myself scrolling up and down between the button instances to confirm whether I’m going crazy or not.</p><h4>## Tips</h4><ul><li>Try to design a consistent button style with many different variations. Create button variations for filled, outline and text buttons that all align with the main style. It’s a small thing to focus on, but the small elements all help contribute to the overall experience.</li><li>Test and design for all possible button states. This includes inactive, hover, active, focus, and disabled states.</li><li>The same thing is true of form fields — if you’re using an outlined style for form fields on your contact form, you should use the same style for any form fields that are in the footer, modals or other call-to-action sections.</li></ul><p><strong>Disclaimer</strong>: <em>I am not an expert in the field of UI or UX. I am someone who has been working in the field for 5+ years, who started when UI and UX were still questionable fields, even if it had been around long enough that some people knew what it was. I’ve seen it grow. I’ve found more and more resources over time. I’ve second-guessed every design decision. I’ve had internal stakeholders question my designs, only to go back to the original design after more vigorous feedback rounds. I’ve had designs that shifted from something I enjoyed, to something the client was happy with.</em></p><p><em>There are so many ups, downs, and confusion in this field, but every time I find new articles, I feel just that little bit more confident in the decisions that I’m making. I hope that this article finds you well, and you’re able to take it and the information it provides with you into your career and also feel just that little bit more confident in your designs and decisions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=421a61affc68" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/design-principles-ux-part-3-421a61affc68">Design Principles &amp; UX — Part 3</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Principles & UX — Part 2]]></title>
            <link>https://uxdesign.cc/design-principles-ux-part-2-4838b433160e?source=rss-d9d73ffa7de------2</link>
            <guid isPermaLink="false">https://medium.com/p/4838b433160e</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Tawni Fus]]></dc:creator>
            <pubDate>Mon, 21 Sep 2020 10:57:26 GMT</pubDate>
            <atom:updated>2020-09-23T11:37:26.112Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design Principles &amp; UX — Part 2</h3><h4>What are Design Principles?</h4><p>While these articles are numbered, they are by no means sequential. If this is your first time diving in, here’s a quick intro:</p><p>The principles that exist in the world of design are all outlined to help you create a design that is usable, aesthetically pleasing, and accessible.</p><p>There are a lot of resources out there that help outline these things, with many opinions, lists, and other related teachings that are all useful in their own rights. I wanted to share in multiple releases, some of the principles and techniques that I’ve learned of and follow as a UI/UX designer.</p><p>Today, we’re going to focus on the following:</p><p><strong>Simplicity</strong><br>The importance of the phrase “less is more”, and the balance between too much and too little.</p><p><strong>Context</strong><br>The importance of providing visual guides, cues, and context for the user in relation to where they are or where things will lead them.</p><p><strong>Error states</strong><br>The system should communicate clearly to the user where and how they’ve made a mistake.</p><h3># Simplicity</h3><p><em>The importance of the phrase “less is more”, and the balance between too much and too little.</em></p><p>“Good design is as little design as possible.” — <a href="https://www.vitsoe.com/gb/about/good-design">Deiter Rams</a></p><p>David Hogue presented an entire talk on how <a href="https://www.youtube.com/watch?v=24wTWjHavhs">Simplicity is not Simple</a>.</p><p>There are even more quotes and articles out there outlining how difficult simplicity in design is and how important it is, enough that I could fill an entire article just linking to them all. The problem that arises with simplicity is a double-edged sword: how much is too much or too little? Where is that perfect balance for this particular implementation? On top of that, where do you start trimming? Is the design what’s over-complicating the end result, or is there too much copy? Is the copy too confusing?</p><p>It feels like sometimes when you get the design <em>just right</em>, it’s like a lightbulb has gone off and now there’s a spotlight on your design. But getting that is like trying to wire the entire electrical system necessary to get it to work. The worst part is, is that not every site will need or benefit from the same level or levels of simplicity. A highly technical website that benefits from providing its users with extremely high-level descriptions, a lot of diagrams and many subsections will have a very different definition of simplicity than a site whose main purpose is to act as a conversion-based landing page with a few bits of text and a form.</p><figure><img alt="Screenshot from Apple comparing 4 iPad models — Pro, Air, regular and mini." src="https://cdn-images-1.medium.com/max/1024/1*T0YNOlW7zvuz1F8w-apkbg.png" /><figcaption>A simple, table-style comparison chart. Screenshot is taken from <a href="https://www.apple.com/ipad/">https://www.apple.com/ipad/</a>, used for illustrative purposes only.</figcaption></figure><p>Keeping the background and the elements, not just the text, from being over-complicated is also important. <a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/Seizure_disorders">Accessibility is a concern when it comes to animation</a>, as users with epilepsy and other seizure disorders can be triggered by the frequency and type of animation you’re using. Avoid overemphasizing elements that don&#39;t need it. Minimize the need for excessive animations — hover transitions between colours, font weights or underlines are all very common on websites, whereas any blinking background behind text is not.</p><h4>## Tips</h4><ul><li>Research what other sites in the same field are doing. You can get a baseline not only on the design itself but the content structure to understand what you feel would work or wouldn’t work.</li><li>Test on different screen resolutions and device sizes. Simplifying the design might be necessary to ensure compatibility across many devices so that you don’t have to create a separate design for each screen size.</li><li>Ask questions and test with your users. If they can’t find the information they need when they need it, it can be a symptom of an overcomplicated or oversimplified design. Perform user testing in a way where you can see your users interacting with your site.</li></ul><h3># Context</h3><p><em>The importance of providing visual guides, cues, and context for the user in relation to where they are or where things will lead them.</em></p><p>This is arguably one of the most missed pieces in the design field. Even today, sometimes I still forget to give the user the context that they need at all times. If you’ve ever hovered over a button that doesn’t change colour or filled out a form only to discover you missed a field but can’t determine which, you’ve been victim to the design not communicating the correct context to you as a user. But how do you even know if you’re missing context?</p><figure><img alt="Animated line signifying scrolling on Volkswagen’s homepage. Bouncing chat bubble drawing the user’s eye to the chat." src="https://cdn-images-1.medium.com/max/1024/1*8wbD_pF-9zREKzrVWoh0tg.gif" /><figcaption>Short GIF taken from <a href="https://www.vw.ca/en.html">https://www.vw.ca/en.html</a>, showing both the guide for scrolling and the bouncing chat bubble for drawing the user’s eye to the chat. Used for illustrative purposes only.</figcaption></figure><p>User testing. Mic drop. Not really, because user testing truly requires a lot more than two words to give it context. By user testing, I mean test with your stakeholders. Make sure what you’re designing covers what they’re anticipating it will do. Test with potential users, ensuring that what they want to do can be done. Test with potential non-users — they may not be using your site, but they should still be able to figure out what it’s for and how to use it with little to no outside assistance.</p><p>Not only that, but you need to test on different device sizes and types — each phone is not made equal, and each device can have you suddenly scrambling to understand whether 1365px or 1367px needs to be your next breakpoint or not. With respect to context, you need to make sure that you’re still communicating what you intend to even on these different devices. Some typical breakpoints are defined here, in a <a href="https://www.w3schools.com/HOWTO/howto_css_media_query_breakpoints.asp">mini-tutorial by W3Schools</a>.</p><figure><img alt="Some common breakpoints used in coding a responsive grid layout." src="https://cdn-images-1.medium.com/max/1024/1*zvHGqWC2JKH5j2ILzR-VcQ.png" /><figcaption>Some common breakpoints used in coding a responsive grid layout. You can plan for different scenarios as outlined above, for example, a common 13&quot; laptop screen would typically be considered over $lg-screen: 1200px vs. phones falling under the $sm-screen: 600px breakpoint.</figcaption></figure><p>A phone should not be missing elements that are accessible on desktop without telling the user why or without a very visible reason for it not being there. A desktop site should not be so mobile-first optimized that it is missing important hover states and keyboard interactions. There’s a lot to keep in mind to ensure your users can complete their tasks successfully, but it can be done with a combination of focus and list-making.</p><h4>## Tips</h4><ul><li>Test with different types of users — they’ll be able to give you unique perspectives that you won’t be able to get in any other way. They’ll likely use different methods and devices, and you’ll be able to capture what the most important information is to them to give them context.</li><li>Look at what other sites in the same field are doing — are you using copy that is going to be jarring to the user to see, making them have to think more to complete the same action?</li><li>Take a look into your analytics if you can — if you have something like <a href="https://www.hotjar.com/">Hotjar</a> accessible, take a look at the heatmaps. If you have access to an analytics tool like <a href="https://www.youtube.com/watch?v=lZf3YYkIg8w">Google Analytics</a>, take a look at how long users are spending on pages. If they aren’t spending a lot of time on key pages, see where they’re going. If they’re spending what seems like a lot of time on key pages, see if its because they’re getting the information or if they’re getting confused and are just staying there trying to get directions.</li></ul><h3># Error states</h3><p><em>The system should communicate clearly to the user where and how they’ve made a mistake.</em></p><p>This ties in a lot with context, but goes a bit deeper into system-user communication. As designers, we’re bridging the gap between a system completing a user’s action and the user themselves, with only an interface.</p><p>Take, for example, your typical checkout process:</p><ol><li>You add items to your cart</li></ol><p>2. You review your cart’s total and items</p><p>3. You enter any shipping and billing information</p><p>4. You enter your payment information</p><p>5. You review everything once more</p><p>6. You place your order</p><p>That’s what it should look like. Sometimes, you may see around step 6, you are suddenly sent back to step 3 or 4 because of an issue with your entered payment or billing information. The biggest frustration is wondering why there wasn’t a check when you were <em>leaving</em><strong><em> </em></strong><em>that step</em> for whether your information was accurate or not. Some forms won’t even tell you <em>where</em> you went wrong, only that something doesn’t look right.</p><figure><img alt="Best Buy contact information form with validation before email address has finished being typed." src="https://cdn-images-1.medium.com/max/1024/1*AATBvsu_wzsnWaUSoDBTCw.png" /><figcaption>Image from Best Buy where they have validation before the user has finished typing their input. Source: <a href="https://www.nngroup.com/articles/errors-forms-design-guidelines/">https://www.nngroup.com/articles/errors-forms-design-guidelines/</a>. Image used for illustrative purposes only.</figcaption></figure><p>That’s not even including the ambiguous error messages in popups, confusing error text for form fields, and just wondering what the text “Error” really means. Sometimes the system throws an error that isn’t easily understandable by your average user and requires assistance from a system administrator. Making sure that you tell your user that is what is important. Give a user an opportunity to fix their errors or guide them to how they can accomplish this. Make it fun or make it serious, but make sure you aren’t being rude, harmful or inconsiderate of your users.</p><h4>## Tips</h4><ul><li>If you can, talk with the developers about when to show what error message. Sometimes they can be very focused on the technical, and may not realize the error text they’re using by default isn’t user-friendly enough. Talking with them can also help them apply the error messages later on when new forms need to be built.</li><li>If you aren’t sure how to communicate what you want to the user, take some time to research. See what other sites are doing, and look into different design patterns like <a href="https://semantic-ui.com/">Semantic UI</a> and <a href="https://material.io/components/text-fields/">Material Design</a> to see how they’re handling error messages.</li><li>Avoid validating before the user has finished inputting all of their data. It comes across rudely and can fluster the user into actually entering inaccurate data because they think what they’re typing is going to be wrong regardless of what they do, or they get confused.</li></ul><p><strong>Disclaimer</strong>: <em>I am not an expert in the field of UI or UX. I am someone who has been working in the field for 5+ years, who started when UI and UX were still questionable fields, even if it had been around long enough that some people knew what it was. I’ve seen it grow. I’ve found more and more resources over time. I’ve second-guessed every design decision. I’ve had internal stakeholders question my designs, only to go back to the original design after more vigorous feedback rounds. I’ve had designs that shifted from something I enjoyed, to something the client was happy with.</em></p><p><em>There are so many ups, downs, and confusion in this field, but every time I find new articles, I feel just that little bit more confident in the decisions that I’m making. I hope that this article finds you well, and you’re able to take it and the information it provides with you into your career and also feel just that little bit more confident in your designs and decisions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4838b433160e" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/design-principles-ux-part-2-4838b433160e">Design Principles &amp; UX — Part 2</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My top 5 frequently forgotten design elements]]></title>
            <link>https://medium.com/design-bootcamp/my-top-5-frequently-forgotten-design-elements-d9af8e8e7835?source=rss-d9d73ffa7de------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9af8e8e7835</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Tawni Fus]]></dc:creator>
            <pubDate>Mon, 14 Sep 2020 20:31:58 GMT</pubDate>
            <atom:updated>2020-09-17T23:54:48.816Z</atom:updated>
            <content:encoded><![CDATA[<h4>These are some elements that should not be forgotten in the design process.</h4><p>As a designer, I do my best to put myself in my user’s shoes. I try to consider all of the different states and screens they could and should experience throughout their journey. Sometimes, I don’t get it right. I write this so that you as a designer can hopefully catch some of these things before you finalize a design, and avoid some unnecessary back-and-forth with the developers.</p><p>Without further ado, let me share with you the top 5 elements I tend to forget about when designing.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3ohhwoBqhih33ck000%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3ohhwoBqhih33ck000%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F3ohhwoBqhih33ck000%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/c5ad5c3c19400aa2ce050e97f0abca46/href">https://medium.com/media/c5ad5c3c19400aa2ce050e97f0abca46/href</a></iframe><h3># 1. Error pages</h3><p>Have you ever visited a site and tried to go to a page that didn’t exist any longer? These are the error pages I’m talking about. Those pesky 400, 403, 404, 500 or even 503 error messages that are scarier and scarier the higher the number seems to go. Somehow, I always seem to forget that these pages do not just inherit the design of the site and that they do actually benefit from unique routes and designs.</p><figure><img alt="A screen capture of Mint’s unclear error page for illustrative purposes only." src="https://cdn-images-1.medium.com/max/1024/1*oB2rR8hvr0HsIrEOeKMBPQ.png" /><figcaption>I grabbed a quick screenshot of Mint’s error page — it wasn’t very responsive to my laptop screen — I can barely understand exactly what’s going on here. This screenshot is used for illustrative purposes only.</figcaption></figure><p>You don’t even need to always design a unique page. A lot of times, while ambiguous, each error code has enough of a description that you can describe to the user what happened without having to create unique error text. As long as you have a consistent list of links to help get them back on track, you can take away some of the frustration they face. Another technique you can use is to just have a general error page, describing that an error occurred, but not describe <em>what</em> the error was. I tend to favour these less, as I prefer to provide more rather than less detail.</p><figure><img alt="A screen capture of Oreo’s clean and simple error page for illustrative purposes only." src="https://cdn-images-1.medium.com/max/1024/1*5bERXoYQtSuPbVvR_fHnuA.png" /><figcaption>Oreo’s error page is on-brand — slightly humourous, clearly communicates what’s happening and gives the user a way back to the homepage to try again. This screenshot is used for illustrative purposes only.</figcaption></figure><h4>## Why is this important?</h4><p>It helps with consistency and helping your users feel like they made a mistake, not a fatal error. These pages should be clear, concise and give the users direct actions to take to help get them back on track. If you’re able to directly tell someone why they’re experiencing the error, then that’s even better. The non-designed error pages can communicate a lack of attention to detail and a level of uncaring, in my opinion. It shows that the designer or development team didn’t take the time or put in the effort to ensure a fully cohesive experience.</p><p>These pages also offer up the opportunity for humour, easter eggs and other cool things that your main site can’t or doesn’t have. It’s a small opportunity for levity and building both brand trust and loyalty. Users may not be visiting these pages often (or at least, hopefully, they aren’t visiting these pages often), but they should still be given some love and attention.</p><p>Some of my favourite error pages include:</p><ul><li><a href="https://dribbble.com/404">https://dribbble.com/404</a></li><li><a href="https://www.canva.com/404">https://www.canva.com/404</a></li><li><a href="https://slack.com/404">https://slack.com/404</a></li><li><a href="https://www.postman.com/404">https://www.postman.com/404</a></li><li><a href="https://www.airbnb.com/404">https://www.airbnb.com/404</a></li></ul><h3># 2. Search results pages</h3><p>Think about the page you see when you complete a Google search — you essentially get a curated list of results based on keywords entered by you, in an easy-to-read format. These pages can often require a different design for mobile and desktop, as typically mobile cannot show the same volume of information as on desktop.</p><p>But think about how it shows up — you have a search bar to redo a search, you have your list of results (sometimes filterable by number of results, sometimes capped and then paginated), and then you usually have other quick links to help you out. When the developer begins on this page, their focus isn’t going to be on including all of the minute details that help make a cohesive experience for a user. Their focus is going to be on creating the MVP — a <strong>M</strong>inimum <strong>V</strong>iable <strong>P</strong>roduct. In essence, the bare minimum of function that if nothing else, doesn’t leave the user floundering for what to do. It’s not going to include the stylistic flairs or the small details that make it different. They may not know which links to include to help guide a user, so they don’t include them. They may not think to highlight or bold the keywords the user searched — all things that come from the design.</p><figure><img alt="Image from Crisp — a visual description of the MVP process of adding small features to make a better overall product." src="https://cdn-images-1.medium.com/max/609/1*cpD75_2-XWyn22MeL4RsCw.jpeg" /><figcaption>Image source: <a href="https://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp">https://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp</a></figcaption></figure><h4>## Why is this important?</h4><p>This page is important to consider for the small pieces of the user experience that help make this page feel like it’s a part of the site. The extended branding on a (hopefully) less-often used page and the highlighting of their keywords in their results to help them find what they’re looking for. This is even more important when considering mobile responsiveness because what is initially coded without design may not be responsive in the way that you as a designer want it to be. Text may wrap or truncate weirdly, or a particular feature may be missing that is important to the overall user experience.</p><p>It also helps in building a more cohesive prototype. By not forgetting this page, there will be no more “Oh, this will go to a different page on the actual site.” responses when asked, “What happens when I click this?”. If you test as a user and try and complete everything possible, you’ll often uncover these less popular pages and be able to include a design or design direct for them. Testing your design with other stakeholders can also help to get more valuable information, too. With all of this, you can create a list of pages to not forget so that in future projects, you can capture them during the design process.</p><p>This also helps to future-proof your design — there will be fewer opportunities for the page to suddenly come up during the final review as something that was originally missed. Oftentimes, the biggest stress of not catching things soon enough is the fact that now that it’s been caught, it’s additional work that has to be done while over budget.</p><h3>#3. Form field error text and validation text</h3><p>When I’m designing a form, I usually manage to get around 80% of the error text added to the style guide to avoid any confusion down the line. But inevitably, I forget something and realize I’ve forgotten it when I’m testing and see something as generic as “Error” as the error text for a form field validation. Thankfully, I’ve not yet run into a situation where I’ve completely forgotten the text, but that’s because I’ve been burned before by other forms not communicating to me clearly where I went wrong.</p><p>There’s a couple of implementations to this — including a list either above or below the form letting the user know where they went wrong or doing inline validation. I’m partial to inline validation, as I can then design each form field to go red and show its respective error text right by where the error is. I find this to be more likely to draw the user’s eye to where the problem actually is, instead of having them scroll around trying to make sure they’ve caught everything that they need to. That’s not saying that you can’t do both — I’ve never personally found a use case for it but it is also perfectly viable.</p><h4>## Why is this important?</h4><p>This validation or error text helps guide the user to the right path of completing the action they’re trying to complete. Without including this, your user is going to think there’s a problem with the button or something else that likely isn’t the fact that they’re missing the @ symbol of their email address.</p><blockquote>This can lead to frustration, and at its most severe, the user having a bad enough experience that they won’t return.</blockquote><figure><img alt="Clear error text letting the user know what’s missing as compared to just the text “Error”." src="https://cdn-images-1.medium.com/max/1000/1*8aJCMG7Dnt-_Ii4fqA_TUw.png" /><figcaption>On the left: Better validation text. You typically want to follow “less is more” for validation text, but this isn’t always possible. On the right: Poor validation text. This doesn’t provide a lot of clarity to the user.</figcaption></figure><p>Putting some time, thought and effort into the text itself helps to decrease the cognitive load on users — this being the time it takes for them to parse the information being given to them. With the risk of information overload and frustration imminent at any given time, we want to reduce this as much as possible. A user shouldn’t have to think harder than necessary just to fill out their login or shipping information. They shouldn’t feel guilty or afraid of being at fault, the system should just politely let them know so that they can get on with their day (or night).</p><h3>#4. Button variations</h3><p>Even today, unless I actively need a button variation, chances are I’ve forgotten it from the style guide. Button variations refer to the buttons (from a developer’s standpoint) called primary, secondary, and tertiary. From a user’s perspective, chances are these are just “buttons” or even “links”. For those more tech-savvy, you may find yourself picking up on the difference between raised, filled, ghost, outline, and text-only buttons. These are all typically included in a style guide to help future-proof the design and make it easier on the developer to take some creative freedom on pages that may not require a full design, but require different variations of smaller components.</p><figure><img alt="Different button states for three styles of buttons — filled, outline, and text." src="https://cdn-images-1.medium.com/max/1000/1*8CgbbWM4-FmN3SBV9rVXCA.png" /><figcaption>Examples of three of the most common button styles. From top to bottom: filled, outlined and text.</figcaption></figure><p>This is something I find I usually have to add in at a later time or approve when the developer comes back with a page, and I then realize I forgot something important because they’ve added it in themselves. In this case, sometimes the developer has designed something that matches nicely with the overall brand tone. Other times, you get something that looks out of place for one reason or another, and then have to provide the additional design. It’s easier for both of you to include as much as you can from the start.</p><p>You can check out <a href="https://material.io/components/buttons">Material’s button design guidelines</a> for a reference of what a really in-depth button portion of a style guide could look like.</p><h4>## Why is this important?</h4><p>The button variations are important for keeping the buttons consistent across all of their states and all possible designs and places it can be added on a site. By planning for everything from the hover to the active state, you’re ensuring nothing odd happens like a button suddenly changing from blue to red when it shouldn’t. In addition to this, it’s important for keeping the designs and development process on par for the component.</p><p>I find that if I start with the small components like buttons, headers, and form fields, including all of the possible states, then chances are I’ll do the same for larger components as well. Things like cards, rows, and even images in different applications can all benefit from being specified in a style guide. I usually start small and work my way up and find that my style guide is more cohesive and robust to pass off to the developer.</p><h3>#5. Responsive tablet designs</h3><p>When I design, I look into Analytics either from Google Analytics or general trends before getting into the process to understand what devices I should plan for first. In every case so far, the tablet has been the least used device type of users. As such, I tend to let these designs fall through the cracks. A lot of times you are okay because a lot of tablets are large enough that the desktop versions look well enough that they don’t require a full redesign.</p><p>The problem comes in when a tablet can’t decide whether it’s going to follow the desktop or mobile design. On certain tablets it will show one or the other, causing an inconsistent experience for different tablet users. The difference in resolutions for the iPad and iPad Pro come to mind — I’ve had to design specifically for tablet because the iPad will take the mobile design, whereas the iPad Pro will take the desktop design. I try and leave a bit of my design time for later in the process to help accommodate this. I don’t tend to design it up-front, because I don’t always need to. I try to test the design once we’re in the development phase to see where the pain points are and could crop up, and then design to target these instead of designing right away.</p><h4>## Why is this important?</h4><p>The biggest reason why this is important is that if you don’t consider this in the design process, you’re ignoring a part of your audience. Your users are going to have less of a good experience than those visiting on the devices you planned for, and this may cause them unnecessary stress and frustration. You’re leaving a design gap that can come off as unprofessional to both prospective and returning users from a different device.</p><p>You want to ensure that you’re considering all of your users, like how you would when planning for accessibility. You shouldn’t directly ignore a user because you don’t want to design for something, or because you never put any thought into it. If you don’t include a design right away, you should at least test through the development process and ensure that the design is actually responsive to these different devices.</p><blockquote>As UI and UX designers, our job is to think for the users before they have to think for themselves.</blockquote><p><strong>Disclaimer</strong>: <em>I am not an expert in the field of UI or UX. I am someone who has been working in the field for 5+ years, who started when UI and UX were still questionable fields, even if it had been around long enough that some people knew what it was. I’ve seen it grow. I’ve found more and more resources over time. I’ve second-guessed every design decision. I’ve had internal stakeholders question my designs, only to go back to the original design after more vigorous feedback rounds. I’ve had designs that shifted from something I enjoyed, to something the client was happy with.</em></p><p><em>There are so many ups, downs, and confusion in this field, but every time I find new articles, I feel just that little bit more confident in the decisions that I’m making. I hope that this article finds you well, and you’re able to take it and the information it provides with you into your career and also feel just that little bit more confident in your designs and decisions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9af8e8e7835" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/my-top-5-frequently-forgotten-design-elements-d9af8e8e7835">My top 5 frequently forgotten design elements</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Principles & UX — Part 1]]></title>
            <link>https://uxdesign.cc/design-principles-ux-part-1-d48de5668775?source=rss-d9d73ffa7de------2</link>
            <guid isPermaLink="false">https://medium.com/p/d48de5668775</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Tawni Fus]]></dc:creator>
            <pubDate>Mon, 07 Sep 2020 15:21:56 GMT</pubDate>
            <atom:updated>2020-09-15T11:48:32.395Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design Principles &amp; UX — Part 1</h3><p>What are Design Principles?</p><p>The principles that exist in the world of design are all outlined to help you create a design that is usable, aesthetically pleasing, and accessible.</p><p>There are a lot of resources out there that help outline these things, with many opinions, lists, and other related teachings that are all useful in their own rights. I wanted to share in multiple releases, some of the principles and techniques that I’ve learned of and follow as a UI/UX designer.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fj2wpZyLy2s70ul4TKo%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fj2wpZyLy2s70ul4TKo%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fj2wpZyLy2s70ul4TKo%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/90f99aaf1a5892bc1065d8b90b8a7e6a/href">https://medium.com/media/90f99aaf1a5892bc1065d8b90b8a7e6a/href</a></iframe><p>Without further ado, let’s get into the following:</p><p><strong>Hierarchy<br></strong>The importance of providing visual emphasis on different elements to communicate their level in the page’s hierarchy.</p><p><strong>Contrast</strong><br>The importance of providing accessible contrast between elements and the background.</p><p><strong>Proximity</strong><br>The importance of grouping related elements.</p><h3># Hierarchy</h3><p><em>The importance of providing visual emphasis on different elements to communicate their level in the page’s hierarchy.</em></p><p>In design, headings are something you should become incredibly comfortable with. They help to communicate different sections on the page, in terms of their relation to the previous sections on the page. They can also help to give your brand personality, depending on the font family and size that you’re choosing to use, as well as the text itself.</p><p>Hierarchy can be communicated by one or many of the following:</p><ul><li>Font size and weight</li><li>Font colour</li><li>Background colour or highlight colour</li><li>Text decoration</li><li>Spacing and dividers</li></ul><figure><img alt="Visual examples of font styles, weight and accents for headers." src="https://cdn-images-1.medium.com/max/1024/1*F8pEFsO07UeC4bsI1_Z4Ww.png" /><figcaption>Examples of heading differentiation styles. Font weight, colour, stylization, and dividers.</figcaption></figure><p>Depending on your website’s theme, you can employ only one of these techniques or as many as visually suits it. I find that I always use different font sizes, as typically the sections of information lose their importance the lower into the hierarchy you go. The other thing that I find I do often, is to modify the font sizes for mobile. Because you’re dealing with a much smaller screen, and sometimes a screen with a different zoom level, larger font sizes can often appear oversized and obtrusive.</p><p>I’ve seen some sites which use a highlight behind a header to give it a burst of colour and some personality, as well as other decoration. I find using lines either beside the heading or underlines are a nice touch, and helps to make it easier to relate body copy to the header in terms of spacing. Font colour for headers can also help to bring a nice differentiating factor between blocks of text, and draw a user’s eye to the header after scrolling through a section.</p><p>The dividers specifically are something I tend to forget about, but are absolutely important, especially in websites which may have long sections of text in between sections, with potentially harder to distinguish headers. Understanding where a section ends can help a user scroll better and can help break up these large sections of text so that they don’t feel like they’ve been scrolling for hours.</p><h4>## Tips</h4><ul><li>Be careful with the fonts you’re choosing for your headers. If you use a decorative or script font, it may seem that the larger font size of headers may help, it doesn’t necessarily in production. Sans-serif and serif fonts are better options for headers, as they should remain legible across all device types and screen sizes.</li><li>If all of your headers are intended to be visually the same, keep in mind that this may get confusing for both developers and your intended users. Make sure to still differentiate your headers from your main body text and from each other, especially if your headers communicate the same thing.</li><li>Try to be consistent in your header use. The developer(s) also need to be aware of this, but as a designer, you should make sure that you aren’t using a font size of 48px for a second-level heading on one page and font size of 48px for a first-level heading on another page.</li><li>Get comfortable learning the different header types for a website and be sure to communicate clearly in your style guide what you want each one to look like after development. Otherwise, you and the developer may find yourself with different expectations.</li></ul><h3># Contrast</h3><p><em>The importance of providing accessible contrast between elements and the background.</em></p><p>Have you ever tried to read red writing on a green background?</p><p>Have you ever had to highlight the text on a page just to read it, because the highlighted colour provides better contrast?</p><p>Have you ever viewed a web page with low screen brightness and been unable to read it? Have you ever increased your brightness and realized you <em>still can’t read the page</em>?</p><figure><img alt="Visual example of poor contrast (1:1) and good contrast (8.8:1)." src="https://cdn-images-1.medium.com/max/1000/1*no38Zq6fZJ1iUX9TbGaRkQ.png" /><figcaption>Examples of good and bad contrast at its most basic. Left: 1:1 contrast, fail. Right: 8.8:1 contrast, AAA.</figcaption></figure><p>That’s the importance of contrast. Being able to read the page. But it goes further than just your average pair of eyes: what about users who face little to no vision? What about the users who view colour differently, or those who view no colour? If someone with good vision is struggling with your site, what is it like for those with less than good vision?</p><p>There are many colour contrast tools that you can use to check if you want to come up with good contrast pairings, and there are also plugins you can use for your respective design tools or even your browsers for testing to both check if the contrast is high enough or view in other colour modes. The higher the contrast value is on the left, the better your contrast on the site. There are different levels for meeting contrast accessibility, which you can find from checking the <a href="https://www.w3.org/TR/WCAG20/">WCAG 2.0 documentation</a>.</p><p>Some of those tools include:</p><ul><li><a href="https://color.review/">https://color.review/</a></li><li><a href="https://webaim.org/resources/contrastchecker/">https://webaim.org/resources/contrastchecker/</a></li><li><a href="https://coolors.co/contrast-checker/112a46-acc8e5">https://coolors.co/contrast-checker</a></li></ul><p>It’s important to remember that different font sizes, weights, and even icons and other elements all have different base contrast ratios to meet. These even differ between compliance levels: A, AA, and AAA all have different ratios, with A being the strictest, while AAA is the latest. You can <a href="https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html">read more on the WCAG 2.1 guidelines</a> to better understand what you need to do to design an accessible site.</p><p>The more you train yourself before the design process to get used to designing for accessibility, the more it becomes something ingrained and habitual for you in the future. These colour contrast guidelines are most important for <strong>elements with which the user will interact with</strong>. This means any buttons, links, headers, body copy, and forms should all follow these guidelines for all of their states to ensure that your users can actually complete actions on your site.</p><h4>## Tips</h4><ul><li>Read up on your guidelines if you aren’t familiar with them. It does get more difficult, but you can still build a beautiful colour palette that is both accessible and suits your brand.</li><li>Remember that your website’s main content doesn’t need to take advantage of your brand palette! Your logo and large blocks of colour can be your brand colour, but the interactive elements, headers and other text can all be darker variations to improve legibility.</li><li>Remember to test your design at all stages. When you’re first prototyping something, test. As you move into development, keep testing. Testing doesn’t actually ever end — unless you hit a point where you’ve run out of time or the site is entirely out of your control.</li></ul><h3># Proximity</h3><p><em>The importance of grouping related elements.</em></p><p>Have you ever used a form where you’re not entirely sure whether the form field and the next adjacent label is actually related to the form field you’re inputting data into? That’s one of the more obvious signs of proximity not being properly taken into account where design is concerned.</p><figure><img alt="Left: example of better spacing between form fields. Right: example of bad spacing between form fields — it’s all equal." src="https://cdn-images-1.medium.com/max/1000/1*8yCvPHfjrqippLJnIzwyVg.png" /><figcaption>Left: Better proximity between form field labels and the form fields. Right: Evenly spaced labels and form fields make for a very confusing form.</figcaption></figure><p>Proximity in my mind is also directly related to spacing, in that your line-height should be small enough that a paragraph looks like a paragraph and not a bunch of poorly structured paragraphs, and that your paragraphs look like they’re properly spaced from each other. This is also important in list design, as you typically want more spacing than your typical line-height, but less spacing than that between your paragraphs. Play around with list spacing — usually this can be modified in the code.</p><p>Not only that, but any related elements like buttons, graphics, or icons should all be close enough to their parent item to make it clear that the items are actually related. A form’s submit button shouldn’t be spaced so far apart from the form that it looks like it’s just a floating CTA button. Icons should be spaced closer to their respective links than the next link. If an image has a caption, the caption should visually look like it’s describing the image and not a floating paragraph with no context.</p><h4>## Tips</h4><ul><li>Do a window test on your site or the design you’re working on if you think that elements may be too far apart. A window test is done by creating a box around a part of the design, resizing the viewport of your design, or resizing the artboard of your design.</li><li>Remember that proximity might change as screen sizes change. Often, I find things I have situated in multiple columns for desktop need to be shifted to only be 1 or maybe 2 columns for mobile, which means the design itself needs to change to be responsive.</li></ul><p><strong>Disclaimer</strong>: <em>I am not an expert in the field of UI or UX. I am someone who has been working in the field for 5+ years, who started when UI and UX were still questionable fields, even if it had been around long enough that some people knew what it was. I’ve seen it grow. I’ve found more and more resources over time. I’ve second-guessed every design decision. I’ve had internal stakeholders question my designs, only to go back to the original design after more vigorous feedback rounds. I’ve had designs that shifted from something I enjoyed, to something the client was happy with.</em></p><p><em>There are so many ups, downs, and confusion in this field, but every time I find new articles, I feel just that little bit more confident in the decisions that I’m making. I hope that this article finds you well, and you’re able to take it and the information it provides with you into your career and also feel just that little bit more confident in your designs and decisions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d48de5668775" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/design-principles-ux-part-1-d48de5668775">Design Principles &amp; UX — Part 1</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello and welcome!]]></title>
            <link>https://tawnifus.medium.com/hello-and-welcome-cc26c7b027c8?source=rss-d9d73ffa7de------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc26c7b027c8</guid>
            <dc:creator><![CDATA[Tawni Fus]]></dc:creator>
            <pubDate>Mon, 07 Sep 2020 14:39:57 GMT</pubDate>
            <atom:updated>2020-09-07T14:39:57.592Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FOF0yOAufcWLfi%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FOF0yOAufcWLfi%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FOF0yOAufcWLfi%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="215" frameborder="0" scrolling="no"><a href="https://medium.com/media/a0220ec5191b70e7613309602ebce94e/href">https://medium.com/media/a0220ec5191b70e7613309602ebce94e/href</a></iframe><p>Hi there!</p><p>Before diving into article writing for the sake of sharing what I’ve learned in the fields of UI and UX, I wanted to first introduce myself.</p><p>My name is Tawni, and I’ve been working as a UI/UX Designer at a marketing company for just over three years. I’ve predominantly worked with the software development team to help design the experiences for the internal software, but I’ve also hopped on some client projects that require a more complicated design.</p><p>In my spare time, I love to bake, read, cook, play video games, crochet, draw, garden — the list goes on. Getting the opportunity at home or for work to make something that not only am I proud of, but that can bring others joy or make their lives easier is what keeps me moving forward.</p><p>I’m hoping that the articles I write and share help give some perspective on UI and UX, or even offer you something new that you may not have seen framed the way I’m framing it. I know it’s difficult because there’s been a huge surge of UI and UX articles respectively, but for every person that posts an article, new perspectives and new conversations are all created.</p><p>Feel free to ask questions or just comment! I respect that my opinions may have flaws and that there will always be something new to learn, and that we can only improve if we’re willing to listen and learn from those who have their own unique experiences. I’m here to both share my knowledge and learn from everyone else. So please, comment away!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc26c7b027c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>