A look at how UX may shift from designing fixed flows to defining how adaptive and agentic systems behave. The article covers generative interfaces, AI-assisted research, design systems for machines, trust, permissions, reversibility, and accessibility. The central idea is worth keeping: designers may draw fewer predetermined paths and spend more time defining the boundaries within which software is allowed to create its own

Short attention spans haven’t killed long-form content: some topics are simply too complex to compress without losing clarity or trust. NN/g argues that longer copy still matters when users need depth, confidence, or strong SEO and AEO signals. The useful part is not “write more”, but structure long content so people can scan it through summaries, bullets, callouts, bolding, and visuals

A usability study with 20 disabled people and family members on how they actually search with AI, Google, and other sources. People switched tools depending on the task: AI was more attractive for complex, personalised questions, while trusted websites and search remained important for high-stakes topics. One especially telling finding: some participants blamed themselves when AI gave a poor answer, assuming they had simply written the wrong prompt

Billing microcopy should answer five things before the user confirms: how much they’ll pay, when they’ll be charged, what changes, whether they can undo it, and whether there are extra costs. The article breaks this into practical patterns like “you’re about to”, “here’s what changes”, and a receipt preview. One especially useful detail: showing the exact path to downgrade makes reversibility feel real instead of theoretical

UX starts before anyone sees the product — in the first meeting, the tone of communication, and the questions a team chooses to ask. The article argues that curiosity and informal human moments can uncover better insights than polished presentations or rigid agendas. In one CRM project, a simple question about how salespeople actually start their day helped the team avoid building several unnecessary features