<?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 Hamzarashid on Medium]]></title>
        <description><![CDATA[Stories by Hamzarashid on Medium]]></description>
        <link>https://medium.com/@hamzarashid3214?source=rss-ef2ed96b7b85------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*6Qee8nAil0ZSoP-Y</url>
            <title>Stories by Hamzarashid on Medium</title>
            <link>https://medium.com/@hamzarashid3214?source=rss-ef2ed96b7b85------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:12:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hamzarashid3214/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[Why the “3-Click Rule” Is a Lie]]></title>
            <link>https://medium.com/@hamzarashid3214/why-the-3-click-rule-is-a-lie-1950f5a38486?source=rss-ef2ed96b7b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/1950f5a38486</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Hamzarashid]]></dc:creator>
            <pubDate>Sat, 19 Sep 2026 21:38:18 GMT</pubDate>
            <atom:updated>2026-09-19T21:38:18.642Z</atom:updated>
            <content:encoded><![CDATA[<h3>It’s not about how many times a user clicks; it’s about how much thinking each click requires.</h3><p>When i first started learning web design, one of the first rules i kept seeing everywhere was the famous “Three-Click Rule.”</p><p>People on design forums, YouTube tutorials, and medium articles would repeat it like gospel: <em>A user should never have to click more than three times to find anything on your website.</em></p><p>Because i took that rule so seriously, i ended up making terrible design choices in my early Figma mockups. I was so terrified of making the user click three or four times that i would cram twenty different options, submenus, and categories directly onto one single screen. I thought i was being helpful, but i was actually just creating a cluttered mess that overwhelmed everyone.</p><p>Chapter 4 of <em>Don’t Make Me Think</em> completely cured me of this obsession.</p><p><strong>Krug’s Second Law of Usability</strong></p><p>Steve Krug drops this truth bomb right at the start of the chapter:</p><p><em>“It doesn’t matter how many times I have to click, as long as each click is a mindless, unambiguous choice.”</em> — Steve Krug</p><p>The number of clicks to get somewhere is actually a terrible metric on its own. What really matters is how much mental effort each click requires, and how confident the user feels while clicking it.</p><p>He compares a great user journey to following a “scent of information.” If every link you click clearly and unambiguously points to what you are looking for, you feel like you are getting closer to your goal. You don’t care if it takes three clicks, four clicks, or five clicks, because you never had to stop and think. It felt completely painless.</p><p>His rule of thumb is brilliant: <strong>Three mindless, unambiguous clicks equal one click that requires thought</strong>.</p><p><strong>Animal, Vegetable, or Mineral?</strong></p><p>To explain what an unambiguous choice looks like, Krug brings up the classic opening question from the game Twenty Questions: <em>“Animal, vegetable, or mineral?”</em></p><p>As long as you understand that anything that isn’t a plant or an animal falls under mineral, the choice is completely mindless. You don’t have to pause, debate with yourself, or scratch your head. You answer instantly.</p><p>Unfortunately, many choices on websites are nothing like that.</p><p>Krug shares an example of trying to buy a printer for his home office. When he goes to the manufacturer’s site, the first screen asks him to choose between two categories:</p><ul><li><strong>Small Business</strong></li><li><strong>Home Office</strong></li></ul><p>Suddenly, you have to stop and think. Which one am i? I work from home, but i run a small business. What happens if i click the wrong one? Will i miss out on the printer i need?</p><p>It feels like standing in front of two mailboxes labeled “Stamped Mail” and “Metered Mail” with a business reply card in your hand, having no idea which slot to drop it into.</p><p>That tiny hesitation is where usability breaks down. Even though it’s only one click, it creates doubt and mental fatigue.</p><p><strong>Don’t confront users with everything at once</strong></p><p>Another great example from this chapter is login screens and subscription forms.</p><p>A lot of sites make the mistake of showing three different complicated choices on a single page all at once:</p><ul><li><em>Already a magazine subscriber but not an online member? Enter your 8-digit code…</em></li><li><em>Already an online member? Log in here…</em></li><li><em>Not a member yet? Sign up here…</em></li></ul><p>When a user lands on a screen like that, they have to read through a wall of text just to figure out which bucket they belong in. And usually, right around that moment, their brain switches from <em>“How do i answer this?”</em> to <em>“Do i even care enough about this article to bother?”</em></p><p>Compare that to a design that breaks the decision into simple, sequential steps — showing only what is relevant to your first choice. Yes, it might add one extra click, but it removes 90% of the confusion.</p><p><strong>Just-in-time guidance</strong></p><p>Of course, some choices in life are genuinely complicated, and you can’t always make them completely mindless.</p><p>When you <em>must</em> present a difficult choice, Krug says you need to provide guidance, but that guidance has to follow three rules:</p><ul><li><strong>Brief:</strong> The smallest possible amount of information that helps.</li><li><strong>Timely:</strong> Appearing at the exact moment the user needs it, not three screens earlier.</li><li><strong>Unavoidable:</strong> Formatted so they actually see it.</li></ul><p>His favourite example of this is the signs painted directly on the street corners in London that say <strong>“LOOK RIGHT”</strong> with an arrow. It’s brief, it appears right where you step off the curb, and it saves tourists who are used to traffic coming from the other direction.</p><p><strong>The takeaway for my own work</strong></p><p>This chapter completely changed how i structure user flows in Figma.</p><p>I stopped trying to compress entire complex tasks into single screens just to keep the click count low. If a checkout process or onboarding flow needs four steps instead of two, that is completely fine — as long as each step is crystal clear and gives the user confidence that they are moving in the right direction.</p><p>Stop counting clicks. Start counting the friction inside each click.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1950f5a38486" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Billboard Design 101: Stop Trying to Reinvent the Wheel]]></title>
            <link>https://medium.com/@hamzarashid3214/billboard-design-101-stop-trying-to-reinvent-the-wheel-cb9f8b6c2373?source=rss-ef2ed96b7b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb9f8b6c2373</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Hamzarashid]]></dc:creator>
            <pubDate>Fri, 18 Sep 2026 16:22:29 GMT</pubDate>
            <atom:updated>2026-09-18T16:22:29.273Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Why following boring design conventions will save your users from getting lost.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F-UI1DnCYR7pAvfDGCstxA.png" /></figure><p>When you are just starting out as a designer, there is this massive temptation to make everything look unique. You want to prove that you have creative ideas. You see the standard ways things are done like navigation bars across the top, standard search boxes, and blue text links and you think, that’s so boring, i can make something much cooler than that.</p><p>So you try designing custom scrollbars or hiding navigation inside weird interactive circles, or using non-standard icons.</p><p>Chapter 3 of <em>Don’t Make Me Think</em> is a giant wake up call against that mindset. Krug explains that if your users are scanning your pages at billboard speed, you have to use techniques that work instantly.</p><p><strong>Conventions are your best friends</strong></p><p>Designers often resist conventions because they feel like they were hired to do something new, not repeat what everyone else is doing. But conventions did not appear out of nowhere they evolved over years because they work.</p><p>Think about stop signs in the physical world. Every stop sign has the same shape, the same red color, and the same position at an intersection. You don’t have to study it you recognize it instantly from 100 meters away in heavy rain.</p><p>Imagine renting a car and finding out that the brake pedal was moved to the left door just because the interior designer wanted to be creative. It would cause an immediate crash.</p><p>On the web, we have the exact same kinds of conventions:</p><ul><li>Logos belong in the top-left corner.</li><li>Primary navigation belongs across the top or down the left side.</li><li>The shopping cart icon represents purchases.</li><li>Search bars look like a simple input box with a magnifying glass or a button that says “Go”.</li></ul><p>When you follow these conventions, users don’t have to waste time figuring out how your interface works. They can immediately focus on the content.</p><p>Krug’s rule on this is gold: <em>Innovate when you know you have a genuinely better idea, but take full advantage of conventions when you don’t</em>. Don’t reinvent the wheel just for the sake of looking clever.</p><p><strong>Create a visual hierarchy that does the thinking for them</strong></p><p>When a screen has a good visual hierarchy, the user’s brain processes what is important without any conscious effort. A good visual hierarchy has three simple traits:</p><ol><li><strong>The more important something is, the more prominent it is:</strong> The most crucial headline should be bigger, bolder, or surrounded by more whitespace. If everything on the page is bold, nothing is bold.</li><li><strong>Things that are logically related are visually related:</strong> Group items together in clear boxes or cards with clean spacing.</li><li><strong>Things are visually nested:</strong> If items belong to a section, make it obvious that they sit inside that section.</li></ol><p>Think of a newspaper front page. You know the biggest news story before you read a single word because it has the largest headline right at the top. When a webpage lacks hierarchy, everything looks equally loud. It becomes visual noise, and the user is forced to scan every single word just to figure out where to start.</p><p><strong>Make it obvious what is clickable</strong></p><p>A huge part of what people do online is hunting for the next thing to click. If you make that hard, they get frustrated fast.</p><p>Ever since flat design became popular, so many websites started stripping away button borders and backgrounds. Suddenly, clickable buttons look identical to plain headings.</p><p>Users shouldn’t have to guess or move their mouse around to see if the cursor turns into a hand. Use clear button shapes, standard link styling, and distinct colors so there is never any doubt.</p><p><strong>Keep the noise down to a dull roar</strong></p><p>Krug talks about three different kinds of visual noise that ruin pages:</p><ul><li><strong>Shouting:</strong> When every element is trying to grab attention with bright badges, exclamation marks, and animations.</li><li><strong>Disorganization:</strong> When things are randomly aligned instead of sitting on a clean grid.</li><li><strong>Clutter:</strong> Squeezing way too much stuff into the screen, lowering what engineers call the “signal-to-noise ratio”.</li></ul><p>His advice here is brutal but necessary: assume everything on the page is visual noise until proven innocent. If an element isn’t actively helping the user accomplish their goal, remove it.</p><p><strong>Clarity trumps consistency</strong></p><p>We are always taught that consistency in UI is sacred. And for the most part, it is — keeping navigation in the same place across every page helps people feel safe.</p><p>But Krug points out a great exception: <strong>Clarity trumps consistency</strong>. If making an element slightly inconsistent makes the entire page significantly clearer, choose clarity every single time. Never sacrifice user clarity just to follow an arbitrary rule.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb9f8b6c2373" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Users Don’t Read Your Design. They Scan It at 60 Miles an Hour.]]></title>
            <link>https://medium.com/@hamzarashid3214/users-dont-read-your-design-they-scan-it-at-60-miles-an-hour-12e5f26cdc6e?source=rss-ef2ed96b7b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/12e5f26cdc6e</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Hamzarashid]]></dc:creator>
            <pubDate>Thu, 17 Sep 2026 17:12:52 GMT</pubDate>
            <atom:updated>2026-09-17T17:12:52.525Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S4RPTLz_DpSOPewf811Q1w.png" /></figure><h3><strong>The harsh reality of how people browse the web, and why designing for perfection is a waste of time.</strong></h3><p>When i started creating websites, i genuinely believed that people would appreciate the care i put into my writing. I would spend hours writing beautiful welcome blurbs, polishing introductory paragraphs, and making sure every feature had a detailed explanation right beside it.</p><p>I pictured the user sitting quietly at their desk, reading from top to bottom, admiring the typography, and carefully weighing all the options before clicking a button.</p><p>Chapter 2 of <em>Don’t Make Me Think</em> completely destroyed that fantasy for me.</p><p>Steve Krug points out that the difference between how designers think people use websites and how they <em>actually</em> use them is night and day. We design for “great literature” or a glossy brochure, but the user is actually looking at a billboard going by at 60 miles an hour.</p><p><strong>Fact 1: We don’t read pages. We scan them.</strong></p><p>One of the most proven facts about web use is that nobody reads every word. Instead, we scan.</p><p>Why do we do this?</p><ul><li><strong>We are usually on a mission:</strong> People go online to accomplish something, and they want it done fast. Krug says users act like sharks — they have to keep moving forward or they die. They don’t have time to read extra fluff.</li><li><strong>We know we don’t need everything:</strong> On any given screen, 90% of what is there is irrelevant to what we need at that exact second. We scan specifically to filter out the noise and find the one piece of information that matters.</li><li><strong>We’ve been doing it our whole lives:</strong> From newspapers to social media feeds, we are trained to skim until something catches our eye.</li></ul><p>Krug brings up this classic Gary Larson cartoon about what people say to dogs versus what dogs actually hear. The owner gives this long, serious speech to his dog Ginger about staying out of the trash, but all the dog hears is: <em>“blah blah blah GINGER blah blah blah GINGER.”</em></p><p>That is exactly how visitors treat our screens. They ignore our paragraphs and only latch onto trigger words that match their immediate task, like “Free”, “Login”, “Pricing”, or their own name.</p><p><strong>Fact 2: We don’t make optimal choices. We satisfice.</strong></p><p>When we design an interface, we assume the user will look at all the available links, compare them rationally, and pick the absolute best one.</p><p>In reality, we don’t pick the best choice — we pick the <em>first reasonable choice</em>. This concept is called “satisficing” (a mix of satisfying and sufficing). As soon as a user spots a link that looks like it might work, they click it.</p><p>Why don’t people look for the best option?</p><ol><li>We are in a hurry, and optimizing takes way too long.</li><li>There is almost no penalty for guessing wrong. If a link takes you to the wrong place, you just click the Back button. That’s why the Back button is the most clicked button in the entire web browser.</li><li>Weighing options doesn’t even guarantee success on a poorly organized site, so guessing is just as effective and way less effort.</li></ol><p><strong>Fact 3: We don’t figure out how things work. We muddle through.</strong></p><p>This was the most eye-opening part of the chapter for me. As designers and tech people, we love figuring out how things work under the hood. We assume regular people care about the logic of our system too.</p><p>They don’t. At all.</p><p>Most people use computers, apps, and websites every single day without having the slightest clue how they actually function. Krug mentions that if you ask average people what a web browser is, a huge percentage will just say, “It’s the box where i type Google to find things.”</p><p>People don’t read manuals or tutorials. They forge ahead, find a weird workaround that happens to work once, and then they stick with that exact workaround forever, even if it’s totally inefficient. Krug compares this to the pauper using the heavy Great Seal of England as a handy nutcracker because to him, it’s just a heavy piece of metal that cracks nuts.</p><p><strong>Why this matters for beginners</strong></p><p>When i first read this, it felt a little discouraging. It made me feel like: Why am i even spending hours trying to design good things if people are just going to rush through and muddle around anyway?</p><p>But Krug explains why it matters so much: muddling through might get the job done, but it is slow, error-prone, and frustrating. When you build a site where things actually make sense at a glance, users don’t have to muddle. They feel smart, they feel in control, and they actually find what they came for.</p><p>If users are going to treat your screens like billboards, stop writing novels. Design a great billboard instead. Make what matters impossible to miss.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12e5f26cdc6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Thought Being Clever Made Me a Good Designer. I Was So Wrong.]]></title>
            <link>https://medium.com/@hamzarashid3214/i-thought-being-clever-made-me-a-good-designer-i-was-so-wrong-3f422812fe4f?source=rss-ef2ed96b7b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f422812fe4f</guid>
            <category><![CDATA[product-thinking]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Hamzarashid]]></dc:creator>
            <pubDate>Wed, 16 Sep 2026 02:05:15 GMT</pubDate>
            <atom:updated>2026-09-16T02:05:15.424Z</atom:updated>
            <content:encoded><![CDATA[<p>What reading Steve Krug’s Don’t Make Me Think taught me about overcomplicating things as a beginner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hnZWCww9Ty79G0G2ZFqXw.png" /></figure><p>When i first started getting into UI and UX, i had this bad habit of trying to look smart. I thought being a good designer meant creating unique layouts that nobody had seen before, with aesthetic typography and clever copy. If a button was just called “Jobs”, i thought it sounded too simple or boring, so i would try to come up with fancy names like “Explore Careers” or “Opportunities” to make it look professional.</p><p>I was so obsessed with making everything look deep and artistic.</p><p>Then i started reading Steve Krug’s book <em>Don’t Make Me Think</em>. And honestly, reading it made me feel kind of embarrassed about my own work, but in a good way. It completely changed the way i look at screens.</p><h3>Nobody wants to solve a puzzle just to click a button</h3><p>In the first chapter, Krug talks about how tiny things on a screen make us stop and think for no reason. He used an example that really stuck with me: job listings on a company site.</p><p>If the navigation just says “Jobs”, the user clicks it in a millisecond without even using their brain. It is obvious. But when a team tries to get clever and names it something like “Job-o-Rama” or some internal corporate term, the user pauses. They hesitate and think, <em>wait, is that the job board or something else?</em></p><p>Krug says that every time a user has to ask a question like that, a little question mark pops up over their head. And every single question mark adds mental workload and drains their energy.</p><p>When i read that, it hit me right away because i was doing that exact mistake in my Figma files. I thought simplicity looked like laziness. But real people don’t use websites to admire how clever we are. They are usually in a hurry, they have things to do, and they just want to get through the screen without feeling stupid. Our job isn’t to show off, it is to remove all the question marks before the user even notices them.</p><h3>Three mindless clicks are better than one painful click</h3><p>Another thing i was completely wrong about was the “number of clicks”.</p><p>When you start learning UI, you hear people repeating this rule everywhere: <em>“Users shouldn’t have to click more than three times to get anywhere.”</em> Because of that rule, i used to cram so many links, tabs, and filters onto one single page just so the user wouldn’t have to click again.</p><p>Krug explains in chapter 4 that the number of clicks does not actually matter that much. What really matters is how hard each click is.</p><p>He gives the example of the old game Twenty Questions, where the first question is “Animal, vegetable, or mineral?”. It’s such an easy, mindless choice that you don’t even have to pause to answer it.</p><blockquote>“It doesn’t matter how many times I have to click, as long as each click is a mindless, unambiguous choice.”<em> — Steve Krug</em></blockquote><p>If a user has to click three or four times, but every single step is completely obvious and they feel confident they are on the right track, they don’t care. It feels effortless. But if you give them one single screen packed with ten confusing options where they have to stop and guess, that one click is way more frustrating than four easy ones.</p><p>It’s not about minimizing clicks, rather it’s about making every choice mindless.</p><h3>The reservoir of goodwill</h3><p>One idea in the book that really made me rethink how i design forms and pages is the “reservoir of goodwill”.</p><p>Krug describes it like this: whenever someone opens your website or app, they arrive with a certain amount of patience in their tank. Some people have a big reservoir, but if someone is in a rush or already had a bad day, their tank is already almost empty.</p><p>Every single time your design creates friction, you drain some of that water:</p><ul><li>When you hide important info like prices or support contact.</li><li>When you punish them for not formatting a phone number with dashes.</li><li>When you ask for personal information that isn’t even necessary for the task.</li><li>When you fill the screen with self-promotional “happy talk” instead of getting to the point.</li></ul><p>If you keep making mistakes and pushing their patience, that reservoir hits zero, and they just bounce.</p><p>Before reading this, i was only ever thinking about visual aesthetics — like what colors look clean together or what card border looks modern. I never once asked myself: <em>is this design decision draining the user’s patience right now?</em> Designing with real empathy means protecting their goodwill, not just making something that looks pretty on a portfolio site.</p><h3>What i am trying to focus on now</h3><p>As a beginner, it is so easy to get lost comparing design styles, switching between design tools, and trying to make everything look like high art. But Krug’s book reminded me that UX is mostly just common sense and honesty.</p><p>You don’t need to reinvent the wheel every time you make a navigation bar. Conventions exist because they help people navigate without getting lost.</p><p>I am trying to stop caring about looking clever. From now on, when i sketch a screen, i just want to ask one thing: <em>is this obvious?</em> Can someone who has never seen this before understand what to do in two seconds without guessing?</p><p>Good design takes time, consistency, and action. Instead of chasing perfection in my head, i just need to build simple things, put them in front of real people, and fix what actually breaks.</p><p><em>If you’re also learning design right now, don’t get trapped trying to look like an expert on day one. Just keep it simple and test it with someone sitting next to you.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f422812fe4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Usability Actually Means (And Why I Was Overthinking It)]]></title>
            <link>https://medium.com/@hamzarashid3214/what-usability-actually-means-and-why-i-was-overthinking-it-065fe8fa27b1?source=rss-ef2ed96b7b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/065fe8fa27b1</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Hamzarashid]]></dc:creator>
            <pubDate>Wed, 16 Sep 2026 02:05:02 GMT</pubDate>
            <atom:updated>2026-09-16T02:05:02.494Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I thought UX was about complicated theories and buzzwords, until i realized it’s just basic common sense.</em></p><p>When i first started trying to learn UI and UX, i honestly felt so overwhelmed. Everywhere you look on Twitter or LinkedIn, people use these huge terms like information architecture, cognitive load, interaction design, and mental models.</p><p>I felt like i was way behind. I thought to be a “real” designer, you needed a psychology degree or you had to memorize a massive list of hundred different rules before you could even touch a layout. I was stuck in that cycle where you keep reading articles and watching tutorials, but you are too intimidated to actually make things because you feel like an amateur.</p><p>Then i read the introduction of <em>Don’t Make Me Think</em>, and the way usability was explained made me take a huge breath of relief.</p><h3>The definition that calmed my anxiety</h3><p>In the book, there is a list of all the fancy attributes people use to define usability — like whether a system is learnable, memorable, efficient, or delightful.</p><p>Those words are fine, but then there was a simple definition that made so much more sense to me:</p><blockquote>“A person of average (or even below average) ability and experience can figure out how to use the thing to accomplish something without it being more trouble than it’s worth.”</blockquote><p>That last part — <em>without it being more trouble than it’s worth</em> — stuck in my head for days.</p><p>It’s not about making a groundbreaking piece of art. It’s not about blowing people away with crazy animations or showing everyone how clever you are. It is literally just making sure that an everyday person can open the screen, get what they came for, and leave without getting a headache.</p><p>When you strip away all the corporate noise, that’s all usability really is.</p><h3>It’s not rocket surgery</h3><p>The book has this motto: <em>It’s not rocket surgery</em>.</p><p>A lot of what good usability comes down to is stuff we already know as human beings, but for some reason, the second we sit down to design or code, we completely forget it.</p><p>When you go to a grocery store or use an ATM, you don’t want to figure out a puzzle. You just want the money or the groceries. But when we become creators, our ego takes over. We want to hide things in slick menus or use fancy names for simple buttons because simple feels too boring.</p><p>Another thing that made me feel less alone is realizing that most teams don’t even have dedicated usability experts. There are billions of websites and apps out there, and only a tiny fraction have full-time researchers checking every screen.</p><p>That means usability isn’t some secret club for specialists — it has to be the responsibility of anyone creating the product. Whether you are a solo developer, a beginner designer in Figma, or just building a small side project, it’s on you to make it usable.</p><h3>You don’t need to know everything to start</h3><p>One of my biggest fears was that i didn’t have enough knowledge yet to know if my designs were “right”. I was always waiting to find the perfect course or the perfect mentor to validate me.</p><p>The intro made a great point about this: you don’t need a giant checklist of every possible usability rule to make something good. Trying to memorize hundreds of guidelines just paralyzes you.</p><p>What actually matters is holding onto a couple of simple guiding principles:</p><ul><li>Remember that people don’t use things the way we hope they will.</li><li>Keep things simple so people don’t have to strain their brains.</li><li>Remember that your work is about serving the person on the other side of the glass.</li></ul><p>I realized i wasn’t stuck because UI/UX is too hard. I was stuck because i was trying to find perfection before taking action.</p><h3>What i am taking away from this</h3><p>From now on, i am trying to drop the imposter syndrome around UX. You don’t need anyone’s permission to care about the user, and you don’t need a fancy lab to start practicing common sense.</p><p>Instead of worrying about whether my screens look like a senior designer made them, my only goal is to make things that don’t make people feel lost.</p><p>If someone of average ability can use my screen to get what they need without cursing at the buttons, that is a win. Everything else is just practice, consistency, and showing up every day.</p><p><em>If you’re also starting out in tech or design, did you ever feel intimidated by all the terminology? What was the first concept that made things click for you?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=065fe8fa27b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Users Don’t Read Your Design. They just scan It at 60 Miles an Hour.]]></title>
            <link>https://medium.com/@hamzarashid3214/users-dont-read-your-design-they-just-scan-it-at-60-miles-an-hour-314655f88f1a?source=rss-ef2ed96b7b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/314655f88f1a</guid>
            <category><![CDATA[double-diamond]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Hamzarashid]]></dc:creator>
            <pubDate>Mon, 14 Sep 2026 14:12:43 GMT</pubDate>
            <atom:updated>2026-09-14T14:12:43.793Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>What Krug taught me about why nobody cares about your aesthetic copy, and how to actually design for real human beings.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1CrQkogVwQ0KkGW3XIJu2A.png" /></figure><p>I thought good design meant explaining everything so thoroughly that nobody could possibly get confused.</p><p>Later i found out i was completely delusional.</p><p>Reading Steve Krug’s <em>Don’t Make Me Think</em> hit me right in the chest, because it forced me to realize that users do not interact with screens the way we think they do. We design for attentive readers, but in the real world, people treat our designs like billboards whizzing by on a highway at 60 miles an hour.</p><h4>The three brutal facts of how people actually use the web</h4><p>As designers, we love to believe users will arrive at our site, admire our layout, weigh every option on the screen, and carefully make the most logical choice.</p><p>In reality, Krug points out three facts that completely destroy that fantasy:</p><ul><li><strong>We don’t read pages. We scan them.</strong> People are usually on a mission. They act like sharks that have to keep moving. They do not read every word on the page; they just glance feverishly across the screen until a word or a button vaguely resembles what they came looking for.</li><li><strong>We don’t make optimal choices. We satisfice.</strong> We do not sit there comparing five different navigation options to find the absolute best path. We pick the very first halfway-decent link that catches our eye, click it, and hope for the best. If it fails, we just hit the Back button and try again.</li><li><strong>We don’t figure out how things work. We muddle through.</strong> Nobody reads the instructions. Most people use software and websites every day without having any clue how they actually function behind the scenes, and they honestly do not care as long as it gets the job done.</li></ul><p>Krug compares it to the classic cartoon where an owner gives a serious lecture to his dog, but all the dog hears is <em>“blah blah blah GINGER blah blah”</em></p><p>That is exactly how users treat your interface. They scan past all your carefully crafted text looking only for their own trigger words.</p><p><em>“We’re thinking ‘great literature’ (or at least ‘product brochure’), while the user’s reality is much closer to ‘billboard going by at 60 miles an hour.’”</em> — Steve Krug</p><h3>Krug’s First Law: Stop making people think</h3><p>Krug has a simple overriding rule for usability: <strong>Don’t make me think!</strong></p><p>Every single time a user has to pause on your page and ask themselves a question, it adds friction. It drains their energy and ruins their confidence in your product.</p><p>When someone lands on your page, all the thought bubbles over their head should be completely effortless:</p><ul><li><em>“Okay, that’s where the search bar is.”</em></li><li><em>“That looks like the main button.”</em></li><li><em>“This is what i came for.”</em></li></ul><p><em>The second their internal dialogue turns into questions, you are in trouble:</em></p><ul><li><em>“Wait, is that a button or just a header?”</em></li><li><em>“Why did they give this tab such a weird, clever name?”</em></li><li><em>“Are those two links leading to the exact same place?”</em></li></ul><p>Your job as a designer is not to make users marvel at your cleverness. Your job is to eliminate every single question mark before it even pops into their head.</p><h4>How to design a billboard, not a brochure</h4><p>If users are going to treat your interface like a billboard, then you have to actually design a great billboard. That means ditching subtle design tricks that look pretty in your portfolio but completely break down when someone is in a rush.</p><ol><li><strong>Stop trying to reinvent the wheel</strong></li></ol><p>Designers hate following conventions because it feels boring. We want to stand out, win awards, and create crazy new interactions. But conventions exist because they work.</p><p>When someone sits in a rental car, they expect the gas pedal to be on the right and the brake to be on the left. If you move the brake just to be “creative,” you cause an accident.</p><p>Keep your logo in the top left. Keep the search bar where people expect it. Use standard shopping cart metaphors. As Krug says, innovate when you genuinely have a better idea, but take full advantage of conventions when you don’t.</p><p><strong>2. Build an aggressive visual hierarchy</strong></p><p>A user should be able to look at your screen with their eyes half-closed and still understand what is most important.</p><ul><li>Things that are more important must be visually bolder, larger, or higher up.</li><li>Things that are related logically need to be grouped together visually.</li><li>Things that belong inside a category need to be clearly nested underneath it.</li></ul><p>When everything on your page is screaming for attention with bright badges, drop-shadows, and banners, the result is just visual noise. When everything shouts, nothing gets heard.</p><p><strong>3. Make clickable things look obviously clickable</strong></p><p>With flat design taking over, so many interfaces stripped away the visual clues that make buttons look like buttons.</p><p>If a user has to hover their mouse around or tap aimlessly to see if a piece of text is clickable, your design has failed. Use consistent link colors. Give buttons real boundaries and shapes. Do not make the user guess what is interactive.</p><h3>“Happy talk must die”</h3><p>One of my absolute favourite rules in the book is Krug’s Third Law of Usability: <strong>Get rid of half the words on each page, then get rid of half of what’s left</strong>.</p><p>We put so much fluff into our interfaces:</p><ul><li><strong>Happy talk:</strong> The empty, self-congratulatory intro text like <em>“Welcome to our platform! We are thrilled to offer world-class tools to empower your workflow…”</em> Nobody reads it. It’s just small talk, and people on the web have zero patience for small talk. Kill it immediately.</li><li><strong>Long-winded instructions:</strong> Users do not read instructions anyway. They only look for help after they have already muddled through and failed three times. Your goal is to make the interface so self-explanatory that instructions aren’t even necessary.</li></ul><p>When you ruthlessly cut out needless words, you reduce the noise level of the whole page, make what is actually important stand out, and save the user’s precious time.</p><h3>Action over perfection</h3><p>I spent months stuck between wanting my UI work to be deeply artistic and wanting it to be functional. I was always comparing tools, second-guessing typography, and waiting for the day i felt like a “master.”</p><p>Reading Krug taught me that great design is not about high art or academic theories. It is about empathy and common sense.</p><p>It’s about having the humility to realize that nobody is admiring your interface — they just want to get in, solve their problem, and get on with their lives.</p><p>Stop overthinking your layouts and stop trying to make every paragraph sound poetic. Make it obvious. Make it painless. Cut out the clutter, test your work with real people, and let action replace perfection.</p><p><em>If you’re currently building or designing something, open your main screen right now and ask yourself: what is one question mark i can remove for the user today?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=314655f88f1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Debating Your Designs in Your Head. Just Watch Three People Break Your Work]]></title>
            <link>https://medium.com/@hamzarashid3214/stop-debating-your-designs-in-your-head-just-watch-three-people-break-your-work-cf002f30df35?source=rss-ef2ed96b7b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf002f30df35</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design-thinking]]></category>
            <dc:creator><![CDATA[Hamzarashid]]></dc:creator>
            <pubDate>Mon, 14 Sep 2026 14:00:19 GMT</pubDate>
            <atom:updated>2026-09-14T14:00:19.640Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Why beginner designers get trapped trying to make everything perfect, and how a simple 10-cent usability test fixes the whole process.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TZPJDWTNk_dh__uOr6CwOQ.png" /></figure><p>When i first started trying to learn UI and UX, i spent so much time just overthinking every single detail. I would sit for days switching between different tools, tweaking button borders, and comparing layout advice, convinced that if i just found the perfect rule book my work would finally be great. But i was not really learning; i was just hiding behind perfection because i was terrified of making something that did not work. Steve Krug explains in his book that all the theories and endless arguments we have in our heads do not mean anything until you actually watch a real person try to use what you made.</p><h4><strong>The endless religious debates that lead nowhere</strong></h4><p>In almost every project or design meeting, people fall into what Krug calls “religious debates”. The visual designer wants the screen to look clean and aesthetic, the developer wants something that makes logical sense in code, and someone else wants to cram three promotional banners onto the page. We sit there arguing back and forth about whether users prefer dropdown menus or sliders, as if there is some universal truth waiting to be discovered.</p><p>The mistake we make is assuming that other people think and browse just like us. We project our own habits onto everyone else, believing that if something feels obvious to our eyes, it will be obvious to the world. But the reality is that there is no such thing as an “Average User”.</p><p>Every single person who opens your website comes with their own mood, their own hurry, and their own weird gaps in knowledge. They do not read your pages carefully like a novel; they glance at the screen for two seconds, scan for anything that vaguely matches what they want, and click the first thing that looks reasonable. When you realize how messy real human behavior is, arguing about what users “like” in the abstract is just a waste of energy. You cannot solve design problems by debating opinions, you solve them by testing what actually works.</p><h4>Why focus groups lie, and why you only need three people</h4><p>A lot of beginners put off user research because they think it has to be this massive, formal scientific project. We think we need a high-end lab with two-way mirrors, expensive recording gear, and dozens of people recruited to match an exact demographic profile. Or even worse, teams schedule a focus group and think they are doing usability work.</p><p>Krug makes a huge distinction here: focus groups are just people sitting around a table talking about their opinions, which is completely useless for finding out if an interface works. Usability testing is about sitting one person down and quietly watching them try to complete a real task. What people say they do in a discussion has almost nothing to do with what they actually do when they touch a screen.</p><p>And you do not need to wait until you have a huge budget or a fully finished product to do it. Testing one single person early on, even when you only have a rough sketch on a piece of paper or an ugly wireframe, is a hundred times more valuable than testing fifty people right before launch when everything is already built and painful to change.</p><p>You do not even need to stress about finding the “perfect” target audience either. Krug advises to recruit loosely and grade on a curve. Unless your app requires deep specialized training like brain surgery, almost anyone will run into the exact same stumbling blocks. If a regular person cannot figure out where to click, your target user is going to get stuck there too. All you need is three people and one morning a month.</p><h4>What happens when you actually sit down and watch</h4><p>Sitting next to someone while they test your design is honestly humbling. It hurts your pride a bit. You spent so much time crafting a layout that feels completely obvious to you, and then a participant sits down, looks right past your bold headline, misses the primary navigation completely, and clicks on an unclickable piece of text.</p><p>Your first instinct in that room is always going to be to jump in, protect your work, and explain what they are doing wrong. You want to say, “No, look over there, the button is right there.” But you have to hold yourself back and stay quiet. If you have to explain the design to them, you have already failed, because you will not be standing behind them when they use it in the real world.</p><p>Your only real job as a facilitator is to keep them talking out loud. When they pause or frown at the screen, you just ask a gentle question like, “What are you thinking right now?” Listen to what they expect to happen versus what the interface is actually giving them. Watching someone get genuinely lost breaks all your assumptions in fifteen minutes, and that honesty is the best thing that can ever happen to your learning</p><p><strong>Stop adding more clutter, start taking things away</strong></p><p>After a test session ends and you see where people got confused, the temptation is always to add more stuff. We want to add an explanatory paragraph, a tooltip, or three steps of instructions at the top of the form. But adding more text almost never works, because nobody was reading the text you already had on the screen.</p><p>Most of the time, fixing a problem means stripping things away rather than piling more on. If users are getting lost, it is usually because there is too much visual noise fighting for their attention, or the clickable cues are way too subtle. Instead of writing more instructions, you need to turn down the volume on everything else and make the main action impossible to miss.</p><p>You also do not need to fix every tiny mistake you saw during the test. You will easily find more problems in one morning than you have time to fix in a whole month. Krug’s rule is to focus ruthlessly on the top two or three most serious roadblocks — the things that actually stopped people from completing their goal — and fix those first. If someone gets slightly turned around for two seconds but finds their way back without help, just ignore it. Good design does not come from chasing a flawless layout on your first try; it comes from consistency, dedication, and taking action on the real friction points right in front of you.</p><p>Stop waiting for the perfect mentor or the perfect time before you show your work to real people. Take whatever rough screen or prototype you have right now, find someone who has never seen it before, and just watch them try to use it. It might sting your ego for a few minutes, but it will save you months of wasted effort.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf002f30df35" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Brain Hates Uncertainty]]></title>
            <link>https://medium.com/@hamzarashid3214/your-brain-hates-uncertainty-ac6ca2c4cfa1?source=rss-ef2ed96b7b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac6ca2c4cfa1</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Hamzarashid]]></dc:creator>
            <pubDate>Sat, 12 Sep 2026 11:58:15 GMT</pubDate>
            <atom:updated>2026-09-12T11:58:15.200Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine clicking “Pay Now.”</p><p>Then… nothing.</p><p>No confirmation.<br>No loading state.<br>No feedback.</p><p>You wait.</p><p>Did it work?</p><p>You click again.</p><p>Now you&#39;re not just using an interface.</p><p>You&#39;re trying to understand what the system is doing.</p><p>This is where psychology becomes extremely important in UX.</p><p>Humans don&#39;t handle uncertainty particularly well.</p><p>When we don&#39;t know what&#39;s happening, we start creating our own explanations.</p><p>And usually, they&#39;re not very comforting.</p><p>That&#39;s why feedback matters.</p><p>Loading indicators.<br>Success messages.<br>Error states.<br>Progress bars.<br>Micro-interactions.</p><p>They&#39;re not decoration.</p><p>They&#39;re psychological reassurance.</p><p>A good interface constantly answers one silent question:</p><blockquote>“What is happening right now?”</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac6ca2c4cfa1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The User Is Not Thinking About Your UX]]></title>
            <link>https://medium.com/@hamzarashid3214/the-user-is-not-thinking-about-your-ux-98976382e882?source=rss-ef2ed96b7b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/98976382e882</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Hamzarashid]]></dc:creator>
            <pubDate>Thu, 10 Sep 2026 15:01:36 GMT</pubDate>
            <atom:updated>2026-09-10T15:01:36.607Z</atom:updated>
            <content:encoded><![CDATA[<p>Users don&#39;t care about your beautiful components.</p><p>They don&#39;t care that you spent three hours fixing an 8px spacing issue.</p><p>They don&#39;t care about your design system.</p><p>And honestly, they shouldn&#39;t.</p><p>They&#39;re trying to get something done.</p><p>Book the ticket… find the product… send the message.<br>understand the information.</p><p>good UX disappears into the background.</p><p>the moment users start noticing the interface something has usually gone wrong.</p><p>Maybe the button is confusing.</p><p>Maybe the information is buried.</p><p>Maybe the system is making them think too much.</p><p>The goal isn&#39;t to make people admire the interface.</p><p>It&#39;s to make the task feel almost effortless.</p><blockquote>The best UX isn’t always the one users notice.</blockquote><blockquote>Sometimes it’s the one they forget was even there.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98976382e882" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX and Psychology]]></title>
            <link>https://medium.com/@hamzarashid3214/ux-and-psychology-74dab6a64cbe?source=rss-ef2ed96b7b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/74dab6a64cbe</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Hamzarashid]]></dc:creator>
            <pubDate>Thu, 10 Sep 2026 14:58:00 GMT</pubDate>
            <atom:updated>2026-09-10T14:58:00.291Z</atom:updated>
            <content:encoded><![CDATA[<p>A lot of designers think good UX means giving users more choices.</p><p>Not always.</p><p>More choices can actually make people less likely to choose anything at all.</p><p>This is called the Paradox of Choice.</p><p>But here’s where it gets interesting:</p><blockquote>The problem isn’t simply “too many options.”</blockquote><p>It’s the mental cost of evaluating those options.</p><p>When every option requires comparison, prediction, and risk assessment, the user&#39;s brain starts asking:</p><blockquote>“What if I choose the wrong one?”</blockquote><p>And suddenly, a beautifully designed interface creates decision paralysis.</p><p>That’s why good UX isn’t about showing users everything you have.</p><p>It’s about helping them understand:</p><blockquote>“What should I choose, and why?”</blockquote><ul><li>This is where things like</li><li>smart defaults</li><li>progressive disclosure</li><li>recommendations</li><li>meaningful grouping</li><li>clear hierarchy</li><li>contextual information</li></ul><p>become powerful.</p><p>You’re not just reducing clicks.</p><p>You’re reducing cognitive load and decision uncertainty.</p><p>And honestly, that’s one of the biggest differences between designing an interface and designing an experience.</p><blockquote>UI shows possibilities.<br>UX helps people decide.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74dab6a64cbe" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>