<?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 Rick Swette on Medium]]></title>
        <description><![CDATA[Stories by Rick Swette on Medium]]></description>
        <link>https://medium.com/@rickswette?source=rss-6fbde65c7df2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dpc7Tbq8cD0ubkZSE8rWSg.png</url>
            <title>Stories by Rick Swette on Medium</title>
            <link>https://medium.com/@rickswette?source=rss-6fbde65c7df2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:14:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rickswette/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[“Data Thinking”: A Case Study for building a usage analytics system]]></title>
            <link>https://medium.com/ux-data/data-thinking-a-case-study-for-building-a-usage-analytics-system-2f0609ba3cc0?source=rss-6fbde65c7df2------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f0609ba3cc0</guid>
            <dc:creator><![CDATA[Rick Swette]]></dc:creator>
            <pubDate>Tue, 12 Mar 2019 19:24:13 GMT</pubDate>
            <atom:updated>2021-08-27T17:00:05.362Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RE5ia8qhULOkEAYn_vnK9w.png" /></figure><h3><strong>“Data Thinking”: How I do product Analytics</strong></h3><p>A case study with real examples.</p><p>There are three steps to this work: The Analytics Strategy, The Event Specification and The Dashboard.</p><h3>Part 1: The “Analytics Strategy”</h3><p>An analytics strategy is a common first phase of a project before beginning the expensive process of building usage analytics into your product. After delivering this work for 4 project teams at Infor, I finally did it. I re-designed the format of the “Analytics Strategy.”</p><p><strong>This is what it looks like:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/985/1*A2Phgkyj5qQCCVx0yibw_w.png" /><figcaption>You can read a copy of it <a href="https://medium.com/ux-data/xm-ios-minimum-measurement-plan-b0423d371aa9">here</a>.</figcaption></figure><p><strong>These are the principles it follows:</strong></p><ol><li>Visual. I was keen on adding abstract additional data visualizations to the document for clarity, but mainly just for the sake of being visual, which keeps viewers reading and engaged.</li><li>Minimal. Many problems and metrics were left off of this document.</li><li>Prioritized. The first scroll of the page is the top of the funnel and I want the reader to get hooked.</li><li>Self serve. I focus my efforts on the narrative version of the document. Basically, just not a deck.</li><li>Framed as problems and solutions. This is my <em>favorite</em> one. It prevents confusion around the tough question of “so what do I do with this data?” This focus, this intent, is so important to get done before you get swept away into analyzing the data you do have.</li></ol><p><strong>Here are the inspirations:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Z-a1ktXZZBNc_5Rgx80NlQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ltqQWxHThltej1L09wlylA.png" /><figcaption>Left: WeWork dashboard. Right: My App dashboard sketch in same style, but grouped into problems.</figcaption></figure><ol><li><a href="https://medium.com/@tsharon/measuring-the-wework-member-experience-dca7312857a2">The WeWork member experience dashboard</a>. I was struck by epiphany when I saw this: Basically, I realized that I needed a design system.</li><li>The exercise of “Problems, <em>then</em> solutions” (read more <a href="https://www.thinkingdimensions.com/blog/it-csi/problem-solving-through-divergent-and-convergent-thinking">here</a> , <a href="https://www.extension.harvard.edu/professional-development/blog/divergent-vs-convergent-thinking-how-strike-balance">here</a> and <a href="https://medium.com/swlh/start-with-problems-not-solutions-8521c53264b2">here</a> ) is one of my favorite wisdoms that is part of the field of Human Computer Interaction . It was uncanny and exhilarating to realize that it could have such a role in building out product analytics for apps and brands.</li></ol><p><strong>How to do it yourself:</strong></p><ol><li>First, identify and prioritize the problems your solution will solve. Then, sketch or simply describe solutions for these problems. This is just the regular process that UX people are trained to do.</li><li>Then, come up with as many metrics that should correlate with the problems which are being solved. I like to say that coming up with metrics is an under-appreciated skill — you can be creative. Remember to not confine yourself to things you can necessarily measure. It’s a brainstorm.</li><li>Scale back to what can be measured, and maybe include some “optional” metrics that are more expensive to calculate.</li><li>And boom you are pretty much done. Now, package up the problems and metrics in some kind of digestible format!</li><li>Finally, Add in your generic “adoption” category. Adoption, engagement itself indicates that users are seeing value and are having their problems solved. (And depending on the sophistication of your org, connect up to sales data and pair adoption with ACV!)</li></ol><p>p.s. Remember to circle back and iterate. Technically the analytics strategy should be a one-to-one with the evolving key drivers the product group is working on.</p><h3>Part 2: Create the event specification</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*BD44k1dcfleRMj0O1_9ccQ.png" /></figure><p><strong>Here is what it looks like:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xyeYfzUVeKPz6S4vEbf4nw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5GXV-F2e36JcsT9_1CZbFg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1mMlsWwyUt_fnMtbmUXzAQ.png" /><figcaption>LEFT: Event Map showing the paths that trigger each event. CENTER: Event table with Properties. RIGHT: Property Table with Values and which Events they are used for.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*J0f_idetxOdI_F2iy6thmQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UeiOmtdwtbLwsxyz_O0SdA.png" /><figcaption>LEFT: Event path description, with Syntax for each event. RIGHT: Metrics Summary.</figcaption></figure><p><strong>Principles:</strong></p><ol><li>I work backwards from the land of interesting metrics I identified, and simply ensure my tool can visualize it.</li><li>Resist breaking minimalism and not adding extra stuff I don’t need.</li><li>Put care into the document. Show respect to the developers implementing the tags.</li></ol><p><strong>Inspirations:</strong></p><ol><li>The Mixpanel “<a href="https://mixpanel.com/blog/2010/03/22/the-death-of-the-pageview/">Death of the page view</a>” article recording where a user is (i.e. “page”) indiscriminately, we lack intent in each item we choose to record, and entropy increases. By doing so, we create data noise that analysts could waste time analyzing, and proliferate a mind-set of not having intent in our research.</li><li>A quote from a somewhat <a href="https://community.segment.com/t/h48abr/saas-event-tracking">obscure page </a>on the Segment.io docs site. It reads:</li></ol><blockquote>“The mistake most people make when installing tracking for SaaS is trying to record everything immediately. Adding tracking on an iterative cycle leads to quick wins and a much better analytics system.”</blockquote><p>This quote clicked with me and reinforced my ability to resist temptation to add more and more events and properties.</p><h3><strong>Part 3: Building the dashboard</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*McTYUOPgwJg9EgWEKUKpjA.png" /></figure><p>Basically, the analytics strategy did the heavy lifting for you. Just go out and execute. I use Google Data Studio to build the dashboard, and rely on modifying the SQL that builds the sources, as opposed to using the GUI “data modeling” tools that Data Studio offers.</p><p><strong>Here is what I have right now:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-zJoJ8wXfd-nFKjMdPNfzA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GrMUpWJrLLlTTk-sjva1uA.png" /><figcaption>Left: Dashboard cover page: Right: Drill ins by Customer.</figcaption></figure><p><strong>Principles:</strong></p><p>First off, the dashboard is basically a straightforward execution from the strategy portion. Metrics, trended, w/ options to drill in. Here are some other notes as I got to the execution.</p><ol><li>Label metrics with explainer text directly in the report. (Don’t fully rely on an appendix).</li><li>I love trend or spark lines. I think they draw the eye and are one of the most effective way to engage the viewer to see a story.</li></ol><p>There is a lot more to say here, but I will leave it at that!</p><h3>Recap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*5-UYcNnBXx6SeROa1Y0wFg.png" /></figure><h4>Why I titled this piece “Data thinking”</h4><p>I call this “data thinking” because you can do a lot with “data” without having well…“data.” A well thought out analytics strategy, created well ahead of product work can be a rudder. This is very similar to the often blogged about “<a href="https://felipecastro.com/en/okr/what-is-okr/">OKR</a>.” My case study is about how when someone asks you to track their app, you can flip the conversation into much more.</p><h4>Coming up with metrics is a creative exercise, one that can be learned</h4><p>It took me a while to get more creative and wholly appreciate the skill of creating metrics. I read a lot of analytics click bait and I just hadn’t run into the idea of “hey, be divergent about coming up with metrics!”</p><h4><strong>Minimalism and “Problems &amp; Solutions”</strong></h4><p>It is not a coincidence that some of my favorite themes from working in software surfaced in this work.</p><p>Learn more about me at <a href="http://rickswette.info/">http://rickswette.info</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f0609ba3cc0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-data/data-thinking-a-case-study-for-building-a-usage-analytics-system-2f0609ba3cc0">“Data Thinking”: A Case Study for building a usage analytics system</a> was originally published in <a href="https://medium.com/ux-data">UX &amp; DATA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we use, I mean, love Slack]]></title>
            <link>https://medium.com/ux-data/why-we-use-i-mean-love-slack-591664fc374f?source=rss-6fbde65c7df2------2</link>
            <guid isPermaLink="false">https://medium.com/p/591664fc374f</guid>
            <category><![CDATA[enterprise-software]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Rick Swette]]></dc:creator>
            <pubDate>Wed, 27 Jun 2018 22:12:06 GMT</pubDate>
            <atom:updated>2018-09-01T01:08:50.233Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k-ClrfPu54Y8NfQhid6Meg.png" /></figure><p><em>The three layer cake of a transcendent app: Utility, Usability and Desirability</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DAaRp67-Tuub49luD4wIQg.png" /></figure><h3><strong>Utility</strong></h3><p><em>Utilities that drive slack’s base layer</em></p><p><strong>1. “The Slack way” of transparency</strong></p><p>Slack affords teams to use public #channels around certain topics which promotes incredible transparency. Imagine joining a new team feeling behind, but having immediate access to every topic being discussed at the org, going all the way back to the beginning. Because so much conversation is happening in these public places, it makes it very easy to replace a “scrum” meeting, or get a quick answer to an important question. You can list a keyword like “analytics,” and get notified when anyone in the org includes it in a public chat. And Slack nailed it in terms of <a href="https://cdn.vox-cdn.com/thumbor/Dwady9I39lDREUTssdlgTz01Eyg=/0x0:440x600/720x0/filters:focal(0x0:440x600):gifv():no_upscale()/cdn.vox-cdn.com/uploads/chorus_asset/file/8454389/GIF___Search_for_people_and_channels.gif">search</a>.</p><p>This is the first on the list because the trust and efficiency the tool affords for a team is what makes it impossible to live without.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*chf-2CcRItpzQrdUn9ScIg.png" /></figure><p><strong>2. Integrations and customizability</strong></p><p>I would argue that integration is paramount to the success of enteprise software. Slack, integrates and it does so especially well. It’s the ultimate gooey personality, compatible with what feels like everything. It also has an API for building your own apps. So like all great enterprise software, its customizable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/1*OD4_pk9oskjBsQPLHalnHw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*Tikl5DcLLc29ym8Dmdan6w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*ImjmPjdeudsLhNdiut76KA.png" /></figure><p>These integrations “streamline your workflows” by letting you get work done right inside of Slack and generally chips away at a fragmented digital life across ecosystems. Here is a simple example:</p><p>Problem: We collaborate in the design tool inVision, and potentially, yet another place to communicate. Ugh.</p><p>Solution: Slack &lt;&gt;Invision integration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/559/1*UQKsVIIwf8-NgU0b7Ahdjg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*P-Tzqzkk5WZe_ZCLjcXsbw.png" /></figure><p>Some other favorite “integrations” are <a href="https://www.polly.ai/slack-poll">Polly polls</a> and <a href="http://paperbot.ai/">Paperbot by Skore</a>.</p><p><strong>3. Communication done right</strong></p><p>The following points could have been filed under usability, but we’re going with utility because Slack solved basic needs of communicating where Email came up short. You can add people to a conversation or reply to a certain part of it (known as a <a href="https://get.slack.help/hc/en-us/articles/115000769927-Message-threads">thread</a>), and you never get weird email signatures, long cc lists, or formatting issues disturbing the zen of the experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*glRyV91anggt2qHc1BeM_g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RFYIKfFH50w4fn3GBue1LQ.png" /></figure><h3><strong>Usability</strong></h3><p><em>A laundry list of doing it right</em></p><p><strong>1.Slack is “minimalist.” </strong>This is mostly everybody’s favorite design rule.</p><p><strong>2. Meanwhile, Slack nails it for the power user. </strong>A very important <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">usability rule</a> (credit to Jakob Nielsen) reads as follows:<strong> </strong>“Flexibility and efficiency of use: Accelerators — unseen by the novice user — may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.”</p><p>Slack Nails this concept of accelerators with the infamous “<a href="https://get.slack.help/hc/en-us/articles/226599368-How-to-use-the-Quick-Switcher-">quick switcher</a>,” a “hidden feature” that does not clog up the interface for the novice, but allows for power users to get things done quicker.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*J-PaM8AVbrMD8jVGelFO4A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/248/1*X4y79ceSdxN1mkgce5vS5A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*Rj_8ErNeqgcWCnOxtxHfCQ.png" /><figcaption>Slacks Keyboard accessibility (especially the quick switcher) is 🔥</figcaption></figure><p><strong>3. Slack gives you three ways of combatting information overload.</strong></p><p>First, Muting. You can mute a channel intuitively, or easily set to “do not disturb mode,” or you can put that mode on a schedule!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*74_07CiVQejdlBKqzKQ4lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*m9mJidD3OUwRnFLFZ1LryQ.png" /></figure><p>Secondly, Slack makes it <a href="https://get.slack.help/hc/en-us/articles/226410907-View-all-your-unread-messages">easy to get caught up.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P4Ao8gkWMrKtFhJcOkhavg.png" /></figure><p>…And finally, they even have a pretty well executed <a href="https://slackhq.com/focus-on-the-important-things-with-highlights-in-slack-5e30024502cd">“highlights”</a> feature which recommends personalized must-see content. This aspect of Slack is on the verge of being a classified under Utility, depending on how the company can execute on it’s <a href="https://www.technologyreview.com/s/608953/slack-ceo-how-well-use-ai-to-reduce-information-overload/">grand vision</a> for this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*4nwgrDoii3TBCPD5-YNgYw.gif" /></figure><p><strong>4. Slack </strong><a href="https://www.appcues.com/blog/slack-user-onboarding-experience"><strong>on-boards</strong></a><strong> you right.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j4JczB-4znHDd1RhsHqxfA.png" /></figure><p>It’s nice to see a product elegantly introduce itself to a first time user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1006/1*3khN5McCY30ruUsQqor9tQ.png" /></figure><h3><strong>Desirability</strong></h3><p><em>The cherries on top, the long tail</em></p><p><strong>1. Slack is reliable.</strong> Reliable in a doesn’t crash kind of way, but also in a doing all the little things way. It let’s you upload a very large file. Or voice conference or screen share. Paste a code snippet with proper formatting. Preview an article when pasting a link. It’s all there. This long tail of features is just impressive and it builds a lot of trust with users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*jxmgXMD_rBOZJG5llQFGtA.png" /></figure><p><strong>2. Obsessive detail. </strong>Slack<strong> </strong>doesn’t just have it all, the pieces are executed immaculately. For example, here is some insight into how they <a href="https://slack.engineering/a-faster-smarter-quick-switcher-77cbc193cb60">improved the quick switcher</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*yC2wBTw4R4D3w5RAgMqYcA.png" /><figcaption>Excerpt from slacks <a href="https://slack.engineering/a-faster-smarter-quick-switcher-77cbc193cb60">improving the quick switcher</a> piece</figcaption></figure><p><strong>3. </strong><a href="https://giphy.com/search/task-success"><strong>Giphy</strong></a><strong> and emoji integrations.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*NclHigj_h8c8I542m2pm1A.gif" /></figure><p><strong>4. Cool loading and error screens.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/290/1*jbK6ZsdYETmP-8ZjBvGziA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oWXqmjmndHMqsTSD8_rMMQ.jpeg" /></figure><p><strong>5. Culture. </strong>Slack affords a culture of transparency in the org, but it also seems to afford culture and humanizing being a worker. Here is an example: It introduced statuses, but instead of a textfield, it forces you to pick a single emoji. Slack actually has a whole feature set for uploading custom emojis- furthering the affordance of expressivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*-Rpc0Nwd1Z1cTCWGguA0Iw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/1*rk3XZGJCm5so4Dt_4qV2JA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k-ClrfPu54Y8NfQhid6Meg.png" /></figure><h3>Conclusion</h3><p>The “craft” (their words not mine) and execution on what seems like literally everything results in a unicorn in the software business. People don’t just like Slack, they freaking <a href="https://twitter.com/SlackLoveTweets?lang=en">love it</a>.</p><p>Thanks for reading. Check me out at <a href="http://rickswette.info/">rickswette.info</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=591664fc374f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-data/why-we-use-i-mean-love-slack-591664fc374f">Why we use, I mean, love Slack</a> was originally published in <a href="https://medium.com/ux-data">UX &amp; DATA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Examples of Insights for Design]]></title>
            <link>https://medium.com/ux-data/insights-for-design-real-anecdotes-b84309a8fc40?source=rss-6fbde65c7df2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b84309a8fc40</guid>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Rick Swette]]></dc:creator>
            <pubDate>Tue, 10 Oct 2017 19:06:35 GMT</pubDate>
            <atom:updated>2019-02-26T05:35:46.144Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1DnLUPAiqf6dpmoFrfdE3Q.png" /></figure><p><em>Anecdotes and perspective from my experience as a design researcher</em></p><p>The part I really care about is these anecdotes. A person may google “design insights” or “user research” and find themselves sifting through highly overlapping process stuff. Instead, I wanted to just give some color to the insights I’ve provided over the years as a <a href="http://rickswette.info/">design researcher</a>.</p><h3>A simple observation that does not require your own research</h3><p><em>You already have it, just bring it to the forefront</em></p><p><strong>e.g. Visitors are more likely to navigate in-page then navigate to a new one &gt;</strong> Put every product in “one page”</p><p>As a digital analyst, I had often been shocked by the lack of engagement on web properties. I cajoled my client to get on board with the “<a href="http://sweetearthfoods.com/products.html">one page</a>” product page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*JW20RienOCh6jMTJUKWosA.png" /></figure><p>I considered these results a success.</p><p><strong>e.g. The first song on Spotify’s “discover weekly” playlist must be amazing to achieve traction on that playlist &gt; </strong><em>Ensure that first song passes as an “amazing song”</em></p><p>My first time trying “discover weekly” I heard a song so incredible that I found myself very encouraged by the promise of the feature. The idea is to ensure the first song in these playlists be of the highest ratings. In my opinion, I think the logic here is sound, where it would be worth considering testing this without “research” to back it — basically, it’s a good hypothesis. The “insight” here is just to apply the often-needed logic of focusing on the top of the funnel.</p><p><strong>e.g. Nielsen’s usability heuristics &gt;</strong> <em>Yeah, buddy!</em></p><p>I still get insane value from these and am fine with working them into an insight I can throw up on the board.</p><h3>Inspired by a great question, not the result</h3><p><em>Ask and you shall receive</em></p><p><strong>e.g. Visitors spend very little time outside of one specific program &gt; </strong>Sell the programs, not the school</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/1*r6C2xtsx_JTwFViRJ7vH1A.png" /></figure><p>I wasn’t surprised by the result, but I’m sure glad I took the time to build 10 Google Analytics segments and put this chart together.</p><p>However, The client was surprised by the lack of overlap. And just as important, the imagery was memorable and powerful for our stakeholders.</p><p>What did surprise me was the idea that came from the result. A lot of the content effort on the site was geared to the overarching program. It became clear that the site had very clear personas that needed to be targeted individually, not addressed in mass.</p><p>*Note: Another possible interpretation is that the lack of overlap was an insufficiency of the design to afford exploring the diverse offering of programs. This would be in contrast to taking the observation at face, as a user need, that applicants are only focused on specific programs.</p><h3>An inherited fact you are making too much of</h3><p><em>You will never have inherited enough legacy</em></p><p><strong>e.g. Students and Faculty listed “leadership” as the least important item they would use to sell prospective students on the school &gt;<em> </em></strong><em>Get leadership content out of the highest level in the navigation and de-prioritize it as a message</em></p><p>Despite the result of a survey, the creative director for this project studied the competition and believed that 1 on 1 “leadership coaching” was a unique and compelling offering for a program in their market. Go with your gut, a/b test, recognize that the you don’t know, and most of all, always be looking to triangulate your data sources.</p><h3>A clever observation that was in plain site</h3><p><em>Refocus in hopes for that special epiphany</em></p><p><strong>e.g. Users will go out of their way to preserve context in their space &gt;</strong> <em>Design a window management system where staying in context is at the forefront</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*aOerknWZy94EbPvoJLgnsA.png" /></figure><p>I noticed a very subtle behavior of users dragging a window simply to obscure less of the other windows in their space. This is similar to what is accomplished by the feature of “cascading windows.” On this project, we found out early that many users were averse to maximizing (by asking them), but through a keen observation, the insight that users want context gained significant more weight.</p><p><strong>e.g. Knowing the weather is relevant to tasks users accomplish in their Maps app &gt;</strong> <em>Lets</em> <em>put a “67 and cloudy” in the map?!</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/418/1*xH1hAEx47UEVyui1KjCwzQ.png" /></figure><p>If your maintaining an open mind, you would have noticed how often weather was part of the total cx happening in maps and this is exactly what apple maps did.</p><h3>A surprising finding that is strong evidence for a particular strategy</h3><p><em>For the lucky ones only</em></p><p>This is what most people think they are going to do when they get their hands on that “data” as they start to slow on the design front.</p><p><strong>e.g. Those who visited Doctor and Affordability pages were more likely to convert then visitors to other pages &gt;<em> </em></strong><em>A</em><strong><em> </em></strong><em>worthy hypothesis: Funnel users through doctor-specific, not clinic-specific conversion flows. Consider ramping up the doctor-centric strategy for content.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/422/1*R__VA9V6dq-Lpog7Eartmg.png" /></figure><h3>A simple tactic that bubbles up as a key element of your new design strategy</h3><p><em>An initial straightforward observation may make a big comeback</em></p><p><strong>e.g.</strong> <strong>Those who apply to the MBA program spend a majority of time in admissions pages and do not visit alumni/careers/news content &gt;<em> </em></strong><em>Sell the program on admissions pages where prospectives are spending a lot of time</em></p><p>This was an early observation that users were not visiting these other pages, but as I worked with the creative director, the way to solve for that became front and center of our pitch.</p><h3>The info is in plain sight and the insight is obvious</h3><p><em>Don’t overthink it</em></p><p><strong>e.g.</strong> <strong>You have as many Facebook visitors as actual visits on the year on your television site &gt; </strong><em>Include Facebook assets and specific strategies that start the CX journey in the Facebook-verse and vice versa</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/835/1*u-WA8MI1PZX-vFZet-bKpQ.png" /></figure><p><strong>e.g. When I surveyed small biz owners, they reacted well to “A Professional Email” over “Private Cloud.” &gt; </strong><em>Message that way</em></p><p>What was typically being advertised as a feature of Google Apps for Business (which you could get set up on your personal domain), started to message itself as Google Domains. I also found that words like “Domains” didn’t resonate either compared to “Professional Email.” My own research with 20 users actually supported such a strategy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sl2QKWuYrphFlwqb123PLQ.png" /></figure><h3>You ran an A/B test, so you feel confident</h3><p><strong>e.g. Landing page A beat landing page B &gt; </strong><em>Use landing page B</em></p><p>“A &gt; B” is “true” in a very specific context. This result is forever tied to the specific circumstances of that test, which will always have limited relevance to the real product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IXXuINnStgxDRJosUNP0QA.png" /><figcaption>A/B test I managed for Alamo.com</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*64mKaLHdFZfBiIGF-YQfRA.png" /></figure><h3>Let’s Recap</h3><p>Basically, free your mind about where your insights can come from and what your takeaways can be.</p><p><strong>Was the insight driven by…</strong></p><ul><li>A hard number (or an a/b test) or guesstimate?</li><li>Your own (primary) or someone else’s (secondary) research?</li><li>A fancy or a darn simple metric?</li></ul><p><strong>Was the takeaway…</strong></p><ul><li>Perceptive or pretty obvious?</li><li>Top-down/design-related or more abstract?</li><li>Controversial or not controversial?</li></ul><p><strong>My point is…</strong></p><ol><li><strong>So much of insights work is a creative process.</strong> The outcomes are a result of the researchers choice to ask a good question, to point something out and prioritize it above other facts, and finally to sell it with appealing actionability.</li><li><strong>So don’t let your work suffer by limiting your “research” to hard numbers or your own primary research. </strong>Try and reduce your bias towards reco‘s that you found yourself or the data sources you’ve been given access to. General truths, not necessarily “data” carry so much of the weight of good design. Step back. If you are doing this work you are a designer, dude. So start acting like one.</li></ol><p>Visit my site to learn more about me: <a href="http://rickswette.info/">http://rickswette.info</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b84309a8fc40" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-data/insights-for-design-real-anecdotes-b84309a8fc40">Examples of Insights for Design</a> was originally published in <a href="https://medium.com/ux-data">UX &amp; DATA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>