<?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 Elyse Bogacz on Medium]]></title>
        <description><![CDATA[Stories by Elyse Bogacz on Medium]]></description>
        <link>https://medium.com/@elysebogacz?source=rss-27760522557e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*gqdz3XgJZ_bVb-6blxkdPw.jpeg</url>
            <title>Stories by Elyse Bogacz on Medium</title>
            <link>https://medium.com/@elysebogacz?source=rss-27760522557e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:25:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@elysebogacz/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[Designing a report? Here are the 3 things you need to know.]]></title>
            <link>https://medium.com/@elysebogacz/designing-a-report-here-are-the-3-things-you-need-to-know-c05533c0ea71?source=rss-27760522557e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c05533c0ea71</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Elyse Bogacz]]></dc:creator>
            <pubDate>Mon, 20 Nov 2017 15:43:33 GMT</pubDate>
            <atom:updated>2017-12-21T19:23:39.344Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_e5uwyHdBsVfsNuo2nOoJA.jpeg" /></figure><p>If there’s a holy grail project for product designers — it entails being able to design something from scratch.</p><p>My most recent holy grail project at <a href="https://www.drift.com/">Drift</a> was also one of the hardest things I’ve tackled this year: reporting.</p><p>There are designers who have created entire careers dedicated to the science of creating and curating data visualizations. It’s hard. There are rules that need to be followed and multiple preferences that need to be accommodated.</p><p>That being said, I had to learn the things that some careers are built around in less than 2 weeks. And because there are so many nuances to designing a good report, I wanted to summarize the things I learned along the way — and hopefully provide a few shortcuts for other designers. Here we go!</p><h3>Picking the key metrics is hard. And “key metrics” change depending on who you talk to.</h3><p>A VP of Sales cares about something totally different than what a BDR or Account Executive cares about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*GmiIEDRzlWWrlf62O4BzFw@2x.jpeg" /></figure><p>Let’s take an engagement funnel for example. It may seem straightforward, but there are so many ways to show that data. Should it be daily counts? Cumulative counts? Is it helpful to show a comparison? Or a projection? Overall conversion? Or conversion by steps? If you’re talking to the right mix of people, the answer is Yes. All the above, please.</p><p>A VP of Sales needs to see the full context of historical data and projections so she can tell if her team is on track to hit their goal. Whereas a BDR needs to know if she’s hitting her daily number, and wants to see how much activity is occurring day by day.</p><p>It’s the same data, but it needs to be organized 2 different ways to actually be considered useful.</p><p>One of the biggest mistakes I see teams make (and I’ve made this one before, too) is to build a report around available metrics. I would like to stress how important it is <em>fight</em> this tendency.</p><p>If you don’t put in the time to discover, track, and expose the right metrics, the odds are that your report will only be partially useful and therefore only partially adopted.</p><p><strong><em>Takeaway #1: </em></strong><em>Talk to all the personas who will be looking at a report to understand what they need to learn from the data.</em></p><h3>Designing with with real data is the key to picking appropriate graphs</h3><p>If you only take away one thing from this post, please make it this: designing with real data is so important.</p><p>I messed this up on the first iteration of Drift’s Playbook report. Here’s what happened:</p><p>I had been designing dashboard cards to display playbook funnel conversion. After 2 days and some light internal testing I came away with a lovely bar graph that had “great colors!” and “looked tight!”</p><p>Fast forward 5 days to when those dashboard cards were live in the product and I realized they were absolutely useless.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/1*cdAO56bRg9aCiEtCbgM9PA@2x.jpeg" /></figure><p>That’s my co-worker Will. Will is a numbers guy. He looks at our engagement funnels and conversion rates. All. Day. Long.</p><p>Guess who I didn’t get some real data from?</p><p>If I had slowed down to talk to Will the Numbers Guy, he would have given a real funnel to consider that when picking a visualization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RjEYkp5I-0rCHAA8J46oEQ.gif" /><figcaption>This is the super hot bar graph that was actually totally useless because when I was designing I made up the data.</figcaption></figure><p>Instead, I had taken a fantastic conversion metric and made it utterly underwhelming by putting it in a bar graph which would end up being more of a sliver, and less of a bar.</p><p><strong><em>Takeaway #2:</em></strong><em> Designing with real data will help you pick the right data visualizations.</em></p><h3>Color theory 101 (AKA learn from others’ mistakes)</h3><p>I’m writing this post so you don’t have to hunt anyone down for help.</p><p>But the person I hunted down to give me info on reporting color theory is <a href="https://www.linkedin.com/in/drewcondon/">Drew Condon</a>.</p><p>My biggest concern was making sure I was picking a palette that would look HOT, but not distract from the data. It’s a bit of an art and a science. I knew Drew had spent <em>months</em> picking colors for his last reporting project. So instead of trying to pick them on my own and doing a poor job, I was able to learn from his journey.</p><p>Here is what I took away:</p><p><strong>You are going to need 2 color palettes: comparative vs. sequential.</strong></p><p>For your comparative palette (dog, cat, horse, pig, etc.), pick different hues of similar saturation. Example : Blue, Green, Red.</p><p>For your sequential palette (open, click, booked), try to pick a palette that goes from light to dark. It could be one color — Light Blue, Medium Blue, Dark Blue. Or a color fade — Green, Green-Blue, Blue, Blue-Purple, Purple.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*_HBKHjobeHRLBllysXtjQg@2x.jpeg" /></figure><p><strong>Use HCL or HSL color scale. Don’t try to use your brand color.</strong></p><p>Use a color scale that will make your reports stand out, but not overwhelm. Stick to middle hues. Avoid pure hues or super light or dark colors when it comes to charts.</p><p>For Drift I ended up using the HSL color scale and<a href="http://davidjohnstone.net/pages/lch-lab-colour-gradient-picker"> this cool little tool</a> to curate our colors.</p><p>Avoid using your brand color in reports. It might be your first instinct to work that fun bright color into your reports, but fight that urge. Pick colors that are actually appropriate for data visualizations and don’t dilute the impact of your brand color.</p><p><strong><em>Takeaway #3: </em></strong><em>Colors matter. Pick a palette that won’t distract from your data.</em></p><h3>So let’s recap…</h3><ol><li><strong>Just because it’s a metric, doesn’t mean it’s useful.</strong> Everyone on your team cares about different things, which means your personas probably do too. You need to touch base with each of your personas in order to discover what <em>they</em> care about, and design around those needs.</li><li><strong>Designing with real data is imperative to picking appropriate data visualizations.</strong> Remember the Numbers Guys, Will? Always talk to *your* Will and get some real data before you start designing. Otherwise you’ll be redesigning your report as soon as it ships (like I had to do).</li><li><strong>Learn from others’ mistakes. </strong>You’ll get much farther if you seek out someone who’s done this before. None of us are any good on our own. When you include your village, you get the best results.</li></ol><p>There are SO many more things that could be added to this list. And even 10x more things that I have yet to learn about designing data visualizations.</p><p>In the meantime, though , I hope these 3 takeaways are useful for you when you’re faced with the challenge of designing reports.</p><p>If you liked (or didn’t like) this post… <em>or</em> if you have some great data visualization tips, I’d love to hear from you. You can shoot me an email at elyse [at] drift.com.</p><p><em>This post was originally published at </em><a href="https://www.invisionapp.com/blog/designing-report/"><em>blog.invisionapp.com</em></a><em> on October 25, 2017.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gtulLxsOXeIz-RtFJ32P5g.png" /></figure><p><strong>This story is published in </strong><a href="http://blog.usejournal.com/"><strong>Noteworthy</strong></a><strong>, where 10,000+ readers come every day to learn about the people &amp; ideas shaping the products we love.</strong></p><p><a href="http://blog.usejournal.com/"><strong>Follow our publication</strong></a><strong> to see more product &amp; design stories featured by the </strong><a href="https://usejournal.com/?/utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_campaign=guest_post&amp;utm_content=elyse_bogacz"><strong>Journal</strong></a><strong> team.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wuw1kCUUftwOONwl6PjdjQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c05533c0ea71" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to stop designing things that won’t get built]]></title>
            <link>https://medium.com/@elysebogacz/how-to-stop-designing-things-that-wont-get-built-45c34cb4f3a?source=rss-27760522557e------2</link>
            <guid isPermaLink="false">https://medium.com/p/45c34cb4f3a</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Elyse Bogacz]]></dc:creator>
            <pubDate>Tue, 27 Sep 2016 17:11:31 GMT</pubDate>
            <atom:updated>2016-11-04T14:25:44.226Z</atom:updated>
            <content:encoded><![CDATA[<p>After sitting down and whiteboarding things out with your product manager and a few engineers, you can’t wait to start cranking away on a new design.</p><p>You spend hours designing and tweaking and wholeheartedly believing “<em>Users will love this!”</em></p><p>And then your designs never make it anywhere.</p><p>That feeling sucks, but it’s also part of the game. It’s the life of a designer. But throughout my time at RunKeeper and now at <a href="https://www.drift.com/?Source=ElyseInvision">Drift</a>, I’ve developed a system to help make sure this doesn’t happen — and to soften the blow when it does.</p><p>I call it the <strong>40/40/20 method</strong>, and it’s ideal for fast moving teams. It allows you to focus on the <em>now</em> while still looking out at the road ahead, which keeps you from wasting time on things that won’t ever be built.</p><p>I started doing things this way because I’ve experienced that scenario described above plenty of times — it’s tough to leave all your hard work on the engineering room floor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*S4T7ceL5uzgXq425.jpg" /></figure><h3>Where the 40/40/20 method started</h3><p>As a designer, I want to explore things fully and understand how things will build upon each other over time. Throw in some <a href="http://blog.invisionapp.com/3-ways-to-design-happiness/">“delightful” moments</a> for users to stumble upon.</p><p>But as a lone designer catering to 2 product teams, that’s not always feasible. Yes, my designs need to be thoughtful, but I also need to work at a pace that keeps 6 high-performing engineers moving.</p><p>Before I started using the 40/40/20 method, I had a process that was (unknowingly) more optimized for keeping our <a href="http://blog.invisionapp.com/designing-with-developer-in-mind/">engineers</a> busy rather than allowing us to quickly tackle the most important thing.</p><p>Our team would talk about an idea, and I’d go off to design the ideal version of it. Then when I showed it to my team, we’d strip things out one-by-one until the only thing left was a design I could’ve pulled together in an hour.</p><p>Bummer.</p><p>This left me constantly scrambling — jumping back and forth between teams, trying not to block anyone, and never really getting ahead. I needed to change my process.</p><p><a href="https://twitter.com/intent/tweet?text=%22What+feels+like+a+trivial+addition+to+you+might+be+a+pile+of+work+for+someone+else.%22+http%3A%2F%2Fblog.invisionapp.com%2F40-40-20-design-process%2F+via+%40InVisionApp">“What feels like a trivial addition to you might be a pile of work for someone else.”</a></p><p>First thing I started doing was spending more time with our back-end team so I could understand what endpoints we had at our disposal, what things we could do with a little bit of work, and what things would require <em>a lot</em> of work to implement.</p><p>I needed to recognize that what feels like a trivial addition to me, is probably a pile of work for someone else.</p><p>After I had all that information, I would <em>still</em> design the ideal… but I broke down the file completely differently into 3 shippable parts:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nt1cLpNX7VIegQ2N.jpg" /></figure><ul><li><strong>40% — MVP. </strong>The highest impact must-haves. Thought through fully, documented fully, back end in place, ready to be passed off to front end for implementation.</li><li><strong>40% — V2.</strong> The nice-to-haves. Mostly thought through. Might need a little back-end work. Ready to be documented whenever engineering is ready for it.</li><li><strong>20% — Innovation.</strong> Sort of thought through. Could be ready for implementation with another 2–4 hours of design work. Probably requires some back-end time.</li></ul><p>Here’s a real example with a recent conversation redesign we implemented, and how we broke it up:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sO7LLAnd6afTkQ-7.jpg" /></figure><p>Bucketing and designing things this way has worked wonders for a couple of reasons:</p><p><strong>I’m only focusing on the “now,” but I can see the road ahead.</strong><br> The beautiful thing about partially designing out those last 2 buckets is that I can stress test a design and have confidence it’s not going to break without spending too much time. Considering how things will scale helps me avoid designing us into a corner — and it saves us lots of engineering time in the long run.</p><p><a href="https://twitter.com/intent/tweet?text=%22Consider+how+things+will+scale+and+avoid+designing+your+team+into+a+corner.%22+http%3A%2F%2Fblog.invisionapp.com%2F40-40-20-design-process%2F+via+%40InVisionApp">“Consider how things will scale and avoid designing your team into a corner.”</a></p><p><strong>I’m not wasting time on things we won’t build.</strong><br> The most obvious benefit is that I’m not spending any extra time in that last 60% unless engineering tells me that we’re going to be ready for it. Usually we get through the second 40%, but not always. Sometimes we get to that last 20%, if we don’t have anything more important come up. In those moments, it’s easy for me to jump back, tie up the loose ends, and go back to whatever next “big thing” I was working on.</p><p>The other major advantage to this?</p><p><strong>I’m able to work on multiple “big things” at a time. </strong><br> This last one is huge because as a small team, speed is our advantage. This process allows me to work on major things for both teams intertwined with each other, but the nature of bucketing helps me keep focused on one milestone at a time. And that allows me to deliver more thoughtful work to both of my teams.</p><p>Here’s a recent example of this process at Drift:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rkaiqKOSta6Us-Op.jpg" /></figure><p>The other thing I like about this process is it respects the limits on my attention span. I’m most productive before lunch, so I try to divide my day into 4-hour blocks. In the morning I work on my “one big thing,” and in the afternoon I give my attention to “everything else.”</p><p>“Everything else” usually means going back to that last 60% on a previous project and documenting a few more days’ worth of work for that other team. Sometimes it means whiteboarding next week’s “big thing” with my PM so he can start planning. Whatever it is , it’s something that needs to get done — but it’s not <em>the</em> most important thing.</p><p>As our team grows, developing a process has been more and more important not only for my productivity, but for my sanity. And keeping sane means knowing I’m not throwing away huge chunks of my time on fruitless explorations.</p><p>I know this process will need to continually adapt and cater to the ever changing needs of the team. But right now, it’s working.</p><p><em>Originally published at </em><a href="http://blog.invisionapp.com/40-40-20-design-process/"><em>blog.invisionapp.com</em></a><em> on September 27, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45c34cb4f3a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 4 Things Marketers Need To Know About Design]]></title>
            <link>https://medium.com/@elysebogacz/the-4-things-marketers-need-to-know-about-design-5fb467fceb08?source=rss-27760522557e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fb467fceb08</guid>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[content-marketing]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Elyse Bogacz]]></dc:creator>
            <pubDate>Tue, 30 Aug 2016 16:22:19 GMT</pubDate>
            <atom:updated>2016-08-30T17:50:13.311Z</atom:updated>
            <content:encoded><![CDATA[<h4>Design Tips That Every Non-Designer Can Use Today</h4><p>My coworker <a href="https://medium.com/u/2d9925ac1dda">Dave Gerhardt</a> approached me last week and asked if I had time to do a quick trade — at Drift we call it a drug deal. (<em>A drug deal is a side deal that’s quick / easy and done outside of normal workload.)</em></p><p>Anyway — he needed a graphic for an article that he was writing. I needed him to look at some copy, so we sat down for 20 minutes to help each other out.</p><p>Since then I’ve realized a trend at every company I’ve worked for is that Marketing usually doesn’t have a designated designer. Marketers are forced to either build relationships with designers and ask for favors OR make design decisions themselves.</p><p>In light of that realization, I wanted to take a few minutes to pull together some design tips for marketers who don’t have a design resource at their side, and are looking for some extra information.</p><p>Here we go!</p><h3><strong>Color Theory 101</strong></h3><p>There’s a science to picking colors and it goes a little something like this:</p><p><strong>Pick colors that are naturally harmonious and you’ll have the best results.</strong></p><p>When you’re picking color combinations the choices are endless. Get out your trusty color wheel, and learn the 4 easy ways to pick colors:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kYCnwqLv2V7TGvCj1oKNyg.png" /></figure><ol><li><strong>Complementary / 2 colors. </strong>Pick your favorite color, then draw a line to color exactly opposite. Boom, you’ve got a match.</li><li><strong>Triad / 3 colors. </strong>Feeling like you need a little more diversity? Start with your primary choice, and instead of drawing a line exactly opposite, draw an equilateral triangle. Now you have a balanced 3 color triad palette.</li><li><strong>Analogous / 3 colors. </strong>Another good trick is to pick the color(s) on either side of the primary color you’ve picked. This is called an analogous palette.</li><li><strong>Monochromatic. </strong>Pick your favorite color, and add variation by the shades you use together.</li></ol><p>If you’re not into picking your own colors on a color wheel, there are plenty of palette generators out there. I often go to Dribbble to grab inspiration from their auto-generated palettes. It’s a nice way to see a set of colors together and figure out what you’re drawn to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/1*m8zOuEAXFxDeUo_4Ki8vaw.png" /></figure><p>We are all professionals so I don’t have to explain why it’s okay to borrow from a color palette but it’s not okay to borrow the drawing or illustration itself without asking the creator. You’re a pro, and you already knew that.</p><h3>Intro to Typefaces</h3><p>Different fonts are designed for different purposes. If you’re publishing on the web and your content is long form you want to pick fonts that were designed for digital reading, not one that you’d see in the finance section of a newspaper.</p><p>Try to only pick one or two at most. Generally, you want one for body copy, and <em>maybe</em> one more to use for CTAs or headlines.</p><p>There’s still lots of debate on the readability of Serif vs Sans Serif for digital. My personal opinion is that if most of your audience is using higher quality screens and your text size isn’t tiny… you can go either way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dTh3yPV-OCUve9RNjjoZ2g.png" /></figure><p>Also — you’re reading this on Medium. Which is actually one of the best examples of content typeface pairings. <a href="https://medium.design/project-tnt-4b9b4ea97cda#.a0c0cd4uu">They use Kievet and Charter</a>.</p><p>If you’re interested in using premium typefaces for content, head over to Typekit or Google Fonts. <a href="https://creativemarket.com/fonts/sans-serif">Creative Market </a>also has some lovely, affordable options.</p><h3>Choosing Better Stock Photos</h3><p>My biggest pet peeve as a content consumer is when the article I’m reading has a shit stock photo attached to it. It makes the content seem spammy or gimmicky.</p><p>Before you make a selection, ask yourself if the photo you are considering answers “yes” to both the following questions:</p><ol><li>captures the topic of your article</li><li>is relatable</li></ol><p>Most people stop at #1. This is an opportunity to do better and make marketing more personal with the visuals you choose.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_YehUUkq1jciHH9s3QbP_w.png" /></figure><p>More and more decent options for stock photos are becoming available every day, although I do agree sometimes you have to dig deep to find them. Here is a list of lovely (and mostly free) resources that I use often.</p><p><a href="http://www.offset.com/">Offset by ShutterStock</a></p><p><a href="https://unsplash.com/">Unsplash</a></p><p><a href="https://stocksnap.io/search/business/sort/relevance/desc">StockSnap</a></p><p><a href="http://negativespace.co/photos/">Negative Space</a></p><p><a href="http://www.gratisography.com/">Gratisography</a></p><h3>How to make your sh*t look great on screens.</h3><p>Lastly, let’s talk about image quality. You put all this work in, lets make sure that your images are as polished as they can be!</p><p>Retina screens make life a little harder because what looks great on your computer, might look fuzzy on a retina.</p><p>I find that 1200px is usually a pretty good width because it 1. Generally looks great on all screens and 2. Isn’t <em>so</em> massive it takes forever to load. If you can, try to use an image that is 2x as big as you’d like it to be and resize it to 50% in your content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O6tYSWoHQqt-ZIjjritvhQ.png" /><figcaption>That’s my dog DJ. He’s on instagram <a href="https://www.instagram.com/djandwinnie/">@djandwinnie</a>.</figcaption></figure><p>How easy this is really depends on the publishing platform you use. On platforms like Medium, life isn’t so hard because they auto size the image for you.</p><p>There we are. Those are the basics. You don’t need to be a designer to make great design choices, in fact I bet most people are more creative than they give themselves credit for.</p><p>If you guys liked (or didn’t like) this article, feel free to shoot me an email! (<strong><em>elyse@drift.com</em></strong>) I’m also on twitter as<strong> </strong><a href="https://twitter.com/elysebogacz"><strong><em>elysebogacz</em></strong></a><strong>.</strong></p><p><strong>PS. Click here to learn more about what we’re up to at </strong><a href="http://drift.com/"><strong>Drift</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fb467fceb08" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We Made The Decision To Add Six More Steps To Our Onboarding — And It Worked. Here’s Why.]]></title>
            <link>https://medium.com/@elysebogacz/we-made-the-decision-to-add-six-more-steps-to-our-onboarding-and-it-worked-heres-why-f737f84d2512?source=rss-27760522557e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f737f84d2512</guid>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Elyse Bogacz]]></dc:creator>
            <pubDate>Mon, 01 Aug 2016 14:34:45 GMT</pubDate>
            <atom:updated>2016-08-30T20:06:13.006Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pT962fvmRMErsIDP_lkhqA.jpeg" /></figure><h4>We just finished implementing a 12 step onboarding.</h4><p>“That’s WAY too many clicks.”</p><p>…is that what you’re thinking? You’re not wrong— that <em>is</em> a lot of clicks. But hear me out for one second.</p><p>I can’t tell you how many PMs and engineers have told me “that’s too many clicks” while we figure out how to chop and condense into something that’s actually <em>less</em> clear.</p><p>Here’s an ideology better than “keep the clicks low”:</p><p><strong>Don’t make me think.</strong></p><p>Aha! Now you’re back with me.</p><p>That’s was our approach with this new onboarding. We asked ourselves.. “How can we make sure each step (no matter how many there are) has such a low threshold of effort that users will fly through it?”</p><p>After spending some time getting our hands dirty — we were able to identify 3 major problems that we needed to correct, and how many steps we needed to do it.</p><p><strong>1. First and foremost — we needed to reduce the time to WOW.</strong></p><p>Our old flow asked the user to do a lot of work and didn’t provide a WOW moment until the very end. By that point a good chunk of people had already fallen off.</p><p>The most important thing we needed was to give our users something to be excited about right from the get go. What’s more exciting than customizing something to mirror your brand? Boom. Let’s start there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BqiW-rYD7CCxuwneKUuuaQ.gif" /></figure><p><strong>2. More focus on PEOPLE talking to PEOPLE.</strong></p><p>The next problem we identified was that a majority of our customers weren’t adding an avatar or setting up a welcome message. Why? Because we weren’t <em>asking</em> them to.</p><p>Because we weren’t suggesting users do those 2 things — they weren’t. Which meant that some of our users weren’t getting the full Drift experience and therefore were missing out on some of the conversations they could be having.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0bk9r-Occ2M-HrgXph8lbw.gif" /></figure><p><strong>3. Last but major question: Soo.. who’s actually setting this up?</strong></p><p>It became apparent to us pretty quickly that the people using and signing up for Drift might not be the person actually putting the code on their company’s website. Instead of dropping them into a screen with 15 technical things they <em>could</em> do and 5 different ways to install… let’s ask just one simple question:</p><p><em>Are you setting this up or is someone else?</em></p><p>You are? Cool —here are the install options. You got this, but we’re here if you need anything.</p><p>Someone else is? That’s cool too — here’s a place invite them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6AbIN8eUuEVmTXbspzINig.gif" /></figure><p>Some of you might be like… “<em>Ummm…. Elyse, the progress bar in your mocks say 5 steps, but this article says 12. Why you lyin’?</em>” Great observation — there’s a set of screens within each “step” that adds up to 12. Bucketing things by theme help keep the user from feeling as if there’s so much work they’ll never finish it! Here’s a chart of the things we themed and bucketed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NCeO6TbsvWmm9y94Vts0cg.png" /></figure><p>There it is. That’s all the secret sauce. Making each step feel like an easy win for the user by only asking or solving for one thing at a time.</p><p>We shipped this new flow live the day before<a href="https://www.producthunt.com/tech/drift-2-0"> we launched our Drift bot on Product Hunt</a> which put it through the ultimate stress test. I have to admit — I was a little anxious, but the reactions were great.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/1*NhTBQJOLYWn8BKHHQcUORg.png" /></figure><p>Awww gee you guys! 🙈</p><p>A designers work is never done. And I’m sure we’ll end up tearing this flow apart to optimize for something else eventually. In the meantime though— I hope this post is useful to anyone looking at their onboarding flow.</p><p><em>If you liked (or didn’t like) this post feel free to contact me! My email is elyse@drift.com. I’m also on twitter at </em><a href="https://twitter.com/elysebogacz"><em>elysebogacz</em></a><em>.</em></p><p><em>p.s. If you want first access to our AI bot that helps you have conversations with your customers at scale — you can get it </em><a href="https://www.drift.com/one-to-one-at-scale/?ref=elysemedium"><em>right here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f737f84d2512" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Everyone at Your Company Should be Able to Use Sketch (& 3 Tips for Making it Happen)]]></title>
            <link>https://medium.com/customer-driven/why-everyone-at-your-company-should-be-able-to-use-sketch-3-tips-for-making-it-happen-e0c713f98791?source=rss-27760522557e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0c713f98791</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Elyse Bogacz]]></dc:creator>
            <pubDate>Wed, 10 Feb 2016 21:54:17 GMT</pubDate>
            <atom:updated>2016-02-11T15:02:47.772Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*qDwLRw71tF2p8EUGOobqPg@2x.jpeg" /></figure><p>I love being a maker.</p><p>In a field that prioritizes user experience, there is nothing more satisfying than working on something that is <strong>impactful.</strong></p><p>You know what I <em>don’t</em> love?</p><p>Exporting assets. Resizing logos. Changing colors in presentations.</p><p>How can I focus on <a href="http://www.appleseeds.org/big-rocks_covey.htm">moving big rocks</a> that make real impact if I’m spending 25% of my day doing tedious production details?</p><p>At Drift I don’t really have this problem anymore.</p><p><strong>Why?</strong> Because everyone on my team uses sketch.</p><p><strong>Why is this such a big deal? </strong>Because all of my teammates having this basic skill set gives me 25% of my making time back. In the past, I was exporting 30 icons x 8 variations = 240 assets! NOW, I am:</p><ol><li>talking to and understanding our customers.</li><li>getting answers that keep our dev team humming along.</li><li>iterating on our UI.</li></ol><p>25% of my day! Do the math, thats roughly <strong>12 more impactful hours a week </strong>— more than a full working day! Here are some examples of how I am able to reclaim that time:</p><h4><strong>Engineers don’t need me to “redline” files or export their assets.</strong></h4><p>The engineering team knows how to go into my file, check the padding, find the type sizes, export their assets. With every file I pass off, I learn a few more things about how I can name my layer structure to reflect our code base. Over time, this process has become even more seamless.</p><h4>Product Management is proactive.</h4><p>If a QA issue comes up with a customer, my PM — Matt — simply grabs my file and compares it to the flow that was implemented in the product. He can then see if something was cut during implementation and get the team working on a fix without dragging in extra people (me).</p><h4>Marketing isn’t afraid to get their hands dirty either.</h4><p>When Marketing needs a logo, they just go and grab it. They know where to go to get our HEX values and how to mock up our logo. They also know where I keep my file of illustrations that they like to use for their content!</p><p>The combined efforts of my team make a <strong>major</strong> impact on my day. Here are a few tricks for implementing this type of shared responsibility on your team so you can get your making time back:</p><h4>Keep Central Files</h4><p>Keep a “Component” folder in DropBox. In that folder, create a file that holds HEX values, typefaces, icons, illustrations, etc.</p><p>Every time you create something that can / should be reused… drop it into the corresponding component file. This takes about 3 extra seconds!</p><h4>Give everyone read-only access</h4><p>This gives your team the freedom to go ahead grab things as they need them. And because the access is read-only, any changes they make w0n’t overwrite your files. This preserves the design team’s organizational efforts.</p><h4>Be a teacher</h4><p>If someone on your team has a question, teach them how to do it! Ever heard this phrase…</p><blockquote>“Give a man a fish and you feed him for a day; teach a man to fish and you feed him for a lifetime”</blockquote><p>…yes, it is relevant here too. Show your teammate how to export. Instead of sending them the file they want, send them the URL to it so they can learn where it is in the file structure!</p><p>Taking the time to get your team using Sketch is totally worth it. It might be some up-front effort on your end, but the ROI is <em>glorious, uninterrupted making time.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0c713f98791" width="1" height="1" alt=""><hr><p><a href="https://medium.com/customer-driven/why-everyone-at-your-company-should-be-able-to-use-sketch-3-tips-for-making-it-happen-e0c713f98791">Why Everyone at Your Company Should be Able to Use Sketch (&amp; 3 Tips for Making it Happen)</a> was originally published in <a href="https://medium.com/customer-driven">Customer Driven</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Tips For Being A Customer-Driven Designer]]></title>
            <link>https://medium.com/customer-driven/6-tips-for-being-a-customer-driven-designer-a95d6da57fc2?source=rss-27760522557e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a95d6da57fc2</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Elyse Bogacz]]></dc:creator>
            <pubDate>Tue, 19 Jan 2016 17:31:35 GMT</pubDate>
            <atom:updated>2016-01-19T22:52:08.289Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mXXJi_T4KBZxSjonEtg5VQ.jpeg" /></figure><p>When I was 16, I started waiting tables at a breakfast joint down the street from my house. Really I only worked 2 mornings a week — but — in those weekly 18-ish hours, I figured out ways to make almost 20% more in tips than my fellow wait-staff.</p><p>Every single trick I stored up my sleeve included going above and beyond for my customers. My section always had the freshest coffee, the hottest food, the best jokes (up for debate), and when something wasn’t right — I fixed it. Even if it meant picking up a portion of their meal out of my own pocket. Those customers came back and they tipped <em>more,</em> because they knew I was going to take care of them.</p><p>That’s called the “Service Mindset”, and it is the most important ingredient in being a customer-driven designer. This whole concept sounds obvious, but there are so many things that get in the way of <strong><em>actually serving the customer.</em></strong></p><p>Let’s talk about a few things that can go wrong, and ways to fix them.</p><ol><li><strong>Listen, don’t assume.</strong></li></ol><p>This is the bread and butter of being a designer. But there are still so many of us that struggle with the golden rule: <strong><em>listen.</em></strong></p><p>The worst thing you can do is <em>assume</em> what you customer wants or needs. And truthfully, there is only so much you can speculate from a survey. You need to <strong><em>talk</em></strong> to your customers. Get out of the building! Meet your customers/prospects for coffee. Understand how they are doing things now and what they wish they could be doing.</p><p><strong><em>Listen to their pain.</em></strong> And then take that pain back to your product team and <strong><em>solve it.</em></strong></p><p><strong>2. If you have to assume, assume you are wrong.</strong></p><p>Sometimes you just need to find a place to start in order to keep the train moving. If you are guessing, then guess! And then assume that your guess is way off.</p><p>Now it’s your job to prove or disprove that hunch by — you guessed it — talking to customers!</p><p><strong>3. Vet your workload, don’t just default to what is asked for.</strong></p><p>A few months ago my PM came to me and said “Elyse, we only need XX — can you design it?.” My reply: “Sure! I can do that.”</p><p>After I spent some time putting it together AND our dev team implemented it, we realized something wasn’t right. To cut to the chase, we built the <strong><em>wrong thing</em></strong> because we <strong><em>assumed</em></strong> (see the pattern here) what would work for our customer! If we had spent 30 minutes doing a little research with 1 or 2 customer calls, we would’ve known that!</p><p>The next day, we immediately changed our work-flow to be even more <strong><em>customer-driven.</em></strong></p><p><strong>4. Test, test, test.</strong></p><p>Test everything and test it often. At Drift we take testing seriously. We only care about building the thing that is going help our customers the MOST. So we <em>listen</em>, and then we <em>test</em>.</p><p>My PM probably has 15 calls a week with customers. This gives me plenty of opportunity to sit in, show what I’m working on, and understand how (or if) our solutions are “<em>the right thing”.</em></p><p><strong>5. Honor your testing findings.</strong></p><p>I’m still surprised when designers use “Well.. WE are the UX experts, right?” as an excuse for not delivering what the customer needs.</p><p>Sometimes customer feedback can conflict with what we designers define as “good design.” When this happens the worst thing to do is dismiss the customer and their feedback because it complicates our beautifully designed interface. That’s not being customer-driven. That is being stubborn!</p><p>We are “UX Experts” because we know (should know) how to understand our customer and design for <em>them,</em> not ourselves.</p><p><strong>6. Iteration is key.</strong></p><p>We can listen, we can test, but we aren’t fully doing our jobs if we stop there!</p><p><strong><em>Iteration is the key</em></strong> to going above and beyond. So don’t let your design process stop after your first round of testing or once your solution is implemented into the product. Iterations are the sprinkles on top that allow you to optimize the product and <strong><em>amaze your customers</em></strong><em>.</em></p><p>When I think about putting all these concepts to work at Drift, I remember what I knew when I was waiting tables in high school: <strong><em>go above and beyond.</em> </strong>Any breakfast can fill a customer up, but it’s the great service and attention to detail that keeps them coming back for more.</p><p><em>Want to see what we’re building at </em><a href="http://www.drift.com/"><em>Drift</em></a><em>?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a95d6da57fc2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/customer-driven/6-tips-for-being-a-customer-driven-designer-a95d6da57fc2">6 Tips For Being A Customer-Driven Designer</a> was originally published in <a href="https://medium.com/customer-driven">Customer Driven</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>