<?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 Chris Murray on Medium]]></title>
        <description><![CDATA[Stories by Chris Murray on Medium]]></description>
        <link>https://medium.com/@chrism_14039?source=rss-94486322615------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2I0NrqTSmq_jr0_wwK6qTA@2x.jpeg</url>
            <title>Stories by Chris Murray on Medium</title>
            <link>https://medium.com/@chrism_14039?source=rss-94486322615------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:03:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chrism_14039/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[When Data Isn’t Enough]]></title>
            <link>https://medium.com/@chrism_14039/when-data-isnt-enough-c687ded0fd2b?source=rss-94486322615------2</link>
            <guid isPermaLink="false">https://medium.com/p/c687ded0fd2b</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[basketball]]></category>
            <dc:creator><![CDATA[Chris Murray]]></dc:creator>
            <pubDate>Wed, 10 Jan 2018 18:59:51 GMT</pubDate>
            <atom:updated>2018-01-10T18:59:51.586Z</atom:updated>
            <content:encoded><![CDATA[<h4>Or, “What Dion Waiters taught me about data-driven design”</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MD35qqWJnAinHqqSXSqTZg.jpeg" /></figure><p>Everyone loves data, right? There’s a thrill in the numbers bearing out the things we suspect to be true… a certain comfort in basing decisions on cold, hard, stats. As the legend Dion Waiters once said,</p><blockquote>“Men lie women lie BUCKETS DNT”</blockquote><h3>Dionwaiters3 on Twitter</h3><p>Men lie women lie BUCKETS DNT RT @H2da_IZZOO: @Me_University @dionwaiters3 http://t.co/HPmgsVcK15 #BUCKETS</p><p>What was Dion getting at? Notions of quality (Dion’s overall game in this case) can be debated, but raw numbers (such as the aforementioned <em>BUCKETS</em>) are harder to deny.</p><p>The idea of data-driven design has really taken off in the era of startups, disruptors and game-changers. Design has always existed in the ethereal gap between art and science; the design rationale is the historical document that explains why certain design decisions were made. With the rise of big data, artificial intelligence, and automation, design decisions become easy; just do what the data tells you… right?</p><blockquote>Here’s the thing. Sometimes you’re starting from scratch. Where’s the data?</blockquote><p>Like an NBA team deciding which player to draft, sometimes there’s not enough data; you need to rely on your team’s expertise and the knowledge that’s available at the time.</p><p>For simplicity’s sake, let’s say you are designing a new website. You’re trying to decide what colour to make the primary Call-to-Action button on said website. Is there a “best colour” to make CTAs? You can do research on historical results and tests that have worked for others, but keep in mind that your audience, the context of the CTA’s appearance, and the intended emotional impact of the CTA may not align with the same factors in past tests.</p><p>So what do you do? Take the context of your project, do your due diligence from a research perspective and…</p><blockquote>shoot your shot.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F11hqQJ44YySw2k%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fnew-york-knicks-jr-smith-3-point-shot-11hqQJ44YySw2k&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F11hqQJ44YySw2k%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="249" frameborder="0" scrolling="no"><a href="https://medium.com/media/fbd148aeefc1831e566806f4598c44c7/href">https://medium.com/media/fbd148aeefc1831e566806f4598c44c7/href</a></iframe><p>Trust your experience and your skills. Make your informed design decision with a solid rationale, and act on it. If you have a hypothesis you want to test, and have the means to set up an experiment, an A/B or multi-variate test can be a great way to drive future design decisions, when you <em>do</em> have the data.</p><p>More importantly, the sooner you take action, the sooner you can learn what works and what doesn’t… increasing your own expertise for the future.</p><p>Data is great — when you have it. I wholeheartedly endorse using data analysis as a directional tool in design; but when you don’t have any (or enough), don’t be afraid to shoot your shot. You never know what you might learn.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F6cvZIhF4ALbEs%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fbasketball-new-york-knicks-jr-smith-6cvZIhF4ALbEs&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F6cvZIhF4ALbEs%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="245" frameborder="0" scrolling="no"><a href="https://medium.com/media/139a4b27da12b51d762f83a9e4e652f0/href">https://medium.com/media/139a4b27da12b51d762f83a9e4e652f0/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c687ded0fd2b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Want to Ramp Up Your E-Commerce User Research?]]></title>
            <link>https://medium.com/granify/want-to-ramp-up-your-e-commerce-user-research-ef413784cc65?source=rss-94486322615------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef413784cc65</guid>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Chris Murray]]></dc:creator>
            <pubDate>Tue, 31 Oct 2017 15:59:57 GMT</pubDate>
            <atom:updated>2017-10-31T15:59:57.830Z</atom:updated>
            <content:encoded><![CDATA[<h4>We made a handy framework to help you get started.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KaG0ln8rElls8Toi.gif" /><figcaption>It’s crucial to focus your user research efforts</figcaption></figure><p>E-commerce has perhaps the most tangible relationship between UX and business impact, as a seamless experience translates into increased conversion rates and a healthier bottom line. The world leaders in online retailers such as Amazon, Nike, Neiman Marcus, and HSN all provide users with an experience that makes it easier than ever to purchase from their websites.</p><p>What drives these great user experiences? Great user research.</p><p>As you conduct user research to craft an e-commerce experience, it can be overwhelming. Do you start with interviews? Market assessments? Personas? What information do you already have, and what is important to yet be gathered?</p><p>At Granify, we developed a framework for planning focus areas in the user research process. This framework will allow you to:</p><ul><li>Easily audit areas of strength and opportunity in your current knowledge base</li><li>Identify the highest-value time investments for your team</li><li>Optimize your process in preparing solutions for retail e-commerce</li></ul><h3>The USE Research Planning Method</h3><p>We call this framework <em>USE</em>: <em>User &gt; Store &gt; Ecosystem</em>. As the goal is to focus your research efforts, it is visualized as a target. The User is kept at the core of the framework, as their needs should drive the design decisions. From there, the Store and Ecosystem make up the middle and outer rings. Each ring can, if you choose, be further divided into quantitative (generally speaking, data and statistics) and qualitative (generally speaking, thoughts and opinions) subsections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ybuvi65GNE4MYBvjdaDo5w.jpeg" /><figcaption>Visualization of our USE Framework. Check out our <a href="https://www.granify.com/our-resources">Resources</a> page for more tools and tips for e-commerce.</figcaption></figure><p>Let’s get started with the Ecosystem and work our way in.</p><h4>Outer Ring: The Ecosystem</h4><p>This layer of the target is the broadest in scope and generally offers the easiest immediate access to research materials. The ecosystem refers to the high-level aspects of the retail environment you are designing for: the vertical, the economy, the buyer attitudes, and the trends for the world your store and customers inhabit.</p><p>You can gather valuable information at this stage from research aggregators such as <a href="https://www.emarketer.com/">eMarketer</a> and <a href="https://www.statista.com/">Statista</a> (though a subscription may be required for more in-depth insights).</p><h4>Middle Ring: The Store</h4><p>What makes your store unique? How is your checkout process performing? Where are your shoppers coming from? Store-level research involves digging into the product, the pricing model, your brand, marketing efforts, and any other initiatives that could impact your users’ experience across channels.</p><p>When researching your own store, it is crucial to leverage experts in your organization who touch a range of aspects of the business (finance, merchandising, marketing, IT, and more). If you’re already involved in these areas, all the better! If not, go in with a clear ask of what you need to know, to optimize the time of the team members who will be collaborating with you.</p><h4>The Center of It All: the User</h4><p>We place the user at the center of this target because the user (shoppers in e-commerce) should be at the core of all of your UX decisions.</p><p>This level of research can be the most intense and requires some practice to gain comfort with. But direct user research is where you will gain the information that allows you to create the best possible experience for every shopper.</p><p>Identify your most important user personas or archetypes, but always remember that each shopper is a person, not a persona. If you are working in an agile framework and building in tandem with ongoing research, have real people test your prototypes to learn what works and what doesn’t.</p><h3>Putting It All Together</h3><p>Plot the pieces of information you already have on the appropriate level of the target. This allows you to make assessments on the risks and rewards of pursuing more information in each category.</p><p>The world of online retail moves so fast that it’s impossible to fill every gap every time. What this framework allows you to do is move fast, knowing that you spent your valuable research time on the most important opportunities for your shoppers. If this story helps you out, or if you have any techniques you’ve used for your own user research projects, I would love to hear about it in the comments.</p><p><em>This is a condensed version of a post originally written for the </em><a href="https://hubs.ly/H092tPc0"><em>Granify blog</em></a><em>. You can read the full version </em><a href="https://hubs.ly/H092v8P0"><em>here.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef413784cc65" width="1" height="1" alt=""><hr><p><a href="https://medium.com/granify/want-to-ramp-up-your-e-commerce-user-research-ef413784cc65">Want to Ramp Up Your E-Commerce User Research?</a> was originally published in <a href="https://medium.com/granify">Granify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 steps to a 90-day website renovation]]></title>
            <link>https://medium.com/granify/10-steps-to-a-90-day-website-renovation-f0f6b2bc3d85?source=rss-94486322615------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0f6b2bc3d85</guid>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[lean-startup]]></category>
            <dc:creator><![CDATA[Chris Murray]]></dc:creator>
            <pubDate>Wed, 30 Aug 2017 14:01:01 GMT</pubDate>
            <atom:updated>2017-08-30T14:01:01.214Z</atom:updated>
            <content:encoded><![CDATA[<h4>Or, <em>“How I learned to stop worrying and </em>❤️<em> post-it notes”</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2PNLAiVerPPAJifeizktpA.jpeg" /></figure><p>What happens when your website no longer meets your needs, and it’s time to redesign? Whether due to market shift, the old version starting to look dated, or a change in your product strategy (PIVOT!), times change and websites must too.</p><p>At Granify, we hit that point this year, and had to answer the question. I’m a big believer in asking questions about questions; sometimes you sound like a 3-year old (“Why?”) but I honestly believe that you can get the best answers just by asking a few more questions.</p><p>Here are 10 crucial questions (and of course, some sub-questions) we asked ourselves that guided our process and led to our new website launching in only 3 months. Hopefully they can help you with your next website redesign.</p><h4>Step 1: In-house or agency?</h4><p>While this is not going to be the answer for everyone, the internal vs. agency question boils down to:</p><blockquote>Can your team design, build, maintain, and iterate on a website at a similar or lesser cost than an agency?</blockquote><p>In our case, after some rigorous project planning and estimating sessions, we felt confident that the answer was yes. With one designer (in this case yours truly) and our Director of Marketing allocating their focus to the project, and accounting for supporting internal resources, we outlined a plan to rebuild the site in 3 months.</p><p>Taking into consideration other benefits, such as pride of ownership and codebase familiarity, we presented the plan to our executive leadership and reached consensus that the site would be built internally. Stakeholders for each stage were defined early.</p><p>So what comes after deciding the “Who?”</p><h4>Step 2: Where will the site live?</h4><p>Whether you already have a live website that you are replacing, or are starting from scratch, the biggest question here is:</p><blockquote>Which tool gives you the best ability to maintain, optimize and iterate on our site over time?</blockquote><p>At Granify, our site has always been hosted on <a href="https://www.hubspot.com/">Hubspot</a>. While it had served us well historically, the redesign presented a prime opportunity to explore other options.</p><p>We looked into migrating to WordPress, as well as hosting on our own servers. While each had pros and cons Hubspot’s interface, WYSIWYG page editor, COS system, and site management tools proved to be the best solution for our needs. As one member of the team said,</p><blockquote>Hubspot does a lot of useful things, it does most of them really well, and it doesn’t do anything poorly.</blockquote><p>Plus, our design, marketing and sales teams already knew how to use it; no extra overhead in on-boarding the entire user base to a new tool.</p><p>So we knew where the end product would live; now to the drawing board.</p><h4>Step 3: What are the goals of the website?</h4><p>You never want to get too zoomed-in on the small things too fast. At the outset, you need to identify at a high-level:</p><blockquote>What, at its core, does this website need to accomplish?</blockquote><p>These goals should drive your subsequent decisions at each step of the process to come.</p><p>For Granify, we needed our new site to enable and enhance our:</p><ul><li><strong><em>Demand generation</em></strong></li><li><strong><em>Content marketing</em></strong></li><li><strong><em>Culture &amp; recruiting</em></strong></li></ul><p>Once we knew what we needed to do, we started getting into those weeds.</p><h4>Step 4: Who is this site really for?</h4><p>It’s all about the user, right? To make a website that users will actually find useful and provide value, start by asking…</p><blockquote>What are the biggest opportunities and pain points for your users?</blockquote><p>Our <a href="https://medium.com/granify/tagged/culture">People</a> team had already done a ton of research into the goals and problems of potential future team members, which proved to be a huge help in directing that section of the site.</p><p>To zero in on demand generation solutions, I worked with our <a href="https://medium.com/granify/tagged/sales">Growth</a> and <a href="https://medium.com/granify/tagged/product">Product</a> teams to uncover the biggest pain points of past, present and future partners. We bucketed areas of focus by user type (marketer, executive, product manager, CRM specialist, IT, and so on) and prioritized accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*-FCFmGrm9TnEewntIANWdA.gif" /><figcaption>Glimpse inside the process: *some* of my post-it notes.</figcaption></figure><p>Were there post-it notes involved? Oh, let me tell you. There were post-it notes involved. We aggregated broader user data into discrete goal-based groups through which we could provide better context to frame our message.</p><p>So with your audience and goals in mind, let’s talk about content.</p><h4>Step 5: How will the content be organized?</h4><p>This is where the sitemap comes in. What are your top-level pages, where do you need to create deep paths, and where can you offer everything at once?</p><blockquote>What should your users’ journeys look like?</blockquote><p>For our purposes, this entailed two primary user types: prospective partner and prospective Granifite (what we affectionately call members of the Granify team 💚).</p><p>Of course there are distinctions and divergences among those users, but our focus landed on creating a deeper potential journey for our Solution and Company sections of the site; to enable prospects of all types to learn more about our cutting-edge product and our world-class people (for real, <a href="https://www.granify.com/our-company/our-team">these people</a> are wicked smart + talented).</p><p>We used <a href="https://writemaps.com/">Writemaps</a> for our site-map planning purposes. It was easy to plan and modify content structure on the fly, as well as share with stakeholders for quick review. Would recommend.</p><h4>Step 6: Where does your in-progress content live?</h4><p>As a website progresses, content gets refined more and more. With copy breaking out of a sitemap’s bullet points and growing increasingly specific, what we found really matters is:</p><blockquote>Who is doing the writing ?</blockquote><p>If your team is still defining the content, your focus is checking for accuracy in details and collaborating in real time. Google Sheets is probably the best place to do this. Our sales and product teams spent a lot of time collaborating in documents to get the direction nailed down early on.</p><p>If you have a dedicated copywriter or content marketer on your team, they will likely have a preferred tool of their own; the G Suite worked well enough for us, but the writing and refinement portion was probably one of the more ad-hoc portions of our project.</p><p>As we got into grammatical edits, Hubspot’s page editor worked great for us as anyone making copy changes could do so in seconds.</p><h4>Step 7: How is it all laid out?</h4><p>Once you have the content structure mapped out in the aforementioned sitemap, you can start planning for hierarchy and interaction.</p><blockquote>What order does this information need to appear in, and where should it take the user next?</blockquote><p>You may have heard of my well-documented <a href="https://medium.com/granify/light-your-design-process-on-fire-54ebe8d6cc09">love of Figma</a> as a collaborative design tool. Working in tandem with another designer we built out wireframes for the full suite of pages over the course of a few days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PJ40gW685aOLeEdb3tZctA.png" /><figcaption>Various homepage wireframe proposals</figcaption></figure><p>Using a component-based system, we re-purposed similarly-composed blocks of content across various pages, in a way that would easily translate to Hubspot’s modular page-building system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*ysXrU16wsjio381P65vh1g.png" /><figcaption>Our navigation component isolated and in use throughout later-stage wireframes in Figma.</figcaption></figure><p>From there, we built interactive prototypes in <a href="https://atomic.io/">Atomic</a> to start some early-stage user tests and make sure the journey felt right. Clicking something and seeing where it takes you is a more authentic experience than simply following a sitemap. So now…</p><h4>Step 8: How do you approach final visuals?</h4><p>With the planning, strategy, and wireframes complete, you need to determine the best workflow for your team to get into high-fidelity visuals. For us the question was:</p><blockquote>Do you build in the browser or create mockups?</blockquote><p>While I love a good mockup, and our Figma wireframes could have been converted to hi-fi visuals with minimal effort, we decided to go straight into HubSpot to build working, interactive visuals from the jump. Why?</p><ul><li>Internal changes on our design team forced us to optimize on a leaner site-building process</li><li>I know my way around a CSS file, and we have killer front-end devs on hand if I got in over my head with too much <em>*gasp*</em> jQuery</li><li>Increased confidence that the HubSpot platform and its modular page-creation tools could support this process</li><li>Our early design strategy involved the creation of reusable components that could be tailored to suit multiple use cases</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NSEX7C0rvLpjt_bxxYlk4w.png" /><figcaption>An example of Hubspot’s reusable modules at work in a page layout.</figcaption></figure><h4>Step 9: What to do with the old site?</h4><p>Since you’re more than likely replacing pages that already exist, you need to decide where to bury the proverbial page bodies. This can get more complicated than it needs to be, but ultimately:</p><blockquote>What is the best way to smoothly replace an entire website worth of content, and make sure people can find it?</blockquote><p>Hubspot has a staging feature that allows you to do 1:1 replacement of existing pages. While this feature likely would have saved us a day or two along the way, our all-hands-on-deck approach in the previous days of the site meant that there were not just new pages to add, but old pages to re-organize and remove.</p><p>The ability to archive &amp; un-publish allowed us to quickly and easily make old pages… <em>disappear</em>. We used Hubspot’s <a href="https://knowledge.hubspot.com/website-user-guide/how-to-use-the-url-mapping-tool-to-redirect-pages">URL mappings</a> tool to redirect any adjacent pages to their new counterparts. For example, our previous parent-level <em>Careers</em>, <em>About</em>, <em>Our Story</em>, <em>Contact</em>, and <em>Press</em> pages were now siblings under an <a href="https://www.granify.com/our-company"><em>Our Company</em></a> parent page. There was a similar re-structuring of our <em>How It Works</em> family of pages that became nested under the new <a href="https://www.granify.com/our-solution"><em>Our Solution</em></a><em> </em>page<em>.</em></p><p>As we cleaned up old pages, we used the <a href="https://knowledge.hubspot.com/articles/kcs_article/cos-general/how-can-i-remove-pages-from-my-sitemap-in-hubspot-s-cos-platform">sitemap editor</a> in Hubspot to ensure we were indexing only the new and relevant pages.</p><p>With all that done, using <a href="https://moz.com/">Moz</a> and Google’s Webmaster tools to ensure that our SEO was all in order was the next step. With that done, it was time to talk launch.</p><h4>Step 10: How do we show it off?</h4><p>So you have this new website, cool and functional and good, very exciting. But… all of that means nothing — if nobody knows about it.</p><blockquote>What are the most effective means of unveiling the new website?</blockquote><p>You’ll likely want to roll out a wave of PR and/or paid advertising to get as many eyes as possible on your product. There are some free and low-cost PR distributors that can get your press releases in front of the right people at the right time. Social media and blog posts can be an effective and high-ROI method of driving organic traffic as well.</p><p>At Granify, we decided to proceed with a mix of press release distribution, blog posts (like the one you’re reading right now… <em>*inception sound*</em>) and a social campaign that highlights high-value content on the new site.</p><h4>How can I apply this to my new website?</h4><p>Of course, a project that impacts such a diverse range of a business as your website is not possible without a range of support and contributions.</p><p>To <em>egregiously</em> paraphrase Pixar founder Ed Catmull…</p><blockquote>“Computers don’t make websites. People make websites.”</blockquote><p>(substitute <em>movies</em> for <em>websites</em> and he said it, I swear)</p><p>It’s important to know your team, and their needs and skillsets. By finding<em> your</em> answers to the 10 questions outlined above, you should have a roadmap in place to drive your next website project to a successful launch!</p><p><em>Check out our new website at </em><a href="https://www.granify.com/"><em>granify.com</em></a><em> and make sure to tell all your friends (and leading eCommerce pros) to do the same. If you have any web redesign stories of your own to share, or have any thoughts on our process, hit me up in the comments and don’t forget to mash that 👏 button (RIP Recommends, you had a good run).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0f6b2bc3d85" width="1" height="1" alt=""><hr><p><a href="https://medium.com/granify/10-steps-to-a-90-day-website-renovation-f0f6b2bc3d85">10 steps to a 90-day website renovation</a> was originally published in <a href="https://medium.com/granify">Granify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Light Your Design Process On Fire]]></title>
            <link>https://medium.com/granify/light-your-design-process-on-fire-54ebe8d6cc09?source=rss-94486322615------2</link>
            <guid isPermaLink="false">https://medium.com/p/54ebe8d6cc09</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Chris Murray]]></dc:creator>
            <pubDate>Mon, 19 Jun 2017 19:46:00 GMT</pubDate>
            <atom:updated>2017-07-06T23:30:06.590Z</atom:updated>
            <content:encoded><![CDATA[<h4>(In a Good Way)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ae4JRgYcTGyQf9p-S81VmQ.jpeg" /></figure><p>Every product design team faces unique challenges in a constantly-shifting landscape. At Granify, we optimize the eCommerce experience by addressing the concerns of online shoppers in real time. The messages we use to address these concerns must align seamlessly with our retail partners’ existing visual identity, UI, and UX patterns to act as an unobtrusive addition to the shopping experience.</p><p>Our process in designing these messages, much like that of many other teams out there, is collaborative in nature. We need to share our work and tear it down to rebuild it — better, stronger, faster, like a digital Six Million Dollar Man. As such, we lean on one another for review, critique, and suggestions. As with any product, we need to ship quickly without sacrificing our design standards. This can cause a tension in our collaborative process, as the feedback loop of review and <a href="https://medium.com/granify/a-critical-analysis-of-feedback-44e1bbde278">thoughtful critique</a> can either encourage reviewers to drop their own projects to review work from a contributor or cause a delay in reviews as reviewers focus on completing a project before switching into review mode. We’ve all heard about the drawbacks of context-switching (and if you haven’t, <a href="https://twitter.com/granify/status/863169106102677505">here’s a tweet</a>) and in optimizing our process we always seek to increase our ability to focus.</p><blockquote>We like to share our work and tear it down to rebuild it — better, stronger, faster, like a digital Six Million Dollar Man.</blockquote><p>In 2016 our design team put a great deal of emphasis on overhauling our creative process. We experimented with tweaks to our review process, toolset, and workflow, and after a few false starts and faceplants, we came across a tool that facilitated a better process, workflow, and product. It was like pouring a can of gasoline onto the spark of our design process, turning it into a roaring blaze of creative output.</p><p>Working primarily with Illustrator, Photoshop, and InDesign we could (and still do) share assets across files, devices and operating systems using Google Drive. While this was better than no sharing system at all (imagine if we were all working off our local devices… *shudders*), this solution had its flaws as a collaboration tool. Every now and then, someone’s Drive just would not sync, and we’d have the painful Slack thread in which two designers tried to determine whose Drive was not syncing before both quitting and re-starting their local Google Drive folders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*l5UZmrQW3E-hFcIR181Ibg.png" /><figcaption>Shared pain at its finest.</figcaption></figure><p>Even worse, the convenience of shared files turned out to be a double-edged sword in collaboration. If two or more designers were working on the same project, at the same time, constant pre-save check-ins and post-save file merges were needed to keep everything running smoothly. In one terrifying (and isolated) instance, the unthinkable happened, and one designer saved over another’s file. A solid hour’s worth of work sent hurtling into the digital aether. Shed a tear for those wasted pixels another day; life must go on. We began to look beyond our existing toolset for solutions.</p><p>We had used symbol-adjacent workflows in our Adobe files (common assets created and linked into an InDesign file or common smart objects in Photoshop) and understood and appreciated the need for a UI-centric tool in our process. We’d heard great things about <a href="https://www.sketchapp.com/">Sketch</a>, but as a Mac-only application, it wasn’t the solution for our team (yes, we have designers using Windows; we’re tolerant like that).</p><p>Setting aside the search for a tool to refine our process, we attempted to streamline our workflow with a new review process. With three members of our design team being designated for visual review, we decided that designs would require unanimous approvals from these reviewers before moving ahead. By using Github’s Review/Approve functionality in Pull Requests, we could hack a tool we were already using. Initially this worked out well, as the reviews could be done asynchronously and at the reviewer’s convenience, with a clear binary of a design being Approved or Requiring Review. No need to drop your current work and hop into a critique, the thinking went, as the reviewer could simply check for Github notifications at the same time as they would typically check their email and then allot some time that day for reviews. Unfortunately, the unanimous review process added delays and overhead to the design process rather than accelerating it, while increasing the delay in our feedback loop. The added turnaround time led to subsequent portions of the process being pushed up against tighter and tighter deadlines. We needed a tool that would allow rapid feedback, exploration and iteration, and we needed a more agile approval process.</p><blockquote>The unanimous review process added delays and overhead to the design process rather than accelerating it.</blockquote><p>In late 2015, a member of our product team had come across an <a href="https://techcrunch.com/2015/12/03/figma-vs-goliath/">article</a> about a new tool called <a href="https://www.figma.com/">Figma</a>, that promised real-time collaboration. They sent it over to the design team, and, intrigued by the premise, we all signed up for their beta. When Figma launched later that year, we each opened it up, played around with it a bit, and created some pretty dumb (but incredibly fun) collaborative graphics. To us, it felt so natural… like Google Docs but for UI design. It was around this time that we were staring down the elephant in the room that was our stale visual review process. As our design manager was working on defining the visual style for a new retail partner’s messaging, he invited the rest of the designers to hop into the file.</p><p>Not to get all clickbait-y with you, but what happened next shocked us. Within 15 minutes, we had generated more iterations, made more tangible and informed visual design decisions, and come up with an end product that would have taken a week under our previous <em>create &gt; post &gt; review &gt; revise &gt; repeat</em> process. In the waning days of the Pull Request review system, our visual design team came to an agreement that the benefits of unanimous approval were not enough to merit the overhead it created. Cool as it was to repurpose a version control tool for design iterations, it wasn’t the solution for us. As a team, we decided that the onus for approving a concept internally would lie solely with the contributing designer.</p><blockquote>Within 15 minutes, we had generated more iterations, made more tangible and informed visual design decisions, and come up with an end product that would have taken a week…</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/0*gzYiNdqUuXcteG_Q." /><figcaption>In the time it takes to type out this critique and suggestion, the reviewer can implement the change themselves 3 times.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/0*Vs96X6UQWPyYQzYy." /></figure><p>Using Figma, all of the designers have a voice in the creation of our messaging, but the designer driving the project has the final word on what moves forward. This has fostered an atmosphere of both creative mindfulness and increased creative confidence. Ownership of our work forces each designer to make thoughtful decisions, while the ability to experiment with rapid iterations and formats of a message gives both contributors and reviewers confidence. It eliminates the need to ask questions like “Have you played with the headline size?” when the reviewer can grab a design, make a copy, and play with the headline size themselves in less time than it would take to type out the question. While a Figma review session is not asynchronous by nature, our team can schedule manageable, mutually-agreeable times that do not disrupt our focus and arguably enhance it.</p><blockquote>The ability to experiment with rapid iterations and formats of a message gives both contributors and reviewers confidence.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*5nV1MJBg6-SyylTHe23DTA.png" /><figcaption>A dashboard design project in collaboration with our Business Intelligence team.</figcaption></figure><p>While the benefits of this open and collaborative review process are evident to our designers, they have spread throughout the organization. In optimizing our process, we have increased the design team’s bandwidth to work with the sales, technology, and product teams. Stakeholders can interact with designers in real time, whether across a desk or across a continent, and see a living history of a design’s evolution in the Figma workspace. Our ever-present push to mobile is accelerated by the ability to use constraints to build responsive designs.</p><p>Gaining speed and confidence in the design process without any sacrifice in quality was a huge win for Granify. Every organization faces their own challenges (we still face more as we grow!), and there’s no silver bullet to solve them all, but through process-minded optimization, you can find the fit for your team. For Granify, Figma was a key tool in transforming the way we create and review solutions. If you have found any awesome tools or techniques that have helped your process, we’d love to hear about them :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54ebe8d6cc09" width="1" height="1" alt=""><hr><p><a href="https://medium.com/granify/light-your-design-process-on-fire-54ebe8d6cc09">Light Your Design Process On Fire</a> was originally published in <a href="https://medium.com/granify">Granify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>