UX Design Patterns And Anti-Patterns

In nearly every advanced design class I teach, I notice the same tendency: students design the layout before they’ve read the content. Even after seeing it so often, I’m still surprised. But I’ve come to realize it’s not because students are intentionally skipping a critical step—it’s because they’ve been taught (implicitly or explicitly) that design starts by styling the page. So they treat the project as a layout challenge instead of a business, brand, communication, or experience problem to solve. They reach for composition, style, and grid too early—hoping these will give them direction. But instead of helping, these tools lock them in. The result? A visual solution that’s precise and polished, but hollow. What I tell them is this: composition, style, and structure aren’t the idea. And they’re not the starting point. They’re finishing tools—like fine‑grit sandpaper. Something you use to refine what you’ve already discovered. Not something that leads you to the solution. Design needs structure, yes. But first, it needs meaning. When you’ve explored concepts and found the story that resonates, the grid helps. It brings shape, clarity, and rhythm—and strengthens the message. But rely on it too soon, and it becomes a cage, keeping you from discovering ideas worth developing. Use structure to support your thinking—not to replace it. When you do, you move design beyond decoration—transforming it into a meaningful, strategic tool to solve a problem, change a mind, and make a difference.

I've found empathy mapping most valuable during early project phases and presentations. Nothing convinces leadership to greenlight a project like showing them you truly understand your target audience's pain points. But, they're not for every situation. For straightforward projects with well-understood users, a quick check-in might be sufficient. The key is using empathy maps as tools for insight, not checkbox exercises. I've seen firsthand how they break down communication barriers between departments. The beauty of empathy mapping lies in its simplicity. The classic version has four quadrants – Says, Thinks, Does, and Feels — though I've found adding "Sees" and "Hears" can provide even more context for certain projects. What matters isn't the exact format but the conversations it sparks. Here's what works in my experience: - Start with a clear purpose. Are you trying to align your team around user needs? Inform a specific design decision? The goal shapes everything that follows. - Ground your map in reality. The most valuable maps come from actual user data – interviews, surveys, support tickets – not assumptions. I've watched teams realize how much they'd been projecting their own preferences onto users when confronted with real feedback. - Make it collaborative. Bring together people from different departments to fill out the map. The magic happens when your developer suddenly realizes why that feature the marketing team kept pushing for actually matters to users. - Keep it alive. The best empathy maps evolve as you learn more. I keep ours visible and revisit them regularly, especially when we're making crucial decisions.

We built fast systems. Somewhere along the way, we forgot to build kind ones. That’s why this simple Korean idea stayed with me. Before a call connects, the caller hears a small voice saying, “You’re about to talk to my mom.” Or my dad. Or my sister. And everything shifts. Not because callers become kinder people overnight. But because the system reminds them that the person answering is human too. It brought back a lesson I learned early in my career building financial products. If you design only for efficiency, you get compliance. If you design for humanity, you get trust. And trust is what makes systems scale. This Korean example is not customer service innovation. It is behaviour design. A tiny nudge that restores empathy in a space where it quietly disappeared. It made me think about how often we build products to optimise flow, not feeling. We fix the steps, but forget the state of the person going through them. We reduce friction, but overlook the fear, frustration or vulnerability underneath. A small tip for product leaders: If your system interacts with people at stressful or uncertain moments, your first job isn’t speed. It’s care. A sentence. A tone. A pause. A reminder that a human sits on the other side. Because most friction in modern life doesn’t come from systems failing. It comes from human connection thinning. We already know how to build fast. The next frontier is learning how to build kind. Not every solution needs a feature. Sometimes it needs a feeling. What would your product look like if empathy was part of the design spec?

AI Overviews are changing how content gets discovered. Here’s how to help AI find and surface your content. We still write for humans first. That hasn’t changed, nor will it. But now there’s a new layer to consider, which is making sure your human-centered content can actually be found by AI. Think of it like this: you can be the most eloquent storyteller in the room, but if you're speaking a language the translator doesn't understand, your message never reaches the audience. The shift is subtle but significant. When you say, "Our shoes are comfortable for hiking long distances," you're connecting with human experience. When you say, "Pressure mapping shows 27% less forefoot compression than competitors," you're giving AI something concrete to work with. The best content does both. How to Make Your Content Do Both: 1) Specificity beats superlatives "Industry-leading performance" tells AI nothing. "Recognized as the most energy-efficient cloud provider by independent testing (2025)" gives it something to reference and cite. 2) Structure for scanning Both humans and AI value clear organization. Use headings that summarize what's coming. Break complex ideas into digestible pieces. Answer implied questions directly within your content. 3) Context through comparison Instead of "lightweight and fast," try "At 250MB, our app is 30% smaller than the industry average, reducing load times by 40%." AI looks for relationships and comparisons, not vague descriptors. 4) Define your terms When introducing a new concept, explain it in a way AI can recognize. Instead of "adaptive learning technology," say "AI-driven personalization that adjusts difficulty based on user performance." This improves clarity for both audiences. The goal isn't ever to write for robots instead of humans. It’s about making sure your human-first content is organized in a way AI can actually work with. We need to become bilingual, i.e., fluent in both human storytelling and machine logic. This evolution asks us to be more precise, more accountable, and more clear about our value propositions. Which, when you think about it, makes our content better for everyone. #AI #ContentStrategy #SEO #hicm

𝗜'𝘃𝗲 𝗱𝗲𝘀𝗶𝗴𝗻𝗲𝗱 𝗼𝘃𝗲𝗿 𝟭𝟬𝟬 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝘀, 𝗮𝗻𝗱 𝗜 𝗵𝗮𝗱 𝘁𝗼 𝗹𝗲𝗮𝗿𝗻 𝘁𝗵𝗶𝘀 𝘁𝗵𝗲 𝗵𝗮𝗿𝗱 𝘄𝗮𝘆: A beautiful UI won’t save a product without substance. I remember building my first app in 2016. I focused purely on design, driven by the ambition to create the most beautiful camera app in the app store. While we were shipping what I thought was "a piece of design," no one was actually using it... You can have the sleekest design, the cleanest layout, the most jaw-dropping visuals—but if the core doesn’t deliver, users won’t stick around. Substance drives value; design amplifies it. Don’t get blinded by the surface. Build the foundation first—solve real problems, meet real needs. Then let the design elevate it. Design becomes unstoppable when it’s backing something real. #ProductDesign #UX #UI #Startups

What if an interface could adapt to your world in real time? Imagine your car’s dashboard subtly shifting to shades of green as you drive through a forest, or an app adjusting to your personal accessibility needs without breaking. For the past few months, I've spoken with many of you and I’ve realized we’re all working toward the same ambitious goal: creating interfaces that offer a seamless blend of brand personalization, true adaptability, and accessibility. This is about building an experience that is not only true to a brand's perception but is also tailored to our individual needs as consumers. My exploration so far has revealed three foundational concepts that I feel are important to make this a reality. In the upcoming months, I’ll be sharing our journey as we explore these concepts. Some ideas will work, some will fail. I don’t know where this path will lead, but I want to bring you along in the process. 1.⁠ ⁠Contextual Awareness This is the idea that an element understands its environment. A button, for example, knows what surface it’s sitting on and adapts accordingly. While tools like Figma use variable collections to simulate this, the approach is often fragile because it lacks a scalable underlying logic. This very challenge was a driving force behind developing the graph engine. I’m excited to share that a solution for this is now possible directly in modern browsers with pure CSS, laying a powerful and scalable foundation for the future. 2.⁠ ⁠Content Awareness Imagine an interface that reflects the content it displays. We see a version of this in Spotify’s UI, which adapts to album art to create a more immersive experience. This principle allows the UI to react dynamically, personalizing the experience in real-time based on its content. 3.⁠ ⁠User Awareness This pillar brings it all together by focusing on the user’s specific needs. It means designing systems that can respond to a user with Parkinson’s who may need more forgiving interaction areas, or accommodating the universal reality that as we get older, we need larger fonts. The key is to make these adjustments without breaking the interface or compromising the brand experience. These three pillars form the blueprint for the next generation of user interfaces. By understanding where an element is, what it contains, and who is using it, we can create experiences that feel truly alive. I think there’s more to discover beyond our current methods. Let's explore what it means to build something truly adaptive, together.

I thought I understood my users. I was wrong. Over multiple field visits across Gurgaon and Delhi, I sat behind Swiggy delivery partners on their bikes. No notebook. No interview guide. Just me and the road. Here's what I actually saw - • Afternoon sun made the screen unreadable. He was guessing, not reading. • One hand on the handlebar, thumb stretching - I had designed for a desk, not a moving bike. • Gate A of a society closes at 10 PM. He knew to go to gate B. Our app had no idea. These weren't edge cases. This was every shift. Every order. Every day. Nobody complained. They just adapted. One of them told me - "Sahab, yahan survive karna padta hai. Ghar ke liye karna padta hai." But here's what struck me most, he wasn't bitter. He was proud. Every delivery meant school fees paid. Every order meant his family was okay. The exhaustion was real. But so was the smile. Today, more than 3 lakh delivery partners depend on this app every single day. That number used to feel like a metric to me. After that ride, it felt like a responsibility. Empathy is not a design principle. It's what happens when you stop looking at users as data points. When was the last time you truly felt what your user feels - not observed, but felt? 👇

99.9999% of case studies I see don't address: → Empathy Way too much "Next, I did this..." Not enough "Here's why we did this..." A well-placed persona image in your study is not a substitute for genuine user understanding. Some ways you can highlight empathy: → Core Needs: Begin your narrative by highlighting the user's fundamental needs. Make their pain points the core of your story, just as you did with your designs. → Insights: Distill the core needs into your primary insights. Showcase these. They guided your design decisions. Let them guide your case study. → How Might We's: A good way to frame problem-solving based on each insight. These show the uncovered potential. → Outcomes: Shift your focus from solely what you've learned to how your solution positively affected the user. How did it make their life better? Tell the story through the user's eyes, not merely as a designer ticking off a checklist. Empathy should have guided every step of your design process. Let it guide your story, too. #ProductDesign #PortfolioTips

Unpopular opinion: if you're going straight to InDesign for your first draft, you're not setting yourself up for success. Don't get me wrong, I love InDesign. But we can't win on design alone. We *can* win on content alone. So why aren't we focusing on content-driven drafts first? I know, I know. Deadlines are tight, and the pressure to get something “designed” ASAP is real. But starting with a templated proposal or copy+pasting content from the last submittal? That opens us up to common issues. You miss details. (Oh, the dreaded "I forgot to update the project/client name.") You leave in boilerplate that doesn’t quite fit. Because, let's be honest, once something looks polished, it feels finished. And that makes it way harder to get meaningful content feedback. Especially when your reviewers are more focused on visuals than messaging. (“Can we add a photo here?” No. That’s intentional white space, thank you very much. "Can we change this photo?" Yes. That's literally our brand placeholder.) About five years ago, I flipped my process and pushed my clients to start their proposals in a plain Google Doc. No design, no imagery, until the content was reviewed, edited, and approved. The feedback was immediately better. I got comments with more substance, fewer distractions. Before you come at me with "that won't work for us because we do too many quick turns" (trust me, so do I)… On fast deadlines, I took a hybrid approach. We’d finalize each section’s content in the doc, and once it hit ~80%, I’d start bringing it into InDesign. I also prepped a blank layout shell while the team reviewed the written content, so design and narratives could move in parallel. Extremely efficient (you know I hate inefficiencies in the proposal process). It’s not flashy, and it feels super counterintuitive (I know, I know!) but it works.

Design Thinking is About Caring Design Thinking is, at its core, about caring for others. Barbara Weedman once witnessed a poignant moment: a single mother struggling to complete a job application at a public computer while holding her baby. She typed with one hand, corrected mistakes, and ultimately left without finishing—exhausted and defeated. When Henrico County began constructing a new library, Weedman asked the architects a simple but powerful question: Could they design computer workstations tailored for parents with infants and toddlers? The result was the Fairfield Parent+Child Carrel—a dedicated workstation with privacy panels, directly connected to a secure play area for young children. This thoughtful space includes a healthcare-grade vinyl mat, a mirror at baby height, and interactive panels that librarians can update for seasonal activities. This initiative embodies Life-Work Integration, moving beyond the traditional notion of work-life balance. Too often, leaders overlook that performance is a byproduct of humanistic values such as empathy, fairness, and collaboration. By nurturing people, businesses become more productive, ethical, and impactful. This is the essence of Design Thinking: enhancing our world through care. The stages, tools, and canvases are merely instruments—the true driving force is empathy. - When we care, we become curious—analyzing trends, defining problems, and understanding customer pains and gains. - When we care, we ideate—aligning ideas, products, and solutions with real human needs. - True value lies not just in customer experience, but in solving problems, saving time, creating opportunities, ensuring accessibility, and fostering safety and self-actualization. We can only be truly empathic if we care. By Design. If this resonates, share it with your network. ---