<?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 Lance Weisser on Medium]]></title>
        <description><![CDATA[Stories by Lance Weisser on Medium]]></description>
        <link>https://medium.com/@Lanceweisser?source=rss-b00d0f02a9cf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vcRoqZSgjY8G7Yb0tqbkdQ@2x.jpeg</url>
            <title>Stories by Lance Weisser on Medium</title>
            <link>https://medium.com/@Lanceweisser?source=rss-b00d0f02a9cf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:39:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Lanceweisser/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[You Didn’t Hire Me]]></title>
            <link>https://medium.com/design-bootcamp/you-didnt-hire-me-34845177d30a?source=rss-b00d0f02a9cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/34845177d30a</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[Lance Weisser]]></dc:creator>
            <pubDate>Mon, 24 Jul 2023 23:30:30 GMT</pubDate>
            <atom:updated>2025-02-20T01:14:29.628Z</atom:updated>
            <content:encoded><![CDATA[<p>The highs and lows of my year-long job-hunting experience</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RVBmBLHufYPn1MZriPZTLw.png" /><figcaption>Tell me Why</figcaption></figure><p>In May of 2018, I moved back to The San Francisco Bay Area after spending ~3 years in Thailand. A lot had changed since I left in 2015. Bootcamps had been cranking out Jr Designers by the thousands, and Sr Designers were no longer in demand. That year I applied for hundreds, if not thousands of jobs. I’ll share a few of my notable experiences, good and bad, and hopefully make the case for a dignified and humane approach to recruiting, interviewing, and hiring moving forward.</p><h3>Ain’t nothing but a heartache</h3><p>In October of 2018, I applied for a job, and after many rounds of remote interviews, in-person interviews, design exercises, and plenty of positivity shared to my face, the company ghosted me, later replying to an email I sent with this: “Our hiring decisions are always group decisions — everybody in the team had a say and vote.” I won’t get into why that is an awful policy here, but that was not even the worst part. A month later I happened to open the Sketch file containing the design exercise I shared with them and one of their Jr Designers was active in the file. This made me really upset since I already felt uncomfortable doing the design exercise in which they specifically asked me to design a concept directly related to their value proposition. Once I had calmed down a bit, I sent an email to their Sr Designer letting him know what happened, how unethical it felt, and that I hoped I wouldn’t see any of my work show up in their product. He apologized and assured me it wouldn’t but even then, I still shake my head at the nerve of those people and have resolved to never do a take-home design exercise again.</p><h3>Tell me Why</h3><p>In January of 2019, I received an email from a recruiter at AWS, a wonderful person named Lowell. An incredibly tenacious recruiter, she set me up with no less than 3 opportunities at AWS. The first one was meant to be onsite in Seattle which I had understood to be remote. The second was an onsite role in Virginia which they had opened up to remote candidates due to the lack of candidates in the area. This role seemed to be a good fit, and after a couple of great remote interviews, they offered to fly me up to Seattle for an onsite at AWS HQ where I would go through the infamous “Amazon Loop Interview”.</p><p>Leading up to the trip I spent more time and energy in prepping and research than I had ever done for an interview. I watched the youtube videos, wrote up 4–5 case studies using the STAR method to map out the Situation, Task, Action, and Results, and generally sweated the details. The week of my interview I felt confident and prepared to bring my best self to the interview. To their credit, Amazon treated me really well. They put me up in a 5-star hotel within walking distance of campus and gave me a per diem for food and entertainment.</p><p>The morning after I arrived I walked to the campus, picked up my badge, and was escorted to the conference room where the interviews would be held. Throughout the whole process, I was treated with respect and although I was pretty nervous, the feedback was positive and direct. Most of the interviews were based on the “Tell me about a time when…” questions which prompted me to share stories about conflicts I had faced in my career and what the outcomes were. One of the interviews that I felt the worst about was “<a href="https://thebarraiser.medium.com/the-bar-raiser-interview-getting-a-job-at-amazon-ab99aedb7490">The Bar Raiser</a>”, a whiteboard design exercise with a Sr Designer in which he gave me prompts for a fictional product to see how I would approach designing it. This was fun and nerve-wracking at the same time and though I felt like I stumbled in my approach to the exercise, apparently, I did well.</p><p>The outcome was bittersweet. I passed the Loop, which was a pretty significant accomplishment since ~1/5 people that Amazon interviews pass it. They then informed me that while they were inclined to offer me the position, at the last minute they had found a local candidate with basically the same qualifications and abilities as me which was ultimately why they chose to go with someone local.</p><p>Why was this still a good experience even though I didn’t get hired?</p><ul><li>I was treated with dignity and respect</li><li>I received generous and hospitable accommodation</li><li>I did the hard work to prepare and passed a pretty high bar in the industry. This gave me some much-needed confidence in myself at a time when I really needed it</li><li>I was given explicit feedback regarding my qualifications, ability, and experience, and ultimately, explicit feedback on why I was not offered the position</li></ul><h3>Ain’t Nothin but a Mistake</h3><p>Today, I received an email response from a really cool company helping Pharmacists spend less time dealing with Insurance paperwork and more time with patients.</p><p>About 14 hours ago I tapped the Easy Apply button on a Principal Design position they were offering, a position that (upon a second glance) I am uniquely well positioned for, having worked directly on Kroger’s Pharmacy software a year prior. About 2 hours ago I received this email from the recruiter: (I’ve added my own comments inline as pull quotes)</p><p>Dear Lance,</p><p>Thank you so much for your interest in our Principal UX Architect/Designer position and sincere apologies for the delay in responding. I’ve reviewed your application and there isn’t enough of a match with our specific needs to continue the process at this time. We have received significant interest and while I’d like to provide specific feedback, I sadly can’t.</p><blockquote><strong><em>Ok, clear response here, nothing new. But wait, there’s more…</em></strong></blockquote><p>This said, I’m personally all about helping others. A few overarching notes that might help you with other applications. Take these suggestions as merely suggestions; the last thing I want to do is be perceived as preaching. I also want to decrease undue expectations (and potential anxieties) that you might get an interview when your application simply has no chance.</p><blockquote><strong><em>Love the framing in this paragraph 👆🏼 a little harsh and very true.</em></strong></blockquote><ul><li>I review many, many, many resumes and cover letters every day. I’m old school so no keyword searches or AI. I’m looking for *very* specific information about you, using the job description (JD) as THE critical first screen. The more you can quickly check off key concepts from the JD, the better the chances you’ll make it past this (crucial) step. Addressing the requirements of the JD upfront in your cover (versus sharing everything you’ve done and your technical knowledge) intuitively makes sense in this context. <strong>Make your content relevant to the description and don’t assume I know all your tribal vernacular.</strong></li></ul><blockquote><strong><em>A lot to unpack here.</em></strong></blockquote><blockquote><strong><em>1. Recruiters review a ton of resumes and cover letters</em></strong></blockquote><blockquote><strong><em>2. They are looking for super specific information and concepts in your cover letter and resume directly from the Job Description requirements</em></strong></blockquote><blockquote><strong><em>3. We should not assume they know what we are talking about when we refer to our qualifications that are not specifically mentioned in the JD</em></strong></blockquote><p>For example: this JD starts with a requirement for a recent track record of executing <strong>end-to-end </strong>deployments of a meaningful product to a cohort of existing users and significant experience in all major facets of HCD.</p><p>Merely mentioning these experiences in your cover will undoubtedly peak my interest. If you have UX or product lead start up or health care experience, mention that. Doesn’t have to be lengthy either. Checking off these requirements will heighten my curiosity, reveal you’ve actually read the JD, and your application will undoubtedly get a thorough review (versus a skim), <strong>which is what you want</strong>.</p><p>And if you don’t meet the main requirements, you may not want to apply. <strong>Someone else does</strong> and all you’re doing is creating more work for both of us, expending energies of various sorts, and again, setting an unrealistic expectation you might land a gig.</p><p><strong>Net sum: Helping me, helps you. You want me as your advocate!</strong></p><blockquote><strong><em>This is where I started to feel a bit embarrased. I failed to read the job description, failed to even include a cover letter, and missed the opportunity to highlight relevant information in a cover letter about myself that would have certainly caused some interest.</em></strong></blockquote><ul><li>Not saying you did this, but please make sure you reference the right role and employer in your cover letters. I tend to forgive however many recruiters and hiring managers, per the below, are looking for ANY reason to ding you.</li></ul><p>- Including a one or two line description of your employers can be EXTREMELY helpful to Mr. Ignorant here. Is it a start up? If so, how many rounds of funding? An enterprise and if so, what business unit? A service provider? What industry? Who were your customers? Without this information, I’m lost and I don’t have the bandwidth to research unless I’m really interested → at this stage, given the application load, recruiters typically are looking more so for reasons to pass on you and move to the next application to finish that task than to promote you! And you want to be promoted…</p><p>- We like numbers.. impact. How did your work impact metrics? The actual numbers aren’t as important (and they should be supportable!) as the overall mindset we’re looking for.</p><p>- I love learning how people spend their “Life” time. I’m hiring humans not automatons. The more human you can make your presentation, the better you’ll do…at least with this outlier who still reviews every line.</p><p>Remember, it’s all about making it past this first screen… <strong>The amount of time you spend customizing your cover (and really assessing if you are good fit) will be offset by the satisfaction of knowing you actually have a shot.</strong></p><blockquote><strong><em>Excellent points about adding context to the employers, including stage of company, relevant industry, and who the customers were. I’ll be looking closely at my resume to make some potential tweaks in how I describe companies.</em></strong></blockquote><blockquote><strong><em>The idea of including impact and numbers is a great one and something I try to do in all of my profiles. As far as highlighting my humanity, I personally find this hard to do for some reason, but it’s a good callout nonetheless.</em></strong></blockquote><blockquote><strong><em>My most significant takeaway in this entire response is probably this: Spend time customizing your cover letter.</em></strong></blockquote><p>And note: your changes may not yield any game-changing results though I can confidently say you’ll definitely get more in-depth reviews by recruiters, which is what you want!</p><p>I wish you every success with your job search and thank you again for your interest in Prescriber Point!</p><p>Best of luck [Redacted]</p><p>Wow! What a great response! And in a template too! This becomes a solid bar to set for those who are going through hundreds of applications and realistically don’t have time or bandwidth to respond to everyone with meaningful feedback as to why they didn’t get hired. Basically, all the recruiter had to do was use a base template and customize one for each position they are recruiting for.</p><p>I also felt kind of dumb reading this because they were absolutely right that I wasted their time and energy by applying without even addressing the basics they specifically asked for in the JD. I made a mistake but also learned from it!</p><h3>I never want to hear you say</h3><p>I give up. That’s the one thing I never want to hear you say. One of the things that sucks the most about hunting for a job is when (unlike my own behavior) you put in the work, write a great cover letter, tick all the boxes, and still get nothing back. How you rationalize the lack of signal is critical to staying positive in your search and avoiding the natural inclination to become desperate. Here are 4 boxes to tick on your way to your dream job:</p><p>1. Is your resume optimized for automated screeners? If not, try creating one in Google Docs and exporting it as a PDF. The additional markup Google provides in the form of sections will help streamline this part of the process and increase your odds of getting your application into the right hands in a format that people can actually consume.</p><p>2. Use Chat GPT for some cover letter and resume inspiration. This is especially helpful when working on summarizing your experiences and qualifications as they relate to a specific job.</p><p>For cover letters try a prompt like this:</p><blockquote>I am going to paste in my resume, then in the following chat message I’ll paste in a job description. Once you have received those two documents, please write a custom cover letter for me that will optimize my chances of getting an interview</blockquote><p>This can provide an output that is super close to what a recruiter might be looking for and if nothing else, can save you a lot of time trying to get phrasing and relevance dialed in.</p><p>For Resume customization, this prompt takes a very similar approach:</p><blockquote>I am going to paste in my resume, then in the following chat message I’ll paste in a job description. Once you have received those two documents, please provide some feedback and guidance on how I might customize my resume in order to optimize the chances of getting an interview for the position.</blockquote><p>This also results in some very clear and practical feedback that should be helpful once you start to narrow down your list to the jobs you are really serious about applying for.</p><p>3. Reach out to your network. This is a tough one for some of us since it may take some exercise in transparency and humility to reach out to peers, friends, or former colleagues, but I guarantee you it will be worth it. It’s a truism that most people want to help other people, especially those they care about. So get that Resume, portfolio, and LinkedIn profile out there in a DM. Something like this might work:</p><blockquote>Hey there, I am actively looking for a job right now and was wondering if you might be open to taking a look at my resume and providing me with some feedback on how I might dial it in. I would be glad to buy you a beer or coffee as thanks if you were willing!</blockquote><p>4. <a href="https://chengeer.medium.com/find-your-perfect-coach-485d1e0dbeb8">Hire a coach</a>. As a caveat, I have never personally done this myself but I have seen a lot of solid results from job coaches and executive coaches. Some even take a pay-if-you-get-hired approach which is pretty cool for those of us who have been unemployed for a while.</p><h3>I want it that way</h3><p>For those of you who were curious about how my story was resolved, the same week I heard back from Amazon, an agency in San Francisco called Yeti reached out to me and ultimately ended up hiring me as a Lead UX designer!</p><p>So why did I write this article, and what’s next? <br>Well, I’m glad you asked because I’m working on building a small application called “Tell me Why”, which will try to fill the knowledge gap between the application process and being passed on, which I hope will be helpful to those of us left wondering why we didn’t get a job.</p><p>Good luck with your job search!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34845177d30a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/you-didnt-hire-me-34845177d30a">You Didn’t Hire Me</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to recruit, interview, onboard, and retain great UX talent]]></title>
            <link>https://medium.com/design-bootcamp/how-to-recruit-interview-onboard-and-retain-great-ux-talent-62da8c959651?source=rss-b00d0f02a9cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/62da8c959651</guid>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Lance Weisser]]></dc:creator>
            <pubDate>Wed, 01 Feb 2023 05:05:53 GMT</pubDate>
            <atom:updated>2025-12-09T19:12:30.128Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Designer standing at a whiteboard thinking about how a flow is going to work within an app" src="https://cdn-images-1.medium.com/max/1024/1*sRK1eJ4TX6Ff96WvWCD3FA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@wocintechchat?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Christina</a> on <a href="https://unsplash.com/s/photos/Designer?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This article is based on my 10+ years of navigating the tech scene, receiving an estimated 1M emails from recruiters, and how I imagine things might be better.</p><h3>Recruiting</h3><p>During tech boom cycles it’s not odd for Senior Designers to get 5–10 cold emails a day from recruiters. If I could give some advice to every recruiter looking to spark some interest, here’s what I would tell them to include in these messages:</p><ol><li>Provide the <strong>name of the company</strong> you are recruiting for. Some designers (myself included) have interviewed at a fair amount of companies. Assume we have already interviewed at the company you are working for. Also, be upfront if you are an agency or internal recruiter so we know who we are talking to and what to expect.</li><li><strong>Salary Range</strong>. We all know this is negotiable but it is a nice way to allow the designer to opt-in to negotiating within and potentially a bit above that range. The bottom end of the range should be targeting the most Jr. person you would hire, and the top end, most Sr.</li><li><strong>Job description. </strong>This is an often overlooked aspect of recruiting which can result in some ridiculous requirements such as “12 Years of Figma Experience” even though Figma was founded 11 years ago. Daniel Burka hits a home run with this great article on <a href="https://library.gv.com/how-to-write-a-great-job-description-for-a-designer-9688c5bf1199">writing great job descriptions</a>.</li><li><strong>Benefits.</strong> This one is pretty simple, if it’s a position for a Contractor or DAO just let them know upfront.</li><li><strong>Tools.</strong> If this is for a founding design position, consider leaving it open to the designer. If there is an existing design system, ask for expertise in the use of that tool. Figma makes this pretty easy at the moment since it does pretty much everything.</li></ol><h3>Interviewing</h3><p>Interviewing is the single most inefficient process I have seen in my 10+ years in the tech world. Everyone seems to have their own approach which is generally a cocktail of confirmation bias, ignorance, and almost 0 data to support hiring decisions or outcomes.</p><ol><li><strong>Don’t</strong> <strong>ask</strong> someone to do an <strong>unpaid design exercise</strong>. Daniel Burka wrote a timeless article on why <a href="https://medium.com/startup-grind/8ac6affd73a7">here</a>.</li><li>A better approach is to ask the candidate to bring 1–3 project <strong>case studies</strong> (<em>1–2 for a more Jr designer, up to 3 for a more Sr Designer</em>) showing how they improved an experience on an existing product, and/or took something from 0–100 for a new product. Encourage them to bring something as relevant to your business as possible and ask them to provide their Role, Task, and Outcome of the project before they present.</li><li><strong>Process vs. Approach.</strong> A lot of hiring managers focus too much on process. Although the process is very important, being able to choose a different approach for each project is more valuable than blindly following a strict but unnecessary process that is irrelevant to the context.</li><li>Give the designer the most specific insights possible regarding the <strong>design-shaped challenges</strong> you are hiring a designer to solve. Then ask them how they have tackled similar problems in their past experience, or learned how to do so in the context of training or education.</li><li>Please, stop evaluating Product Designers and UX Designers like they are Visual Designers. <a href="https://medium.com/u/33ffad61d7c7">Tait Wayland</a> knocks it out of the park with this <a href="https://uxdesign.cc/stop-evaluating-product-designers-like-were-visual-designers-a470cff49990">great article</a> on the topic.</li></ol><p>Some general thoughts: Be transparent about the job you are hiring for and the impact you’d like to see the new hire make. Don’t ask the designer to do anything unethical in the interview process. Focus on case studies and actual outcomes over their educational background, who they know, or what they look like. Look at their Linkedin before cold emailing them. I can’t tell you how often I’ve received emails for Dev positions 😖.</p><h3>Hiring &amp; Onboarding</h3><p>Great! You found a designer! Now how do you get them to stick around?</p><ol><li>Don’t take forever to make a hiring decision</li><li>Make an offer in writing by email along with the job description</li><li>If at all possible, give them more money than they are expecting</li><li>Find out when they can start and plan out in detail how they will get their machine and get logged on to it.</li><li>Set them up with an email before their start date and send access information to the email address they provided during the recruiting process so they can log into their machine when they get it</li><li>If possible, find out what tools they need and have them pre-installed on their machine with access to previous design assets and research available to them. (I have never seen this happen, it would be huge)</li><li>Give expectations regarding what they should accomplish in their first 30/60/90 days</li><li>Revisit Step 3 from Interviewing. Ask the question: “Do you have access to the tools and resources you need to address the design challenges we hired you to solve?”</li><li>Provide them access to the Stakeholders and Representative Users they’ll need to better understand the specifics of the challenges they are up against. Ask them to present their findings, and listen when they do.</li><li>Pair them with the person who has the deepest level of insight into the product market, the representative users and their needs, the business stakeholders and their needs, and finally the technical constraints involved. This is usually a Product Owner but could also be a Director of Product or even a C-level person in a smaller company.</li></ol><h3>Retaining</h3><ol><li>Make sure there is an established cadence of understanding/discovery, prototyping, testing, iterating, testing again, shipping, measuring, iterating, and shipping again. If something happens that changes market conditions, your organization should be open to going back to the understanding/discovery phase.</li><li>A weekly/monthly/yearly cadence should include regular touchpoints with Product Owners, Design Critiques with other Designers, Technical Feasibility meetings with Developers, User Testing results with Stakeholders, and Design implementation reviews with Developers. They should also get a schedule of standups, 1:1s, and a clear expectation for reviews/raises.</li><li><strong>Regular communication</strong> regarding step 3 from the interview. Ask the question: “How do you feel you have addressed the design challenges so far? And, “Do you have access to the tools and resources you need to continue addressing them?” Follow-up question: “Do you need a new challenge?”</li><li>Provide your designers with <strong>opportunities to learn and grow</strong>. Not long after I was hired into my current role I asked my company if they would pay for my Ondeck Design Fellowship and they did! Not only that but just the other day I told my practice manager I wanted to improve my visual design skills and he just approved an expense for me to enroll in Dive Club’s Become a visual trendsetter course by <a href="https://medium.com/u/2108f789ab44">Fons Mans</a>! Huge Ws right here.</li></ol><p>Depending on their personality and temperament, some designers will be looking for new challenges on a regular basis. Others may be looking to iterate on one product over time, dialing it into perfection. Some may want to do both, working on more than one product or feature in parallel. Understanding what your designers are looking to do and positioning them in the organization appropriately is a huge opportunity that I rarely see companies thinking through.</p><p>Hey, thanks for reading! Hopefully, this is a helpful and informative article for those of you building a design presence at your companies. Please let me know if there was anything especially noteworthy or informative with some claps and a follow! If you have any questions feel free to hit me up on Twitter using @lanceweisser</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62da8c959651" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-to-recruit-interview-onboard-and-retain-great-ux-talent-62da8c959651">How to recruit, interview, onboard, and retain great UX talent</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recognition vs. recall]]></title>
            <link>https://medium.com/design-bootcamp/recognition-vs-recall-2944e26ed1b2?source=rss-b00d0f02a9cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/2944e26ed1b2</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[heuristics]]></category>
            <dc:creator><![CDATA[Lance Weisser]]></dc:creator>
            <pubDate>Fri, 30 Dec 2022 06:00:50 GMT</pubDate>
            <atom:updated>2025-06-14T12:39:42.777Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A pixelized representation of the famous painting, The Son of Man, 1946 by Rene Magritte. A man wearing a bowler hat with an apple in front of his face." src="https://cdn-images-1.medium.com/max/1024/1*QNVpR3sFGfcsLGptLUjNWA.png" /><figcaption>Photo by <a href="https://unsplash.com/@simonppt?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">SIMON LEE</a> on <a href="https://unsplash.com/photos/Ee8TPGyrpmk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>Mobile recipe sites suck.</h4><p>Most recipe sites on the internet have tons of ads at the top of the screen, followed by a lengthy list of ingredients and measurements. The slightly better-designed sites have a button that allows you to create or share a grocery list of all the ingredients, and the really good ones even allow you to share the amounts needed. <br>Yet even with great ingredient management comes a certain level of complexity that our brains are just not optimized to comprehend.</p><p>My main beef 😫 with these sites is this:</p><figure><img alt="A screenshot of a step by step list of directions for a recipe on a mobile recipe site." src="https://cdn-images-1.medium.com/max/1024/1*uGNe9IuhEKD3-WGlKlHvUA.png" /><figcaption>Screenshot of the directions section on a mobile recipe site</figcaption></figure><p>When I get to the instructions they never list the amount of the ingredients to mix in at the most crucial second that you need them. I then invariably find myself scrolling all the way back up searching for the ingredient list. Naturally, I scroll up too far and hit the wall of ads, then scroll back down to find that the recipe called for 1 tsp. of paprika, not in fact one tablespoon.</p><p>Meanwhile, my onions have gone from being nicely caramelized to sadly blackened. Oof.</p><h3><strong>Miller’s Law</strong></h3><p>Why did this happen? Well, there is some science involved and it starts with a guy named George Miller back in 1956. In what came to be known as <a href="https://lawsofux.com/millers-law/">Miller’s Law</a>, he found that 7 ± 2 was the number of items we could hold in our short-term memory at any given time. Recent studies show this number has most likely dropped to the 5 ± 2 range as our attention spans have become shorter over time.</p><h3><strong>Recognition Vs. Recall</strong></h3><p>Pairing Miller’s Law with Nielsen Norman’s <a href="https://www.nngroup.com/articles/recognition-and-recall/">Recognition vs Recall Heuristic</a> provides some key insights into why I couldn’t remember how much paprika to add.</p><p>When I first saw paprika in the list of ingredients I <em>recognized</em> it as a spice we had on hand and even pulled it out of our spice drawer.</p><p>The problem was <em>recalling</em> the quantity the recipe called for after gathering 7 other ingredients and sautéing the onions.</p><p>In conclusion, the great opportunity for these recipe sites and any other site with complex information that users need just in time is to show the amount needed in line with the directions. That way I could have glanced over at them –and rather than recalling the amount– I could recognize the 1 teaspoon unit of measure, reach for the paprika with one hand, grab the measuring spoon with the other, and measure it right into the pan. Who knew quick access to ingredient measurements would result in perfectly caramelized onions and a happy family?</p><p>You might imagine other scenarios in which this approach would be advantageous. I’d love to hear about them in the comments!</p><p>Meanwhile, if you are interested in reading more about Heuristics, check out this Medium article I wrote on <a href="https://medium.com/user-experience-design-1/a-quicker-heuristic-analysis-589cb8a6561a">A Quicker Heuristic Analysis</a>.<br>Enjoy!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2944e26ed1b2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/recognition-vs-recall-2944e26ed1b2">Recognition vs. recall</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A quicker heuristic analysis]]></title>
            <link>https://uxdesign.cc/a-quicker-heuristic-analysis-589cb8a6561a?source=rss-b00d0f02a9cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/589cb8a6561a</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[heuristic-evaluation]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[heuristics]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Lance Weisser]]></dc:creator>
            <pubDate>Thu, 24 Jan 2019 00:49:13 GMT</pubDate>
            <atom:updated>2020-04-05T07:40:03.574Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>Don Norman’s 7 Stages of Action and Jakob Nielsen’s classic 10 point evaluation condensed into a potent 5 point product design review.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nUKOQNrUNIvKto9rDIkf7g.png" /><figcaption>5 point heuristic analysis</figcaption></figure><p>If you have ever done a full 10 point heuristic analysis as The Nielsen Norman Group recommends it, you know how long it can take to complete a full analysis and present the findings. While the results of this approach are comprehensive and powerful, sometimes we don’t need all ten. In fact, I think we can expose <em>more</em> crucial violations <em>quicker</em> if we cut the number of steps in half.</p><p>While reading Don Norman’s perennial Design of Everyday Things many years ago, I was absolutely floored by the simplicity presented by the following questions he formulated in <a href="https://en.wikipedia.org/wiki/Seven_stages_of_action">The Seven Stages of Action</a> and the profound implications they present when examined thoroughly…</p><p>1. What do I want to accomplish?<br>2. What are the alternative action sequences?<br>3. What action can I do now?<br>4. How do I do it?<br>5. What happened?<br>6. What does it mean?<br>7. Is this okay? Have I accomplished my goal?</p><p><em>Excerpt From: Don Norman. “The Design of Everyday Things.” iBooks.</em></p><p>After a couple of years of studying and putting into practice Don’s seven stages of action and seven fundamentals of design along with <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">Jakob Nielsen’s ten heuristics</a>, I began asking myself, “How might we create a shortcut to a full Heuristic Evaluation by reframing the test in light of its underlying core design fundamentals?” I then started working on remixing and reducing the twenty-four stages, fundamentals and heuristics into a 5 point analysis that has been incredibly helpful for me when analyzing existing applications for heuristic violations and usability issues.</p><p>I have added two examples to the evaluation below to get you started and an email link further down which you can use to request a template of the evaluation for later use. Enjoy!</p><h3>5 Point Heuristic Analysis</h3><p>January 10th, 2018</p><h3>#1. Where am I?</h3><p>Heuristics referenced include; #3 User Control and Freedom &amp; #1 Visibility of system status</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eAXtkwjzoZANn0E-6qsA6A.png" /><figcaption>Google Maps interface</figcaption></figure><h4>How might I know where I am?</h4><ul><li>Is there an active navigation element and label visible?</li><li>If the navigation model follows an unconventional design pattern, does it still provide an explicit enough conceptual model for a representative user to get a sense of where they are in relation to other areas of the application?</li><li>Is the system accessible to people with disabilities?</li></ul><p>In the example of the Google Maps interface above, Google is literally showing me where I am physically located and also showing me where I am in relation to other sections of the application by highlighting the Explore icon and text label in blue. Where this way-finding pattern might break down in practice is when a user has difficulty distinguishing colors (Up to 5% of all male users is a stat suggested by some publications). So in our analysis, this interface would get plus points for navigation, layout, conventionality and conceptual model and get dinged for accessibility.</p><p>One reason why this analysis is so powerful is that (like <a href="https://lawsofux.com/occams-razor.html">Occam’s Razor</a>) it immediately points us towards what might be the single most crucial heuristic violation/action item on this particular screen.</p><blockquote>I would recommend that Google add a visual indicator to the active icon such as an underline, arrow, filled icon or dot which would give a colorblind user an additional means of identifying which element is active without being forced to rely on color.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jB08qzP7MoqL_va4lq3ujg.png" /><figcaption>Monochromatic mockup of what the recommended changes might look like in this scenario</figcaption></figure><h3>#2. What can be done here?</h3><p>Heuristics referenced include; #6 — Recognition rather than recall &amp; #2 — Match between system and the real world</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c5B4rFRMEtDw7EVWus6VnA.png" /><figcaption>Thumbtack home page</figcaption></figure><h4>How might I know what can be done here?</h4><ul><li>Are options available and visible to the user?</li><li>Are signifiers present that indicates the ability of a user to engage with them?</li><li>Are the next steps a user should take presented in a conventional manner that they will recognize?</li></ul><p>In the example of Thumbtack’s home page shown above, the options are so well defined and laid out, I can’t find anything other than good to say about it. The logotype in the top left clearly tells me where I am, the bold heading tells me what the site is for, the menu in the top right describes three other things I might want to do here with elegantly simple phrases like: “Join as a pro”. As my eye continues to travel down the page I see another very clear piece of text on an elevated search bar that simply asks: “What’s on your todo list?” with a bold weight zipcode next to it (most likely fed by a reverse IP lookup) and a tasteful blue button/icon signifier next to that. I also love the conventional “help-text-esque” placement of a small play button icon with a label that reads “See how it works”, which of course, plays an explainer video as expected. Just when you thought the page couldn’t get any better, you see a row of five beautifully designed icons (incidentally nailing <a href="https://lawsofux.com/millers-law">Miller’s law</a> of 7 + or -2) with labels indicating what are most likely the five most popular categories of services in my area or the services that provide the highest business value to Thumbtack. Notice the way the container for the five options sits on the seam of a new div with a grey background which gives the scent of additional information below the fold rather than using some awful indicator like an <a href="https://uxdesign.cc/dear-web-designer-let-s-stop-breaking-the-affordance-of-scrolling-fe8bf258df7b">animated arrow pointing downward</a>. Watch and learn my friends.</p><p>The only tiniest of criticisms I could offer here would be that the contrast of the grey text in the top right corner (15.23:1) is not AAA WCAG accessible. If they darkened the color to #505050 they would be good to go.</p><p>So overall, the options are clearly defined, signifiers give strong indications, and the next steps are clearly outlined! This homepage gets 4.75 stars in my book. Well done <a href="https://medium.com/u/6ef9fd7547a0">Thumbtack Design</a> team!</p><p>As a bonus round, I put a 10px Gaussian blur on the screenshot to see how the <a href="https://www.leemunroe.com/visual-hierarchy/">visual hierarchy</a> holds up and I would say it is on point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X21DO7x60WQ-a6vhWDf8Hg.png" /><figcaption>Blurred Thumbtack homepage screenshot</figcaption></figure><h3>#3. What will happen if I do it?</h3><p>Heuristic referenced; #2 — Match between system and the real world</p><h4>What are my expectations?</h4><ul><li>If I tap or click this button, what do I expect to happen?</li><li>If I swipe the card to the right, will it slide to the right in as natural a manner as swiping a paper card on a table?</li><li>If I click on an article with a compelling title, does the content of the article match the expectations created in my mind when I clicked it?</li></ul><h3>#4. What is happening now that I did it?</h3><p>Heuristic referenced; #1 — Visibility of system status</p><h4>Reactions to my actions</h4><ul><li>Now that I tapped the button, how is the interface responding to my action?</li><li>Is the screen animating in a certain direction?</li><li>Is there a new screen loading? How do I know?</li><li>Are there multiple indicators of processes in action? How do I know the differences between them?</li></ul><h3>#5. What happened?</h3><p>Heuristics referenced include; #9 — Error Prevention &amp; #3 — User control and freedom</p><h4>Completion of my interaction</h4><ul><li>Were my expectations regarding what I thought would happen validated or invalidated?</li><li>Did the transition between states make sense?</li><li>If I swiped to the left, did the screen push to the left?</li><li>If I completed a task, do I now know that it is complete?</li></ul><h3>Pros and cons of doing a 5 step analysis vs 10</h3><p><strong>Pros:</strong> The primary advantage here is speed. Using the 5 step eval I can get through an evaluation of a screen in less than 5 minutes whereas in the 10 step eval I often get bogged down by terminology, frustrated by how many violations there are and defining what the severity rating of those violations might be. In the past, I could have spent days working on an evaluation of a 3 screen checkout process using the 10 step method.</p><p><strong>Cons:</strong> The rigorous scientific approach Jakob Nielsen took in his 10 step evaluation shouldn’t be downplayed. This 5 step evaluation has only been tested in my own experience and would need a lot more documented results to be as reliable as the full 10 step approach.</p><h3>Call to action</h3><p>This is where you come in! Please try this evaluation out and let me know how it works for you. I would love to hear about how it fits into your design process as well as any opportunities you see for improvements. Also please add any thoughts you may have in the comments.</p><p>You can also <a href="/service/mailto:ldweisser@gmail.com">shoot me an email</a> to get access to a Dropbox Paper Template of the evaluation you can use to do evaluations on your own.</p><p><strong>Disclaimers, legal stuff, inspiration, and thanks</strong></p><p>This analysis was inspired by Don Norman’s Seven Stages of Action along with his Seven Design Fundamentals and Jakob Nielsen’s 10 Heuristics of Design.</p><p>Special thanks to <a href="https://medium.com/u/51b9f2c2c907">Stedman Halliday</a> and <a href="https://www.joshfry.me/">Josh Fry</a> for edits and suggestions and to <a href="https://unsplash.com/@joannakosinska">Joana Kosinska</a> whose Unsplash image I used for the background of the title graphic which is set in <a href="https://optician-sans.com/">Optician Sans</a>.</p><p>As a disclaimer, I want to emphasize that the outcomes of this evaluation should not be compared to a full 10 step Heuristic Evaluation in terms of comprehensiveness but rather should be viewed as a quick first step when a full evaluation is not feasible in the context of your design process. I also recommend you first study the original 10 step evaluation and familiarize yourself with the heuristics in it for best results when using this 5 step evaluation.</p><p>The first version of this analysis was created by Lance Weisser on Wednesday, December 7th, 2016</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=589cb8a6561a" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/a-quicker-heuristic-analysis-589cb8a6561a">A quicker heuristic analysis</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>