<?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 Anthony Menecola on Medium]]></title>
        <description><![CDATA[Stories by Anthony Menecola on Medium]]></description>
        <link>https://medium.com/@AnthonyMenecola?source=rss-5d3f0bf999ec------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vV2RjR3GchP3PmIPoaJbLw.jpeg</url>
            <title>Stories by Anthony Menecola on Medium</title>
            <link>https://medium.com/@AnthonyMenecola?source=rss-5d3f0bf999ec------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:49:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@AnthonyMenecola/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[UX reviews: a template for success]]></title>
            <link>https://medium.com/@AnthonyMenecola/ux-reviews-and-a-template-for-success-a0868c21d677?source=rss-5d3f0bf999ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0868c21d677</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[review]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[Anthony Menecola]]></dc:creator>
            <pubDate>Wed, 08 Sep 2021 13:48:47 GMT</pubDate>
            <atom:updated>2021-09-08T15:28:18.373Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An illustration of a computer screen accompanied by a hand holding a red pencil." src="https://cdn-images-1.medium.com/max/1024/1*W4Kf427Doeqxp-D-EfdZPg.jpeg" /><figcaption>Illustration by <a href="https://medium.com/u/cba3d4661521">Daina Lightfoot</a>.</figcaption></figure><h4>How to structure your next UX review to get actionable feedback — plus a Figma template to use</h4><p>Two fundamental aspects of working on distributed product teams are sharing context and seeking feedback on your work. In order to achieve alignment and rally the team around a common set of goals, it’s important that you structure and deliver your thoughts clearly and intentionally. This will ensure your audience gains the appropriate amount of context so they can provide you with actionable feedback.</p><p>In this article, I will share a structure that I’ve found to be useful when preparing for a UX review. There’s also a <a href="https://www.figma.com/community/file/1017156961406727571">Figma template on our Community profile</a> that accompanies this blog post to help you fully prepare for your next review.</p><h3>What is a UX review?</h3><p>A UX review is a stakeholder check-in where the team presents a recommended experience they’re looking to move forward with. This is a time to explain rationale, field any open questions, and gather specific feedback that may need to be addressed before moving forward. UX reviews differ from more traditional design reviews in that <a href="https://ux.shopify.com/the-magic-of-collaborating-across-disciplines-762e8903c6d0">stakeholders from various disciplines and teams</a> can be invited to participate and provide feedback once the team has an idea for a recommended direction.</p><p>There are many scenarios in which a team could benefit from a UX review. Perhaps the team is looking for stakeholder input on a contentious topic that has been difficult to resolve. Or, when the team is confident in their recommended approach and are looking to gut-check on their considerations and rationale. UX reviews are helpful when you are <a href="https://ux.shopify.com/theres-no-i-in-feedback-7dfae2def569">looking for specific feedback</a> for the goal you’re trying to achieve.</p><h3>How to prepare for a UX review</h3><h4>Who should be involved?</h4><p>It’s incredibly important to consider your audience when preparing for a UX review. Who in your organization is a stakeholder within your product area that you would want to provide UX feedback? Are there technical considerations which impact your UX decisions? Does your UX shift the product strategy or impact another team’s work? Your invite list should be limited to your UX team (research, content, design, FED) and key decision makers or representatives (leads or directors from UX, project management, engineering, data) from areas which may be impacted.</p><p>Try to keep the attendee list low in order to ensure everyone has a chance to provide feedback without prolonging the length of the review. Keep in mind that you can always share a recording if you are presenting via video call, and/or share action items with others after the meeting ends.</p><p>Now you know who to invite, let’s look at how to structure your UX review.</p><figure><img alt="A preview of a Figma template for UX reviews, which shows a project introduction with: project name, list of team members, and the contents of the structure, including Index, Intro, Feedback, Context, Thinking, Show, Notes, Next Steps." src="https://cdn-images-1.medium.com/max/1024/1*QY4lebfZC6G5yk444ZMFIw.png" /><figcaption>A preview of the accompanying UX Review Figma template.</figcaption></figure><h3>UX review structure</h3><h4>Introduction</h4><p>Keep this short and sweet. Think of this as an overview of who you are, the team you’re a part of, and the topic of what you’ll be covering in your review.</p><h4>Feedback</h4><p>Without being explicit about what feedback you are, and are not looking for, things can easily get off track. For instance, if the content design is still being worked on, it’s beneficial to call this out ahead of time so the feedback you receive is focused. In the event that a question gets asked that is off topic, or starts to derail the conversation, you can politely remind attendees of the areas of feedback you’re looking for and ask for that particular discussion to be continued outside of the review time.</p><h4>Context</h4><p>You are the expert in your respective domain. Try to summarize the context of <a href="https://ux.shopify.com/a-process-for-solving-workflow-design-problems-cdd1187a3d83">the problem you’re trying to solve</a> so that the audience has a general understanding without getting too granular. As an example, some useful artifacts to help aid in problem definition could include Jobs to be Done, or “How might we…” statements.</p><h4>Thinking</h4><p>Before you get into showing any specific design or flows, explain to the audience how you approached thinking about the problem. What actors were considered when designing the proposed solution? Was there any research that was conducted or consulted that supports the problem, topic, or design being discussed? Were any specific UX principles used in guiding the decision making? All of these can help set the stage for the work you will be showing.</p><h4>Show</h4><p>Once the audience has context on the problem you’re solving and you’ve explained the thinking that went into your proposed solution it’s time to show the audience your recommended solution.</p><p>It can be helpful to walkthrough an end-to-end flow before fielding any questions. This way, the audience can get an understanding of the bigger picture before diving into specific feedback about individual screens, components, or content. Focus on showing your recommended UX direction first and be prepared to speak to why you feel this is the best direction. Make sure to have your explorations nearby in case suggestions come up that you may have already explored, but aren’t in favor of. If you’re only showing a few screens or states of a component, you can simply add them to the presentation slides. If what you’re showing is more of a complex flow, you can include link(s) to a separate document or prototype.</p><h4>Notes</h4><p>This is a dedicated area where you can assign a notetaker to capture notes throughout the meeting. This will ensure you can focus on presenting and answering questions without needing to write down every question or piece of feedback that arises. These notes will help you assemble a list of action items and next steps that can be taken after the review. It will also allow you to explain why you may intentionally choose not to address certain feedback.</p><h4>Next steps</h4><p>Summarize all of the next steps that you and the team will address as part of the feedback that was received during the review. These next steps should be shared with the attendee list and any other individuals who may be interested shortly after the review. It will help level-set the audience on expectations and make sure everyone is clear on the path forward. It’s worth noting that not all feedback <em>needs</em> to be addressed. It is up to you and the team to make a judgment call on what can be actioned on and what may need more clarification or investigation.</p><h4><em>Bonus: Make it asynchronous</em></h4><p>If you work on a distributed team in various parts of the world, scheduling a time that works for everyone can be a challenge. Luckily, this structure works really well if it is pre-recorded. You could record audio and/or video of you walking the audience through the context and recommended UX direction before directing them to write their own notes and feedback in a shared document (perhaps in Figma comments, or a Google doc).</p><p>If there is a significant amount of context to be shared with the audience, it can even be helpful to record a pre-read which covers the context portion before a UX review happens. It will allow invitees to prepare for the meeting ahead of time and even come prepared with questions.</p><p>I recently did exactly this while working on the onboarding UX for <a href="https://www.shopify.com/inbox">Shopify Inbox</a>. Since there were two existing products which were coming together under one new product name, I wanted attendees to have context on the before and after experience of onboarding. This context was incredibly important for attendees, but talking about it during the UX review would’ve taken longer and taken time away from the feedback we were looking for.</p><h3>UX reviews help you become a better designer</h3><p>Practice makes progress. Over time, you will build up experience with storytelling and improve your confidence when presenting your solutions. By including attendees that have a diverse set of roles and experiences you’ll also begin to broaden your understanding of the type of feedback you receive, which will ultimately help you design better solutions for the next review.</p><p>UX reviews are a really great way to present your work, explain and defend rationale, and obtain valuable feedback from stakeholders. By structuring your thoughts in a clear and cohesive manner you will set the team and yourself up for a successful review.</p><p><em>Do you have anything to add? I’d love to know what has worked well for you when reviewing your work with others. Let me know your thoughts on </em><a href="https://twitter.com/AnthonyMenecola"><em>Twitter</em></a><em> and make sure you check out the Figma Community template!</em></p><p><a href="https://www.figma.com/community/file/1017156961406727571/UX-Review-template"><strong>View the UX Review template on Shopify’s Figma Community profile ↗</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0868c21d677" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bridging The Gap: UX/UI]]></title>
            <link>https://medium.com/@AnthonyMenecola/bridging-the-gap-ux-ui-ab511108383f?source=rss-5d3f0bf999ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab511108383f</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Anthony Menecola]]></dc:creator>
            <pubDate>Mon, 15 Aug 2016 14:01:52 GMT</pubDate>
            <atom:updated>2016-08-15T14:01:52.792Z</atom:updated>
            <content:encoded><![CDATA[<h4>Getting started with visual design</h4><p>As a Product Designer working within a consultancy it’s critical to understand the business and talk to users in order to understand their behaviors and pain points. We can then begin to ideate, validate, and iterate on solutions to specific problems that surface throughout this discovery. So what happens when it’s time to start thinking about the visual design of the UI? How do we bridge the gap between solving problems and creating a beautiful user interface?</p><blockquote>Visual design is just as much of an iterative process as the user experience. Exploration is essential to understanding what works well, and what doesn’t.</blockquote><p>Visual Design isn’t some magical dust that’s sprinkled onto wireframes hoping they grow into beautiful products. It’s a process that craves exploration in order to see how we can push the boundaries of brand colors, typography, and information hierarchy into new territories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bcjSYaf8IltIzw4Csj9j1g.png" /><figcaption>Several visual iterations for a profile card component.</figcaption></figure><p>In a recent post, fellow Pivot David Ghent recently wrote about the <a href="https://medium.com/product-labs/3-tips-for-better-visual-design-on-an-agile-team-ae4a2a712914#.7k9sqo3vm">3 Tips for better visual design on an agile team.</a> David recommends setting aside time during your week to explore visual design directions and I couldn’t agree more. By exploring visual implementations alongside the problems you are trying to solve, you will ultimately reduce the time it takes to arrive at a visual style you and the client are happy with.</p><blockquote>Defining visual styles early in a project ensures designers and developers have a baseline for using colors and typography consistently. Even when they change over time.</blockquote><p>In order to assemble a baseline of styles that developers can get started with we need to start simple. Gather a list of colors, fonts, and logos into a library to get the wheels in motion. Over time, these styles will grow to include more items such as iconography, forms and inputs, patterns, grids etc. Below are some scenarios you may find yourself in when trying to assemble these items.</p><h4><strong>Existing Brand</strong></h4><p>If the brand has an existing guidelines document you can use this as your starting point to extract the information you need to get started with visual explorations.</p><p><em>Be careful! These guides are often built by branding and marketing teams that often do not have the greatest context when it comes to building mobile or web applications. Treat them simply as a starting point. Create color combinations that have </em><a href="http://jxnblk.com/colorable/demos/text"><em>sufficient contrast</em></a><em> and define </em><a href="https://typeanything.io/"><em>type combinations</em></a><em> that scale well and create proper information hierarchy. Marketing sites are NOT web or mobile apps, and thus, it’s important for you to define your own set of guidelines.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eSgiKYU7TK4cBHCNEBEIgw.png" /><figcaption>Existing brand guidelines are a great resource for locating existing colors and type choices</figcaption></figure><h4><strong>No Guidelines — Existing Logo &amp; Website</strong></h4><p>You won’t always have the luxury of having access to existing materials so in order to get the answers you need you’ll have to get creative. You can use a color picker app or browser extension extension to pinpoint the colors and fonts used on an existing website or document. Personally, I really enjoy <a href="http://sipapp.io/">Sip by the Olá Brothers</a> (copies color code to the clipboard!) and the <a href="https://chrome.google.com/webstore/detail/whatfont/jabopobgcpjmedljpbcaablpmlmfcogm?hl=en">What Font browser extension for Chrome</a>. Otherwise, pop open your browsers web developer tool to inspect the CSS and see what colors and fonts are being used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gn6eWdWesNb7IX9k9f8c6w.png" /><figcaption>Your browsers web inspection tool can be very handy for obtaining the information you’re looking for</figcaption></figure><h4>No Existing Brand</h4><p>You may have the opportunity to make recommendations on the visual direction for the brand and product. Lucky you! There are several exercises you can run with your client to get them involved in the process.</p><p><strong>Competitive Brand Audit<br></strong>Take some time to look at the existing market and competitors to see where there is opportunity to set your product apart. Look at things like logos, color schemes, visual aesthetic and tone of voice to understand where the opportunity is for your brand and product to stand out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iPTEtxZJ9oscFFpD5Ddr9Q.png" /></figure><p><strong>Mood Boards<br></strong>By assembling a mood board of color palettes, imagery, and other visuals pertaining to your brand and posting them up in your workspace you will allow the team to gain visibility into the aesthetic direction you’re aiming for. I recommend using a tool like <a href="https://niice.co/">niice.co</a> or <a href="https://www.pinterest.com/">Pinterest</a> to aggregate visual search results from multiple sources, but you could always keep it simple and use Google.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ST0ipluQoJSUBKGxaW087g.jpeg" /></figure><p><strong>Visual Style Research<br></strong>Take some time to get inspired. There are a lot of <a href="https://www.lightningdesignsystem.com/">great</a> <a href="http://rizzo.lonelyplanet.com/styleguide/design-elements/colours">products</a> out there that have <a href="https://material.google.com/">beautifully</a> <a href="http://airbnb.design/building-a-visual-language/">thought out</a> <a href="http://ux.mailchimp.com/patterns/">visual</a> <a href="https://material.google.com/">design languages</a>. Explore what’s been done and assess what could work well for your product. At the end of the day you will have to figure out what works for you and your team and why it works. Don’t be afraid to explore multiple directions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r5fRFlQuuU1uWQdSWms0DA.png" /></figure><h4>Managing Design Debt</h4><p>As you begin to explore the endless possibilities for visual design direction you will inevitably end up with a lot of discarded explorations within your files known as <a href="https://austinknight.com/writing/design-debt/">design debt</a>. These explorations, while incredibly important, can begin to clutter the overarching visual direction for your product. Keep an active page or art board for ideation where you can play around while allowing the rest of your file to remain clean and focused.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qieWWb0UKhvIjiAMQttaWg.png" /><figcaption>Create art boards within your style guide for color palettes, typography, form fields</figcaption></figure><p>The thought of visual design can be daunting when all your focus is on solving the problems pertaining to the product. By starting the discovery early and iterating often you’ll allow the necessary time to explore and see what works well for your product. Your pattern library is going to grow as you’re solving different problems over multiple user scenarios. Keep things as tidy as possible and take a step back every once and a while to make sure you’re remaining consistent with your design decisions. Your team will thank you for it.</p><blockquote>Do you work at a consultancy, agency, or on a internal product team? I’d love to hear what has worked well for you and your team! Leave a comment or <a href="https://twitter.com/AnthonyMenecola">hit me up on Twitter</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab511108383f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving from Photoshop, to Sketch, and back.]]></title>
            <link>https://medium.com/product-labs/moving-from-photoshop-to-sketch-and-back-b27fbd1bb0c6?source=rss-5d3f0bf999ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/b27fbd1bb0c6</guid>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[photoshop]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Anthony Menecola]]></dc:creator>
            <pubDate>Wed, 08 Apr 2015 16:40:36 GMT</pubDate>
            <atom:updated>2017-05-01T20:23:07.557Z</atom:updated>
            <content:encoded><![CDATA[<p>As designers we are constantly switching between tools and adding plugins/add-ons/libraries to our applications to help supercharge our workflow and efficiency. So what happens when we introduce yet another application into the mix?</p><p>Since its release, I’ve been a big fan of <a href="http://bohemiancoding.com/sketch/">Bohemian Coding’s Sketch 3</a>. It has some incredible features that, as a Product Designer, allow me to work more efficiently. However, things weren’t always this way. Like many of my peers I was daunted with the idea of another tool I had to familiarize myself with. Would it really be worth it in the end? How steep would the learning curve be? Would this shiny new tool replace the ones I’ve been using for years? The answer is no. Not completely. In this article, I hope to propose a few ways you can customize your Sketch workflow to help make switching between applications a breeze.</p><p>While Sketch has been my “go-to” tool over the past few months, I still find myself inside of Photoshop and Illustrator multiple times throughout any given day. One of the biggest frustrations when I first started working with Sketch was that all of the keyboard commands and shortcuts that I was already familiar with were completely different. So, I changed them to suit my needs.</p><p>It’s incredibly easy to create your own application shortcuts within OSX. For a nice breakdown and additional shortcut recommendations head on over to <a href="http://sketchshortcuts.com/">http://sketchshortcuts.com/</a></p><p>Below are some of the main shortcuts that I’ve set up to make switching between Photoshop, Illustrator and Sketch a breeze.</p><p><em>Note – These are my own personal preferences that I’ve found useful. Feel free to create the shortcuts that you use most in order to maximize efficiency on your own workflow.</em></p><h3>LAYOUT</h3><h4>⌘ + ‘</h4><p>Show/Hide Grid</p><h4>⌘ + ;</h4><p>Show/Hide Smart Guides</p><h4>⌘ + R</h4><p>Show/Hide Rulers</p><h4>⌘ + ⇧ + }</h4><p>Move To Front</p><h4>⌘ + }</h4><p>Forward</p><h4>⌘ + {</h4><p>Backward</p><h4>⌘ + ⇧ + {</h4><p>Move To Back</p><h3><strong>TYPE</strong></h3><h4>⌥ + <strong>←</strong></h4><p>Tighten</p><h4>⌥ + <strong>→</strong></h4><p>Loosen</p><h4>⌘ + ⇧ + &gt;</h4><p>Bigger</p><h4>⌘ + ⇧ + &lt;</h4><p>Smaller</p><h3><strong>BONUS</strong></h3><h4>⌘ + ⌥ + <strong>↓</strong></h4><p>Collapse Artboards and Groups</p><p>While many of these suggestions will help streamline your workflow between apps, it can be a bit of a pain when switching computers or pair designing with a colleague that has their own preferences. In the long run, if you can spare the 10–15min setup time it will make working between these applications much smoother.</p><p><em>Have anything to add? I’d love to hear how you’ve streamlined your workflow between applications. Hit me up on Twitter:</em></p><h4><a href="https://twitter.com/AnthonyMenecola">@anthonymenecola</a></h4><p>FURTHER READING</p><h4><a href="https://medium.com/sketch-app/making-the-switch-a5e73642c4c3">Making the Switch</a></h4><p>By: <a href="https://twitter.com/KounterB">@KounterB</a></p><h4><a href="https://medium.com/sketch-app/mastering-the-bezier-curve-in-sketch-4da8fdf0dbbb">Mastering the Bézier Curve in Sketch</a></h4><p>By: <a href="https://twitter.com/pnowelldesign">@pnowelldesign</a></p><h4><a href="https://medium.com/@lorenzvs/saving-time-in-sketch-7042142c8a8e">Saving time in Sketch</a></h4><p>By: <a href="https://twitter.com/dearlorenz">@dearlorenz</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b27fbd1bb0c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-labs/moving-from-photoshop-to-sketch-and-back-b27fbd1bb0c6">Moving from Photoshop, to Sketch, and back.</a> was originally published in <a href="https://medium.com/product-labs">Product Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>