ADHD UX

There is a person who reads emotional context in real time, adjusts their behavior without being asked, anticipates your needs before you articulate them, knows when to engage and when to disappear, and makes the whole thing feel effortless while managing a dozen simultaneous interactions with complete strangers in a loud, unpredictable environment. That person is not a UX designer. That person is a great bartender. The ambient intelligence system your product team is spending millions of dollars trying to build has been running perfectly behind a bar counter since before any of us had a job title. No sensors. No behavioral data pipeline. No design sprint. Just years of direct attention to what people actually need in real human moments. I wrote about the five things great bartenders do that most UX teams have never figured out, why the bar is the clearest real-world model for ambient intelligence, emotional context, and zero-UI that the field has access to, and three shifts designers can steal directly from hospitality practice. This one is fun. It is also genuinely useful. And it ends with an assignment to go somewhere with good cocktails.

Most features show users what is happening. This one had to show users what happens if they do nothing. Bridging the gap between a data scientist's model and a user's decision required a collaboration I did not fully anticipate and a design philosophy I had to build from scratch.

The brief sounded straightforward. Build a feature that shows users the cost of inaction: what happens financially, operationally, and strategically if they delay the decision the product recommends.

Six words into the implementation conversation with the data scientist I was working with, it was not straightforward.

"The cost of inaction is a function of at least seven independent variables, and the interaction effects between three of them are nonlinear, which means we cannot display a single number without misrepresenting the model."

This is the moment that defines predictive UX: the gap between what the data is capable of expressing and what a user needs to understand in order to make a better decision. The data scientist's model was correct. The interface the model implied, seven variables with nonlinear interactions displayed to a user who came to the product to make a business decision, was not going to help anyone.

This is the story of closing that gap. It took longer than either of us expected, required a design philosophy that did not exist when we started, and produced something I am genuinely proud of. It also taught me more about the intersection of data and UX than any other project in 25 years.

In 1994, a brain-computer interface moved a single cursor across a screen. By 2024, a paralyzed individual was typing 90 characters per minute using neural signals alone. By 2027, the first consumer BCI wearables will be on shelves, governments will be codifying neural rights into law, and the UX field will be asked to design for a surface it has spent thirty years not thinking about. The human mind itself. This is not a future scenario. The non-invasive consumer BCI timeline runs from 2024 to 2026 for rapid prototypes and medical applications, and 2027 to 2030 for widespread consumer adoption and AI integration. The research is confirmed. The regulatory frameworks are being drafted. The hardware is shipping. What does not exist is a design discipline adequate to the challenge. No existing framework accounts for neural variability across users. No current consent architecture is built for neural data. No error recovery pattern exists for actions the user did not consciously initiate. And every design principle the field built was built for a physical input mechanism that BCI removes entirely. I wrote about what every previous paradigm got wrong about the input layer, why 2027 is when BCI becomes a UX problem rather than a research problem, and the three shifts that define what responsible BCI UX practice actually requires. This is the most consequential design challenge the field has ever faced. The designers who start building its vocabulary now are writing the canon that everyone else will reference when the market arrives.

Every design decision you have ever made was a hypothesis about how a human brain would respond. You called it intuition. You called it experience. You called it good taste. Some of it was. Most of it was a well-meaning guess made without access to what was actually happening in the mind of the person on the other side of the interface. The era of the educated guess is ending. Neurodesign applies neuroscience directly to UX: eye-tracking that maps where attention lands before conscious awareness directs it, biometric feedback that predicts user frustration in real time before it surfaces as churn, EEG and galvanic skin response measurement that accesses cognitive and emotional states that no post-task interview can reach. A 2025 study confirmed that biometric feedback can predict user frustration before users can articulate it. The tools are no longer research lab equipment. They are in consumer wearables and production-grade camera systems right now. The ambient intelligence era, driven by emotional context, zero-UI experiences, and systems that act without being asked, requires design decisions grounded in neurological reality rather than behavioral proxy. A zero-UI healthcare system making medication recommendations needs to be built by a team that understands how the brain processes risk. An emotional context product reading physiological signals needs designers who understand what those signals mean cognitively. I wrote about what neurodesign actually requires, why every previous UX boom produced better behavioral observation and the same gap in neurological understanding, and the three shifts that move the field from guessing to knowing.

Your product has a debt problem that does not show up on any balance sheet. It shows up in your support ticket volume, your churn rate, and the designer on your team who has spent the last three sprints maintaining a mess instead of solving a problem.72 percent of respondents in a Pendo survey said they have encountered UX issues in their organization. 30 percent attributed those issues directly to a lack of investment in UX design. And AI is making this worse, not better. The same speed at which AI tools produce design artifacts is the speed at which they produce design inconsistency, and a team without rigorous design governance feeding its generative tools is not building faster. It is accumulating debt faster.UX debt is the most expensive liability most product organizations are carrying and the only one nobody has a budget line to address. The ambient intelligence era will make this reckoning happen faster than any previous paradigm, because systems that act on users’ behalf require cleaner design foundations than screens ever did. I wrote about what every previous UX boom added to the debt load, why the ambient intelligence era makes UX debt existential rather than just expensive, and the three shifts that turn it from a hidden cost into a managed asset. If you lead a design team, run a product organization, or own a roadmap that has ever shipped a shortcut with a plan to fix it later, this is the article for the planning session you are about to have.

This episode is about the UX prediction everyone else is getting half right. The industry consensus says 2027 is the year interfaces disappear and agents just act on our behalf. I break down why that story flatters the technology, what's actually changing in how agents and interfaces work together, and the one design decision I'd bet the next era on. If you build products, this is the constraint you need to be designing around now.

Every design principle you were trained on told you to remove friction. The FTC just fined Epic Games $520 million for following that advice too well. The Click-to-Cancel Rule is now enforced. The Iliad Flow, the multi-screen cancellation ordeal that made joining a service one click and leaving it an epic journey, is now a regulated dark pattern. If a user can join in two clicks, they must be able to leave in two clicks. This is not a compliance story. It is a design philosophy story. The field spent thirty years teaching frictionless as a virtue and optimization as a goal, and in 2026, the regulatory environment is writing the correction into law because the industry did not write it into its own design standards first. Research published in 2025 named the deeper consequence: in AI-supported decision-making, the frictionless approach leads to automation bias, where users uncritically accept AI recommendations, degrading human skills and weakening professional accountability. A field that removed friction from human decision-making also removed the deliberateness from human decisions. I wrote about how intentional friction is the most undervalued design skill in the field right now, why every previous UX boom created the conditions for frictionless design to be weaponized, and the three shifts that separate designers who build products users trust from designers who build products regulators eventually correct.

The NIL economy is worth $2.75 billion in 2026. Eighty-four percent of it flows to football and men’s basketball players. Every other college athlete in every other sport is competing for the remaining sixteen percent, with no platform designed to find them, match them, or close the gap between their genuine market value and the sponsors who would pay for access to their audience. That is not a market problem. That is a design problem.NIL238, currently in patent-pending status, is the platform built to close that gap: AI-powered athlete-sponsor matching, compliance guidance built directly into the deal flow, and a sponsor experience designed around curated recommendations rather than directory browsing. Women’s volleyball and softball have seen triple-digit NIL growth. Engagement on women’s athletes' social accounts is nearly three times higher than that of the average influencer. The sponsors exist. The platform that matches them intelligently and guides the deal to a compliant close does not yet exist at the scale the market requires. I wrote about how UX is the missing piece in every college athlete’s sponsorship strategy, what every previous attempt at NIL matching got wrong, and the three design shifts that make NIL238 work where other platforms have not. If you work in sports technology, athletic administration, brand marketing, or UX strategy and you want to understand what a well-designed NIL platform actually looks like, this is the article that makes the case.

Most teams are designing from opinion and calling it intuition. The teams that will define the next decade are designing from signal and letting AI close the gap between what they believed and what is actually true. Sixty-five percent of design teams now use AI to accelerate interface creation and test UX hypotheses. The acceleration is real. The discipline to close the loop between that acceleration and genuine design improvement is missing in most organizations. Teams are generating more designs faster without a rigorous mechanism for understanding which ones work and why, and without feeding that understanding back into the next decision. The data capture and AI refinement loop is not a tool. It is a practice, and it has four specific phases: defining what signal actually matters before building anything, capturing behavioral, contextual, and qualitative data simultaneously rather than in silos, letting AI surface patterns that humans then interrogate and act on with judgment the AI cannot supply, and running that cycle continuously rather than saving all validation for a big, expensive periodic study. I wrote about what every previous UX boom got wrong about learning from users, why the ambient intelligence era makes this the highest-leverage design practice available, and the specific loop that separates teams that compound their design quality from teams that generate output without compounding anything. If you lead a design team, run a product organization, or make decisions about how design and data work together at your company, this article reframes what your process should look like.

The average American driver loses 43 hours a year to traffic, a full work week spent staring at brake lights. The technology to fix this exists right now. The reason most cities still feel broken is not a sensor problem. It is a design problem, and almost nobody in UX treats it as such. Delhi’s AI-managed traffic corridors have reduced signal wait times by 30 percent. Bengaluru’s adaptive traffic control system is cutting travel times by up to 15 percent on key stretches. Hangzhou’s City Brain project has measurably reduced both congestion and pollution. The engineering behind these systems is genuinely excellent, and it is advancing faster than most UX professionals can keep up with. What is almost entirely missing from these deployments is design. Ambient intelligence, zero-UI, systems that act without being asked: these are not future predictions for traffic infrastructure. They are the current operating reality of traffic management in major cities, and the trust architecture, explanation design, and graceful failure thinking that UX has been developing for AI products have barely been applied to a domain that needs them urgently. I wrote about why traffic is the most consequential, least-examined UX opportunity in the field right now, what every previous UX boom got wrong about where design responsibility ends, and the three shifts that would let UX designers actually contribute to one of the most important ambient intelligence systems already shaping daily human life. If you work in UX, civic technology, urban planning, or AI product strategy, this is the article that points to a real, underserved, urgently needed space almost nobody in the field is occupying yet.

Adults over 60 control 27 percent of global consumer spending. They account for 34 percent of global wealth. There are 58 million Americans in this demographic right now, heading to 74 million by 2035. Smart aging device adoption is up 36 percent in two years. Smart home adoption among seniors is up 33 percent. Telehealth use is up 41 percent. This is the fastest-growing, wealthiest, most brand-loyal demographic segment in the developed world. And most digital products designed for them start by making the font bigger and calling it inclusive design. That is not inclusive design. That is condescension with a design system applied to it. I have been building CareHub 65+ for this user for years. The design brief is more demanding than any younger user demographic I have designed for. The user is unforgiving of products that treat aging as a limitation to be managed rather than a life stage to be served. And the market opportunity, $4.2 trillion in 2025 growing at 7.6 percent annually, is larger than most teams have recognized because they have been too busy making the font bigger to look at the numbers. I wrote about what the research actually says about aging and digital technology, what every previous UX boom got wrong about this user, and the three shifts that separate silver economy design done right from silver economy design that is just smaller type made larger.

Sarah, 34, marketing manager, shops online twice a week, prefers email. Sarah is not a user. Sarah is a design team’s refusal to sit with ambiguity. The persona is the most beloved tool in the UX practitioner’s kit and, in its current form, one of the most quietly damaging. Not because it was wrong when Alan Cooper invented it in the 1990s. It was exactly right for its moment. But that moment was thirty years ago, before behavioral data at scale, before real-time user telemetry, before AI capable of dynamically modeling individual user behavior. Spotify’s user research team found that music discovery behavior now correlates more strongly with AI interaction patterns than with age, income, or location. Airbnb discovered that personas built on travel preferences became obsolete the moment users started using AI to plan trips. A Columbia University study confirmed that AI-generated personas contain critical flaws and that creating accurate user representations remains a fundamentally human activity requiring empathy, observation, and methodological rigor. The ambient intelligence era, driven by emotional context and zero-UI experiences, requires a model of the user that updates in real time as context shifts. The static demographic archetype cannot do this. It was not built to do this. I wrote about what the persona got right, what it gets wrong now, and the three shifts that replace it with something the next wave of UX actually requires. If you work in UX research, product design, or design leadership and your team still runs persona workshops as the foundation of a product brief, this is the article to read before the next one.

The design industry has been stripping interfaces down for thirty years and calling it progress. By 2027, the stripping will be finished by AI, and what remains will reveal whether designers understand what they were actually building. Research identifies hyperminimalism and predictive UX as the defining design challenge of 2027. Not minimalism as an aesthetic. Hyperminimalism as a structural consequence of AI handling what the visual layer previously had to make explicit. The menu that helped you navigate ceases to be necessary when the AI already knows what you need. The form that captured your input becomes redundant when the system predicts it. The confirmation screen disappears when ambient intelligence has already acted. What remains after this displacement is not a cleaner interface. It is a different kind of design problem: how do you design the residue of what cannot yet be handled invisibly? How do you design the recovery path when the prediction fails? How do you design the spectrum between presence and absence across a system that expands and contracts based on what the AI knows about you right now? I wrote about what every previous UX boom got wrong about simplicity, why hyperminimalism and predictive UX are the same design problem viewed from different angles, and the three shifts that separate interfaces that have been thoughtfully reduced from interfaces that have been carelessly emptied. If you work in UX, product design, or design strategy and you are planning a redesign for 2027, this is the article that reframes what you are actually designing for.

Your AI explained its decision. The user trusted it. The explanation was wrong, the decision was wrong, and the trust made everything worse.Research confirms that merely adding explanations to AI decisions increases user trust and perceived fairness, regardless of whether the explanation is accurate or the decision is correct. HCI researchers have named this category of problem: placebic explanations, explanations devoid of actual justificatory content that produce trust without producing understanding.By 2028, over 40 percent of enterprises will adopt hybrid computing architectures, making explainability critical to every AI interaction. The EU AI Act requires explanations. The US has demanded them. But nobody has clearly defined what a good explanation actually is, and the design industry is building explanation interfaces at scale without having answered that question.The next wave of UX, ambient intelligence, emotional context, and zero-UI, operates in domains where misplaced trust is not a usability problem. It is a patient outcome, a financial decision, an autonomous action taken on someone's behalf without their full understanding of why.I wrote about what the research actually says about XAI and trust design, why every previous UX boom created new legibility and new manipulation simultaneously, and the three shifts that separate explanation interfaces that earn trust through accuracy from explanation interfaces that are the most sophisticated dark pattern the field has ever built.If you work in AI product design, UX strategy, or technology leadership and you are building systems that explain themselves to users, this is the article that reframes what you are actually responsible for.

Your interface does not know you are having a bad day. By 2027, it will.The sentient interface is the next design frontier, and the gap between what these systems can already perceive about users and what designers have thought about how to handle that perception is going to produce the most significant UX failures the industry has ever shipped.OpenAI's multimodal models can already interpret tone and images simultaneously. Hume AI is building voice interfaces that respond to emotional cues in real time. Wearables are tracking heart rate variability and behavioral signals continuously. The capability is not five years away. It is in development, in testing, and in early production right now.By 2027, sentient interfaces will shift from a research concept to a standard feature in consumer, healthcare, automotive, and enterprise products. And the designers who have not yet asked what they are permitted to infer, how they should disclose what they know, and what happens when the emotional inference is wrong are already behind the conversation that will define whether these products build trust or erode it.I wrote about what every previous UX boom got wrong about who was doing the understanding, why 2027 is the year sentient interface design becomes a practice rather than a prediction, and the three shifts that separate designers building emotionally intelligent products responsibly from designers building intrusive ones confidently.If you work in UX, product strategy, or technology leadership and you want to understand what is coming before it requires explaining, this is the article to read before the end of this quarter.

You have been designing for the wrong user. The next interface you build will not wait for instructions. It will take them. Jakob Nielsen named it in January 2026. Delegative UI. The shift from Conversational UI, where you ask an AI a question and decide what to do with the response, to a model where you assign a goal and an agent plans, executes, and iterates autonomously while you are doing something else entirely. Gartner projects that 40 percent of enterprise applications will embed task-specific AI agents by the end of 2026, up from under 5 percent in 2025. Most of those implementations will need an interface layer that did not exist a year ago, built on design patterns that the field has not yet established, for a trust and accountability model that looks nothing like anything designed before it. Research on what goes wrong is already underway. Microsoft Security’s 2026 red teaming report documented delegation chain failures, trust escalation, and accountability breakdowns in deployed agentic systems. Gartner forecasts over 2,000 legal claims related to AI agent failures by the end of 2026. These are design failures wearing the costume of technology failures. I wrote about what every previous UX boom got wrong about control, why Delegative UI breaks every assumption the field was built on, and the three shifts that separate designers building agentic systems that earn trust from designers building agentic systems that erode it.If you work in UX, product strategy, or technology leadership and you are building in the agentic AI space, or about to, this is the article to read before your next sprint.

Eighty-eight percent of organizations now use AI in at least one business function. One percent have achieved anything close to AI maturity. The gap between those two numbers is not a technology problem.It is a fluency problem. And the industry is solving it badly.McKinsey found that demand for AI fluency jumped nearly sevenfold between 2023 and mid-2025. Deloitte's 2026 survey of over 3,000 global leaders found that the AI skills gap remains the single biggest barrier to integration, even as worker access to AI rose 50 percent in the same period. Most organizations do not lack AI tools. They lack AI judgment. And those are not the same problem.The next wave of UX is driven by ambient intelligence, emotional context, and zero-UI experiences. The fluency required to design these systems is meaningfully different from the prompt fluency that most current AI training programs are building, and the organizations that cannot tell the difference are going to spend the next three years generating impressive-looking AI activity without generating products that actually work.I wrote about what genuine AI fluency looks like versus what familiarity with AI tools looks like, why every previous UX boom created the same gap between vocabulary and instinct, and the three shifts that separate organizations building real capability from organizations building the appearance of it.If you lead a design team, run a product organization, or make decisions about AI investment and talent strategy, this is the article that belongs in your next planning conversation.

There is no such thing as an unbiased competitive analysis. And the moment your team starts believing AI has finally solved that problem is the moment your bias becomes invisible to you.AI-powered competitive analysis tools are being marketed as the solution to subjective bias, information overload, and slow manual research. The pitch is seductive: feed in your competitor's product, get back an organized, pattern-identified, objective summary in minutes.The hallucination research tells a different story. AI hallucinations are not random errors. They are plausible, confident, fluent statements that may or may not be true, and the research shows this is a structural property of how these systems are trained and evaluated, not a bug that gets fixed with a better prompt.For the next wave of UX, ambient intelligence, emotional context, and zero-UI experiences, the most important competitive differentiators are invisible to any analysis method built around interfaces. An AI tool asked to evaluate a competitor's emotional inference system or ambient decision logic will generate a confident answer about something it has no way of actually knowing.I wrote about why every previous UX boom introduced a method that felt like it solved bias and actually relocated it, and the three shifts that separate competitive analysis that holds up from competitive analysis that just sounds like it does.

Physicians spend more time documenting care than delivering it. Epic built the system that made that true.According to the AMA, physicians work 57.8 hours a week and spend less than half of those hours on direct patient care. Ninety-two percent of nurses say EHR systems have negatively impacted their job satisfaction. Documentation is the number one driver of physician burnout. And a major implementation study found that five years after Epic go-live, 32 percent of users remained dissatisfied or very dissatisfied with the system.Epic powers over 250 million patient records. It is the operating system of American healthcare. It is also, by every measure of its primary users' experience, the most expensive usability failure in the history of enterprise software.Epic is now investing in ambient AI documentation, a redesigned interface, and an agentic AI roadmap. These are real and meaningful steps. They are also not enough if the underlying design philosophy does not change.I wrote about how I would approach the redesign: what the ambient intelligence era makes possible that no previous technology did, the three shifts I would build the new architecture around, and why adding AI to a system designed for data capture produces a faster version of the wrong thing rather than a better version of the right one.If you work in health tech, UX, product strategy, or clinical informatics, this is the article for this moment.

The product that captured your users' attention was not designed to serve them. It was designed to capture them.Fifty-seven percent of US adults identify as smartphone addicted. Brain scan research has confirmed that personalized recommendation systems trigger the same neural pathways as addiction. Infinite scroll, autoplay, and notification architecture designed to generate compulsive checking are not side effects of good design. They are the designed outcome of a business model that treats user attention as a resource to be extracted.The next wave of UX, built on ambient intelligence, emotional context, and zero-UI experiences, has the potential to be the first paradigm shift that closes the gap between what technology is capable of doing to users and what designers have been willing to ask whether it should.I wrote about what mindful design actually requires in practice, why every previous UX boom expanded that gap rather than closed it, and the three shifts that separate designers building the next generation of products responsibly from designers building it and deferring the consequences.This is not a comfortable article. It is not meant to be.If you work in design, product, or technology leadership and you have ever shipped something that captured more of your users than it served, this one is for you.

Your product is illegal in more countries than you think. And the countries where it is not illegal yet are writing the law right now.More than 30 countries now have enforceable digital accessibility laws. The European Accessibility Act began enforcement in June 2025 and applies to any business selling into EU markets, regardless of where that business is headquartered. In the US, over 5,000 digital accessibility lawsuits were filed in 2025 alone, a 27 percent increase from the prior year, with settlements ranging from $5,000 to $120,000 plus legal fees. And 96.8 percent of existing websites currently fail basic compliance standards.The next wave of UX, driven by ambient intelligence, emotional context, and zero-UI experiences, changes the accessibility equation more fundamentally than any previous paradigm shift. For the first time, the design philosophy required to compete at the frontier of the field and the design philosophy required to serve the full range of human capability are the same philosophy.I wrote about what the global regulatory landscape actually looks like right now, what every previous UX boom got wrong about who it was building for, and the three shifts that separate organizations building globally compliant products from organizations accumulating legal exposure they have not yet been invoiced for.If you lead a design team, run a product organization, or make decisions about digital products that reach global markets, this is the article to read before your next compliance conversation.

The idea behind Zero-UI is more than thirty years old. Mark Weiser described it at Xerox PARC in 1988 as the age of calm technology, when technology recedes into the background of our lives. The best computer is a quiet, invisible servant.Most of what is currently being called Zero-UI is not that. It is a voice command layer on top of a screen-based product, or a gesture system that replaced a button, or an ambient device that collects behavioral and biometric data without the user fully understanding what that means.The infrastructure to actually realize Weiser's vision is now here. The design discipline required to deploy it responsibly is still being built. The gap between those two things is where the most important and most dangerous UX work of the next decade is happening.I wrote an in-depth piece on what Zero-UI done right actually requires: how to design system judgment rather than just system actions, why invisible systems need audit layers more than visible ones do, and why the consent model the entire industry is currently using is borrowed from a paradigm it was designed to replace.If you are building in this space, leading a team that is, or advising an organization that thinks Zero-UI is on their roadmap, this is the article to read before the next project scoping conversation.

The most dangerous person in your design organization is not the underperformer. It is the creative director who cannot let anything leave the room without their fingerprints on it. I wrote the article that most creative leaders need to hear and that most of their teams have been waiting for someone to say out loud. Teresa Amabile's 45 years of research at Harvard identified autonomy and psychological ownership as prerequisites for genuine creative output. When designers feel they own the problem, they bring their full capacity to it. When they are waiting for approval at every stage, they bring enough to get through the review. The difference is not subtle, and it shows up in the work. The next wave of UX is built on ambient intelligence, emotional context, and zero-UI experiences. All three require iteration speeds and creative risk-taking that approval-bottleneck leadership makes structurally impossible. This is about the creative leader who rewrites every brief, opens Figma files at 11 pm to leave forty comments, and cannot let a presentation reach a stakeholder without personally revising the narrative. It is about what that behavior costs in output quality, team attrition, and competitive position. It is also about what to do instead.

Your best designer has not had an original idea in three weeks. Your meeting schedule is the reason.The research on this is not ambiguous. The average knowledge worker spends 392 hours per year in meetings. Three out of four of those meetings are considered totally ineffective by the people inside them. Half are scheduled during the exact windows when creative professionals are neurologically at their peak. And it takes 23 minutes to fully recover focus after a single interruption, which means most designers are never actually in the deep creative state where the work that matters gets done.The next wave of UX is driven by ambient intelligence, emotional context, and zero-UI experiences. All three require the kind of sustained, original thinking that a meeting-heavy calendar makes structurally impossible.I wrote about what the research actually says, why meetings are only half the problem (the tool stack your team runs on is doing the other half), why this is about to become more consequential than it has ever been, and the three shifts that protect the conditions creative professionals need to do their best work.If you lead designers, manage product teams, or run a company that hired creative people for creative output, this is the article you need to read before you schedule your next sync.

Anyone can follow a recipe. Very few people can actually bake bread.I spent time thinking about why that distinction is the most accurate description of where UX design is right now, on the edge of the most technically complex and humanly demanding shift the field has ever faced, and why the practitioners who will define it are not the ones with the best frameworks.They are the ones who developed real craft. Who studied their failures more carefully than their successes. Who got comfortable working without a recipe long before the conditions demanded it.The next wave of UX is driven by ambient intelligence, emotional context, and zero-UI experiences. None of these have established patterns yet. None of them can be navigated by following a methodology. All of them will separate the practitioners who built genuine instinct from the ones who got very good at applying other people's thinking.I wrote about what that looks like, why every previous UX boom made the same separation, and the three shifts that will determine which side of that line you end up on.If you work in design, product, or technology leadership, this one is less comfortable than it looks from the title. That is the point.Read it. Share it with someone who needs to hear it. And ask yourself honestly when the last time was that you made something you did not already know how to make.

Every spring, someone shows up to the first sailboat race of the season absolutely certain they are ready. The gear is right. The vocabulary is right. The confidence is high.Then the race starts and the water explains, quickly and without apology, the difference between knowing the words and having the feel.That dynamic is playing out across every design team and product organization in the industry right now, and the body of water is AI.I wrote about what sailing teaches about learning UX in the age of ambient intelligence, why every major UX boom in history produced the same sorting between people who got on the water early and people who waited on the dock, and what the three conditions of the current race demand from every designer and product leader paying attention.This is not a metaphor for its own sake. It is a precise description of exactly where the field is and exactly what it costs to treat new conditions as though your old instincts are enough.If you have ever sailed, you will feel this immediately. If you have never sailed, you will recognize the dynamic from somewhere else in your career.Either way, the season has started. Read it, share it with someone who needs to hear it, and ask yourself honestly whether you are on the water or still on the dock.

Large companies do not buy startups because they ran out of engineers. They buy them because a small team with limited resources built something that a massive organization with every advantage could not.That should be the most uncomfortable sentence in the industry. Somehow it rarely is.What happens next is the part nobody talks about honestly. The acquired team gets welcomed. The culture preservation promises get made. And then the integration installs exactly the process machinery that was the reason the large company needed to buy the small one in the first place.Six months later, the product velocity is gone, half the founding team has left, and somebody is scheduling a retrospective to figure out what happened.I wrote about why this pattern is about to become even more consequential as ambient intelligence, emotional context, and zero-UI reshape the next wave of UX. About why the next boom belongs to the teams nimble enough to build it. About the moment the acquired team stalls and the organization does not look inward at the process that caused the problem but outward, to an agency, as though the issue was ever a skills gap. And the three shifts that separate organizations actually moving from organizations performing movement in Slack.If you are a founder, a product leader, or someone inside a large organization who has watched this happen and wondered whether it had to, this one is for you.Read it. Share it with the person who just scheduled the meeting about the meeting. And ask honestly whether your process is building the future or protecting the past.

What if the most important design surface of the next decade is invisible? I am a UX designer, not an engineer -- and after completing the entire Anthropic Academy curriculum, I became convinced that the way we think about interfaces, interaction, and experience design is about to be disrupted more completely than it was by mobile. Today I want to talk about ambient intelligence, zero-UI, and why the designers who are paying attention to AI infrastructure right now will be the ones writing the playbooks everyone else follows in five years. Let's get into it.

Most teams think they practice inclusion. Most teams practice a snapshot. Research at the start. Accessibility audit at the end. Ship the product. Move to the next thing. Repeat. What that process produces is a product built for one version of a user, frozen in time, in a world where users are anything but frozen. Their health changes. Their context changes. Their stress levels, cognitive load, and physical capacity change from day to day and year to year. And the product stays exactly where it shipped. That is not inclusion. That is a photograph of inclusion. The next wave of UX, built on ambient intelligence, emotional context, and zero-UI experiences, makes it possible for the first time to create something genuinely different: inclusion that follows the user through their actual life rather than capturing them once and moving on. I wrote about what that looks like, why every previous UX boom preserved the same blind spots while advancing everything else, and the three shifts that separate teams building products that truly adapt from teams that are still running annual audits and calling it done. If you work in design, product, or technology leadership, this one will either validate the work you are already doing or name the work you have been putting off.

I am going to ask the question directly that most design content dances around.Is Zero-UI a real design paradigm or is it the kind of idea that sounds visionary at a conference and disappears when the actual work starts?I have been thinking about this for a long time, and I finally have an answer I am willing to defend. The short version: it was a buzzword. It is not anymore. The infrastructure that was missing in 2015 when the conversation first emerged is arriving right now, and the combination of ambient intelligence, emotional context, and sensor-driven computing is turning a philosophy into a practice faster than most design teams are tracking.The longer version is in the article. I wrote about what every UX boom got wrong about where interaction lives, why this moment is categorically different from every previous announcement of the interface's death, and the three shifts that separate designers who will build Zero-UI products from designers who will just talk about them.If you work in UX, product, or technology leadership and you have an opinion about where the field is going, this will either confirm your thinking or challenge it. Either outcome is worth your time.Read it, share it, and tell me where you think I am wrong.

One in four adults lives with a disability. Most of the digital products they use were not designed for them. They were designed for someone else, then patched to accommodate them afterward. That is not accessibility. That is managed exclusion.AI is about to make that distinction impossible to sustain.The next wave of UX, driven by ambient intelligence, emotional context, and zero-UI experiences, is also the first wave with the genuine technical capability to center accessibility as architecture rather than afterthought. Not a compliance layer. Not an audit checklist. The actual foundation of how the product thinks about its users.I wrote about what that looks like, what the industry has gotten wrong across every UX boom in history, and the three shifts that designers need to make right now if they want to be part of building something that actually works for everyone.This is the most important design conversation happening right now. It is also the one getting the least attention in the rooms where product decisions get made.

AI built it. Now what?

A lot of designers and founders are sitting on AI-generated prototypes that look finished and fall apart the moment a real user touches them. The layouts are clean. The thinking is missing. And the gap between the two is getting harder to hide.

I wrote about why AI makes design judgment more important, not less. Why the next wave of UX, driven by ambient intelligence, emotional context, and zero-UI experiences, has no tolerance for people who skipped the fundamentals because the tools made production feel easy.

If you are a designer, a founder, or a product lead who has been moving fast and building on a foundation you never fully laid, this article is for you.

The tool got faster. The craft did not get optional.

Read it, share it with your team, and ask yourself the one question at the end that is going to be uncomfortable for a lot of people.

I am going to say what the industry has been too polite to say out loud.

People are lying on their resumes about AI experience. Recruiters are too underprepared to catch it. Companies are hiring bad talent and wondering why their AI initiatives are stalling. And the whole cycle keeps spinning because nobody wants to be the one to call it.

I will.

The next wave of UX is not coming from better interfaces or shinier design systems. It is coming from ambient intelligence, emotional context, and zero-UI experiences, and it will expose every fake credential in the room the moment it arrives. The gap between what people claim to know and what they actually know is about to become very, very visible.

If you are a designer, a product manager, a founder, or a recruiter, this one is for you. Especially if it makes you a little uncomfortable.

Read the full article. Share it with your team. Send it to the last person who listed "AI-powered design" on their resume because they used ChatGPT once.

The industry needs more honesty and fewer buzzwords. This is a start.

Most designers are looking for the next big UI trend. They’re looking at spatial computing or refined glassmorphism. They’re looking in the wrong place.The real boom isn’t in how things look—it’s in how they anticipate.We are moving away from clicking buttons and toward "Intent-Based Orchestration." In this new era, the best interface is the one that disappears. If you’re still designing for clicks instead of outcomes, you’re preparing for a world that’s already behind us.In this [Article/Episode], I break down:

• Why the "Pixel-First" era is ending.
• How Generative UX will redefine design systems.
• The skills you need to survive the shift from Designer to Orchestrator.

Two UX designers walk into a ring. Same brief, same tools, same deadline. One walks out with the contract. The other walks out wondering what just happened. In this piece -- and on this episode -- we get into exactly what separates them, why AI is not the threat most designers think it is, and what it actually takes to stay relevant when the pace of the craft is accelerating faster than any design system can keep up with.

The screen just left the building.

For thirty years, UX had a container: edges, pixels, a scroll direction everyone agreed on. That container is dissolving. Spatial computing, AR, VR, mixed reality. The next platform does not live behind glass. It lives in the room you are standing in, responds to how your body moves through it, and makes motion sickness a design failure and presence the new measure of usability.

I write about what UX becomes when the frame disappears. About immersive technology, brand strategy, and the gap between what digital experiences promise and what they actually feel like to be inside.

Currently playing: something spatial. Something that fills the room.

The world is not short on technology. It is short on people who know how to make it feel like it was made for humans.

I'm a UX designer who stopped believing the work belongs only inside tech. The same thinking that fixes a broken checkout flow can fix a broken benefits system, a hospital interface that burns out clinicians, an AI product nobody knows how to use. Human-centered design is not a product-team problem. It is the problem of our moment — and it needs people willing to take it somewhere it hasn't been yet.

I write about that. About brands that forgot why they mattered. About systems that were designed without the person in mind. About the gap between what technology promises and what it actually feels like to use.

Currently playing: whatever sounds like someone who figured something out and can't stop thinking about it.

Unboxing UX -- The soundtrack for designers who think in systems and feel in pixels. Deep focus, creative flow, and the kind of tracks that make wireframes feel like poetry. Curated by [Your Name], Senior UX Designer. Press play. Open the box.

The slow, beige, committee-approved death of a brand that once felt like a calling.That's what happened to Lululemon. Not a scandal. Not a bad CEO. Just the pressure to appeal to everyone — until it meant something to no one.I broke down what actually broke: the product that got predictable, the innovation chief who left and took the pipeline with her, the community that got optimized into a transaction. Then I wrote the five-move playbook I'd run if it were mine to fix.I write about brands that used to mean something and what it costs them when they forget why.Currently playing: whatever a brand sounds like right before it decides to be brave again.

I design experiences people use without noticing — which means I've spent years throwing user research, frozen bananas, and stakeholder mystery liquid into a blender and calling it a sprint.I'm a UX designer who believes the chaos isn't a detour. It's the road.Currently playing: whatever track makes wireframes feel like therapy. Probably something by Floating Points or a lo-fi playlist titled "ship it" that I made at 11pm before a deadline.

This one is going to hit hard and I hope leaders take note.

Designers are often told they ask too many questions.

Why are we building this?
Who is this actually for?
What problem are we solving?

After 20+ years watching companies grow, reorganize, and lay off entire departments, I’ve come to a different conclusion.

Those questions aren’t friction.

They’re leadership.

In this article and episode, I break down why UX leaders are built for the C-suite, and why the very mindset that gets pushed down in organizations is the one that should be leading them.

Because the next generation of executives won’t be defined by control.

They’ll be defined by clarity.

There are too many AI design tools right now.New ones every week. New features every day.Most people are stuck trying to choose the right one.That’s the wrong focus.In this article and episode, I break down why tool selection is less important than commitment, how real leverage comes from workflow, and why depth beats breadth in an AI-driven design world.Because the advantage isn’t the tool.It’s how you use it.

The idea of a “target audience” is breaking.Users don’t behave like segments. They behave like individuals in moments.In this article and episode, I break down the shift to “one user, right now,” how AI is enabling real-time experience assembly, and why creative and targeting are collapsing into a single optimization layer.Because the future of UX is not designing for groups.It’s designing for the individual in the moment.

Generative AI started as a novelty.Chatbots. Content generation. Impressive outputs.But it didn’t change how work actually got done.Now that’s shifting.In this article and episode, I break down the move from generative AI to agentic UX, where systems don’t just respond, they plan, decide, and act on behalf of the user.Because the future of UX is not interaction.It’s delegation.

I’ve spent the last month in meetings debating registration and login UX. Multiple senior leaders. Strong opinions. Endless discussion. And I keep coming back to the same question. In 2026, why are we still designing this from scratch? In this article and episode, I break down why registration and login should be standardized, how teams get stuck over-optimizing solved problems, and where UX effort should actually be spent. Because the best login experience is the one users never think about.

Searching for funding is usually the wrong focus.Funding doesn’t validate your product. It amplifies it. If what you’ve built isn’t working yet, funding won’t fix it.In this article and episode, I break down why most teams chase funding too early, what investors are actually looking for, and why real traction matters more than any pitch.Because funding isn’t the milestone.It’s the result.

Most companies don’t have an execution problem. They have a thinking problem. In this piece, I explore the idea of “Ideas as a Service” and whether companies would pay for structured, continuous thinking the way individuals pay for education. A model that sits above execution, challenges assumptions, and builds real capability over time.

I've sat in enough PI Planning events to know exactly what's wrong with them , and it's not the engineers. It's that we keep pulling UX/UI designers into a model built for delivery teams and wondering why the design work never gets ahead of the build. In this episode, I break down what the best orgs are doing differently, and why separating design planning from delivery planning might be the most cost-effective change a scaled agile org can make.

I wish I had learned this earlier.Not tools. Not frameworks.Just one habit.Always ask why.Some of the biggest mistakes in my career didn’t come from bad execution. They came from solving the wrong problem. And the only way to catch that is to question what seems obvious.In this article and episode, I break down how asking “why” changed how I approach UX, product, and leadership, and why it matters more than ever in a world of increasing complexity.

“Recommended for you” is not personalization.

I learned that the hard way. We built what looked like a strong personalization engine. It had data, logic, and segmentation behind it. It should have worked.

It didn’t.

In this article and episode, I break down why most personalization is broken, the difference between targeting and real-time behavioral understanding, and what it actually takes to create experiences that feel relevant instead of ignored.

Because personalization is not about who the user is.

It’s about what they need right now.