<?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 Thomas Meimarides on Medium]]></title>
        <description><![CDATA[Stories by Thomas Meimarides on Medium]]></description>
        <link>https://medium.com/@tmeimarides?source=rss-761ba31f3b9c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SqwDyUbtFE9Mv-yZafq-Cg.jpeg</url>
            <title>Stories by Thomas Meimarides on Medium</title>
            <link>https://medium.com/@tmeimarides?source=rss-761ba31f3b9c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:29:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tmeimarides/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[My take on design leadership]]></title>
            <link>https://medium.com/axial-product-and-design/my-take-on-design-leadership-31064a727a71?source=rss-761ba31f3b9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/31064a727a71</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Thomas Meimarides]]></dc:creator>
            <pubDate>Thu, 06 Apr 2017 15:01:08 GMT</pubDate>
            <atom:updated>2017-04-06T21:47:29.710Z</atom:updated>
            <content:encoded><![CDATA[<p>Being a leader is more than just being the most senior or tenured designer on the team. In the year+ that I’ve been UX Director at Axial, I’ve gotten a crash course in design leadership. Here are some insights I’ve learned through the crucible of product design at a small startup that may sound obvious on the surface, but when you’re in the day to day, are useful to step back and remember.</p><h3><strong>Empower independence</strong></h3><p>The biggest challenge and transition for me from being an individually contributing designer to becoming a design leader was really encouraging my team to follow their own paths and processes, and checking my own opinions. Every designer approaches a problem differently and will have a different solution. The important thing to remember as a design leader is that there is a delicate balance between providing guidance, maintaining direction and velocity, and knowing when to allow a designer to explore and wander in order to find the right path back on their own. I’ve heard managers often say that it’s important to sometimes let a team member make a mistake or fail (within reason) in order to help them learn the lesson for themselves, and that’s the same principle. With independence, trust that your team and processes will help guide the solution forward, and own that responsibility without undermining or over-influencing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I3PU3oUypv41QxJ6." /><figcaption>After a recent trip to Africa and flying over the plains, the networks of natural wildlife trails and paths was astounding. They all lead to a common point or central point. You have to trust that instincts and other driving factors will get everybody to the right destination.</figcaption></figure><h3><strong>Teach, don’t tell</strong></h3><p>Having been at Axial for longer than most of my team, there’s a lot of historical context for decisions, directions, challenges and solutions living in my head. When someone without that context is grappling with a challenge, I have to remember to provide that context in my feedback in a way that encourages their independent arrival at a solution. This isn’t Inception, and this isn’t dictating a solution. After all, whatever solution I have in mind may not be the best one, anyway. Combining ideas and exploring feedback while empowering their own independent problem-solving process tends to lead to better outcomes, in both the short and the long-term.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/455/0*WmFIjxbNCKI5pK5z." /><figcaption>Basically, don’t be like Homer when he tries to teach.</figcaption></figure><h3><strong>Open up the process to non-designers</strong></h3><p>One of the best things we’ve done at Axial (full credit to our VP of Product for encouraging and stoking this fire) is to open up our design sessions and ideation to the rest of the organization. We now hold bi-weekly Design Studios with members from all groups across the company where we posit a challenge or concept (or we invite attendees beforehand to submit ideas), and then give everyone 10 minutes to sketch or write on paper how they would approach or solve the problem. We each get 2–3 minutes to stick our sketch on the wall and explain our thinking, and at the end, everyone gets a couple of votes to ‘dot-vote’ their favorite components or ideas. It’s been a great way to synthesize and identify strong ideas to guide the design team as they start to formally think through a problem in their next project, or 6 months later when finally tackling that set of features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*kUfH0H6KVPIQ7nPO." /><figcaption>From a Design Studio with the Engineering team</figcaption></figure><p>Additionally, these design studios give those outside of the team a sense of how design and product thinks about the everyday challenges we face and our customers face, and shows how the design process works. We’re actively seeing more participation in the studios, and getting positive feedback from everyone involved.</p><h3><strong>Don’t limit your critiques and process to just your team, vertical, or other artificial constraint</strong></h3><p>Design is organization wide. It affects every part of your brand, product, and user experience. Even if your marketing team is a different team in a different building or state, you have to extend your process to include them (and they to you). You have to meet regularly to talk about design and collaborate to solve problems together. A potential or current customer doesn’t know about your hierarchy, but they notice when your marketing site, your sign up process, your core application, and your engagement emails are all inconsistent in voice, experience, or visual treatment.</p><h3><strong>Right, duh, I’ve heard all this before.</strong></h3><p>None of this came as a surprise to me. I’ve been reading about, talking to, and working with great design leaders for a long time. What did come as a surprise, and the ‘aha!’ moments came when it was MY turn to be that voice. As a design leader, you’re working with a different set of filters and tools, with different objectives. It’s about listening to your team, and collaborating without preconception and without ego. It’s providing context where necessary, and providing the freedom to explore and ideate in a safe and productive way. It’s lifting and supporting your team from behind as well as pulling them forward from the front. And it’s making sure that design is part of every conversation.</p><h3>What else does being a design leader mean? I welcome your thoughts in the comments.</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31064a727a71" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axial-product-and-design/my-take-on-design-leadership-31064a727a71">My take on design leadership</a> was originally published in <a href="https://medium.com/axial-product-and-design">Axial Product and Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Read These Product Design Links]]></title>
            <link>https://medium.com/axial-product-and-design/read-these-product-design-links-d992cde8580?source=rss-761ba31f3b9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d992cde8580</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Thomas Meimarides]]></dc:creator>
            <pubDate>Mon, 12 Dec 2016 22:49:37 GMT</pubDate>
            <atom:updated>2016-12-12T22:50:13.838Z</atom:updated>
            <content:encoded><![CDATA[<p>Here’s what’s inspiring us this week:</p><p><strong>Thomas:</strong> I enjoyed reading @kristoforts’ post about user testing. Most of our testing at Axial is done remotely with our customers. <br><a href="https://uxdesign.cc/i-sat-through-hours-of-user-testing-sessions-heres-what-i-learned-ead5166a4528#.he0yqrqup">https://uxdesign.cc/i-sat-through-hours-of-user-testing-sessions-heres-what-i-learned-ead5166a4528#.he0yqrqup</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-pZasCJanU59md64nHwCzw.jpeg" /><figcaption>One of the outputs of a qualitative research meeting.</figcaption></figure><p><strong>Thomas:</strong> @tessrothstein’s post about interactive UX research was also pretty great, and is similar to how we’ve started bi-weekly qualitative research sessions here at Axial. Instead of presenting UX findings in a boring presentation or bulleted list of improvement ideas, getting interactive with the team by regularly viewing select usage or session replays, playing guessing games around the questions or pain points then seeing where you were right, or generally workshopping problems makes UX research much more actionable and engaging.<br><a href="https://medium.design/make-your-findings-interactive-d83a2204b11e#.pycsk4hl4">https://medium.design/make-your-findings-interactive-d83a2204b11e#.pycsk4hl4</a></p><p><strong>Sarah: </strong>Here’s a tool being developed by Adobe Research and the computer science department at the University of Toronto. It’s a system generating design layouts. Although the elements and layout are both fairly rough, you can easily see how a tool like this could be helpful and incorporated into a design process. <a href="http://www.dgp.toronto.edu/~donovan/design/index.html">http://www.dgp.toronto.edu/~donovan/design/index.html</a> and Khoi Vinh has a more thorough write-up here: <a href="https://www.subtraction.com/">https://www.subtraction.com</a></p><p><strong>Sarah:</strong> Here’s a good article describing the use of illustrations in product design. The idea that metaphor is a strong driver in determining what kind of illustration should be used may seem like an obvious choice, but I think is often overlooked in favor of style.<br><a href="https://medium.com/shopify-ux/effectively-using-metaphor-in-product-illustration-62bdccbe14e4#.dum9gsa97">https://medium.com/shopify-ux/effectively-using-metaphor-in-product-illustration-62bdccbe14e4#.dum9gsa97</a></p><p><strong>Thomas:</strong> File this one under ‘when algorithms and good intentions go horribly wrong, because robots are dumb’<br><a href="http://qz.com/857122/an-algorithm-rejected-an-asian-mans-passport-photo-for-having-closed-eyes/">http://qz.com/857122/an-algorithm-rejected-an-asian-mans-passport-photo-for-having-closed-eyes/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d992cde8580" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axial-product-and-design/read-these-product-design-links-d992cde8580">Read These Product Design Links</a> was originally published in <a href="https://medium.com/axial-product-and-design">Axial Product and Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do you design a UX to find the right industry out of 20,000?]]></title>
            <link>https://medium.com/axial-product-and-design/how-do-you-design-a-ux-to-find-the-right-industry-out-of-20-000-5f59147192e5?source=rss-761ba31f3b9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f59147192e5</guid>
            <category><![CDATA[taxonomy]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[search]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Thomas Meimarides]]></dc:creator>
            <pubDate>Thu, 08 Dec 2016 14:14:18 GMT</pubDate>
            <atom:updated>2016-12-08T19:59:47.479Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Abstract: </em></strong><em>We’ve used a list of ~200 classifications to identify companies on Axial. This isn’t enough, so we’re increasing it to ~20,000. Here’s the story of why, and also how we’re working to ensure the UX for this critical information is both useful and helpful. This an insight into the design and product processes at Axial, as well as the things we’ve learned from developing this over the last year.</em></p><h3><strong>A brief history &amp; context of industry selection.</strong></h3><p>At Axial, one of the key pieces of information we collect from our customers is industry. For customer profiles, these are the industries in which they operate, the industries they’re focused on for new investments or acquisitions, or the industries in which they have past experience. Axial’s current taxonomy is a heavily modified version of <a href="http://www.investopedia.com/terms/g/gics.asp">GICS</a> with 16 top level sectors and 198 unique industries. When I first joined Axial, one of my first projects was to design a UI to find and select the appropriate industries from this hierarchy. Since that first design, as much as we tweaked and tampered, it just wasn’t enough. UI could only get us so far, because at the end of the day it was our taxonomy that was holding us back — which opened up a whole new can of worms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-HpxK_F1TD58Xk5sNtcYYg.png" /><figcaption>Browsing works when you have a smaller list, but the UI requires a lot of space, and certainly won’t scale to hold 100s of industries within 100s of groups</figcaption></figure><h3><strong>From 200 to 20,000</strong></h3><p>One of the things we consistently heard from customers was that the classifications simply weren’t granular enough. Customers looking to find specific companies in a particularly specialized space could only go so far, and then would regularly have to sift through many results that were in tangential industries that ultimately didn’t interest them. The ability to keyword search and exposing industry descriptions helped somewhat with discovery, but ultimately didn’t solve the problem. Adding keyword filtering to the UX helped further refine the results, but led to confusion later on in the matching results because the level of information was still pretty general at a glance, and those matching keywords weren’t easily surfaced for context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*1aMJzu_Kw88aV186Xt2zQA.gif" /><figcaption>Searching helps, but the UI input makes it hard to quickly add many relevant industries. And, if you don’t really know the name of the industry, you’re SOL.</figcaption></figure><p>A recent example would be a customer support call I observed where an investor on Axial was looking specifically to buy companies to grow the business of an existing energy drink brand. They were looking to either vertically grow by gaining access to distribution networks to get their product into more national grocery chains such as Walmart or Target, or to horizontally grow by acquiring more consumer soft drink or energy drink producers. Listening to the customer try to find the right industries under “Consumer Goods &gt; Food Beverage &amp; Tobacco &gt; Soft Drinks and Packaged Foods and Meats” and “Retail &gt; Food Retail” was not only painful, but I also knew that when he selected those industries, he would also get results for companies producing processed meat snacks, candy, or granola; food processing companies, and companies classified as restaurants or restaurant groups, small chain grocers and convenience stores! Read: not what he’s looking for, and not as targeted as we’d like!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/0*SbpM5RTpGP4ljuoS." /><figcaption>Speaking of meats… “Heh heh yeah right Lisa, a wonderful, maaagical animal” credit: <a href="http://mariah.stonemarche.org/favlinks/pigtree.gif">http://mariah.stonemarche.org/favlinks/pigtree.gif</a></figcaption></figure><p>So, what to do? About a year ago, we decided it was time to offer more granularity of industry options, so we began to explore switching from our current GICS taxonomy to use <a href="http://www.census.gov/eos/www/naics/index.html">NAICS</a>. NIACS is the federally maintained standard used by the US Census Bureau and IRS to classify North American companies, and has 20 top level Sectors, with about 2,000 industry groups, and about 20,000 individual unique industry classifications. Beyond mapping our existing taxonomy to the new taxonomy, our biggest challenge was figuring out how to help our customers find the right industries out of so many options, buried under multiple levels of group classification. <strong>How do we present all these options to our users, and how do we help them quickly find the right industries for them?</strong></p><h3>Browsing vs Searching</h3><p>One of our biggest initial challenges was inherent bias by current customers who were used to ‘browsing’ the entire list and picking what they were used to. In testing early prototypes with existing customers and new customers who weren’t used to using Axial, everybody overlooked the search box completely and gravitated towards a big collapsible tree of sectors, groups, and industries. But once they expanded a group, they very quickly got lost in the details. Taking a stab within a group that seemed logical at first sometimes got them to an industry that best described their company, but often times they struggled to find related industries that had different parent groups. So for the energy drink focused customer I mentioned earlier, he would find ‘<em>Manufacturing</em> &gt; <em>Soft Drink Manufacturing</em> &gt; <strong><em>Soft drinks manufacturing</em></strong>’, but would clearly miss both ‘<em>Manufacturing</em> &gt; <em>Flavoring Syrup and Concentrate Manufacturing</em> &gt; <strong><em>Soft drink concentrates (i.e., syrup) manufacturing</em></strong><em>’</em> and ‘<em>Wholesale Trade</em> &gt; <em>Other Grocery and Related Products Merchant Wholesalers</em> &gt; <strong><em>Soft drinks merchant wholesalers</em></strong><em>’</em>. All of which would be really relevant to him.</p><p>This also doesn’t consider a customer who may think they know specifically what his company does, but doesn’t consider themselves a “manufacturer” and so doesn’t think to look under “manufacturing” to find the right industry. <strong>It became pretty clear early on that “browsing” was simply not a good user experience. We should let computers do it!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*_n2BkPDh66W_JuulAy-xag.gif" /><figcaption>“Computers can do that?”— <strong><em>Homer Goes to College </em></strong>S05E03 — <a href="https://frinkiac.com/caption/S05E03/786751">https://frinkiac.com/caption/S05E03/786751</a></figcaption></figure><p>Early in our discovery process, some of our engineers built a command-line classification tool to allow us to quickly search the NAICS taxonomy by keyword and rank the resulting industries within their group and sector hierarchy. After some more work, we also mapped our existing industries to compare how existing data would be classified in the new taxonomy once we were ready to migrate to the new system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yVTJtS0DGyRbv5gxAbXnJg.png" /><figcaption>Good for quick internal searching &amp; examining results, better than browsing the NAICS site or searching in Excel. Huge thanks to <a href="https://medium.com/u/18736ac13f77">Jon Jia</a>, <a href="https://medium.com/u/b2b3920e71c0">bugra</a>, and Doug Shore.</figcaption></figure><p>Searching was much easier both because it was a more natural and less intimidating input, and because it also allowed us to narrow the massive tree of options down to a few relevant terms. The UX team was pretty convinced that “search” was way better than browse, but had to fight that “I want to browse everything” FOMO mentality. One challenge was determining how much of the hierarchy context was necessary to show in the results, and as I’ll explain more in a second, we needed to figure out how would we handle selection at the group level, vs the bottom industry level. We also have yet to test how many results to return for more generic searches, and how to rank results to best fit what we think the customer is looking for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*QM-4wzjanptOO3iyKTo7Qg.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*1UNnwcyqPqdzd21HPpRqfA.gif" /><figcaption>When there’s too many results — <strong>Homer the Smithers</strong> S07E17 — <a href="https://frinkiac.com/caption/S07E17/266032">https://frinkiac.com/caption/S07E17/266032</a></figcaption></figure><p>We also assumed that investors, brokers and CEOs would likely know their specific NAICS 6 digit code from filling out their tax forms, and searching for ‘312111’ would be a fast way for them to find ‘Soft Drink Manufacturing’. But, we were wrong: not a single customer we spoke with knew their code off hand, and needed instead to search by keyword.</p><h3>To multi-select, or not to multi-select</h3><p>Once we settled on the idea that searching should be the only way to surface either keyword matches or isolated groups, we uncovered an interesting challenge in allowing users to select at higher levels. If an investor is less interested in a specific industry, but instead says ‘We’ll invest in just about anything in the manufacturing sector, provided the revenue and growth rates meet our expectations,’ we certainly don’t want to make them have to select the nearly 4,000 industries within Manufacturing. If you search and see matching results, you may not see other industries in the same group that don’t have that term, and if you can’t see them, you can’t select them. We assumed that selecting a group or sector would inherit all the children within it, whether you could see them or explicitly choose them or not, because that’s how the matching algorithm works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/149/1*HCXoKMOXKwDP-DL2qu0PrQ.gif" /><figcaption>Select some? None? All? Everything everywhere?</figcaption></figure><p>With this in mind, we realized that the implicit ‘select-all’ behavior of selecting a group or sector wasn’t ideal, because in most cases, it would not show the customer everything they would actually be matched against. So, for the next iteration, when someone selects at the group level, we only select the industries that are visible within the result set, and we indicate that there are additional industries that can be shown. If the user chooses to, they can view those additional industries that don’t match the keyword search, which will display all industries within the parent group. Now that the entire group’s children are visible, but still constrained to the group the user initially chose from, the user can simply say “I want this whole group” which will select all of the industries within it.</p><h3>Next steps</h3><p>Using the <a href="http://www.census.gov/cgi-bin/sssd/naics/naicsrch?chart=2012">NAICS</a> website, Excel lists of sectors groups and industries, our industry classifier command-line tool, and quick whiteboard sketches and mockups has gotten us this far, but now that we’re more confident about the right direction the UX needs to take, we need to really test it live. Our next task is to build an actual working prototype that incorporates keyword and group searching and displays appropriate results, and testing user’s ability to select the most appropriate individual industries, groups, or even sector levels. Once we’re confident this is right, we’ll begin to retool how we display industries on user’s profiles, deals, investment mandates, and prior transaction pages, and search results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*SHiNJlv_2XVI7Bj7v51t4w.gif" /><figcaption>Always be testing — <strong>The Itchy &amp; Scratchy &amp; Poochie Show</strong> S08E14 — <a href="https://frinkiac.com/caption/S08E14/222605">https://frinkiac.com/caption/S08E14/222605</a></figcaption></figure><h4>Once we’re done, the roughly 11,000 firms on Axial will not only be able to be much better classified, but will also see a dramatic increase in the quality of their recommendations, introductions, and matches because of better industry data.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f59147192e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axial-product-and-design/how-do-you-design-a-ux-to-find-the-right-industry-out-of-20-000-5f59147192e5">How do you design a UX to find the right industry out of 20,000?</a> was originally published in <a href="https://medium.com/axial-product-and-design">Axial Product and Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Read These (Product Design Links)]]></title>
            <link>https://medium.com/axial-product-and-design/read-these-product-design-links-f89c6a506906?source=rss-761ba31f3b9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f89c6a506906</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Thomas Meimarides]]></dc:creator>
            <pubDate>Wed, 30 Nov 2016 20:11:05 GMT</pubDate>
            <atom:updated>2016-11-30T20:16:53.394Z</atom:updated>
            <content:encoded><![CDATA[<p>Here’s what’s inspiring us this week:</p><p><a href="https://medium.com/u/761ba31f3b9c"><strong>Thomas Meimarides</strong></a><strong>:</strong> <a href="https://medium.com/u/7ca8972daf76">Intercom</a> has a great writeup on mobile browsers being the future universal app. I’ve often overlooked how many native apps drive you into a browser within their app. Adding this to <a href="https://think.storage.googleapis.com/docs/mobile-app-marketing-insights.pdf">recent measures for the number of apps a user</a> will use to daily, the mobile browser is an even more universal medium. All of you mobile-web proponents from years ago can come back out of hiding and say “we told you so!” <a href="https://medium.com/swlh/browsers-not-apps-are-the-future-of-mobile-c552752ff75#.x429adi72">https://medium.com/swlh/browsers-not-apps-are-the-future-of-mobile-c552752ff75#.x429adi72</a></p><p><a href="https://medium.com/u/61e9fda36826"><strong>Sarah Adams</strong></a><strong>:</strong> Unfortunately this link is best enjoyed by people who live in New York. A group of designers (artists?), have opened up a store to help you analyze your digital data. There are interesting devices and workshops that prod you about what kind of information you are sharing with the world.<br><a href="https://theglassroomnyc.org/">https://theglassroomnyc.org</a></p><p><a href="https://medium.com/u/61e9fda36826"><strong>Sarah Adams</strong></a><strong>:</strong> Make sure to turn your sound on for this experience, it’s a fun and creepy one. I don’t want to reveal too much, but based on your web connection and interactions this website shows just how much it knows about you. Good insight into seeing what you can track about a visitor’s presence on your site.<br><a href="https://clickclickclick.click/">https://clickclickclick.click</a></p><p><a href="https://medium.com/u/761ba31f3b9c"><strong>Thomas Meimarides</strong></a><strong>:</strong> When I first started reading this, I was all 🤔 😫. It was only about halfway through that I realized that <a href="https://medium.com/u/e46a1bba73bb">Keaton Herzer</a> was being sarcastic. At that point, i was just 😳 😂. A good laugh and moment of serious self reflection and deprecation for any product designer: <a href="https://blog.prototypr.io/the-ideal-design-workflow-2c200b8e337d#.yioqbwil5">https://blog.prototypr.io/the-ideal-design-workflow-2c200b8e337d#.yioqbwil5</a></p><p><a href="https://medium.com/u/761ba31f3b9c"><strong>Thomas Meimarides</strong></a><strong>:</strong> Two more quick ones from me. I also have forgotten about print-only style sheets. If you talk to your customers, it’s likely that they definitely print out certain pages of your app or experience, especially if they’re ordering something. Delta, I’m looking at you. And if it prints poorly, it reflects poorly on your brand: <a href="https://uxdesign.cc/i-totally-forgot-about-print-style-sheets-f1e6604cfd6#.boxopuexa">https://uxdesign.cc/i-totally-forgot-about-print-style-sheets-f1e6604cfd6#.boxopuexa</a>. <br>And following up to some other conversations we’ve been having about chat-based UX, I thought this article was insightful and interesting: <a href="https://www.smashingmagazine.com/2016/11/does-conversation-hurt-or-help-the-chatbot-ux/">https://www.smashingmagazine.com/2016/11/does-conversation-hurt-or-help-the-chatbot-ux/</a>.</p><p><a href="https://medium.com/u/61e9fda36826"><strong>Sarah Adams</strong></a><strong>:</strong> This is perhaps one of the most universal of universal remotes. A quick peek at the screen on the remote appears to show a beautiful and intuitive UI. But it does bring up questions — why not have these capabilities built into our phones? Why another gadget? On the site it says the remote control supports Uber, and I do wonder about the experience of ordering an Uber from your…remote.<br><a href="https://remote.sevenhugs.com/">https://remote.sevenhugs.com/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/892/1*EABY4z_WO-nmQxEVUt7Prg.png" /><figcaption><a href="https://www.amazon.com/Simpsons-Talking-Universal-Remote-Control/dp/B009S6P5IE">https://www.amazon.com/Simpsons-Talking-Universal-Remote-Control/dp/B009S6P5IE</a></figcaption></figure><p><strong>Thomas:</strong> as Sarah and I were slacking about the Uber remote, I remembered this thing of beauty, and quickly added it to my amazon cart.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f89c6a506906" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axial-product-and-design/read-these-product-design-links-f89c6a506906">Read These (Product Design Links)</a> was originally published in <a href="https://medium.com/axial-product-and-design">Axial Product and Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Read These (Product design links for your  holiday commute)]]></title>
            <link>https://medium.com/axial-product-and-design/read-these-product-design-links-for-your-holiday-commute-ec4e2df57c99?source=rss-761ba31f3b9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec4e2df57c99</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[medium]]></category>
            <dc:creator><![CDATA[Thomas Meimarides]]></dc:creator>
            <pubDate>Wed, 23 Nov 2016 16:45:27 GMT</pubDate>
            <atom:updated>2016-11-23T17:28:11.135Z</atom:updated>
            <content:encoded><![CDATA[<p>Here’s what we’re reading this week as we prepare and recover from the great Annual American Turkey Bloat™</p><p><strong>Thomas</strong>: After last weekend’s group-texting with friends about the current state of college football, (and partially wanting to throw my phone out the window as a result), this proposed simple iMessage notification tweak by @lewisplushumphreys to group together multiple short incoming messages caught my eye. Apple are you watching? <a href="https://medium.com/@lewisplushumphreys/rethinking-message-notifications-on-ios-c201edea59a2#.wts5d4wgl">https://medium.com/@lewisplushumphreys/rethinking-message-notifications-on-ios-c201edea59a2#.wts5d4wgl</a></p><p><strong>Thomas:</strong> If for nothing else, to validate that I’m not a the only one fighting the good fight, I enjoyed reading about other designer’s top UX or usability issues they encounter in the world. Testify 🙌 🙌 🙌 🙌 🙌 🙌 <a href="https://medium.com/swlh/the-8-worst-ux-mistakes-coming-from-experts-692884971f80#.sac9pn4p5">https://medium.com/swlh/the-8-worst-ux-mistakes-coming-from-experts-692884971f80#.sac9pn4p5</a></p><p><strong>Sarah: </strong>This is a visually lovely site with some weird little usability quirks. Overall good branding and illustration that works to recommend places to check out across the globe. Another benefit is they’re curated by designers, so not the typical tourist list.<strong> </strong><a href="http://www.onthegrid.city/">http://www.onthegrid.city/</a></p><p><strong>Sarah: </strong>To be transparent, this link is blatant self-promotion. Over the course of a few days I pitched in on a small project started by some really smart creative people. The goal was around sharing out ways we communicate with each other through difficult conversations. The references to tools and frameworks are helpful for any team. <a href="https://www.thegreattask.us/misgiving">https://www.thegreattask.us/misgiving</a></p><p><strong>Thomas:</strong> This post from Jared Spool last October was recently resurfaced to me, and it’s remarkable to see how Axial’s design team taking this to heart over the last year has dramatically improved our process. There’s still a lot more we need to do, but remembering this lesson (and expanding this to other parts of the organization as well) is key to building good products is constantly observing and talking to your customers. It’s like mom telling you every day for 18 years to wash your hands before dinner, and then you forget for a while, until a few bad colds sideline you and you realize she was onto something there. <a href="https://medium.com/@jmspool/fast-path-to-a-great-ux-increased-exposure-hours-afde796f2e43#.http0wgqs">https://medium.com/@jmspool/fast-path-to-a-great-ux-increased-exposure-hours-afde796f2e43#.http0wgqs</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec4e2df57c99" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axial-product-and-design/read-these-product-design-links-for-your-holiday-commute-ec4e2df57c99">Read These (Product design links for your 🦃 holiday commute)</a> was originally published in <a href="https://medium.com/axial-product-and-design">Axial Product and Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Read These (Product Design Links, 11/14/16)]]></title>
            <link>https://medium.com/axial-product-and-design/read-these-product-design-links-11-14-16-77ac655be8a4?source=rss-761ba31f3b9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/77ac655be8a4</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[seo]]></category>
            <dc:creator><![CDATA[Thomas Meimarides]]></dc:creator>
            <pubDate>Tue, 15 Nov 2016 22:53:09 GMT</pubDate>
            <atom:updated>2016-11-15T22:53:09.944Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the <em>first</em> of a weekly series of Product Design, Product Management, or otherwise 👍 👏 🙌 👌 🤘 links by the Axial product team: <a href="https://medium.com/u/61e9fda36826">Sarah Adams</a>, <a href="https://medium.com/u/ce303763af1d">Giff Constable</a>, <a href="https://medium.com/u/6dabbea8e895">Dan Lee</a>, <a href="https://medium.com/u/761ba31f3b9c">Thomas Meimarides</a>, &amp; <a href="https://medium.com/u/aa43a5e1ed9c">Simon Riker</a></p><p><strong>Thomas</strong>: I really liked this article from Nielsen Norman Group about bounce rate. It brings back PTSD memories of working for a marketing agency and the obsession over lowering bounce rates without considering the underlying user behavior or even acknowledging that every visitor will bounce, but if your product is successful, they’ll return, and return often.<br><a href="https://www.nngroup.com/articles/return-visits-not-bounce/"><strong>Optimize for Return Visits, not Bounce Rate</strong></a><strong><em> </em></strong><em>(by Aurora Bedford @ Nielsen Norman Group)</em></p><p><strong>Sarah:</strong> This week was eventful, to say the least. One small piece of design I kept encountering Tuesday evening was this little jittering dial on the New York Times’s infographics displaying the election forecast. I’m not the only one that found it rather stressful to watch, &amp; it generated a lot of discussion and speculation online. Here the creators of the UI explain their decisions in designing it.<br><a href="http://vis4.net/blog/posts/jittery-gauges-election-forecast/"><strong>Why We Used Jittery Gauges in Our Election Forecast</strong></a> (<em>by Gregor Aish @ vis4.net</em>)</p><p><strong>Sarah: </strong>This was such an exciting project to watch unfold. In little under a week Sougwen Chung managed to organize and create a comprehensive database of organizations representing civil rights, marginalized groups, and climate change that need support. Togetherlist is one of the most recent examples of the importance of design pattern libraries, by building off an existing language, they were able to move quickly while making something work well &amp; look good. Using tools like Pad.Riseup, Google Surveys, and Nomadlist’s UI pattern, they were able to quickly gather information and build. Already they’re working on incorporating more features.<br><a href="http://togetherlist.com/"><strong>Togetherlist</strong></a> (<em>Started by Sougwen Chung</em>)</p><p><strong>Sarah:</strong> Recently the Harvard Museum released an online catalogue of 32,000 works from their Bauhaus collection. The scope of the collection is large, and they also published an essay on the influence and history of the school. Unfortunately the site is pretty hard to navigate and the photos are disappointingly small. But it’s a great resource to have both for research and inspiration.<br><a href="http://www.harvardartmuseums.org/tour/the-bauhaus/slide/6450"><strong>Harvard Museum’s Online Bauhaus Collection</strong></a></p><p><strong>Thomas: </strong>I re-read this Medium post about designing confirmations about once a month as it pops up in various recommended lists or feeds. It’s on point, every time, and he even includes a .sketch file to download so you can cheat and reuse!<br><a href="https://uxdesign.cc/designing-confirmation-278d159723e#.m08ieccjl"><strong>Designing Confirmations</strong></a> <em>(by Andrew Coyle @ Flexport)</em></p><p>Follow for weekly link round up and other product musings. And of course, show some love.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77ac655be8a4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axial-product-and-design/read-these-product-design-links-11-14-16-77ac655be8a4">Read These (Product Design Links, 11/14/16)</a> was originally published in <a href="https://medium.com/axial-product-and-design">Axial Product and Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>