<?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 Zarina Majidova on Medium]]></title>
        <description><![CDATA[Stories by Zarina Majidova on Medium]]></description>
        <link>https://medium.com/@zarina.majidova.m?source=rss-7704cdc1736------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GNYT__IVywL-RTtyExSFcg.jpeg</url>
            <title>Stories by Zarina Majidova on Medium</title>
            <link>https://medium.com/@zarina.majidova.m?source=rss-7704cdc1736------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:12:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zarina.majidova.m/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[O-1A Extraordinary Ability Visa as a Product Designer]]></title>
            <link>https://medium.com/@zarina.majidova.m/o-1a-extraordinary-ability-visa-as-a-product-designer-ad99ba167d0e?source=rss-7704cdc1736------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad99ba167d0e</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[o1-visa]]></category>
            <category><![CDATA[immigration]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Zarina Majidova]]></dc:creator>
            <pubDate>Sun, 19 Jul 2026 20:16:48 GMT</pubDate>
            <atom:updated>2026-09-21T23:56:17.782Z</atom:updated>
            <content:encoded><![CDATA[<p>I completed my master’s degree in the U.S. and stayed to work on OPT (12-month post-graduation work authorization). Since my degree was not STEM-designated, I was not eligible for the STEM OPT extension (24-month extension for eligible STEM degrees). That meant I had only one chance in the H-1B lottery (the U.S. government’s drawing for high-skilled work visas). Unfortunately, I was not selected.</p><p>The H-1B lottery results came out in early April leaving me with only 4 months before my OPT expired. In practice, I had only about 2 to 2.5 months to find legal representation, collect evidence, and prepare the petition, even assuming I did not receive an RFE (Request For Evidence, a request for more documents or information) from USCIS. Even with premium processing (paid expedited service that guarantees faster case review, in my case 15 business days), the petition needed to be filed at least 6 weeks before my OPT expiration to allow enough time for USCIS to make a decision and for the approval notice to arrive by mail before I lost my work authorization.</p><p>Anyone who has dealt with US immigration and employment authorization knows how high the stakes are. I strongly encourage anyone in a similar situation to start preparing as early as possible. Living with that level of uncertainty for months is exhausting. When I finally received my approval, I felt a huge sense of relief. I could finally make long term plans again, upgrade my furniture, buy season tickets to the opera, and finally buy that Le Creuset set.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*emBOQfL23N7qgjRrPpmgyg.png" /></figure><p>The reason I’m sharing my experience is that Reddit threads and articles helped me a lot while I was preparing my case. I hope this article does the same for someone else.</p><p>Before we get started, I’m not an immigration attorney, and nothing in this article should be taken as legal advice. I’m only sharing my personal experience, which may or may not apply to your situation. Please consult a qualified immigration attorney about your case.</p><h4>What is O1 visa?</h4><p>The O-1 is a U.S. nonimmigrant work visa for people with extraordinary ability or achievement in their field. It has 2 categories: <br>1. O-1A for people in science, education, business, and athletics<br>2. O-1B for people in the arts, film, and television.</p><p>This article focuses on the O-1A process.</p><h4>Do I need an attorney?</h4><p>Technically, it is possible to prepare an O-1 petition without an attorney, and some people report doing so successfully. However, based on my experience, I would strongly recommend working with a qualified immigration firm/attorney.</p><p>Having evidence that meets the criteria is only part of the process. The legal brief is arguably the most important part of the petition, and writing a strong one requires experience and specialized knowledge that is difficult to gain in a short period of time.</p><p>At the same time, don’t expect your attorney to build your case for you. Their job is to present your case in the strongest possible way based on your profile and the evidence you provide. No attorney can win awards for you, publish your work, feature you in the media, judge competitions on your behalf, or make your manager write a recommendation letter. If someone promises they can create this kind of evidence for you or guarantee any outcomes, you are definitely being scammed.</p><p>I strongly recommend reading the <a href="https://www.uscis.gov/policy-manual/volume-2-part-m-chapter-4">USCIS Policy Manual section on O-1 beneficiaries</a> before getting started. I can’t stress this enough, do not rely on AI-generated summaries or interpretations. Read the full section carefully and consider how each requirement applies to your own case.</p><h4>Choosing Legal Representation</h4><p>You can either work directly with a U.S. immigration attorney or through an immigration platform that works with U.S. immigration attorneys. I chose the second option. Throughout my case, I mainly worked with a case manager, an immigration attorney, and several other members of the legal team. For simplicity, I’ll refer to all of them as “attorneys” in this article.</p><p>In my experience, the case managers handled the day-to-day preparation of my petition with incredible attention to detail, while the attorney was responsible for the legal strategy and ultimately reviewed and filed the petition.</p><h4><strong>Cost</strong></h4><p>The O-1 process can be very expensive. Depending on your attorney’s fees, filing strategy, and whether you use Premium Processing, the total cost can range from $10,000 to $20,000 or more. USCIS filing fees continue to increase, so the total cost may be even higher by the time you apply. Make sure you understand the costs and risks before starting the process.</p><p>I put together a table summarizing the typical costs associated with the O-1 process because I do not want anyone to be blindsided by how expensive it can be. The information is accurate as of July 2026, although USCIS fees may change over time. Some of the estimates are based on the quotes I received during my application process, so your costs may be lower or higher depending on your circumstances.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bK0xflLijIqiUCw9LxbXbw.png" /></figure><p><strong><em>Note:</em></strong><em> Despite its name, the Asylum Program Fee does not mean you are filing for asylum or have any connection to the asylum process. It is a fee that many employment-based petitioners pay to help fund the U.S. asylum program.</em></p><h4>Approval rate</h4><p>The O-1 visa has historically had an approval rate above 90%, but this number can be misleading. The O-1 is highly specialized, expensive, and usually takes months even years of preparation. Many immigration law firms decline cases that do not meet the USCIS criteria, so a large number of weaker cases are never filed.</p><p>For comparison, the H-1B lottery has received between roughly 340,000 and 780,000 registrations annually over the past few years. By contrast, USCIS received only about 10,000 O-1A petitions in FY2023.</p><p>Another thing to keep in mind is that the published approval statistics include initial petitions, extensions, and other O-1 Form I-129 filings. They also include O-2 petitions (support personnel for O-1 beneficiaries) in statistics reported for the overall O classification. As a result, the approval rate for first-time O-1 petitions is likely much lower than the overall published approval rate</p><h4>Petitioner</h4><p>The O-1 does not allow self-petitioning. You need either a U.S. employer or a U.S. agent to act as your petitioner.</p><p>I chose the agent route because it gave me more flexibility and control over my career. With an employer-sponsored O-1, you are authorized to work only for that employer. As a designer, part of my income comes from freelance and consulting projects, so having an agent made much more sense for my situation.</p><p>Using an agent does add to the overall cost. I have heard of people using friends or acquaintances as their agents to cut costs, but I didn’t want to take the risk, so I hired an experienced agent recommended by my attorneys. Agent fees vary widely. I received quotes ranging from about $800 to $4,000 (I know, crazy!).</p><h4>Advisory opinion</h4><p>As part of the O-1 process, you need an advisory opinion letter(also called a consultation letter or no objection letter). For designers, USCIS recognizes AIGA (American Institute of Graphic Arts) as the relevant peer group.</p><p>At the time I applied, obtaining the letter cost me $410 in total. You first need to become an AIGA member, since only members can request an advisory opinion. Membership is usually around $250 for the Professional tier, although I was able to get it on sale for $160. The advisory opinion itself cost another $250.</p><p>AIGA team reviews your resume, LinkedIn profile, portfolio, and other materials to provide the letter. They can refuse the request if they believe you do not qualify.</p><p>Some applicants obtain advisory opinion letters from experts in their field. It is usually cheaper or free. If you choose that route, the expert should be independent and should not have any affiliation with you. Because I had a very tight timeline and wanted to reduce the risk of an RFE, I decided to get the letter from AIGA.</p><h4>Employment letters</h4><p>An O-1 petition must include a job offer or, at minimum, letters of intent from the companies you plan to work with. If you are filing through an agent and intend to work for multiple companies, all of those engagements should be included in your itinerary. This includes current employment, consulting work, contracts, and prospective opportunities supported by letters of intent or job offers. The itinerary should clearly describe the work you plan to perform during your O-1 validity period.</p><h4>Letters of recommendation</h4><p>Letters of recommendation are not required, but they can help tie your case together. I included 6 letters from different stages of my career, including former managers, colleagues, project partners, and one independent expert.</p><p>From what I’ve seen online, people often place far too much importance on recommendation letters. In my opinion, they should only support the rest of your evidence. USCIS may give them less weight if they see them as subjective opinions, so your main evidence should be objective and, whenever possible, publicly verifiable.</p><p>There are also services where you can pay experts to review your portfolio and write a recommendation letter. I know that there is nothing inherently wrong with that, but I personally chose not to use them. I can’t justify paying hundreds of dollars for a one or two page letter that is likely written using AI and templates, especially when USCIS may not even give it much weight.</p><p>Now that we’ve covered the basics, I’ll go through each criterion, explain which ones I claimed and describe my strategy.</p><p>Since my petition was approved without an RFE (Request for evidence), I don’t know which specific criteria USCIS accepted or how they evaluated each one. The only thing I know for certain is that at least 3 criteria were accepted as that is the minimum required for approval.</p><p>My attorneys suggested to claim 7 out of the 8 O-1A criteria. In my opinion, 5 of them were strong, one was moderate, and one was a stretch that I was hesitant to include.</p><h3>Criterion 1: Receipt of nationally or internationally recognized prizes or awards for excellence in the field of endeavor</h3><p>I only had one international design award that I believed qualified under this criterion.</p><p>One important thing to know is that most academic awards, scholarships, and student honors do not qualify, even if they are highly competitive.</p><p>USCIS is very specific about this criterion. The award should match the field you’re applying under. For example, if you’re applying as a product designer, a music award would not satisfy this criterion, even if it were a Grammy.</p><p>The award should be issued to you personally. Your name should appear on the certificate or other official documentation. You cannot submit an award issued to your employer as your own even if you designed the product (even if you are the sole designer of that product) unless your name is explicitly mentioned in the award documentation or listing.</p><p>As evidence I included the certificate, the congratulatory letter, the public winner page with my name and winner badge, and an interview published by the award organization.</p><p>My attorneys also included evidence about the award itself, such as its international scope, who it is intended for, how entries are judged, the qualifications of the jury, and evidence that winners are selected on merit (pay-to-win awards do not qualify).</p><p><strong><em>Side note:</em></strong><em> Professional awards can be unreasonably expensive to obtain even if you are well qualified. Entry fees often range from a few hundred dollars to well over a thousand dollars. Some major awards require winners to purchase mandatory winner packages after the judging process is complete. I want to be clear that these fees do not influence the results, they cover official winner benefits such as inclusion in the winners directory, the right to use the award label and logo, promotional materials, and other forms of recognition. For example, Red Dot winner packages for the Product Design competition currently start at around €4,900. Without purchasing a winner package, recipients cannot be included in the official winners listing or use the Red Dot label and other official winner benefits. The last time I checked, they also charged an additional €950 for a winner profile, separate from the winner package.</em></p><p><em>I also found it difficult to apply for awards because many of my strongest projects were covered by NDAs and couldn’t be used for personal submissions. If you’re still building your O-1 profile, I recommend applying for awards consistently and creating independent work that you can submit without violating NDAs. Awards can become a significant part of the overall cost of an O-1 petition.</em></p><h3>Criterion 2: Membership in associations that require outstanding achievements</h3><p>As a general rule, memberships that are open to anyone who pays a fee or meets an experience requirement do not satisfy this criterion. USCIS is looking for associations where membership requires outstanding achievements in the field, as judged by recognized experts.</p><p>I didn’t have any memberships that I felt met this criterion. My attorneys suggested including my recognition as an ADPList Top 50 Mentor because they believed there was an argument that it could qualify.</p><p>Personally, I considered it a long shot and don’t think it satisfied the criterion, but the fact that ADPList vets its mentors and has an acceptance rate of around 30% may have helped.</p><h3>Criterion 3: Published material about you in professional or major trade publications or other major media</h3><p>I had multiple articles and interviews over the years that I shared with my attorneys. They decided that only 4 were strong enough to include under this criterion and the rest were submitted as additional evidence.</p><p>Based on my experience, there are several things that make an article more likely to satisfy this criterion:</p><ul><li>It should be written by an independent journalist, and the author’s name should be listed in the article.</li><li>It should focus on you as a professional. For example, if you’re applying as a singer and the article is about your dating life or celebrity gossip, it likely won’t qualify.</li><li>It should relate to the field you’re applying under. For example, if you’re applying as a designer but the article is about you winning a sports competition or volunteering, it does nothing for your case.</li><li>It should be published by a major media outlet or a trade publication.</li></ul><p>The petition should also explain why each publication qualifies, supported by objective evidence such as its readership, reach, reputation, website traffic, or other relevant metrics. My attorneys included simple web screenshots and publicly available, verifiable information about each publication.</p><p><strong><em>Side note</em></strong><em>: This is just my personal opinion, I think the timing of your media coverage matters. If you’ve been working as a designer for 5 years and all of your articles are published in the few months before filing your petition, it may look fabricated. I have no evidence that USCIS views it this way, but I think it’s better if your professional recognition is spread out over time instead of appearing all at once right before your filing.</em></p><h3>Criterion 4: Participation as a judge of the work of others</h3><p>I had judged two hackathons and served as a reviewer for a university student design cohort.</p><p>My attorneys suggested that we include only the hackathons. They explained that reviewing a student cohort, even as an invited industry expert, might carry less weight and could weaken the argument.</p><p>For each judging activity, I submitted confirmation letters from the organizers, public information about the competition and the organizing companies, and supporting documents such as judging rubrics, invitation emails, and news articles about the events.</p><h3>Criterion 5: Original scientific, scholarly, or business-related contributions of major significance</h3><p>A few years ago, I designed a feature that was later used by millions of people and eventually became an industry standard within its niche. (Because the project is covered by an NDA, I can’t share any details publicly.)</p><p>Initially, I didn’t want to claim this criterion because I wasn’t sure the evidence was strong enough. I had designed the feature as part of my job, not as an independent designer, and I didn’t hold a patent. The company itself never patented it because they didn’t expect it to become so widely adopted. That said, I was responsible for the entire feature, including the logic, user flow, UI, and overall design.</p><p>My attorneys encouraged me to include it. To support the claim, we submitted evidence such as the original design files with timestamps, a case study, product adoption numbers, screenshots showing similar implementations by other companies, letters from industry professionals describing the influence of my work, and additional supporting documentation, including public industry reports from that time. The legal brief tied all of the evidence together and explained why the work was both original and significant. Although I’m not sure whether this criterion was ultimately accepted, I think we made a strong case for it.</p><h3>Criterion 6: Authorship of scholarly articles</h3><p>I didn’t claim this criterion because I had nothing that qualified. I had never published scholarly articles or research papers.</p><p>Because I only had 2 months to prepare my O-1 petition, there wasn’t enough time to produce and publish academic work. If this is a criterion you’re interested in claiming, it’s something you need to start working on years in advance.</p><h3>Criterion 7: Leading or critical role for distinguished organizations</h3><p>This criterion has two parts.</p><p><strong>1. You need to show that the organization is distinguished.</strong> In my case, this was fairly straightforward because I currently work for a Fortune 500 company that is a leader in its industry. We also claimed my leading and critical roles at two previous employers: one of the largest banks in its region and a highly successful startup.</p><p>One thing is important to note that, don’t assume USCIS already knows these organizations or that stating they are a Fortune 500 company or one of the largest banks in the country is enough. You still need to provide objective evidence demonstrating the organization’s reputation, achievements, and standing within its industry.</p><p><strong>2. You need to show that your role was leading or critical. </strong>To support this criterion, I included letters from my managers and product partners, objective internal documents identifying me as the lead designer on key projects, some of the original design works, performance reviews, internal awards, and other evidence demonstrating my impact on the organization.</p><h3>Criterion 8: High salary or other significantly high remuneration</h3><p>This criterion is fairly straightforward if your income is high enough.</p><p>As a designer working in tech in the Bay Area, my compensation is naturally much higher than the national median. But USCIS doesn’t compare your salary only against the U.S. or world average. They also consider your occupation and geographic area. Unfortunately (or luckily) for me, the San Jose–Sunnyvale–Santa Clara Metropolitan Statistical Area (the MSA where I am based) is the highest-paying metropolitan area in the United States for my occupation.</p><p>To strengthen this criterion, we used my total compensation, including my base salary, annual bonus, RSUs, and additional income.</p><p>It’s also important to provide objective evidence showing how your compensation compares to others in your field and geographic area. My attorneys used sources such as O*NET, U.S. Bureau of Labor Statistics wage data, and other publicly available salary reports.</p><p>All in all, the O-1 visa can be extremely stressful, and time-consuming. At times, it felt unfair that I had to go to these lengths just to be able to continue working. At the same time, I recognize that, as an international professional, I am not entitled to live or work in the U.S. unless I meet the legal requirements. For me, the O-1 was the best option available at this stage of my career.</p><p>While my case was being prepared and later processed by USCIS, it took up a lot of mental space. I often found myself thinking about different scenarios: what if it wasn’t approved, what if I received an RFE, or what if I had to leave the country and start over somewhere else. At one point, there were discussions about being transferred to company’s European office for a year or two and then returning to the U.S. on a transfer visa which felt extreme to me.</p><p>One thing that helped was making sure my life didn’t completely revolve around immigration. I planned vacations and weekend trips, booked concerts and shows, and took day trips so I always had something to look forward to. It definitely didn’t eliminate the anxiety, but it made the waiting period a little easier.</p><p>I know this can be a stressful time for many international students and professionals. Hopefully, one day you’ll look back on this period and be glad it’s behind you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad99ba167d0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Design Builds Habits: A UX Take on Alta app]]></title>
            <link>https://uxplanet.org/when-design-builds-habits-instead-of-features-a-ux-take-on-alta-app-8ce3479f4ecf?source=rss-7704cdc1736------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ce3479f4ecf</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[habits]]></category>
            <category><![CDATA[fashion]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[habit-building]]></category>
            <dc:creator><![CDATA[Zarina Majidova]]></dc:creator>
            <pubDate>Mon, 02 Feb 2026 10:17:23 GMT</pubDate>
            <atom:updated>2026-06-22T21:23:19.728Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently started using a digital wardrobe app called <a href="https://www.altadaily.com/">Alta</a>, and it became part of my daily life. It reshaped how I think about my clothes, my habits, and consumption in general.</p><p>This could have been a standard usability analysis, but interfaces change with every update which means a UI I criticize today can be completely different in the next release. So my focus here is to analyze how design shapes habits, mindsets, and everyday behavior.</p><h3>What is Alta?</h3><p>Alta is a digital wardrobe app that helps you organize what you own, plan outfits, and track how often you wear your clothes. You can add items by taking photos or uploading images from online stores, categorize them, build outfits, and log what you wear on a calendar. You can do that by searching items or forwarding receipts too.</p><p>For me, one of the most fun things about Alta is the AI avatar. You can upload your body and face photos to create a digital version of yourself and try outfits on it instead of guessing how pieces might work together. This makes experimenting with combinations fast and low-effort.</p><p>You can create outfits manually or let Alta suggest combinations based on weather, occasion, and other inputs. As of now, Alta is entirely free to download and use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tbghRPJgon8YUsLW863OiQ.png" /><figcaption>Screenshots from Alta app</figcaption></figure><p><strong><em>Disclaimer:</em></strong><em> This article is not sponsored or requested by Alta.</em></p><p>Now I want to talk about how using Alta changed the way I think about my wardrobe and my habits.</p><h4>1. Realizing how much I actually own</h4><p>The most time-consuming part of using Alta is adding your existing clothes. That usually means taking photos of each item or uploading images from product pages. For most people, it is mostly photos, since many items were bought over the years and probably no longer exist online.</p><p>Photographing and cataloging my clothes made me to realize how much I actually own:</p><ol><li>Clothes bought just because they were on sale</li><li>Items purchased for occasions that never happened</li><li>Pieces I never got rid of because they were expensive despite not wearing them</li><li>Clothes I avoid wearing because they are uncomfortable or I just do not like them</li><li>Items that looked great on models but are not flattering on me</li><li>Clothes that do not fit properly, either too small, too big, or oddly cut</li><li>Things ordered online that I was too lazy to return</li><li>Clothes that “just need tailoring” and will never see a tailor (let’s be real)</li><li>Items I completely forgot I owned</li><li>“What was I thinking” items</li></ol><h4>2. Decluttering what I do not need</h4><p>While adding items to my digital wardrobe, I found myself mentally sorting everything. Do I want to keep this? Do I actually see myself wearing it? Or is it just taking up real estate in my closet?</p><p>There is a popular rule that says if you did not wear something in the last 6 months or will not wear it in the next 6, it should be gone. I think this is a decent starting point, though not universal.</p><p>By the end of this process, I donated around 25 percent of my clothes and threw out another 10–15 percent. I only kept the items I really like or pieces I can realistically work into outfits.</p><h4>3. Tracking cost per wear</h4><p>I believe that the real cost of an item is not its price, but its cost per wear. A $30 blouse worn once is more expensive than a $600 scarf worn hundreds of times.</p><p>Alta tracks cost per wear automatically. You add the purchase price once, and every time you include an item in an outfit, the app recalculates its cost per wear. This data makes it easier to decide what is worth keeping, what can be donated, and what was never a good purchase to begin with.</p><p>My personal rule of thumb is to aim for a cost-per-wear of at least $5, with $1 being the ultimate goal.* Beyond personal finance, this mindset is also better for the environment. So much clothing waste comes from items worn once and discarded. Reducing cost per wear forces you to buy fewer things and use them more.</p><p>Like most rules in this process, this works best when applied with common sense. You probably won’t wear $1,200 heels 1,200 times and you certainly won’t wear a $10,000 coat 10,000 times. Realistically, there aren’t even enough winter days in a lifetime to make that happen.</p><p><em>*This assumes U.S. pricing and varies across countries and economic realities.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jTmwF1ukGbNhRfH_KqchFw.png" /><figcaption><em>An item view showing a $250 coat worn 10 times, with cost per wear calculated based on outfits logged since January.</em></figcaption></figure><h4>4. Shopping my own wardrobe</h4><p>This is one of the best habits I developed with Alta. Whenever I have an occasion and need an outfit, I open my digital wardrobe and start mixing and matching what I already own. Tops, bottoms, dresses, shoes, jewelry, bags. I only buy something new if I do not have anything that works.</p><h4>5. Wearing what I already own</h4><p>This sounds so obvious, it is very easy to wear the same clothes every day just because they are comfortable and require no thinking.</p><p>Alta shows how many items are in your digital wardrobe and your closet usage, essentially the percentage of items you actually wear. Personally, I aim for around 90 to 95 percent usage within a year. If your usage is below 30% or even 50%, it probably means your closet is either underutilized or filled with items that do not really belong in your life.</p><p>Seeing this information challenges me to reconsider my typical approach to outfits. Every time I create a look, I try to include at least one item I have not worn that month.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*-HpiIvdDHdlrqc34mEdz5w.png" /><figcaption><em>Closet overview showing total items and the percentage of my wardrobe I actually wore.</em></figcaption></figure><h4>6. Planning outfits ahead</h4><p>For most people deciding what to wear can be a daily struggle, particularly in the mornings. Planning outfits in your head works sometimes, but it is easy to forget.</p><p>One of the most useful features of a digital wardrobe is the ability to plan and save outfits in advance. Whenever I have the time I pre-plan my looks for the upcoming week, so in the morning all I have to do is grab the items I’ve already selected. This removes a surprising amount of decision fatigue and makes getting dressed feel almost automatic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*40VS0cU_fMNd1tYuGXn7FQ.png" /><figcaption><em>The calendar view makes patterns visible, including my very obvious favorite work bag.</em></figcaption></figure><h4>7. Tracking how much each outfit costs</h4><p>Street interviews where people list what they are wearing and how much it costs are always interesting. $80 jeans, $200 shoes, a $100 sweater, a $1000 coat, jewelry, a designer bag. A simple outfit can add up very quickly.</p><p>Alta shows the total cost of an outfit, including clothes, shoes, accessories, and jewelry. Seeing that number attached to a look makes it clear how easily prices stack. A seemingly simple outfit can cost hundreds, and sometimes thousands.</p><h4>8. Shopping more mindfully</h4><p>As these habits stacked up, my shopping behavior changed. Tracking cost per wear and seeing how much of my wardrobe went unused made me more selective. I now buy items only if I can realistically see myself wearing them multiple times ($5 per use rule) and pairing them with what I already own. No more buying 28th pair of straight-leg jeans. No more “this bag is kind of cute, I have to have it,” when I know I will wear it once, if that.</p><p>Alta also shows your most and least worn items, so I know where to invest more and what to stop buying.</p><h4>9. Digitally trying on before buying</h4><p>I have a simple rule/trick for this. When I am considering buying something new, I add it to my digital wardrobe and try building outfits with it first. I usually put it on my AI avatar, which looks close enough to me to be genuinely useful.</p><p>If the item works naturally with what I already own, it is a good sign. If it creates friction, or requires buying additional pieces just to make it wearable, it usually is not worth it.</p><h4>10. Applying the same structure beyond my wardrobe</h4><p>Once I started seeing what I owned and what I actually used, I applied the same logic to other areas of my life. Makeup, hair products, skincare, perfumes. Just simple inventories in the Notes app on my MacBook and iPhone, nothing fancy. Listing what I have, noticing what I actually use, and making a conscious effort to finish things before buying more.</p><p>Habit building always takes time and effort. No app can do that work for you. But good design can enable it, support it, and multiply the effort you are already willing to make.</p><p>In a time when many products are optimized for doomscrolling, unnecessary spending, trend chasing, and pure attention extraction, it is genuinely refreshing to see teams designing for better outcomes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ce3479f4ecf" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/when-design-builds-habits-instead-of-features-a-ux-take-on-alta-app-8ce3479f4ecf">When Design Builds Habits: A UX Take on Alta app</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Most Annoying UX Patterns of the Modern Web. Part 2]]></title>
            <link>https://uxplanet.org/the-most-annoying-ux-patterns-of-the-modern-web-part-2-49ce31fb3e15?source=rss-7704cdc1736------2</link>
            <guid isPermaLink="false">https://medium.com/p/49ce31fb3e15</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Zarina Majidova]]></dc:creator>
            <pubDate>Thu, 22 Jan 2026 05:56:35 GMT</pubDate>
            <atom:updated>2026-05-08T22:13:29.798Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently wrote an article about the <a href="https://medium.com/ux-planet/the-most-annoying-ux-patterns-of-the-modern-web-6605ae2fb6e5">most annoying UX patterns of the modern web.</a> This is Part 2. There are too many things wrong with the internet for one article to cover.</p><p>Consider this a continuation of a very long list of small, avoidable annoyances that test your patience every day.</p><h4><strong>1. “Continue Watching” items caused by end credits</strong></h4><p>You finish a movie, exit during the last 3 to 7 minutes of credits, and later see it still sitting in your <em>Continue Watching</em> list. Most people do not watch credits. Unless it is a Marvel movie and you are waiting for a post-credit scene, the experience is already over.</p><p>Streaming platforms have enough data to understand this behavior. They know where credits begin and when the narrative ends. Treating credits as required viewing turns <em>Continue Watching</em> into a technical artifact rather than a useful feature.</p><p>Over time, the list fills up with content you have already finished but now have to remove manually. For people who care about clean, functional lists, this is an unnecessary annoyance that should not exist in 2026.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/0*RjMbsgipbAJeuGjJ.png" /><figcaption>Source: Alphr</figcaption></figure><h4><strong>2. Streaming TV apps missing basic functionality</strong></h4><p>Many streaming platforms offer full control on web and mobile, but remove basic features from their TV apps. A common example is the inability to remove a movie or show after you opened it and decided not to watch it.</p><p>On most TVs, there is no way to clean this up. The item stays in your list until you open the same platform on your phone or laptop and remove it there. For people who use streaming apps primarily on TV, this is frustrating. The TV is the main surface and basic list management should not require switching devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/0*uTAKVmp2DOvnMpeg" /><figcaption>Source: Google Play</figcaption></figure><h4><strong>3. Alphabetical keyboards on TVs</strong></h4><p>While we are already talking about TV UX, typing on a TV deserves its own complaint. There is almost nothing worse than entering text with a remote. The alphabetical keyboard somehow manages to make that experience even slower.</p><p>Most people type every day using QWERTY keyboards. That muscle memory is deeply ingrained. Alphabetical layouts break it completely and force users to hunt for every letter, turning a simple search into a chore.</p><p>Typing on a TV will never be enjoyable, but choosing an alphabetical keyboard actively makes it worse. This is unnecessary friction added to an already frustrating task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fyCEBa_1NOk2zu79.png" /><figcaption>Source: <a href="https://shkspr.mobi/blog/2023/06/just-use-qwerty/">Terence Eden’s Blog</a></figcaption></figure><h4><strong>4. Full-screen location modals during search</strong></h4><p>You search for something local on Google, like a tailor or café, and before you can see the results a full-screen modal appears asking for your precise location.</p><p>Location access request itself is reasonable, but the way it is requested is not. Blocking the entire screen forces a decision at a moment when the user is trying to scan results.</p><p>Modals should be reserved for only urgent or critical actions. A banner or inline prompt at the top of the page would communicate the same thing without interrupting the flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OPsZ-3QL1kdJ6gqlguiQwg.png" /><figcaption>Google Search Results</figcaption></figure><h4><strong>5. Chatbots placed on the left side of the screen</strong></h4><p>Most people expect chat interfaces to appear on the right side of the screen. Messaging apps, support chats, and assistants have reinforced this pattern for years. Most people are right-handed, and even left-handed users have internalized this pattern through years of repetition. The right side has become the default mental model for conversational UI. When a chat opens on the right, it feels expected and easy to ignore or engage with on demand.</p><p>Putting chatbots on the left disrupts that expectation and feels distracting the moment it appears. Amazon’s AI chatbot Rufus is perfect example. Opening on the left feels awkward and unhelpful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGsoVdfB02LUj_EgpNKzUQ.png" /><figcaption>Amazon’s Rufus AI</figcaption></figure><h4><strong>6. Checkout flows packed with forced add-ons</strong></h4><p>You pick a flight, confirm the details, and try to pay. Instead of finishing the purchase, you are stopped by a series of “optional” offers.</p><p>Airline websites do this all the time. Seat selection, insurance, car rental, hotel deals, priority boarding. Each appears on its own screen and requires a decision before you can move forward.</p><p>On an airline website, user’s intent is to buy a ticket. Every extra step delays that outcome and turns a straightforward task into annoyance. Add-ons work better when they stay in the background and appear only after interaction. A list with expandable options would solve this. If user clicks on car rental, show the details. Otherwise, let them continue.</p><p>Airlines want to maximize revenue per customer. That goal is understandable. I, as a designer, believe that business goals do not justify deliberately irritating users. Designing friction into a critical flow feels disrespectful of users’ time and patience.</p><h4><strong>7. Push notification overload</strong></h4><p>Some apps send so many push notifications that users eventually disable them entirely in system settings. When that happens, useful messages disappear along with the noise.</p><p>I recently downloaded the Macy’s app. Within two days, I was receiving multiple notifications a day about dresses I might like, sales I did not ask for, and promotions I was not interested in. Turning notifications off from Settings app was inevitable. But that also removes delivery updates and order status alerts which I did not mind receiving.</p><p>In a world already full of interruptions, multiple marketing pushes a day from the same app is excessive. Used sparingly, push notifications can be valuable. Used aggressively, they train users to block them completely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HZfibq9SewT6L_sn.jpg" /><figcaption>Source: Evam</figcaption></figure><h4><strong>8. Ads inside your email inbox</strong></h4><p>Email is supposed to be a utility. Open it, read messages, respond, leave. When ads start competing with actual emails reading them becomes harder than it needs to be.</p><p>My first email address was on Yahoo, and I still have access to it. Many old accounts are tied to it, so occasionally I have to log in. Every time I do, ads dominate the interface. It feels like only half of the screen is dedicated to actual email, with the rest filled by banners, promoted content, and visual noise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fxr31s33sxsEA3ds2hAs2g.png" /><figcaption>Yahoo inbox</figcaption></figure><h4><strong>9. Unskippable feature tours and walkthroughs</strong></h4><p>Feature tours, walkthroughs, and coach marks can be useful in very specific cases. New tools, complex workflows, or genuinely confusing features sometimes benefit from guidance.</p><p>The problem starts when these tours become mandatory. Unskippable slides, forced steps, and overlays you cannot dismiss until you have clicked through everything. This is especially irritating when you already know the product but opened a new account, reinstalled the app, or logged in on a new device.</p><p>People do not read instructions by default. Most users explore interfaces by doing, not by studying. Forcing them through explanations they did not ask for just creates friction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IN6tvyl1i3DJDIuJEdYFYw.png" /></figure><h4><strong>10. No way to unsubscribe from email subscriptions at once</strong></h4><p>You enter your email somewhere once, maybe for a discount or a download, and suddenly your inbox is flooded with email subscriptions. Newsletters, promotions, and updates you do not remember signing up for. Most email clients now offer unsubscribe options, but you still have to unsubscribe from each email subscription one by one.</p><p>When dozens or hundreds of subscriptions pile up, cleaning them up becomes a repetitive task. There is no bulk unsubscribe, no reset, no fast way to reclaim your inbox (and peace). Accidental email subscriptions are very common. Getting rid of them should not feel like a project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xZOPuxk6UWg2977I3qHn4A.png" /><figcaption>Gmail inbox</figcaption></figure><h4><strong>Bonus: App rating prompts that escalate</strong></h4><p>You download an app, barely start using it, and are immediately asked to rate it. More often than not, the prompt appears too early and interrupts the task you actually came for.</p><p>You tap a rating just to make it disappear. Instead, a second prompt appears asking you to write a review. If you accidentally agree, you are redirected to the app store or review page and pulled out of the app entirely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*MnVRclnkhi38Jkej" /><figcaption>Source: Dribbble</figcaption></figure><p>None of these patterns are catastrophic on their own. They are small, familiar, and easy to dismiss. Individually, they waste seconds. Collectively, they drain attention, patience, and trust. Good UX is sometimes about removing friction that never needed to exist in the first place.</p><p>This is not the end of the list. Unfortunately.</p><p>If there is a UX pattern that ruins your mood feel free to share it with me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49ce31fb3e15" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/the-most-annoying-ux-patterns-of-the-modern-web-part-2-49ce31fb3e15">The Most Annoying UX Patterns of the Modern Web. Part 2</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Most Annoying UX Patterns of the Modern Web. Part 1]]></title>
            <link>https://uxplanet.org/the-most-annoying-ux-patterns-of-the-modern-web-6605ae2fb6e5?source=rss-7704cdc1736------2</link>
            <guid isPermaLink="false">https://medium.com/p/6605ae2fb6e5</guid>
            <category><![CDATA[deceptive-patterns]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ads]]></category>
            <dc:creator><![CDATA[Zarina Majidova]]></dc:creator>
            <pubDate>Thu, 01 Jan 2026 01:41:27 GMT</pubDate>
            <atom:updated>2026-06-01T18:23:48.382Z</atom:updated>
            <content:encoded><![CDATA[<p>I am a UX designer, which means I can no longer use the internet without noticing everything that is wrong with it.</p><p>This article is about UX patterns that are frustrating, widely adopted, and somehow still treated as acceptable at massive scale. If you have never noticed them, consider yourself lucky. Once you do, they become impossible to unsee.</p><p>Before getting into the list, one clarification. Many of these patterns exist for business, legal, or regulatory reasons. It is an argument that they make the experience worse, and that the world would be a slightly better place if they were not treated as default solutions.</p><h4>1. Cookie consent banners</h4><p>Cookie consent banners are legally required, but their current execution is one of the most disruptive patterns on the web. Cookie consent banners became mandatory due to privacy regulations such as the EU’s GDPR and the California Consumer Privacy Act, introduced by lawmakers to limit uncontrolled data tracking and give users legal rights over how their data is collected and used. However they often block content entirely, appear before any meaningful interaction, and demand a decision from users who have not even had a chance to understand what they are consenting to.</p><p>As a result, users stop reading, stop thinking, and click “Accept” just to make the interface go away. A pattern designed to protect users ends up conditioning them to ignore it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QzlEAp_45qdIMEbM.png" /><figcaption>Full-screen cookie modal that blocks content before any interaction.</figcaption></figure><h4>2. E-commerce pop-ups that block the product you came to see</h4><p>You have probably been there. You are scrolling Instagram and the algorithm works almost too well. It shows you the exact product you only thought about (No, you did not say it out loud. I believe you).</p><p>You click, ready to see the product. Instead, a cookie banner appears before the image loads. You tap “Accept” because at this point we have all surrendered, haven’t we?</p><p>Then a pop-up asks you to sign up for emails. You close it. You try to scroll. Another pop-up appears offering 10–20% off. You close it too. You finally reach the product images, start to engage, click on a related item, and the same pop-up appears again. By now, you are no longer excited.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1owTApAk3HyiZZNOwwzUsQ.png" /><figcaption>Interruptive sign-up modal at a high-intent moment.</figcaption></figure><h4>3. Registration walls</h4><p>You search for something specific, find the perfect article, click the link, read the title, and immediately hit an unskippable registration wall (looking at you, NY times). Instantly.</p><p>You are asked to create an account or pay to read 100 words you came for. Yes, it is a business model. That does not make it any less irritating.</p><p>If content is behind a paywall, users should know that before they click. Medium does this well by clearly labeling member-only articles in search results. If you are not a member and not willing to pay, you do not waste time or emotional energy. Google, take notes!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Z7EcIZsLMKL7nUmo" /><figcaption>Account required before content access.</figcaption></figure><h4>4. Ads everywhere, all at once, all the time</h4><p>You try to read an article and are immediately surrounded by ads. One on the left, one on the right, one at the top, one in the middle of the content, and a video ad auto-playing in the corner for no reason at all.</p><p>At this point, reading becomes work. Your attention is constantly pulled away from the thing you came for, and the experience feels chaotic rather than informative.</p><p>Ads are often necessary to support free content. But when they dominate the layout and compete with the content itself, they defeat their own purpose. If the interface feels like it is fighting for your attention something has gone seriously wrong.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NT0WCWnErY06jjCGmPqM-w.png" /><figcaption>Ads surrounding the content from every possible direction.</figcaption></figure><h4>5. Ads that look like content</h4><p>Some ads do not look like ads at all. They are intentionally designed to blend in with real content, mimicking headlines, layouts, and even typography. This is a <em>deceptive pattern</em> often referred to as <em>disguised ads</em>.</p><p>The goal is to make users click without realizing they are interacting with advertising. When users cannot reliably distinguish content from promotion, they stop trusting both. I have covered this pattern in detail in <a href="https://medium.com/ux-planet/deep-dive-into-deceptive-patterns-recognize-and-avoid-disguised-ads-39576d672b36">a previous article on Medium</a>, where I explain how disguised ads work and why they are harmful to user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zNP5T0DGzhL_vkuU.png" /><figcaption>Sponsored content disguised as editorial.</figcaption></figure><h4>6. Forced “What’s New” Pages After Updates</h4><p>The “Update Chrome” button sits in the top corner of the browser and does not go away until you click it. Eventually, you do. The browser restarts and immediately opens a new tab with a “What’s new” article.</p><p>When users click update, they are signaling one thing only: finish the update. Opening extra pages pulls attention away from the task they were already doing. Updates should return users to their previous context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WRFAHkYNVIf00V-O.png" /><figcaption>What’s New in Chrome article.</figcaption></figure><h4>7. “Watch an ad to continue” interruptions</h4><p>You are in the middle or just at the beginning, of a game, a video, or an article, and everything stops. To continue, you are required to watch an ad. Sometimes 30 seconds. Sometimes several in a row. No skipping.</p><p>On a recent flight, I tried to start a movie and was greeted by five unskippable ads before the film even began. Apparently, watching the movie required additional data collection, brand exposure, and a test of my patience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/0*vFOl-As5UfxdZgTU" /></figure><h4>8. Forced app updates</h4><p>You open an app to do something simple and are immediately redirected to the App Store. An update is required. You wait, the app reloads, and sometimes you are asked to log in again.</p><p>This usually happens for security patches, API changes, or backend compatibility issues. All valid reasons.</p><p>From a user perspective, it is still disruptive. In many cases, this could have happened automatically in the background instead of at the exact moment the user needed the app. If an update is mandatory, it should be as invisible as possible. Blocking access should be the last option, not the default.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qayg0Z9eEdWVpDWvXhDJQQ.png" /><figcaption>Forced app update that blocks basic usage.</figcaption></figure><h4>9. Hiding prices behind a contact form</h4><p>You are interested in a product or service and want to see the price to decide if it is even worth considering. Instead of a number, you get a form.</p><p>Email, phone number, zip code, and possibly your pet’s name and family history. At the end, a message appears saying, “We will contact you.”</p><p>What follows is a sales call where you repeat the same information, ask for the price again (they wouldn’t tell you), and after a 15-minute lecture finally learn that the product is wildly overpriced for your needs. A single number could have saved everyone this time.</p><p>This pattern is known as price obfuscation or lead capture gating. It prioritizes sales metrics over user efficiency and replaces transparency with friction.</p><h4>10. Unsubscribing that requires logging in</h4><p>This is self-explanatory. You receive a marketing email and decide to unsubscribe. Reasonable. You click the link and are taken to a page that asks you to log in before you can stop the emails.</p><p>At this point, the experience starts feeling hostile. If you remember your password, you waste time. If you do not, you reset it just to escape more emails and waste more time. If a system can send you emails, it can stop sending them without requiring authentication. Anything else feels like deliberate friction.</p><p>There are dozens more UX patterns that frustrate me as both a designer and a user.</p><p>At first, these things seem minor. One pop-up, one extra step, one unnecessary interruption. But they stack up. Eventually, they push you to that familiar moment where you seriously consider throwing your phone across the room, yelling at your laptop, or both.</p><p>I am not sure if anyone has quantified how much time these patterns waste, but it is worth thinking about. All these tiny interruptions steal something far more valuable than attention. Time.</p><p>This is not the full list. View <a href="https://medium.com/@zarina.majidova.m/the-most-annoying-ux-patterns-of-the-modern-web-part-2-49ce31fb3e15">Part 2</a> for more.</p><p>If there is a UX pattern that makes you irrationally angry, you are not alone. Feel free to share your worst UX nightmare.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6605ae2fb6e5" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/the-most-annoying-ux-patterns-of-the-modern-web-6605ae2fb6e5">The Most Annoying UX Patterns of the Modern Web. Part 1</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inside the UX and Product Design Interviews: From Recruiter Call to Final Offer]]></title>
            <link>https://uxplanet.org/inside-the-ux-and-product-design-interview-from-recruiter-call-to-final-offer-00a6dac21cea?source=rss-7704cdc1736------2</link>
            <guid isPermaLink="false">https://medium.com/p/00a6dac21cea</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[job-interview-preparation]]></category>
            <dc:creator><![CDATA[Zarina Majidova]]></dc:creator>
            <pubDate>Tue, 11 Nov 2025 04:56:49 GMT</pubDate>
            <atom:updated>2026-07-31T21:16:43.640Z</atom:updated>
            <content:encoded><![CDATA[<p>Job hunting as a designer can be a humbling experience. But it’s something almost all of us go through at least once. I recently shared <a href="https://medium.com/ux-planet/job-hunting-as-a-ux-ui-designer-in-2025-what-worked-for-me-and-what-didnt-61f15c75fbc6">what worked and what didn’t for me</a> in my own search, and the response to that article encouraged me to write another one, this time focusing specifically on design interviews.</p><p>Every company structures interviews differently, but most follow a similar flow: a recruiter screening, a conversation with a hiring manager, a portfolio walkthrough, and often a panel or case study presentation. Some startups skip steps and hire after 1 or 2 interviews, while larger companies can stretch the process into 5 or more rounds.</p><p>Understanding what each stage is really about, what they’re testing, how to prepare, and what to say can help you approach it with clarity. I hope the next 10 minutes of reading will make that difference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*tTT5hVOnUAuj5LEh" /><figcaption>Image source: Indeed</figcaption></figure><h3>1. Recruiter Screening</h3><p>The first step is almost always a short call with a recruiter/talent acquisition specialist. It might be over the phone or a quick video chat, and usually lasts about 15–20 minutes. Their main goal is to confirm that you meet the basic requirements and that your expectations align with the company’s.</p><h4>What to Expect</h4><p>Recruiters usually give a short overview of the company and the role before asking a few standard questions. Expect to:</p><ul><li>Introduce yourself and summarize your background.</li><li>Confirm your location, work authorization, notice period, and availability.</li><li>Discuss salary expectations, relocation, or hybrid versus remote preferences.</li><li>Briefly talk about your design experience and process.</li></ul><p>Many recruiters use scheduling tools like Calendly, so you’ll probably choose your own time slot. Some also use AI notetakers during the call (they’ll usually mention it at the start).</p><h4>How to Prepare</h4><p>Read the job description carefully before the call and make sure you can speak to each key requirement. Tailor your short (usually up to 1 minute) introduction to highlight what they’re looking for. You’re essentially helping the recruiter fill in their internal notes, so make their job easier by mirroring the role’s language.</p><p>Keep in mind that recruiters are not designers, so it’s best to avoid deep design jargon. Be respectful of their time and keep your answers short and to the point.</p><p>About salary expectations: I personally prefer to be upfront. It saves everyone time if expectations don’t match, even though you’ll hear plenty of conflicting advice about this online. Do what feels right for you.</p><h4>What to Ask Them</h4><p>At the end, they’ll usually ask if you have any questions. Saying “no” can sound like you’re not really interested, so use that moment to ask things you really want to know about the role or the company. Avoid questions recruiters probably wouldn’t have answers for: things like design system specifics, tools, or workflow details. I suggest to ask questions like:</p><ul><li>Is the team cross-functional or design-only?</li><li>Is this a hybrid, on-site, or remote role?</li><li>Does the company cover relocation costs?</li><li>What are the next steps in the process?</li></ul><p>Treat this call as a gateway. Your goal is to make sure both sides are aligned so you can move on to the real design conversations.</p><h3>2. Interview with the Hiring Manager</h3><p>The hiring manager interview is about seeing whether you can actually do the job and whether they’d want to work with you every day. This stage is arguably the most important one.</p><h4>Who Hiring Managers Are</h4><p>Hiring managers are usually design leads or managers, but sometimes they’re product managers, depending on how the company is structured. In startups or smaller companies, the hiring manager could be the CEO or CTO.</p><p>Before the interview, take some time to look them up on LinkedIn, Google, or their professional portfolio. Adjust your approach depending on their background. If they’re a designer, you can go deeper into design thinking, decision-making, and critique. If they come from a product or business background, focus more on collaboration, user outcomes, and how your work solves real problems.</p><h4>What to Expect</h4><p>You’ll get questions that explore your process, teamwork, and how you handle challenges and you are expected to ask a few questions at the end. Common ones include:</p><ul><li>Walk me through your design process.</li><li>How do you handle feedback or conflicting opinions?</li><li>Tell me about a time you disagreed with stakeholders.</li><li>How do you collaborate with engineers or product managers?</li><li>What’s a design problem you’re proud to have solved?</li><li>How do you stay current in design trends and tools?</li></ul><h4>How to Prepare</h4><p>Do your research. Learn a bit about the company’s products and the problems they’re trying to solve. Mentioning something specific you noticed, like a small interaction detail in their app or a recent feature launch, shows genuine interest and preparation. Personally, I never go overboard with this. Do enough to show that you care, but not so much that it turns into a free design audit or unsolicited critique.</p><p>If you can, align your portfolio stories with the company’s focus. For example, if they’re a B2B fintech company, mention your experience designing for complex flows, scalability, or compliance-heavy environments.</p><h4>What to Ask</h4><p>Hiring managers expect specific questions. Ask things that help you understand what the role and culture are really like. Some examples:</p><ul><li>How does the design team collaborate with product and engineering?</li><li>What are some challenges the team is currently facing?</li><li>How is design success measured here?</li><li>Do you collaborate with sales teams to improve user experience?</li><li>Do you have a dedicated UX research team?</li></ul><h3>3. Portfolio Walkthrough</h3><p>This stage is sometimes part of the hiring manager or panel interview, but more often it’s a dedicated session focused entirely on your portfolio.</p><h4>What to Expect</h4><p>You’ll have about 45 to 60 minutes to present 2 or 3 projects. The goal is to tell a clear story about how you approach problems and make decisions.</p><p>Your audience is usually the hiring manager and a designer who’s there to ask design-related questions. Remember, they were not part of your project team, so don’t assume they know the context. Keep things simple, explain enough background for someone new to understand, and highlight your role clearly.</p><p>They might ask you to present specific projects they’ve already reviewed, but in most cases, you’ll lead the session. I usually choose 2 or 3 projects that show range. For example, one mobile and one web project, or one fintech and one healthcare. If you have something that aligns with the company’s domain, start with that.</p><h4>How to Structure It</h4><p>Think of each project as a short narrative:</p><ul><li><strong>Problem:</strong> What challenge were you solving?</li><li><strong>Role:</strong> What exactly did you do?</li><li><strong>Process:</strong> How did you approach it (research, design, collaboration)?</li><li><strong>Solution:</strong> What did you design, and why?</li><li><strong>Impact:</strong> What changed because of your work?</li></ul><p>Avoid slides packed with screens or flow diagrams. Mention design tools only if relevant , what they care about most is how you think. Talk about tradeoffs, priorities, and how feedback shaped your decisions.</p><h3>4. Panel Interview or Case Study Review</h3><p>This is the part that makes most designers sweat. You are presenting your work to a small crowd, usually a mix of designers, product managers, and engineers, while answering questions in real time. It can be intense, but it is also your chance to show how you think under pressure.</p><h4>What to Expect</h4><p>Panel interviews often replace or expand on a portfolio walkthrough. Instead of a casual chat, you are asked to walk through one strong project in depth. Expect anywhere from 3 to 7 people in the room/video call. The session usually lasts between 60 and 90 minutes. You will present your case study, answer questions throughout, and have a few minutes at the end for your own questions.</p><h4>How to Choose the Right Project</h4><p>Pick something that shows your full process: discovery, design, iteration, and validation. If you are mid or senior-level, choose a real project rather than a conceptual one. But if all your projects are academic or speculative, that is fine too, as long as you can clearly explain your reasoning and how you approached user problems.</p><p>Avoid showing something that is just a collection of polished screens. The best case studies reveal how you make decisions, including tradeoffs, challenges, experiments, and collaboration moments that shaped the final outcome.</p><h4>How to Present It</h4><p>I strongly recommend using slides instead of scrolling through a webpage. It helps you control pacing and keeps the story focused. For example, the project I used in my panel interviews had around 35 slides, and I spent about 30 to 60 seconds on each.</p><ul><li>Start with <strong>why</strong> the project mattered: the problem, the users, and the goals. Give enough context so everyone follows along.</li><li>Explain <strong>your role</strong> and highlight where collaboration played a key part.</li><li>Walk through <strong>the process</strong>: research, insights, design iterations, and feedback loops.</li><li>Finish with <strong>results and learnings</strong>: what impact your work had, what changed, and what you would do differently next time.</li><li>Keep slides clean and visual with minimal text. People stop paying attention when your slides look like essays.</li></ul><p>If you are nervous (and most people are), remind yourself that the panel is not there to fail you. They just want to see how you think aloud and whether you can communicate across different roles.</p><p>Case study panels can feel overwhelming because you are juggling your story, timing, and constant questions. I found it helps to pause briefly after each section to let people jump in. It makes the conversation feel collaborative instead of like a performance.</p><p>When someone challenges your decision or asks something unexpected, do not panic. It is better to say, “That is a good point, I have not looked at it from that perspective,” than to get defensive. Authenticity lands better than perfection.</p><h3>5. Site Visit or Final Interview</h3><p>If you have reached this stage, congratulations. You are one step away from an offer. The site visit is meant to see how you interact with the team rather than test your design ability. Not every company does this step, so you might still receive an offer after panel interview without it.</p><h4>What to Expect</h4><p>Companies usually invite you to their office for a half or full-day visit. You might have lunch with the team, sit in on a meeting, or tour the office. The goal is to give everyone, including you, a sense of what working together would feel like day to day. If you live out of state, they usually cover your travel expenses or fly you in.</p><p>Expect several short conversations with designers, product managers, and team leads. The tone is relaxed, but you are still being evaluated on how you communicate, how curious you are, and how well you connect with people.</p><h4>How to Approach It</h4><p>Let’s start with the obvious: what to wear. Dress code depends on the company, and they will usually let you know if they have a formal policy. When in doubt, business casual is the safest option.</p><p>It is completely normal to feel nervous. They know and expect it. The best advice is to be yourself: they already like you enough to bring you in. Be curious, friendly, and professional. Ask about how teams collaborate, what challenges they are currently tackling, and what the design culture feels like in practice.</p><h3>Bonus: Design Challenges</h3><p>My advice about take-home design challenges is simple: <strong>do NOT do them!</strong></p><p>It is almost 2026, and somehow companies still think asking for free labor is acceptable. Serious, well-structured organizations have moved on from this practice. If you receive a take-home design challenge, consider it a red flag.</p><p>If you still want to give the company a chance, suggest a 30 to 60-minute whiteboard challenge or a portfolio walkthrough instead. If they genuinely want to understand how you think and work, those should be more than enough. If they keep pushing for a take-home assignment, that should tell you everything you need to know.</p><p>Even if the prompt looks unrelated to their actual product, remember that your ideas and design solutions can still be reused or adapted later.</p><p>From my personal experience, every serious company that eventually offered me a job never asked for a take-home challenge. The ones that did never led to an offer.</p><p>Of course, the decision is yours. But there is no bigger red flag in this entire job-hunting process than an unpaid design challenge. I understand it’s tempting to accept because you don’t want to lose an opportunity, but any company that truly values designers will never ask you to work for free. Getting rejected is never fun, but getting rejected after spending days on some hypothetical design challenge just adds insult to injury.</p><p>Design interviews take time, patience, and a bit of luck. Sometimes you get the offer, sometimes just the experience. Every round teaches you how to communicate your work a little better. Keep refining, stay curious, and don’t take rejection personally, it’s part of the process.</p><p>If you ever want to talk about job hunting or interview prep, I’m on <a href="https://adplist.org/mentors/zarina-majidova">ADPList</a> and happy to share what I’ve learned.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=00a6dac21cea" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/inside-the-ux-and-product-design-interview-from-recruiter-call-to-final-offer-00a6dac21cea">Inside the UX and Product Design Interviews: From Recruiter Call to Final Offer</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Evaluating the User Experience of Zara’s Online Store]]></title>
            <link>https://uxplanet.org/evaluating-the-user-experience-of-zaras-online-store-71790986bcf0?source=rss-7704cdc1736------2</link>
            <guid isPermaLink="false">https://medium.com/p/71790986bcf0</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[online-shopping]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Zarina Majidova]]></dc:creator>
            <pubDate>Thu, 04 Sep 2025 07:34:23 GMT</pubDate>
            <atom:updated>2025-09-11T21:02:46.068Z</atom:updated>
            <content:encoded><![CDATA[<p>Zara is without a doubt one of the most popular fashion brands worldwide, but whenever I’ve tried shopping on their website, I’ve found it confusing to navigate. In this article, I’m looking at the site both as a shopper and as a user experience specialist to break down the issues more systematically. Fair warning: once you notice these problems, you won’t be able to unsee them. Let’s dive into the analysis.</p><h3>First Impressions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y1nAbuD6-AwLiLk53WNAag.png" /><figcaption><a href="https://www.zara.com/us/">Zara US</a> homepage</figcaption></figure><ul><li><strong>Unusual entry point: </strong>The first thing you see on Zara’s homepage is a random product or collection, dropped in without context. No categories, no overview, just one item staring at you. It feels like starting a book from the middle.</li><li><strong>Tiny product description: </strong>The description text is so small it might as well not exist. Unless you zoom in, you can’t read it, which makes it useless and definitely not accessible.</li><li><strong>Overall effect: </strong>The site is clearly chasing a “minimalist” aesthetic, but in doing so it sacrifices orientation. Instead of helping users get their bearings, the homepage leaves them confused from the start.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8wQXrPGczemsLaaB6eoBsQ.png" /></figure><ul><li><strong>Aggressive pop-ups: </strong>The site “welcomes” you right away with 2 banners: the mandatory cookie notice and a full-width subscription modal. The cookie banner is understandable since regulations require it, but the subscription prompt feels totally unnecessary. Most users come to Zara’s site to browse new arrivals or shop, not to sign up for marketing texts. As both a shopper and a designer, I find this extra layer intrusive. Pop-ups and modals should be reserved for vital information only, otherwise they’re just one more annoying “x” you have to click before you can even see the page.</li><li><strong>Navigation size</strong>: The main navigation text is too small. Even at 125% zoom, it’s still hard to read. That’s frustrating for people with normal vision, and downright inconsiderate for anyone with presbyopia or other common vision issues that make small text difficult to see. For a site used by millions, this is a basic accessibility miss.</li><li><strong>Inconsistent sizing: </strong>The visual hierarchy feels completely off. The Zara logo is oversized, the hamburger menu is strangely larger than it should be, and yet the navigation and product text are tiny. The mismatch makes the interface look unbalanced and harder to scan. Instead of guiding the eye, it feels like everything is competing for attention in the wrong proportions.</li></ul><h3>Finding Products: Search and Navigation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/424/1*y5BII43geKsqoI4fv2Mrzg.png" /><figcaption>Search bar styled as plain text</figcaption></figure><ul><li><strong>Unclear search bar:</strong> The search doesn’t even look like a search bar. Without the universal magnifying glass icon, it comes across as plain underlined text. There’s no hint text like “Search for products” and no clear sign that it’s even clickable. For an e-commerce site, this is a major miss. Search should be the easiest and most obvious tool on the page.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M4E15SqUjmtLHVNPtKagrw.png" /><figcaption>Search bar focus state with unclear layout</figcaption></figure><ul><li><strong>Confusing focused state</strong>: Clicking into the search doesn’t expand it in place as you’d expect. It throws you onto a separate page with tiny text asking what are you looking for. The transition feels unnatural, and the new layout is unpredictable and unintuitive. For something as central as search, the experience adds friction instead of making things easier.</li><li><strong>No hover states:</strong> Almost nothing on the site responds to hover. The only feedback I noticed was product names getting underlined, but even the main navigation menu offers no visual change. Without hover states, users can’t easily tell what’s clickable and what isn’t, which hurts clarity and makes the interface feel unfinished.</li></ul><h3>Persistent <strong>Visual Overlaps</strong></h3><p>One of the most frustrating patterns I noticed on the Zara website is the way elements overlap each other. The ironic part is that this problem has one of the simplest fixes. Just adding a solid background or even a subtle blur effect to fixed menus and elements would easily solve it.</p><ul><li><strong>Logo overlaps with interface: </strong>As you scroll, the oversized Zara logo sits directly on top of content. It’s already unusually large for a corner logo, and when it overlaps product information it becomes distracting taking significant space on top left corner.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KkmadbP1ZMM05Yo3T3zABA.png" /><figcaption>Zara logo overlapping product listings</figcaption></figure><ul><li><strong>Fixed category overlay: </strong>The category menu (Women, Men, Kids, Home, Massimo Dutti) floats over content without a background. On darker images, the text becomes unreadable, and when it overlaps with product labels, both sets of text lose clarity. Instead of aiding navigation, it creates visual noise.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lA8gLjqmBI5SJy3q5sIs2Q.png" /><figcaption>Category menu overlapping product text</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0771fjeXxrCQNW-d1dQt1w.png" /><figcaption>Search bar blending into dark background</figcaption></figure><h3>Interaction and Layout Problems</h3><ul><li><strong>Clickable and non-clickable text look the same: </strong>As discussed earlier, almost nothing has a hover state. On top of that, there are no visual cues to help users understand what is clickable and what is not. For example, the “New” label is not clickable but looks identical to the product name, which is clickable.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/394/1*RWM8OabtdXWqLT_zZBjjSw.png" /><figcaption>Label and product name styled the same</figcaption></figure><ul><li><strong>Important product information placed unpredictably: </strong>Key details appear in the least expected spots. For example, composition info is tucked away in the bottom-left corner, while other tiny labels are hidden at the screen edges, so small they’re almost invisible.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MCmNVEI5nHno9uMCQkh-bA.png" /><figcaption>Product page with oversized image and excessive white space</figcaption></figure><ul><li><strong>Excessive white space and oversized imagery: </strong>The product images are sometimes unnecessarily large and don’t fit within a standard laptop screen. This creates wasted space and forces users to scroll more than they should just to view an item. At one point, I had to zoom out to 50% to see an entire dress on a model, which speaks to how impractical the layout is.</li></ul><p>In just a few minutes of exploring Zara’s website, several usability issues stand out: intrusive pop-ups, unreadable text, inconsistent overlays, and confusing navigation. For a brand of this scale, users should expect a smoother and more accessible shopping experience.</p><p>The purpose of this review isn’t to criticize Zara’s designers, but to highlight areas where the site could improve. Some of these problems also affect accessibility, and most of them could be addressed with relatively simple fixes: clearer visual cues, better text sizing, and small layout adjustments. Improving these details would make the experience more accessible for all users without compromising the brand’s style.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71790986bcf0" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/evaluating-the-user-experience-of-zaras-online-store-71790986bcf0">Evaluating the User Experience of Zara’s Online Store</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Job Hunting as a UX/UI Designer in 2025: What Worked for Me and What Didn’t]]></title>
            <link>https://uxplanet.org/job-hunting-as-a-ux-ui-designer-in-2025-what-worked-for-me-and-what-didnt-61f15c75fbc6?source=rss-7704cdc1736------2</link>
            <guid isPermaLink="false">https://medium.com/p/61f15c75fbc6</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[job-search]]></category>
            <dc:creator><![CDATA[Zarina Majidova]]></dc:creator>
            <pubDate>Thu, 21 Aug 2025 07:01:39 GMT</pubDate>
            <atom:updated>2026-07-23T03:43:35.186Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been job hunting for a little over two months. The first month, I focused on updating my portfolio and case studies. The second month was filled with interviews: 10 companies and more than 25 interviews in total, since most had multiple rounds.</p><p>Eventually, I received 3 offers. One was verbal but didn’t move forward because of timing, and 2 were official. I also stopped interviewing with 2 other companies once I accepted the offer, so maybe it could have been more. I accepted the offer that made the most sense for me and didn’t require moving out of state.</p><p>I’m sharing what helped me in this journey and what didn’t, in case it’s useful to anyone going through the same thing. The process can be overwhelming, discouraging, and exhausting. If you’re currently searching, I hope spending 10 to 15 minutes reading this can save you some time and frustration. Just a heads-up: there is some complaining, probably more than you expect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GMsrdtF7xGXQCLv8.png" /><figcaption>Image Source: UX Collective</figcaption></figure><h3><strong>What DID NOT work</strong></h3><p>One of the first things people say when you’re job hunting is: “You have to network! Reach out to people! Ask for referrals!” But to be honest, none of that worked for me and as an introvert, it felt like torture at times. So let’s break them down:</p><h4><strong>1. Networking events</strong></h4><p>I went to 3 of them, and each one felt like a total waste of time. They were marketed as great opportunities to make connections, but in reality, I mostly ran into:</p><ul><li><strong>People who only wanted to talk about themselves</strong>, how important they are, and what they’ve achieved without asking a single thing about me. It felt rude to interrupt, so I just stood there listening to things I didn’t even understand or care about. At one of those events, my friend got trapped by someone lecturing her on the syntax of a coding language that stopped being relevant in the early 2000s. They went on for an hour.</li><li><strong>People on a mission to meet everyone</strong>, who quickly introduced themselves, followed me on LinkedIn, and then immediately moved on to the next person. They treat the event like a checklist, just another way to pad their LinkedIn with more “connections.”</li><li><strong>Startup founders, </strong>who<strong> </strong>are looking for people to work for free in exchange for equity in their next big idea. It is usually something like “Uber, but for books” or “a dating app, but different.” Sure, in theory it could work, but in practice you will probably end up on endless video calls about half-baked ideas, maybe crank out some app designs, and then watch everyone drop it in a month or two. The truth is, only about 1-2% of startups get venture funding after they have built an actual product, if that. At the pure idea stage, the odds are probably lower than 0.1%. Whether you want to gamble on that is your call.</li><li><strong>Students or new grads</strong> who were trying to impress or hoping I was hiring. That’s completely fine and understandable, but as a job seeker myself, I wasn’t in a position to help.</li><li><strong>That person from a big-name company</strong> who made working there their entire personality. You know the type. They are almost ready to tattoo the company logo on their forehead. (I actually met someone who tattooed the company logo on their arm.) Every sentence starts with “We at [company] do it differently” and every 2 minutes they “have to” remind you they work there, just in case you forgot it in the last 120 seconds. They constantly repeat how “special” they are because they were “chosen out of thousands of applicants.” I think those people attend these events just to boost their egos.</li><li><strong>Salespeople</strong>, usually realtors, who just hand out business cards and try to pitch homes to people attending the event.</li><li><strong>Creeps.</strong> Sadly, this happened too. After one event, a man followed my friend and me to our car, then found us on Instagram and started messaging us.</li></ul><p>If you’ve had better experiences, that’s great, but for me, networking events were exhausting and unproductive.</p><h4>2. Cold messaging recruiters or hiring managers on LinkedIn</h4><p>I’m almost sure most, if not all, recruiters hate this. Everyone does it, which means their inboxes are flooded with hundreds of similar messages. Even if you put in the effort to write something personalized and thoughtful, there’s a good chance it will never be opened. Most of the time, you’ll either be ignored or politely brushed off.</p><p>The last thing you need during a job search is seeing your message left unread or “seen” with no reply. LinkedIn often suggests reaching out to people from your school or mutual connections who work at the company. I tried that too, and it never led to anything useful.</p><h4><strong>3. Tailor your resume for every job</strong></h4><p>This is one of the most common pieces of advice you’ll hear, but it’s not the magic solution people make it out to be. Yes, tailoring your resume can sometimes help, but doing it for every single application takes a huge amount of time and there’s no guarantee a real person will even see it once it goes through the ATS.</p><p>I tried customizing my resume for each role for a full week and didn’t notice any real difference in the number of responses I received. If you have extra time and want to give it a try, go for it. But for me, it was just waste of time. My time was better spent improving my portfolio and focusing on the volume of applications instead of endlessly tweaking my resume.</p><h4><strong>4. Mass applying with AI tools</strong></h4><p>I didn’t personally try this approach, but I’ve seen others use it. It seems efficient at first. You upload your resume, set filters, and apply to dozens of jobs in a few clicks. But in reality, most of those applications end up stuck in ATS systems and are never seen by a real person, especially if your resume doesn’t closely match the job description.</p><p>The roles are often not a good fit, and there’s no personalization. Recruiters can usually tell, and it makes your application easy to overlook. On top of that, many of these tools charge you, but don’t deliver any results.</p><p>One of the biggest issues is that these tools make it easy for people to apply to jobs they’re not qualified for. As a result, job postings receive hundreds or even thousands of applications, many of which are irrelevant. This makes it harder for qualified candidates to stand out, and it overwhelms recruiters who are already short on time. It might work occasionally, but from what I’ve seen, it mostly leads to frustration and wasted effort.</p><h3>What WORKED</h3><p>Now I want to share a few things that actually worked for me. I can’t say which one played the biggest role, because I applied them all more or less at the same time.</p><p>I don’t want to disappoint anyone, but there’s no shortcut or secret formula, despite what many “career coaches” promise. One of the most frustrating parts of job hunting is how quickly the algorithm floods your feed with ads from career coaches &amp; LinkedIn gurus. They promise a dream role if you just buy their course, post staged thank-you notes from “clients,” and churn out LinkedIn posts with fake screenshots, vague success stories, and “Comment YES for my guide” traps. The “secret guide” is always the same recycled fluff: write a cold email, mention something from their profile, add a compliment. Some even go to extremes, suggesting you “bump into” the CEO with your résumé in hand. Their goal is to funnel you into a $300 course teaching you how to write a résumé and say “thank you” after interviews. They prey on people who are already drained and make you feel like you’re missing a shortcut.</p><p>Enough complaining and here are the things that really helped me. Some are specific to design roles, but many can be applied to other jobs as well.</p><h4><strong>1. Optimizing my resume for ATS</strong></h4><p>One of the biggest improvements I made was making my resume more ATS-friendly. A few things that helped me:</p><ul><li>Review multiple job postings in your field and location, note the skills and requirements that come up most often, and include them in your resume exactly how they are listed if they apply to you. Most recruiters rely on ATS or AI tools to filter applications, so your resume needs to clearly mention them to get flagged. You are basically helping the ATS understand that you are a good fit.</li><li>The idea that resumes should always stay on one page has been outdated for at least a decade. It’s funny how people share Elon Musk’s resume as an example: “The richest man on Earth has a one-page resume while an intern at JP Morgan has a three-page one.” But you have to understand that his resume is short because he does not need to look for jobs or pass ATS systems. Realistically, he does not need a resume. Trimming too much for brevity can actually hurt you because the system may not recognize that you are qualified. And if you are reading this, unlike Elon Musk, you probably need the ATS to recognize that you are. My point is, 2 or even 3 pages are completely fine as long as the content is relevant and well-organized.</li><li>Pay attention to formatting. Use a layout that ATS systems can parse easily. A beautifully designed resume in Figma may look impressive, but if the system cannot read it properly, it will not help you.</li><li>Add important links as full URLs instead of hyperlinking words. ATS systems can miss embedded links. This also helps platforms like Workday prefill forms more accurately during applications saving you a lot of time.</li></ul><h4><strong>2. Redesigning my portfolio</strong></h4><p>As a designer, the chances of getting a job without a presentable portfolio are very low. I used to host mine on Behance, mostly showing the interfaces I designed without going into much detail about the process. Over time, I realized it wasn’t flexible enough and didn’t really represent me as a product designer. I wanted something more personal, something that could highlight my thought process and give people a better sense of who I am.</p><p>I knew I needed my own website, but I had avoided it for years because I wasn’t comfortable with no-code tools. They felt too limited, too expensive, and not enjoyable to work with. This might work well for others, but as someone used to Figma’s flexibility and intuitive interface, I couldn’t get past the restrictions.</p><p>Figma announced Figma Sites at Config 2025. Since I already was an advanced Figma user, learning the new feature came naturally. After spending 8-10 hours a day for about 5 days, I launched my portfolio website. I’ve been updating it ever since, adding projects, refreshing content, and experimenting with styles and animations. It’s still evolving. You can see it here: <a href="https://www.zarinamajidova.com/">zarinamajidova.com</a>.</p><p>Having a Behance or Dribbble portfolio is still better than nothing, but your own website gives you far more freedom to present your work the way you want.</p><h4><strong>3. Showing my design process, not just the final results</strong></h4><p>People have very different opinions about what a design portfolio should look like. Almost every day, I see posts on LinkedIn telling designers exactly what to do. Some say, “No one wants to see your sketches or travel photos.” Others say, “Don’t just show the final screens, show how you solve problems.” Some even claim portfolios are useless. Most of these people aren’t even designers, and the ones who are rarely share their own portfolios. The truth is, if you try to follow every piece of advice, you’ll just end up confused.</p><p>As a product and UX designer, I believe showing your process is just as important as showing the final design. The final screens show what you created, but the process shows why you created it that way. It explains your thinking, how you approach problems, and the reasoning behind your design decisions. Anyone can put together nice-looking screens, but if your research and analysis clearly explain your choices, that belongs in your portfolio.</p><p>In almost every interview I’ve had, I’ve been asked about my design process, how I start, how I make decisions, how I collaborate, and how I hand off work to developers. That’s what hiring teams care about, so your portfolio should reflect that too.</p><h4><strong>4. Showing the impact of my work</strong></h4><p>This one can be tricky, not every project gives you the chance to measure impact with data. Some projects don’t even go live. But there are still different ways to show the results of your work.</p><ol><li><strong>Use data, if available<br></strong> If you have access to metrics, include them. For example: “Redesigned the onboarding flow, reducing drop-off by 20%”, “Improved product page layout, resulting in 12% fewer returns”</li><li><strong>Share usability testing results<br></strong> If there’s no product data, usability testing can show how effective your design is. Even testing with just 5 users is valuable. You can say something like: “4 out of 5 users were able to complete the task without help”</li><li><strong>Highlight indirect impact<br></strong>In startup projects, maybe your design helped secure funding or attract new users. That’s still meaningful impact, even without formal data or testing.</li><li><strong>Reflect on personal projects<br></strong>If it’s a conceptual or self-initiated project, show what you learned. Key takeaways, challenges you solved, or new methods you tried can help demonstrate problem-solving.</li></ol><p>No matter the type of project, choose the best way to show how your design made a difference.</p><h4><strong>5. Applying consistently</strong></h4><p>You might hear some people say applying online doesn’t work anymore and that your only chance is to network and reach out to people. But in my experience, it was the opposite. For over a month, I applied to 5–10 positions every day and got interviews with 10 different companies through online applications, yet not a single one came from cold emails/messages or networking events.</p><p>That said, most applications get stuck in the ATS and are never seen by a real person. You’ll get auto rejections, recruiters who reach out and then disappear, or emails with follow-up questions that go nowhere. It’s frustrating, and I know we’re all tired of hearing, “It’s not you, it’s the system.” But in this case, it really is the system. Rejections don’t define your value as a designer or as a person.</p><h4><strong>6. 30-45 second intro for each interview</strong></h4><p>Even after doing many interviews, I still felt nervous at the start of each one. The first few minutes set the tone and shape how the interviewer perceives you. That’s why I prepared a short intro script I could use and adjust as needed.</p><p>Most interviews start with “Tell me about yourself,” so having a clear answer makes a big difference. You can use a simple structure like this:</p><blockquote><em>I’m </em><strong><em>[First name, Last name]</em></strong><em>, a </em><strong><em>[Your title, e.g., Product and UX/UI Designer]</em></strong><em> with </em><strong><em>[X years]</em></strong><em> of experience designing for </em><strong><em>[industries or domains]</em></strong><em>. One project I’m especially proud of is </em><strong><em>[Your best project]</em></strong><em>, which </em><strong><em>[brief impact or result, ideally with numbers]</em></strong><em>. I’m excited about the opportunity at </em><strong><em>[Company name] </em></strong><em>because </em><strong><em>[1–2 reasons why you’re interested, aligned with their mission, product, or design culture]</em></strong><em>.</em></blockquote><p><strong>Example:</strong></p><blockquote>I’m Alex Chen, a product designer with 5 years of experience in e-commerce and edtech. One project I’m proud of is redesigning the mobile checkout for ShopNow, which reduced cart abandonment by 22% and increased completed purchases by 15%. I’m excited about this role at Duolingo because I admire your focus on playful, user-centered learning and want to design experiences that make language learning feel effortless.</blockquote><p>This structure worked well for me in almost every interview. It’s straightforward, adaptable, and helps you sound confident without feeling scripted.</p><p>If you want to learn more about UX design interviews and how to prepare for them, I wrote <a href="https://medium.com/design-bootcamp/inside-the-ux-and-product-design-interview-from-recruiter-call-to-final-offer-00a6dac21cea">an article covering what to expect</a> at each stage. Check it out!</p><p>I recognize that the strategies that didn’t work for me may be effective for others and what worked for me might not apply to everyone. My goal in sharing this is to offer a personal perspective that might support others navigating their own job search.</p><p>The process can be challenging and, at times, discouraging. Between automated rejections, unanswered follow-ups, and prolonged silence, it’s easy to feel disheartened. But it’s important to remember that these responses often reflect flaws in the system, not in your abilities or value as a professional.</p><p>Stay focused, keep refining your approach, and don’t take the process personally.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61f15c75fbc6" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/job-hunting-as-a-ux-ui-designer-in-2025-what-worked-for-me-and-what-didnt-61f15c75fbc6">Job Hunting as a UX/UI Designer in 2025: What Worked for Me and What Didn’t</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Usability Testing Metrics and How to Use Them]]></title>
            <link>https://uxplanet.org/usability-testing-metrics-and-how-to-use-them-2b77cb353793?source=rss-7704cdc1736------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b77cb353793</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Zarina Majidova]]></dc:creator>
            <pubDate>Sun, 17 Aug 2025 08:13:48 GMT</pubDate>
            <atom:updated>2026-05-14T21:47:48.964Z</atom:updated>
            <content:encoded><![CDATA[<p>Usability testing should always be part of product development. Ideally, it is conducted before release, but in practice it can be useful at different stages. It’s worth pointing out that, testing isn’t a goal in itself. Without knowing exactly what you want to measure, you risk ending up with feedback you can’t interpret or act on.</p><p>Every usability study can focus on a different aspect of the experience, and the right metrics depend on your research goals. This article outlines some of the most common usability testing metrics and how they can be applied in practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LrrEeg-AKr9UCWQa.jpg" /><figcaption>Image Source: Unsplash</figcaption></figure><h3>Scenario</h3><p>To make the following metrics easier to follow, let’s use a single scenario throughout:</p><p><strong><em>Suppose your team has just released a new “Add to Wishlist” feature in an e-commerce app. You want to understand whether users can find and use it without confusion.</em></strong></p><p>For this, you recruit 5 participants and give them realistic tasks, such as <em>“Find a product you like and add it to your wishlist.”</em> As we go through the metrics, we’ll refer back to this example to see how each measurement works in practice.</p><h4>1. Task Success Rate</h4><p>Task success rate is the most widely used and arguably the most important usability testing metric. It’s a simple yes-or-no measure: <strong>were participants able to complete the task or not?</strong></p><p>Most product teams often set a benchmark for this metric, such as requiring at least 80% of participants to succeed before a feature is considered ready for launch. The exact threshold depends on the product, its complexity, and how critical the task is.</p><p>In our example, the task is: <em>“Find a product you like and add it to your wishlist.”</em> If 4 out of 5 participants complete it successfully, your task success rate is 80%. If only 2 succeed, you know the design needs improvement before release.</p><h4>2. Time on Task</h4><p>Time on task measures <strong>how long it takes participants to complete the task</strong>. Even if users eventually succeed, taking too long can be just as problematic as failing altogether.</p><p>Teams often set benchmarks for how much time a task should reasonably take. For simple interactions, the expectation might be less than a minute. If participants consistently take 5 or more minutes, you can assume that real users who are far less patient in wild would likely give up before finishing.</p><p>In our wishlist example, you might expect users to spot the “Add to Wishlist” button within 5 seconds of opening a product page. If a participant spends a full minute scanning the screen before finding it, that’s a clear signal the feature isn’t obvious enough.</p><p>When documenting this metric, run a timer during each attempt. For example:</p><ul><li>Participant 1: 10 seconds</li><li>Participant 2: 70 seconds</li><li>Participant 3: 18 seconds</li></ul><p>Time on task is also useful for tracking learning curves. For example, a participant might need 70 seconds on their first attempt, but only 30 seconds the second time. The difference shows how quickly users adapt, which is valuable for features that require repeat usage.</p><h4>3. Error Rate</h4><p>Error rate tracks <strong>how often participants make mistakes while completing a task</strong>. A task can still be completed successfully, but if users stumble through errors along the way, that’s a sign the design isn’t intuitive.</p><p>Errors can include things like:</p><ul><li>Clicking the wrong button</li><li>Misinterpreting an icon or label</li><li>Navigating to the wrong screen before correcting themselves</li><li>Repeatedly trying an action that doesn’t work</li></ul><p>In our wishlist example, the task is: <em>“Find a product you like and add it to your wishlist.”</em> Suppose one participant tries tapping the product image itself instead of the “Add to Wishlist” icon, or another participant keeps adding the item to favorites instead of wishlist. Even if they eventually manage to add an item to the wishlist, those detours count as errors.</p><p>To document this metric, you simply note down the mistakes for each participant. For example:</p><ul><li>Participant 1: 2 errors (tapped product image, opened cart)</li><li>Participant 2: 0 errors</li><li>Participant 3: 1 error (confused by unlabeled heart icon)</li></ul><p>High error rates suggest that users are guessing. Even if task success and time on task look acceptable, frequent errors reduce long-term satisfaction with the product.</p><h4>4. Number of Assists</h4><p>The number of assists measures <strong>how often a facilitator or moderator needs to step in and help a participant complete a task</strong>. In an ideal world, participants should be able to figure things out on their own. Every time you have to explain, clarify, or point something out, it signals a usability issue.</p><p>In our wishlist example, the task is: <em>“Find a product you like and add it to your wishlist.”</em> If a participant stares at the screen for over a minute and finally asks, <em>“Where is the wishlist button?”</em> and you have to show them counts as an assist.</p><p>Documenting this is simple:</p><ul><li>Participant 1: 0 assists</li><li>Participant 2: 1 assist (needed help locating the icon)</li><li>Participant 3: 2 assists (asked what “wishlist” means, then couldn’t find the button)</li></ul><p>Tracking assists is valuable because it shows where users would likely get stuck in real-world conditions where no one is there to guide them. Even if task success looks high, a design that depends heavily on assistance isn’t usable in practice.</p><h4>5. Path Deviation</h4><p>Path deviation measures <strong>how closely participants’ actions match the intended or optimal path</strong> you designed for completing a task. In other words, it tracks the detours users take.</p><p>A task can still be completed successfully, but if participants wander through unnecessary screens, click unrelated elements, or backtrack multiple times, it suggests your design isn’t guiding them clearly enough.</p><p>In our wishlist example, the optimal path might be:</p><ol><li>Open a product page</li><li>Click the “Add to Wishlist” button</li></ol><p>If a participant instead goes:</p><p>Home page → Cart → Back to Home → Product page → Add to Wishlist, that’s a path deviation. They got there in the end, but the extra steps reveal friction.</p><p>You can document this by mapping each participant’s actual path and comparing it to the intended one. For instance:</p><ul><li>Participant 1: Followed optimal path (0 deviations)</li><li>Participant 2: Went to Cart first (1 deviation)</li><li>Participant 3: Opened Search → Home → Product page → Wishlist (2 deviations)</li></ul><p>High deviation rates don’t always mean failure, but they do show where your design is misleading.</p><h4>6. Perceived Ease of Use</h4><p>Perceived ease of use is a simple attitudinal metric: after completing a task, you ask participants <strong>“On a scale of 1 to 10, how easy or difficult was this task?”</strong> The score reflects their subjective impression.</p><p>For example, after asking participants to add an item to their wishlist, you might collect ratings like:</p><ul><li>Participant 1: 9</li><li>Participant 2: 7</li><li>Participant 3: 5</li></ul><p>You can then calculate the average across all participants. Many teams set a minimum threshold (for example, an average of 6.5 or higher) as a goal.</p><p>This metric matters because people’s perception of difficulty often shapes their willingness to return. Even if they succeed quickly, if they <em>feel</em> the task was confusing, they’re less likely to trust or enjoy using the feature.</p><h4>7. Error Recovery Rate</h4><p>Error recovery rate measures <strong>how often participants are able to recover from mistakes on their own</strong> during a task. This metric shows whether users can recognize the error and fix it without external help.</p><p>In our wishlist example, a participant might first tap the shopping cart instead of the “Add to Wishlist” button. If they realize the mistake, go back, and then successfully add the product to the wishlist, that counts as an error recovery. If they get stuck or abandon the task, that’s a failed recovery.</p><p>You can document this by tracking errors alongside recovery attempts:</p><ul><li>Participant 1: 2 errors, 2 recoveries (100% recovery rate)</li><li>Participant 2: 1 error, 0 recoveries (0% recovery rate)</li><li>Participant 3: 3 errors, 2 recoveries (67% recovery rate)</li></ul><p>An important detail is whether users even notice they’ve made an error. If they don’t realize it, that can be a serious problem. For example, if someone taps “Add to Wishlist” but nothing happens and they assume it worked, you need to make the interaction clearer.</p><p>It’s also worth noting that error recovery isn’t equally critical for every product. For some apps, a missed wishlist item isn’t the end of the world. But in domains like financial services, healthcare, or insurance, making sure users immediately recognize and recover from errors is essential.</p><h4>8. Confidence Level</h4><p>Confidence level measures <strong>how confident participants feel about the actions they took during a task</strong>. Even if they completed it successfully, a low confidence score suggests they weren’t sure they did the right thing which often translates into hesitation or second-guessing in real use.</p><p>This is typically measured by asking a simple post-task question like:<br> <em>“On a scale of 1 to 5 (or 1 to 10), how confident are you that you completed the task correctly?”</em></p><p>In the wishlist example, a participant might add an item but not see a confirmation message or clear animation. As a result, they think, <em>“I’m not sure if it worked.”</em> That’s a low confidence score, even though technically the item was added. Another participant might click <strong>“Add to Favorites”</strong> instead of <strong>“Add to Wishlist”</strong> and believe they succeeded. In that case, confidence might be high, but the task success rate is actually a failure because they didn’t complete the correct action.</p><p>Documenting this can look like:</p><ul><li>Participant 1: Confident (9/10)</li><li>Participant 2: Unsure (4/10, didn’t notice confirmation)</li><li>Participant 3: Confident but incorrect (8/10, used Favorites instead of Wishlist)</li></ul><p>Confidence level is valuable because it reveals gaps between what users think happened and what actually happened. Low confidence often points to poor feedback or unclear system status. False confidence exposes mislabeling or misleading design choices. Both are signals to refine clarity and trust in the interface.</p><h3>Documenting Usability Metrics</h3><p>Collecting the data is only half the job. Documenting it in a consistent, readable way is just as important. You don’t need specialized software. Simple spreadsheets, Notion tables, or even pen and paper all work.</p><p>Here’s an example of how a simple table might look:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p9u4UWHWgbWakz3EadK0gQ.png" /><figcaption>Notion table</figcaption></figure><p>For usability testing with a larger number of participants, it can also be useful to record demographics such as age, gender, or level of digital experience. This helps you see whether certain usability issues correlate with specific groups. For example, adding an item to a wishlist may feel completely natural for Gen Z participants but less intuitive for Gen X, revealing design assumptions that might exclude part of your audience.</p><p>Usability testing metrics turn observations into actionable insights. The key is to focus on the ones that align with your goals, document them consistently, and look for patterns across participants.</p><p>If you’d like to dive deeper into strategies for running stronger usability studies, check out my article: <a href="https://medium.com/design-bootcamp/5-ways-to-improve-your-usability-studies-8033b88f9fd0">5 Ways to Improve Your Usability Studies</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b77cb353793" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/usability-testing-metrics-and-how-to-use-them-2b77cb353793">Usability Testing Metrics and How to Use Them</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Designer’s Guide to WCAG Accessibility]]></title>
            <link>https://uxplanet.org/a-designers-guide-to-wcag-accessibility-15d96b3ff09f?source=rss-7704cdc1736------2</link>
            <guid isPermaLink="false">https://medium.com/p/15d96b3ff09f</guid>
            <category><![CDATA[wcag]]></category>
            <category><![CDATA[wcag-guidelines]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Zarina Majidova]]></dc:creator>
            <pubDate>Wed, 16 Jul 2025 05:25:32 GMT</pubDate>
            <atom:updated>2026-05-07T16:57:09.336Z</atom:updated>
            <content:encoded><![CDATA[<p>Accessibility is a core part of creating inclusive, effective design. One of the most widely recognized standards in this area is WCAG. But what exactly is WCAG, and why does it matter for designers?</p><p>WCAG stands for Web Content Accessibility Guidelines. It was first published by the W3C’s Web Accessibility Initiative (WAI) in 1999, with major updates in WCAG 2.0 (2008), 2.1 (2018), and the latest WCAG 2.2 (2023). These guidelines set the international standard for making web content more accessible to people with all abilities (Thanks, Wikipedia!).</p><p>You can find the official documentation here: <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">WCAG 2 Overview</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_IOeeMBr0WMwRnX5k55B1w.jpeg" /><figcaption>Source: <a href="https://accessibilityspark.com/wcag-navigation-pattern/">Accessibility Spark</a></figcaption></figure><p>The official language is written with developers in mind, and it can take a lot of time to interpret and translate it into practical steps for design. I’ve done the hard part for you! Here is your WCAG-based accessibility checklist you can keep in mind while designing any product:</p><h3>1. Color Contrast</h3><p>Getting contrast right is one of the fastest ways to make your designs more accessible. Here are the minimum contrast ratios according to WCAG guidelines:</p><p><strong>Text vs. background:</strong><br> • Normal text: at least 4.5:1<br> • Large text (≥18pt regular or ≥14pt bold): at least 3:1</p><p><strong>UI component</strong>s (icons, borders, form fields, etc.): at least 3:1</p><p>Before you hand off your designs (I recommend doing it at early stages of the design process), quickly test your color combinations. There are several Figma plug‑ins you can use. A super handy tool is the <a href="https://webaim.org/resources/contrastchecker/">WebAIM Contrast Checker</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VpitFyFxBxdSdfBfytyyrw.png" /><figcaption>Source: Halo Lab</figcaption></figure><h3><strong>2. Focus Styles (Visible Focus)</strong></h3><p>Making focus visible is a key part of designing for keyboard and assistive‑technology users. In your interface, the focused element should stand out visually. For example, a button might show a bold outline, a link might get an underline, or a form field might glow with a clear highlight when it’s active. This lets users instantly see where they are on the screen as they navigate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*-mKCKJuE4qtAOqLvb9Hh5Q.png" /><figcaption>Source: Material 3 UI</figcaption></figure><h3><strong>3. Target Size</strong></h3><p>Interactive elements need to be easy to hit, especially on touch devices. Interactive areas (buttons, links, icons, checkboxes, etc.) should be at least <strong>24×24 px </strong>(According to WCAG 2.2). If your icon or element is smaller than that, add extra padding or spacing around it. This helps users with motor challenges and makes your design more touch‑friendly overall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bq35ZF_VKpcnxHTl.jpg" /><figcaption>Source: <a href="https://www.accessguide.io/">Access Guide</a></figcaption></figure><h3>4. Clear Labels &amp; Instructions</h3><p>Buttons, icons, and form controls should have clear, descriptive labels, not just vague icons. For example, use “Download PDF” instead of only a down arrow. Icons can mean different things in different cultures or contexts. A star might represent rating or favorite depending on the situation, so do your best to pair icons with clear text labels.</p><h3>5. Keyboard Navigation (Logical Focus Order)</h3><p>This is mostly handled by developers, but it’s important for designers to understand. When someone navigates using only a keyboard (pressing Tab), focus should move through interactive elements in the same order they appear visually. Focus should follow a predictable, top‑to‑bottom, left‑to‑right flow.</p><p>Good example: Name field → Email field → Submit button</p><p>Bad example: Name field (left column) → Submit button (bottom right) → Email field (back up left)</p><h3>6. Error Identification &amp; Suggestions</h3><p>When a user makes a mistake in a form, make sure the error is easy to notice and understand. Show a clear error message near the field and explain how to fix it. Use both text and visual indicators, not just color like red alone. For example, include an icon and helpful copy such as “Password must be at least 8 characters.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2J2PWTGKtpA84mos" /><figcaption>Source: HBO Max login</figcaption></figure><h3>7. Consistent Navigation</h3><p>Repeated elements such as menus, headers, and footers should stay in the same place across all screens. Avoid changing menu layouts from page to page unless it is absolutely necessary.</p><h3>8. Avoid Traps</h3><p>Make sure users can always move forward, go back (where relevant) or exit an element. For example, if you use a modal window, include a clear “Close” button or an “X” in the corner so users can easily leave it. Users should not feel stuck with no way out.</p><h3>9. Motion Sensitivity</h3><p>Avoid motion effects that might cause dizziness, nausea, or even seizures for some users. Respect operating system settings like “Reduce Motion,” and give users a way to turn off animations. For example, avoid parallax scrolling, automatic carousels, or looping animations unless the user can pause or control them.</p><h3>10. Error Prevention (for complex tasks)</h3><p>For important actions like submitting a form or making a payment, help users avoid mistakes. Include a confirmation step, an option to undo, or a clear review screen before final submission. For example, use a progress indicator and a “Review Your Order” page so users can double‑check details before completing the task.</p><p>By considering these WCAG principles early in your design process, you will create products that work for more people, in more situations, with less friction.</p><p>Use this checklist as a starting point and keep learning, testing, and refining. Every pixel, label, and interaction you design has the power to include or exclude. Let’s make sure we’re designing for everyone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15d96b3ff09f" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/a-designers-guide-to-wcag-accessibility-15d96b3ff09f">A Designer’s Guide to WCAG Accessibility</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I Learned from Designing a Product Used by 4 Million People Daily]]></title>
            <link>https://uxplanet.org/what-i-learned-from-designing-a-product-used-by-4-million-people-daily-1ebe5dbc2d48?source=rss-7704cdc1736------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ebe5dbc2d48</guid>
            <category><![CDATA[mobile-app-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Zarina Majidova]]></dc:creator>
            <pubDate>Sat, 24 May 2025 01:41:15 GMT</pubDate>
            <atom:updated>2025-05-27T08:24:45.977Z</atom:updated>
            <content:encoded><![CDATA[<p>When you’re working on a product used by millions on a daily basis, creativity starts to look a little different. It’s no longer about what’s trendy or what makes your portfolio pop, it’s about reliability, trust, and small decisions that quietly scale. You’re designing for everyone: the 21-year-old who grew up with apps (literally), the 72-year-old who finally downloaded app with their grandchildren’s help, and everyone in between.</p><p>Here’s what I’ve learned and what I wish someone had told me when I started designing for large-scale systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aACpMJ1KEPPj_7Bs.png" /><figcaption>Image source: <a href="https://kodytechnolab.com/blog/mobile-app-design-process/">Kody Technolab</a></figcaption></figure><h4><strong>1. Don’t Mess with Muscle Memory</strong></h4><p>Even if your new design is more logical or beautiful, users won’t see it that way if it breaks what they’re used to. If someone’s been tapping the “+” button in the top corner for years, suddenly moving it to the bottom right closer to the thumb doesn’t feel like an improvement. At this scale, intuition matters less than habit.</p><h4><strong>2. Roll Out Changes Gradually</strong></h4><p>One of the worst things you can do is drop a full redesign overnight. Users open the app expecting a 5 second familiar task and end up lost in a new layout. Big changes should feel almost invisible. Test, observe, and phase them in piece by piece. Give people time to adapt, especially when they use your product daily.</p><h4><strong>3. Work with Qualitative Researchers</strong></h4><p>Numbers will tell you what’s happening. Qualitative research tells you why. You might notice a high drop-off rate at a certain point in the sign-up flow and start assuming why it’s happening. But don’t (honestly don’t). Just ask!</p><p>Team up with UX researchers early and often. When you’re dealing with millions of users, you need to hear from everyone, not just the vocal early adopters. Context is everything.</p><h4><strong>4. Keep a Human Feedback Loop Alive</strong></h4><p>Have a group of <strong><em>design partners</em></strong>, people from different age groups, tech comfort levels, and accessibility needs. Talk to them regularly. Test ideas with them before launch. They’ll surface friction points no dashboard can show you. Design shouldn’t live in a Figma file or inside your team’s Slack. If you’re not familiar with working with design partners, here’s an <a href="https://www.unusual.vc/articles/what-are-design-partners">article</a> that covers everything you need to know.</p><h4><strong>5. Get Out of the Way</strong></h4><p>Yes, animations are fun and illustrations can create warmth. But at scale, the most respectful thing you can do is get out of the user’s way. The best interface is one that helps them do what they came to do, nothing more, nothing less. Save the glossy moments for when they actually add clarity or calm. Most of the time, users just want to get things done.</p><p>Designing for scale forces you to let go of ego. You’re not here to impress, you’re here to support. It’s less about being a trendsetter and more about being invisible, reliable, and relentlessly user-focused. I still love designing bold, expressive interfaces, but now I know when to let them shine, and when to let them disappear.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ebe5dbc2d48" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/what-i-learned-from-designing-a-product-used-by-4-million-people-daily-1ebe5dbc2d48">What I Learned from Designing a Product Used by 4 Million People Daily</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>