<?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 Patrick Cox on Medium]]></title>
        <description><![CDATA[Stories by Patrick Cox on Medium]]></description>
        <link>https://medium.com/@pcrides?source=rss-904324500917------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*t3d5ni9j0OuCpiOUhwkmQQ.jpeg</url>
            <title>Stories by Patrick Cox on Medium</title>
            <link>https://medium.com/@pcrides?source=rss-904324500917------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:05:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pcrides/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[Rebooting a Classic]]></title>
            <link>https://medium.com/lunch-ux/rebooting-a-classic-cb7cd24f6491?source=rss-904324500917------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb7cd24f6491</guid>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[lunchux]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Patrick Cox]]></dc:creator>
            <pubDate>Tue, 10 Jul 2018 07:37:45 GMT</pubDate>
            <atom:updated>2018-07-10T07:37:45.610Z</atom:updated>
            <content:encoded><![CDATA[<p>The year was 2014. The location, Lehi Utah. The local design community was boring to say the least. Enter a middle aged UX designer who really had an itch to “pay-it-forward” for all the people that had helped him become a better designer one small bit sized twitter post or DM at a time. (that’s me if you haven’t guessed).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dDuWrT6waYltjraORF35jw.png" /><figcaption>Check out Lunch JS, they do some really great stuff, I promise.</figcaption></figure><p>After attending a <a href="https://www.meetup.com/lunch-js/">Lunch JS meetup</a> and having a great time despite not knowing about anything, anyone was talking about, I thought “wow, developer meetups are great, why?” Well, turns out it’s because they are practical and focussed on teaching not presenting. So, with the help of my fellow designer <a href="https://medium.com/u/92add053657b">Derek Cramer</a> I started <a href="https://www.meetup.com/lunchux/">Lunch UX</a>.</p><p>We had a good run and went from like 13 attendees to 100+ before I was asking to join another meetup group, PDA (product design association).</p><h4>In The Beginning</h4><p>I wanted to start a designer meetup that was not about the person speaking, but about the topic. I wanted the people speaking to be real designers in our community that were working on real problems, those problems being the topics. I really just wanted attendees to learn something practical that they could go back to work with that afternoon or the next day and apply.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5M8ILNlcA6pWhLiZewXpCw.png" /><figcaption>The first five events of the OG Lunch UX. If you weren’t there they were great events, I promise.</figcaption></figure><p>Not knowing anything about running a meetup or getting someone to buy lunch for a small group of people I used my friends and myself to get things going. I used Meetup.com to manage the events and their platform was really great not only for managing the events but also allowed people to find us pretty quickly. While the first few events were mostly friends and co-workers, by the 4th or 5th event we really started to pickup steam and had about 50 people in attendance. Mostly due to Instructure buying us free lunch.</p><h4>A Lot Great Feedback and Memories</h4><p>As more people attended I was getting cornered after the event by people who wanted to express how much fun they were having at the events and telling me stories about how they applied something at work that they had learned in a past event. It was working!</p><p>It was fantastic to hear that people were getting more than just full belly’s, especially because we had some pretty interesting presentations. Since I wanted to have real people present, that meant that we would have real people present some very unpolished and unpracticed presentations. But this lead to some really fun awkward moments and interesting shared experiences that bonded the group together.</p><p>One of the classic memories I have was the time <a href="https://medium.com/u/9ddca0b230e1">Mark McClellan</a> thought is would be fun to throw his sweet-ass t-shirts (that I wear on a daily basis) into a crowd of 100+ people. It started out well, but quickly turned into a poor woman in the front row getting plastered in the face by a rolled up Pulp Fiction themed t-shirt.</p><p>With plenty of awkward memories, <a href="https://medium.com/u/6fdae7bd2af6">Danaan Clarke</a> joining the crew to help pay for meetup dues, and adding “dutch lunch” — an informal small meetup in between larger events — the events became almost too big to organize.</p><p><em>Here’s the archived list of the original meetups: </em><a href="http://webbushka.github.io/lunchUX-SLC-history/"><strong><em>LunchUX Event History</em></strong></a></p><h4>A New Hope</h4><p>After hosting the largest Lunch UX, mostly due to the amazing <a href="https://medium.com/u/19c787f3e4ff">Emmy Southworth</a>, I got an offer from the crew over at the PDA organization to join them. They had been in business for a few years hosting events as the local iDXA chapter before stepping away from that and rebranding. There events were generally held after or before work and I saw them more focussed on higher level topics and presentations from more polished presenters. Basically, the opposite of what we were trying to do, but they had some good experience organizing and running events and two of the organizers <a href="https://medium.com/u/7f57ec77593b">Wade Shearer</a> and Andy Branch were stepping down to start the <a href="https://medium.com/front-conference">Front Conference</a> so it felt like a good blending of groups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EIRbGiXoRRgszpyMBs2xFg.png" /><figcaption>You better check out Front Conference, it’s fantastic. Again, I promise.</figcaption></figure><p>The advantage for us was exposure and help organizing events, the advantage for PDA was the larger event attendance. It was a great marriage and I loved working with <a href="https://medium.com/u/f999d53e96aa">Ben Peck</a> to merge the two groups together and create some really great events for our local community.</p><p>After dissolving the original Lunch UX meetup page and moving everything over to PDA, the community grew rapidly. Too quickly if you asked me. We now had a website, a meetup page, a slack community, and two or more events a month. I really started to struggle with the direction of the larger group and started to feel like the original goal of Lunch UX was being lost, really just impart to the sheer size and activity of the community. It became harder to find those real people who wanted to present to such a larger group and catering to a large diverse audience only highlighted the original problems I was having before joining forces — broad, non-practical topics.</p><p>I left PDA only 6 months after merging the groups to focus on new career opportunities.</p><h4>The Feedback Never Stopped</h4><p>Shortly after leaving PDA, they rebranded the group to Product Hive (one of my favorite re-brands of all time) and kept growing and growing. Since then <a href="https://medium.com/u/f999d53e96aa">Ben Peck</a> and crew have done some really great things for the local design community in Utah by creating a mentorship program, connecting out of work designers directly with hiring managers, and hosting some really amazing events with some really fantastic presenters from around the country.</p><p>Despite all of these great things, I would still get Slack messages and texts from people old Lunch UXer’s about bringing the original Lunch UX back. But getting the band back together always felt overwhelming. I couple years later, I received a Slack comment that struck a cord with me and I couldn’t get it out of my mind for weeks until <a href="https://medium.com/u/73dde36fdc6d">Andy Page</a> and <a href="https://medium.com/u/6fdae7bd2af6">Danaan Clarke</a> suggested it was time to reboot Lunch UX — it seemed like the right time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4vzxcGETy_kk_Azi9J-3xg.png" /><figcaption>Brought back the original George Bush eating corn logo. We’ll never change it, I promise.</figcaption></figure><p>Knowing what worked and what failed from the original group, we have tweaked a few things but the overall goal of using real designers to teach other real designers something small and practical is still at play. After teaching the <a href="https://www.meetup.com/Lunch-UX/events/251196302/">first reboot event</a> the positive feedback has already started to roll in.</p><blockquote>“I loved this format of design practice and learning from one another. In short: today was awesome. The design community needs more..” — <a href="https://medium.com/u/9d530ab0ef43">Jacob Yates</a></blockquote><p>Okay, okay, I’ll stop yackin’, but I’m really excited for the future of Lunch UX and its place in our little local design community. I hope that we can find that same old magic in meetups to come and that people will continue to learn new things and have some awkward fun along the way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb7cd24f6491" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lunch-ux/rebooting-a-classic-cb7cd24f6491">Rebooting a Classic</a> was originally published in <a href="https://medium.com/lunch-ux">Lunch UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[For My Daughters]]></title>
            <link>https://medium.com/@pcrides/for-my-daughters-4b35c47a578a?source=rss-904324500917------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b35c47a578a</guid>
            <dc:creator><![CDATA[Patrick Cox]]></dc:creator>
            <pubDate>Tue, 10 Jul 2018 05:59:40 GMT</pubDate>
            <atom:updated>2018-07-10T05:59:40.863Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>For My Daughters</strong></p><p>The very second you were born I’ve been scared.</p><p>And that’s never gonna change.</p><p>You already know more about who you are then I do about myself.</p><p>Stay that way.</p><p>Be courageous. Be strong. Be weak. Be scared. Be happy. Be sad.</p><p>Be who you are and nothing less.</p><p>When the world pushes you to be anything less, stand tall.</p><p>Always remember that you have nothing to prove to anyone.</p><p>You are already the greatest person I know.</p><p>Your mom should always be your hero, she will always be mine.</p><p>Kiss and hug her everyday, make sure she knows you love her.</p><p>Just try to love your mom more than I do… I dare you.</p><p>Focus on those around you, improve their lives and your life will be great.</p><p>Never demand anything, never ask for anything.</p><p>Give back to those who have given to you and you’ll have the world.</p><p>Don’t be selfish.</p><p>Don’t be dumb.</p><p>Say thank you.</p><p>Say you’re welcome.</p><p>Eat with you mouth closed.</p><p>Don’t eat off the serving dish, always use a plate.</p><p>Really listen to people while they speak.</p><p>It’s easy, just speak less.</p><p>Forgive.</p><p>Be silly. Be goofy. Be funny.</p><p>Listen to rap, jazz, rock, pop, country, classical… shit, just enjoy music.</p><p>Disagree with others, but never hate them for it.</p><p>Love with all your heart, don’t play games and be honest.</p><p>Drive fast sometimes and always wear you seatbelt.</p><p>Get out of a speeding ticket.</p><p>Find some trouble, but find it wisely.</p><p>Do something that scares the hell out of you often.</p><p>Surround yourself only with people who want to lift you up.</p><p>Don’t just swear when you are angry.</p><p>Fight sensorship, fight bigotry, fight hate, fight fear.</p><p>Create a lot of things.</p><p>Paint.</p><p>Draw.</p><p>Write.</p><p>Get really good at math.</p><p>Be proud of everything you create, hold it high in the air and smile.</p><p>Find your God.</p><p>Get addicted to relationships and nothing else.</p><p>Fail alot, but always learn what went wrong.</p><p>Always be accountable, own up and don’t blame anyone of anything.</p><p>Practice, then practice some more.</p><p>Find something you love and keep doing it.</p><p>Drink lots of water and learn to love veggies, then eat a snickers.</p><p>Giggle often.</p><p>Laugh often.</p><p>Make your self laugh everyday.</p><p>Make everyone else laugh everyday.</p><p>Cry often, heaven knows I do.</p><p>Commit yourself to someone and when things get hard, never quit.</p><p>Love them until it hurts.</p><p>The greatest relationships you’ll ever have will be the hardest.</p><p>The greatest gifts you’ll ever get you won’t know until later.</p><p>Always be happy, but find out what pure joy feels like.</p><p>I will always be there for you, everything I do or will do is for you.</p><p>Just keep holding my hand.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b35c47a578a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[001 — How to Properly Add Friction to Your Designs (feat. Patrick Cox)]]></title>
            <link>https://medium.com/lunch-ux/001-how-to-properly-add-friction-to-your-designs-feat-patrick-cox-782405f05740?source=rss-904324500917------2</link>
            <guid isPermaLink="false">https://medium.com/p/782405f05740</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[graphic-design]]></category>
            <dc:creator><![CDATA[Patrick Cox]]></dc:creator>
            <pubDate>Tue, 10 Jul 2018 05:54:23 GMT</pubDate>
            <atom:updated>2018-07-10T06:02:52.453Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.meetup.com/Lunch-UX/events/251196302/"><strong><em>The first event of the Lunch UX</em></strong></a><strong><em> </em></strong><em>reboot was graciously hosted by our friends at Mojo Marketplace downtown SLC. I taught at the kickoff event… and this, is what I taught…</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*dPyFhor4P4jOjffj5DP18w.png" /><figcaption>Santaquin Man Sends Lambo to Tow Yard Hours After Winning It</figcaption></figure><p>“Santaquin Man Sends Lambo to Tow Yard Hours After Winning It”<strong> </strong>was the <a href="https://www.ksl.com/?nid=148&amp;sid=18580451&amp;title=santaquin-man-sends-lamborghini-to-tow-yard-hours-after-winning-it"><em>KSL</em> headline</a> December 2011.</p><p>David won a $380,000 Lamborghini Murcielago from a Maverick gas station contest titled <em>Joe Schmo to Lambo</em> while attending a college football game in November of 2011. <strong>“</strong>I couldn’t believe I won it!<strong>”</strong> The Lamborgini was given to him during the game and he was immediately able to drive it home that same Saturday.</p><p><em>What would be the first thing you would do?</em></p><p>Well, just like all of you would have done, David started giving rides to all his family and friends. But, within six hours of winning the super car he hit some gravel on the side of the road and smashed it up. David and his friend spun out of control and “ended up in a field, and I back-ended a couple of fence posts.”</p><p>David’s brand new ride could no longer be driven. Fortunately, for one of the entry requirements for the contest was the winner had to provide proof of insurance to get the keys. The super car was later towed to a body shop in Las Vegas and repaired. Happy ending.</p><p>The irony in this story however is that David also won a $5000 driving school pass at the Miller Sports Park to be trained on how to drive such a powerful car properly “Yeah, I got it on Saturday and I wrecked it on Saturday.”</p><p><em>Imagine if Maverick had also required him to use the driving school pass first in order to truly take possession of the keys?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*s3Ft7fMoTn6ZN9lnoZuqwg.png" /><figcaption>Adding friction properly can turn the average user into this guy.</figcaption></figure><h4>Do Make Me Think</h4><p>Stories are generally told methodically and thoughtfully if the story teller wants his audience to truly be engaged. As designers, we are told all the time that we should tell stories with our designs and to tell better stories with our workflows and visual treatments we sometimes need to slow our users down to keep them engaged.</p><p>It’s been a pretty common and shared attitude that efficiency means speed — time on task. But moving too fast can have disastrous consequences for your users. Poor poor David and that sweet Lambo.</p><p>Designing strategic friction in your user flows allows users to be more thoughtful, this leads to better quality, which leads to more confident users, which leads to a more trusted truly efficient product that people will want to use day in and day out.</p><p>There are at least three decent sized benefits to adding friction to your designs:</p><ul><li>Prevent users from making mistakes and keep them in control.</li><li>Create power users through constant education.</li><li>Improve retention and adoption by making them try or build things.</li></ul><p><em>How does one add friction to accomplish these things?</em></p><h4>Design Exercise: Error Prevention</h4><p><strong>Problem #1: Canopy.</strong> Customer service gets at least one call a week from a user who has accidentally deleted a contact or multiple contacts and cannot recover them in the UI. Sometimes they accidentally delete all of their contacts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/1*MgGTq1AVHNZchyD_ed-HyA.png" /></figure><p><em>Now it’s your turn.</em></p><p>Take a few minutes to find the problem in the screenshot to the left, sketch or write our some possible solutions and if you’d like share them in a comment below.</p><h4>Design Exercise: Create Power users</h4><p><strong>Problem #2: Slack.</strong> Users complain that they need new features that already exist in the app, in some cases for months. Also, customer service and the product management team have noticed that new feature adoption is really low.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*c_kY1NtJoG4_OqwQfDL6zA.png" /></figure><p><em>Now it’s your turn.</em></p><p>Take a few minutes to find the problem in the screenshot to the left, sketch or write our some possible solutions and if you’d like share them in a comment below.</p><h4>Design Exercise: Build Retention</h4><p><strong>Problem #3: Tidal.</strong> While the on-boarding flow and interaction are very well designed and efficient, customers don’t subscribe afterward. If they do they subscribe they rarely return within a few days and eventually cancel their subscription.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*5_rATtk5VbNBBIVI1Ex-ZA.png" /></figure><p><em>Now it’s your turn.</em></p><p>Take a few minutes to find the problem in the screenshot to the left, sketch or write our some possible solutions and if you’d like share them in a comment below.</p><h4>Slow Your Users Down</h4><p>We can design better user stories and experiences if we can properly slow them down when more time and attention is needed to move safely and effectively inside the product.</p><p>Speed is not efficiency. Efficiency is control followed by speed. <em>Think Vin Diesel.</em></p><p>Meaningful interactions and experiences should <strong>prevent errors, teach users to become power users, build user retention</strong> and adoption and make people think.</p><p>Later skaters.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=782405f05740" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lunch-ux/001-how-to-properly-add-friction-to-your-designs-feat-patrick-cox-782405f05740">001 — How to Properly Add Friction to Your Designs (feat. Patrick Cox)</a> was originally published in <a href="https://medium.com/lunch-ux">Lunch UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Field Trips!]]></title>
            <link>https://medium.com/ux-at-canopy-tax/field-trips-b78d974f8e51?source=rss-904324500917------2</link>
            <guid isPermaLink="false">https://medium.com/p/b78d974f8e51</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[design-teams]]></category>
            <dc:creator><![CDATA[Patrick Cox]]></dc:creator>
            <pubDate>Fri, 05 Jan 2018 18:01:02 GMT</pubDate>
            <atom:updated>2018-01-05T18:08:03.817Z</atom:updated>
            <content:encoded><![CDATA[<p>Our product designers are embedded on product delivery teams. Each team is basically a small product development team that contains all the parts and pieces that design, build and maintain a chunk of <a href="http://canopytax.com/">Canopy</a>. The skinny is that we don’t work and sit with our design peers on a daily basis — we work and sit with our squads. While this provides gigantic benefits for delivering a great, well-designed product quickly, along with a plethora of other benefits, there is a possibility that we could become isolated from the design team we belong to.</p><p>While we have worked out a bunch of methods for coming together as a design team during a regular work week, we wanted to find a way to replicate the friendships you make when you sit next to each other on a daily basis. One method that we have been working out is going on quarterly field trips together as a design team. We have only been doing this tradition for the last two quarters but it has already paid off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ROCwDyq2cCeySUXQZvUHKQ.gif" /></figure><h4>Learning</h4><p>We do have some requirements for field trips though — it’s not only about getting out the office and having fun and making friends. We want to take field trips that will inform us about design or process or empathy or anything that will make us better designers and contributors to the Canopy culture and vision. The other goal is to learn from a lot of other disciplines and industries and discover how they create and deliver their products and services.</p><h4>Baer Bronze Fine Art Foundry</h4><p>Last September, we kicked off our field trip tradition by taking a few hours after lunch to take a tour of <a href="https://www.baerbronze.com/">Baer Bronze Fine Art Foundry</a>: a 25-year-old bronze casting and fabrication company that converts artists’ sculptures into beautiful bronze statues. Not only was it awesome to see their bronze and wax studio, but we learned a lot about their complicated process of casting a mixed media sculpture from molding to casting to final patina and even discovered what wax and metal chasing was.</p><p>It was amazing to see a process from a completely different industry that had plenty of similarities. They experience some of the very same hand off problems and quality problems that we face at Canopy and had some pretty interesting ways they work around them. Another huge benefit in taking the tour was to see how they were able to balance a fast-paced, rigid, very iterative process with a product that requires so much care, accuracy and attention to detail. One of the best things to see was how they occasionally fail, what they learn and how they recover from these occasions. Heaven knows we fail from time to time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ylyb474GqSwZKYs_ZXvz0g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cDcZ4vQZIHDJ3UQ81W9z1w.jpeg" /><figcaption>Our team; Danaan, Sarah, Nick, Andy and Chelsea getting the full tour from Baer Bronze Wax Chaser Alison</figcaption></figure><h4>The Giving Tree</h4><p>As we were brainstorming some ideas for a fourth quarter field trip, we thought it would be appropriate to plan something more service oriented, to give back and maybe build some empathy as a team. One of our local malls has a Sub for Santa Giving Tree support program where you can pick names of children, families or seniors and provide them Christmas gifts that they would otherwise not receive, giving them a little boost of happiness to a hard Christmas season.</p><p>We felt like participating in this program as a design team would meet our field trip criteria. Taking a longer lunch break, we traveled down to the Giving Tree and picked a handful of names from the tree and did a little gift planning. While we didn’t get a chance to meet any of the children or seniors that we chose to purchase gifts for, lessons in empathy and understanding were had, and I know personally it changed the way my family approached our own Christmas traditions this year.</p><p>Beyond providing a little piece of happiness for those less fortunate than ourselves, while we were at the mall we decided to take advantage of the food court. Some of the team attempted to down some stale Chinese food that had been sitting in a wok for hours while the rest of us realized that Chick-fil-a is not always that great. We even managed to spend a few minutes browsing those wonderful mall exclusive stores. Did you know Hot Topic now has clothing that isn’t all black?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*mTsmmRhPs3SuKLtx9zP_Vg.jpeg" /></figure><h4>What’s Next?</h4><p>We still need to decide what to do for the upcoming 2018 first quarter field trip, but we already have some great ideas including a sausage factory tour and an artist who makes their own oil paints from scratch. We’ll see what the future holds and keep you posted on what we do and what we learn from these team getaways.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b78d974f8e51" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-at-canopy-tax/field-trips-b78d974f8e51">Field Trips!</a> was originally published in <a href="https://medium.com/ux-at-canopy-tax">Canopy Product Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experimenting with Pair Design]]></title>
            <link>https://medium.com/ux-at-canopy-tax/experimenting-with-pair-design-fe84ffaf6eb9?source=rss-904324500917------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe84ffaf6eb9</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Patrick Cox]]></dc:creator>
            <pubDate>Thu, 28 Dec 2017 17:01:02 GMT</pubDate>
            <atom:updated>2017-12-28T17:01:02.289Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8c333d_YNEHG4q3UDb1wTA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/5fNmWej4tAA?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Helloquence</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>You might have heard of pair programming, where two developers work together at the same workstation on the same projects. In a typical pair setup, one developer actually writes the code on her sweet, lighted mechanical keyboard while the other sits back, observes and reviews the ideas and code being created.</p><p>While implementations vary, the goals of pair programming remain the same; consistent code, increase quality, build teamwork via collaboration, mentorship / learning, better decision making procedures and decrease in troubleshooting time.</p><p>Realizing that these goals directly match up to <a href="https://medium.com/ux-at-canopy-tax/creating-team-principles-a5635b58282c">our design principles</a> we wondered if pair designing would be beneficial to our products and team members. With specific goals in mind, we decided to pair up designers who were working on similar products to figure out what might work.</p><p>Some pairs were focused on mentorship, where a senior designer would be teaching a junior designer directly rather than working on projects together. Other pairs were matched based on skill level so they could focus more on working together and reviewing each other’s work.</p><p>After experimenting with different methods, times and techniques, most pairs were meeting a few days a week for an hour or two to discuss projects and progress, as well as communicating daily either in person or via Slack to ask and answer questions.</p><h4>Discovered benefits</h4><p>While the experimentation continues and the methods being used continue to evolve, the benefits have been pretty clear and even surprising.</p><p><strong>Consistency -</strong> Pair designing has helped designers stay consistent to <a href="http://www.canopytax.com/">Canopy</a> guidelines and styles through more frequent alignments.</p><p><strong>Mentorship -</strong> Meeting frequently to practice and learn skills (while working through real problems) has elevated our junior designers at a rapid pace.</p><p><strong>Collaboration -</strong> Initially, I was worried that pair design could potentially eliminate overall team collaboration because pairs would become dependent on each other rather. However, pairs are sharing more with the rest of the team than before and overall collaboration has improved.</p><p><strong>Critiques -</strong> Critiques now happen within the pair itself and this removes the stress of presenting work to a crowd and group designer think. Critiques are now more useful and practical than ever before.</p><p><strong>Speed -</strong> Understanding that I currently have limited data - I feel like designs are being created and moved into development faster. I think this is mostly because the designer has the need to have designs ready and doesn’t get isolated for long periods of time with little collaboration or alignment.</p><p><strong>Iterative design -</strong> Canopy has a highly iterative and collaborative product and engineering environment and iterative design can be hard to maintain when designers are isolated. Design pairing has improved our iterative design process by allowing smaller designs to be reviewed more frequently. It has also helped designers prioritize their projects more efficiently, shadow other designers, improve communication and sharpen their own skills.</p><h4>Iterate, iterate, iterate</h4><p>As you can probably tell, implementing pair design has reaped some serious benefits for our team. But initial benefits aside, it is a drastic change in procedure and is still an experiment. Each pair is trying different methods and techniques, iterating quickly, discovering wins and uncovering problems.</p><p>This is an exciting time to be a designer at Canopy, and we will continue to share our pair design failures and wins with you as we evolve and grow!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe84ffaf6eb9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-at-canopy-tax/experimenting-with-pair-design-fe84ffaf6eb9">Experimenting with Pair Design</a> was originally published in <a href="https://medium.com/ux-at-canopy-tax">Canopy Product Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Should be Consistent?]]></title>
            <link>https://medium.com/ux-at-canopy-tax/what-should-be-consistent-8327d5c03910?source=rss-904324500917------2</link>
            <guid isPermaLink="false">https://medium.com/p/8327d5c03910</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Patrick Cox]]></dc:creator>
            <pubDate>Sat, 16 Dec 2017 09:46:20 GMT</pubDate>
            <atom:updated>2017-12-18T22:26:08.545Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cj0AUNP1ngxexwXQrlx3cA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/zFz3jThypsA">Mr Cup</a></figcaption></figure><p>For the past few months we have been working on our Canopy product design system or “style guide” or “component library” or “design language” or whatever the kids call it these days, but it has just never felt right.</p><p>The goal of any good design system thinger is consistency and it seems pretty easy to define:</p><blockquote>an agreement, harmony, or compatibility, especially correspondence or uniformity among the parts of a complex thing.</blockquote><p>We need a consistently designed and built product for sure, we need this uniformity in our designs and a particular harmony across every aspect of our app, but creating a design system artifact was where it started to feel not exactly good for us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fSRb8LqgYFFP5A72_wIC6g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/dbicjj8Yj8Y">Berto Mcario</a></figcaption></figure><p>What we really needed was the create the beginnings of our own, Canopy <a href="https://medium.com/@hellostanley/design-doesnt-scale-4d81e12cbc3e">GLUE team</a>.</p><p>After sitting down with other designers and developers, it became clear that before we go to far down this wandering road we needed to define for ourselves what we actually needed to be consistent. We not only need to know what needs to be built but we also need to give everyone on our product and dev teams something to align on. Here’s what we came up with.</p><p><strong>We need consistent…</strong></p><ul><li><em>Brand</em></li><li><em>Look and feels</em></li><li><em>Behaviors</em></li><li><em>Motion/animation</em></li><li><em>Interactions</em></li><li><em>Content management</em></li><li><em>States/views</em></li><li><em>Name/terminology/nomenclature</em></li><li><em>API standards</em></li><li><em>Accessibility</em></li></ul><p><strong>Bam!</strong> Now we have the real concepts we need to worry about instead of guessing as to what will be consistent. It’s super easy to get caught in the trap of consistency and begin to homogenize your app thinking that the same, repeatable UI components are the answer to the consistency problem.</p><p>Chasing UI components are not the answer, the answer is alignment of consistent values AND components. The only way to define those values and components is to break down what should be consistent.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8327d5c03910" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-at-canopy-tax/what-should-be-consistent-8327d5c03910">What Should be Consistent?</a> was originally published in <a href="https://medium.com/ux-at-canopy-tax">Canopy Product Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating Team Principles]]></title>
            <link>https://medium.com/ux-at-canopy-tax/creating-team-principles-a5635b58282c?source=rss-904324500917------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5635b58282c</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Patrick Cox]]></dc:creator>
            <pubDate>Sat, 16 Dec 2017 09:10:10 GMT</pubDate>
            <atom:updated>2017-12-16T16:38:01.604Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7WzVFy8R7t4bhvXhLcS2DQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/UHDx3BHlFvY">Mpho Mojapelo</a></figcaption></figure><p><a href="http://canopytax.com/">Canopy</a> is growing very fast.</p><p>That means we are hiring fast. And this means we have a greater risk of losing our way and our values as a team. Adding team members at a rapid pace can quickly alter the way a team behaves if one or two of those members don’t align to current values, behaviors and standards… <em>have you ever heard the phrase “herding cats?”</em></p><p>We all have a set of personal values whether we can define them or not. These values echo who we are, what we believe in, define our goals and generally predict our behavior. Teams also have values whether we can define them or not. At Canopy, we decided to define these team values early on in order to prevent us from being shepherds of cats.</p><h4>Defining the team values</h4><p>According to Stephen Covey, values are defined as “Beliefs and opinions that people hold regarding specific issues or ideas, and are ultimately internal, subjective, and malleable.” Each designer has a particular set of values — how they interpret design overall as well as their own design work. For example, designers value quality differently; some believe the success of the final design as the determining factor for quality while some believe quality means making the best decisions possible with the given information at the time and some believe quality is a combination of the artifact and the process.</p><p>Prior to going from from two designers to seven in eight months we sat down and defined the values we wanted to own on our team, what values can we agree on? What values will we look for in the interview process? These values should act as the buffer when interviewing candidates. They <em>should</em> help us assess the alignment of a candidate quickly and help us ensure that we are asking the right questions during interviews in order to understand the candidates values, beliefs and behaviors. As an added bonus, we shouldn’t have to force the candidate to perform lame homework exercises that only waste everyone’s time because we truly understand what we are looking for, not only from a design process side, more importantly — their behavior.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WaxdhKvNnlaJNgj_Lo-n6w.jpeg" /><figcaption>Photo <a href="https://unsplash.com/photos/BbQLHCpVUqA">Alejandro Escamilla</a></figcaption></figure><p>We started by defined a small set of values:</p><ul><li><em>Designers should believe that collaboration creates a better products.</em></li><li><em>Designers should believe their design is much more than their deliverable.</em></li><li><em>Designers should believe that frequent feedback is vital to making great design decisions.</em></li><li><em>Designers should believe in the business goals and their importance.</em></li><li><em>Designers should believe that mentoring others is just as important in their day-to-day activities as creating beautiful, usable designs.</em></li><li><em>Designers shouldn’t believe that their time is more valuable than others.</em></li><li><em>Designers should believe that openness, honest collaboration and respect facilitates the creation of a great working environment.</em></li></ul><p>From these values we could begin to interview candidates properly along side examining their hard design skills so that we could hopefully prevent hiring mistakes.</p><h4>Solidify them as principles</h4><p>After creating this first set of values, more values were added and the list got rather lengthy. We needed a shorter list, a list that was easy to remember and a list that was more firm. Values are held beliefs that are movable, malleable but what we really needed was hard principles that can withstand the test of rapid growth and iteration. So, we decided to narrow this value list down and solidify them in strong, opinionated principles.</p><p>We designed our principles by defining the opposing values of each — taking a cue from the Agile Manifesto. This makes remembering and honoring these values easier to understand by explicitly defining the values we don’t want along side those we do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YRX3XNf4yHph9oDtSqPeEg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/8StEwJBI7qg">Marl Clevenger</a></figcaption></figure><p>Here are our current team principles:</p><p><strong>Decision quality OVER outcome quality. </strong>The quality of a design or a designer should not be judged by the success of failure of the outcome but rather determined decision making best practices.</p><p><strong>Mentorship OVER dependency. </strong>We may have stronger skills or expert knowledge is certain aspects of our jobs, but we should proactively mentor and teach others to be better rather than force everyone to use our expertise.</p><p><strong>Practicality OVER theoretical. </strong>Design actually doesn’t make everything possible. Instead of focussing on high level design theories we get our hands dirty in the practical operations of design so that we can produce a product we can sell.</p><p><strong>Collaboration OVER isolation. </strong>Collaboration and communication happen as frequently as humanly possible. We collaborate with other designers, developers, product managers and all other cross-functional teams on a daily basis to ensure that we are making the right decisions quickly and not marrying ourselves to our own personal ideas.</p><p><strong>Wholistic product ownership OVER feature ownership. </strong>Despite working directly on feature development teams we own the entire design of the product —expressing pride in all aspects of the product, not just the parts that we have designed ourselves.</p><p><strong>Generosity OVER selfishness. </strong>We are a team of designers that understand the best products are created together and not by the brilliant ideas of one individual. We are generous in giving our expertise, time, skills and feedback to others and we should be humble when receiving feedback and criticism.</p><p><strong>So far so good.</strong> I’m proud to belong to a great design team that has taken the time to define who we are and who we want to be. Each member of the team, regardless of experience and skill level, are thoughtful about how their behavior impacts the product and the Canopy team as a whole — <em>there is no herding of cats going on.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5635b58282c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-at-canopy-tax/creating-team-principles-a5635b58282c">Creating Team Principles</a> was originally published in <a href="https://medium.com/ux-at-canopy-tax">Canopy Product Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>