<?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 Nisha Thomas on Medium]]></title>
        <description><![CDATA[Stories by Nisha Thomas on Medium]]></description>
        <link>https://medium.com/@nishathms?source=rss-1ed5eccfc4a6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Nisha Thomas on Medium</title>
            <link>https://medium.com/@nishathms?source=rss-1ed5eccfc4a6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:24:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nishathms/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 UX patterns work (and why they’re starting to break)]]></title>
            <link>https://medium.com/@nishathms/why-ux-patterns-work-and-why-theyre-starting-to-break-6360206e1880?source=rss-1ed5eccfc4a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/6360206e1880</guid>
            <category><![CDATA[ux-pattern]]></category>
            <category><![CDATA[ai-ux-patterns]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Nisha Thomas]]></dc:creator>
            <pubDate>Fri, 30 Jan 2026 13:43:12 GMT</pubDate>
            <atom:updated>2026-01-30T13:43:12.099Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PTOj6LV0vgV7PvZP19Gm1g.png" /><figcaption>User interacting with a digital environment. Source: ChatGPT</figcaption></figure><p>Your hand hovers over the trackpad. You’re about to design something you’ve designed a hundred times before; another hamburger menu, another search icon…and it feels inevitable.</p><p>Different brands, different systems, yet users just know. We call them “best practices” and move on.</p><p>But that’s not why they work.</p><p>The real reason lives in the oldest part of ourselves.</p><h3>What Your Brain Actually Wants</h3><p>Here’s what changed everything for me: the brain doesn’t optimize for quality. It optimizes for survival using minimum energy.</p><p>Every decision costs calories. Every moment of confusion triggers alarm systems designed for threats that no longer exist. When you open an app, your brain isn’t wondering what delightful interaction awaits, it’s calculating the fastest escape route.</p><p>UX patterns succeed because they whisper: <em>You’re safe here. No thinking required.</em></p><p>A magnifying glass means search because it’s mentally cheap. A checkbox means multiple selection because your brain already knows the script. A wizard feels safer than a blank form because it transforms overwhelming into manageable.</p><p>We don’t reduce cognitive load. We eliminate it.</p><h3>The Autopilot Inside</h3><p>Over time, repeated interactions rewire your brain. Neural pathways form. Procedural memory builds. The scrolling, filtering, tapping, all of it stops being conscious.</p><p>You’re no longer using an interface. You’re running a script compiled directly into your nervous system.</p><p>This explains why breaking a pattern feels like friction, even when the new design is objectively better. You’ve interrupted an existing pathway and forced someone to think. And thinking is expensive.</p><p>Users cling to clunky interfaces not irrationally, but because familiar and inefficient beats unfamiliar and better. Every time.</p><h3>The Prediction Engine</h3><p>Here’s what neuroscience reveals or is believed to be: your brain doesn’t react to the world, it predicts it.</p><p>Right now, it’s running millions of tiny simulations about what happens next. You’re not experiencing reality; you’re experiencing your best guess about reality, then checking if you were right.</p><p>When a blue underlined word turns out to be a link, your prediction succeeds. Everything feels intuitive. But when that text isn’t clickable, when the button doesn’t behave like a button, the engine fails. Conscious reasoning kicks in. Stress hormones release.</p><p><strong>Intuitive UX is simply low prediction error.</strong></p><p>We design systems that behave exactly how the brain expects, so it can stay in low-power mode, so users never think about the interface at all.</p><h3>Decision Environments, Not Interfaces</h3><p>People don’t optimize. They satisfice. They choose defaults, avoid friction, prefer obvious next steps, rarely explore all options.</p><p>Defaults shape behavior more than any content you write. Progressive disclosure outperforms full exposure. Wizards beat blank canvases even when slower.</p><p>That “Buy Now” button, that pre-checked signup, that default “Yes”…these are decisions made by environments, not people. The environment always wins.</p><p>UX patterns don’t mean “best possible solution.” They mean “least mentally expensive solution.”</p><p>Good enough and familiar beats better and unfamiliar, which means we might be trapped by our own nervous systems , running on hardware that hasn’t updated in 200,000 years.</p><p>Until recently, this was just philosophy.</p><h3>When the Contract Breaks</h3><p>The patterns are failing. You’ve felt it as a designer, that sense something’s off, that the old rules don’t quite work.</p><p>Traditional patterns were built for linear, predictable, deterministic systems. But we’re now designing for AI-driven, probabilistic, non-linear systems that are alive in ways software never was.</p><p>We’re putting chatbots in buttons. Agents in menus. Making AI pretend to be software. The mental model no longer matches reality.</p><p>Deep in users’ prediction engines, something misfires. The brain keeps guessing wrong. The energy bill climbs.</p><p>This is why AI products feel awkward, not because the AI is bad, but because we’re forcing new wine into old bottles, and the bottles are cracking.</p><h3>The Real Evolution</h3><p>Traditional UX asked: “What should the interface look like?”</p><p>Modern UX asks: “What mental model does the user need?”</p><p>Future UX will ask: “How predictable is the system in resolving user intent?”</p><p>We’re moving from designing things to designing relationships. From crafting screens to orchestrating understanding. From making interfaces to making sense.</p><p>Success will be measured not by usability alone, but by trust, predictability, and alignment between human expectations and system behavior.</p><p>The patterns we’ve relied on for decades might not survive this journey.</p><h3>The Invisible Design</h3><p>A UX pattern is really a cognitive contract: an agreement between how users think, how systems behave, how much effort is required, and how safe the interaction feels.</p><p>When you honor that contract, users don’t think. They flow.</p><p>Somewhere deep in their brain, a message appears: <em>Safe. Known. No threat here.</em></p><p>When everything works perfectly, they look up and say: “It just feels right” or the term “intuitive”.</p><p>That’s not feedback. That’s the highest compliment a system can receive. It means you made them feel safe enough. And sometimes, being invisible is the most beautiful thing you can design.</p><h3>What Comes Next</h3><p>So how do we design for systems that think, learn, and occasionally surprise us?</p><p>The answer isn’t to abandon patterns, it’s to evolve them. The goal is no longer just usability. It’s predictability, trust, and shared understanding between human and machine.</p><p>Here’s where to start.</p><p><strong>Design for confidence, not certainty.</strong> AI can’t promise perfection, but it can expose its reasoning. Show why a suggestion was made. Surface confidence levels. Trust comes from helping users understand how sure the system is (not from pretending it’s infallible).</p><p><strong>Make the model visible through interaction, not documentation.</strong> Design patterns that teach capability gradually: what the system understands, what it struggles with, where its boundaries lie. Discovery should feel natural, inevitable.</p><p><strong>Build trust through small, consistent wins.</strong> Don’t start with high-stakes automation. Begin with suggestions instead of decisions, drafts instead of actions, guidance instead of authority. Let users experience success in low-risk moments first. Predictability compounds.</p><p><strong>Design for course-correction.</strong> Traditional UX assumes users get it right the first time. AI UX assumes they won’t. “Not quite, let me try again” should feel like collaboration, not failure. The system improves with the user.</p><p><strong>Embrace progressive disclosure.</strong> Don’t show everything upfront. It overwhelms and breaks mental models. Reveal power as understanding grows. Let the interface evolve alongside the user’s confidence.</p><p><strong>Create feedback loops that feel consequential.</strong> Every regeneration, edit, thumbs-up should be a learning moment. Users need to sense they’re shaping the system, not just reacting to it. Make feedback participatory, not performative.</p><p>The patterns we build now will shape how millions understand AI for the next decade.</p><p>We’re no longer designing interfaces. We’re designing cognitive contracts between human expectations, system behavior, uncertainty, and trust.</p><p>Make them clear. Make them honest. Make them human.</p><p>That’s the work ahead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6360206e1880" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quiet to confident – embracing growth as an introvert]]></title>
            <link>https://medium.com/@nishathms/quiet-to-confident-embracing-growth-as-an-introvert-464ef734b99b?source=rss-1ed5eccfc4a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/464ef734b99b</guid>
            <dc:creator><![CDATA[Nisha Thomas]]></dc:creator>
            <pubDate>Fri, 26 Jul 2024 23:42:22 GMT</pubDate>
            <atom:updated>2024-07-26T23:42:22.645Z</atom:updated>
            <content:encoded><![CDATA[<p>As I wrapped up my day with another successful presentation, I reflected on my journey.</p><p>I used to dread presentations. Each time, I’d struggle to find my voice and often felt overwhelmed. Everything changed when I joined my previous team. My manager was incredibly supportive, helping me find ways to present comfortably. He encouraged me to express my ideas in my own style and provided backing whenever I needed it. With this, I gradually gained confidence.</p><p>Now, as a senior designer, I realize how crucial it was to be in the right environment. It’s not just about overcoming introversion but finding people who believe in you.</p><p>Here are a few strategies that helped me get started:</p><ol><li>Find a supportive team and leader who trusts you rather than micromanaging. Remember, your ideas are important and unique.</li><li>Connect with mentors who understand your strengths and struggles, providing you with more tailored guidance.</li><li>Prepare a list of key points before meetings so you have a reference if you feel nervous.</li><li>In virtual calls, use the chat feature to share your thoughts. This helps others grasp your perspective and makes it easier for you to discuss them later.</li><li>Embrace mistakes. Introverts often overthink their communication. Accept that nobody has everything figured out.</li><li>Practice your presentations, including recording yourself. This process may take time, but it helps identify areas for improvement.</li></ol><p>I’d love to hear from others in similar situations. How did you navigate these challenges?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=464ef734b99b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 steps to navigate Design career in core Marketing teams]]></title>
            <link>https://medium.muz.li/7-steps-to-navigate-design-career-in-core-marketing-teams-d060a8498110?source=rss-1ed5eccfc4a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/d060a8498110</guid>
            <category><![CDATA[steps]]></category>
            <category><![CDATA[development-and-growth]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Nisha Thomas]]></dc:creator>
            <pubDate>Tue, 16 Jun 2020 06:42:10 GMT</pubDate>
            <atom:updated>2020-06-23T09:12:27.932Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever been the lone warrior trying to build a design team in a huge marketing organization? Have you struggled to explain why design matters so much to the success of a great marketing plan?</p><p>Let us go through some of the simplest tips to help you get started and navigate marketing team as a designer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NxnB0UK60XqPvO-r95FTSQ.png" /></figure><p>In today’s fast paced society, with billions of ads trying to convince customers, a poor design can be disastrous. Is design valued and understood by non design folks? Well, we cannot blame them. Think of an instance where you had to explain the marketing strategy and its impact to customers as a designer. Does it sound tiresome? It works the same. Not everyone out there is a designer. Hence, we as designers should strive to take ownership on building a design first culture, so that it co-exists with the rest of the team.</p><p>Easier said huh? What next?</p><p><strong>Develop a plan on how design can contribute to the team’s business goals</strong></p><p>Research and Design are the two most crucial areas, closest to the customer. They support the purchase decision of the customer. A great marketing plan with a mediocre design is nothing but a failure. People value good experience alongside quality and not mere discounts. A persuasive design bridges the gap between successful marketing and visibility of your product/service.</p><p>Be involved in marketing meetings. I know that sounds like an added task to your already hectic day. Design can deliver great end results only by being part of the entire project lifecycle. Core focus on brilliant aesthetics will fail to serve the needs of the customer and can in huge loss for the business. While aesthetics is one part, usability and holistic experience is another. To be a great design lead, get to know your team’s goals, sales figures and roadmap. Work backwards from this data. Figure out apt solutions which ties back to the overall marketing goal.</p><p>Great design solutions = Happy customers = Success of the product and ROI</p><p><strong>How to ensure you are an inevitable part of important discussions?</strong></p><p>First target? Your manager and skip levels are your best buddies. Yes, you read that right. It might take a bit of convincing skills. Guide them through the journey, explain the intent and how this supports business objectives.</p><p>After every project, document your process, linking marketing goals and design solutions. Yes, nothing works in a marketing team if you fail to summarize it in figures! If possible, capture the impact generated via fresh design.</p><p>Share your learnings with the wider group. Take necessary feedback. Towards year-end, there should be a pool of data to summarize design’s contribution. Capture the misses as much as you promote the success. No project is perfect. Every miss is a learning opportunity, so specify your action plan to rectify them in the upcoming projects.</p><p>Take time and earn trust of your team. We all strive for immediate solution towards every problem we come across. Your ability to suggest effective solutions, supported by past data will help you be in the good books.</p><p><strong>How to ensure your solutions are objective and not subjective?</strong></p><p>The biggest curse of design is the subjectivity of the field leading to <em>n </em>number of feedback. You might observe everyone within the room having an opinion which is often personal. I say “IGNORE”. Grab your diary, capture relevant feedback and ignore the rest. Aim towards solving the constructive feedback captured during every review phase.</p><p><strong>UX research and A/B testing will be your best friends</strong></p><p>For every project, refer the research docs. It specifies the user journey and states the pain points of the customer. Fulfilling the goals of the business, solutions via design is interlinked to research data.</p><p>If you find yourself stuck between various valuable feedback within the team, use this as an opportunity to A/B test. This is the magic pill to define the right approach. Iterate and re define if required basis learnings.</p><p><strong>Does it make sense to invite every member to a project review session?</strong></p><p>While you would definitely want to play the good Samaritan, this is not the time. Limit the review process to the highly relevant peers and stakeholders. Failing this approach will not only block your ability to time manage deliverables but will contribute to several open-ended questions. Remember, as we move closer to the deadline, all eyes are on design. There will be no mercy given to justify what went wrong. So act wise!</p><p>Encourage healthy feedback sessions which are constructive in nature. Debate for the right points and note down relevant conclusion.</p><p><strong>Conduct design sessions</strong></p><p>Design Hours? Design Talks? Go for it. Explain the contribution of design across projects. Use this as a platform to highlight trends in design which could be useful for your upcoming projects. It is OK if only a few show up initially. Once your session gains relevant popularity, in no time, it will be room full.</p><p>Guide the team on how to assess time taken to complete a given design task, and why. Do not let others “assume” the time taken for your job nor commit to timelines without pre alignment. Take ownership of your job and accept nothing less.</p><p><strong>What matters the most?</strong></p><p>Network and earn trust. Develop a friendly attitude towards your team and all stakeholders you work alongside. While there will definitely be moments of conflict, try to sort this out. If you struggle, seek help from your senior leadership and keep them informed. Do not let these thoughts sink in. It leads to an explosion of emotions and thereby earn you the title of being “unprofessional”. We must co-exist as a team, communicate strongly when the situation demands but never bossy! After all, nobody prefers a bossy co-worker.</p><p><em>Further, updates on how to build networks and grow as an individual designer within a marketing team will be captured in my upcoming article :)</em></p><figure><a href="http://bit.ly/34kSkxu"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PHpyFfRjRcRrnBUJL5JlDA.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d060a8498110" width="1" height="1" alt=""><hr><p><a href="https://medium.muz.li/7-steps-to-navigate-design-career-in-core-marketing-teams-d060a8498110">7 steps to navigate Design career in core Marketing teams</a> was originally published in <a href="https://medium.muz.li/">Muzli - Design Inspiration</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>