We often describe products as user friendly. But what happens when users are not system friendly?

Several years ago, while working on a client pitch from a remote location, I encountered severe network constraints—connectivity was unreliable, bandwidth was limited, and even basic actions such as loading a page took considerable time. What seemed like a situational limitation at the time later surfaced as a broader UX design insight.

Most UX design work happens in controlled environments. We design on fast Wi-Fi, using high-performance devices, in relatively distraction-free settings. However, many users interact with digital platforms under very different conditions, including limited connectivity, using low-end devices, in harsh lighting, or under time pressure.

These are not edge cases. These are the everyday realities of real-world systems. Read More

When Apple launched Assistive Access in 2023, Tim Cook said something that should be obvious to anyone building digital products but somehow still isn’t: the best technology is technology that we build for everyone. Apple didn’t bolt accommodations onto an existing user interface. They rebuilt the experience from the ground up, stripping apps down to their essential functions and designing for how people actually process information. What they launched was cleaner, faster, and easier for everyone, not just users with disabilities. This wasn’t a happy accident. It is what happens when you design for the hardest user in the room.

Most companies design for efficiency. They do not design for how people actually move through the world. The neurodivergent user makes that gap and the upside of closing it impossible to ignore. Read More

As many experts have predicted, artificial intelligence (AI) has delivered massive productivity gains in 2025. According to the Reveal 2026 Top Software Development Challenges Survey, 52% of organizations increased their productivity last year. Many achieved these gains by incorporating AI, embedding analytics, and automating repetitive work.

At the same time, economic pressures are reshaping organization’s expansion plans. A quarter of organizations are planning to cut their spending in 2026. More than half (54%) are delaying product launches or expansions and 43% are reducing their innovation budgets. This creates structural tension. Teams are trying to integrate more intelligence into their products while operating under tighter budgetary constraints. Demand remains strong, but execution capacity has narrowed.

A low-code platform context means moving away from custom-coded AI black boxes toward modular, drag-and-drop AI components that enable rapid iteration without heavy development overhead. This tension is central to developing the product experience in 2026. AI, analytics, and economic pressures are now shaping how teams design, build, and ship intelligent software. Read More

There is a type of user that UX designers rarely celebrate: one who opens a product, finds one path that works, and never deviates from it. No feature discovery. No curiosity. No Oh, what does this button do? This user has found his groove and is staying in it.

While the temptation is to call this a UX design failure, it’s not. It’s actually one of the most honest signals your product can receive, and designing for it instead of against it might be the smartest move you can make. Read More

I write most of my columns as playbooks: the system, the principles, and the work in front of us. This column is different. This time, I don’t have a framework to give you. What I have is a growing conviction about what work remains distinctly ours as UX designers—and I worry about what we might inadvertently relinquish if we don’t pay attention.

We’ve been spending a lot of energy asking what artificial intelligence (AI) will change about UX design. We’ve given far less attention to asking how working with AI might change UX designers. I’ve watched capable designers become faster over the last two years without growing more perceptive. AI often hands us more answers while eroding our patience for uncertainty. It can connect us to an ocean of information about people while distancing us from the people themselves. The risk I keep circling back to isn’t our losing the ability to do the work. It’s our becoming highly efficient makers who drift further and further from the people who we serve, the consequences of our designs, and the meaning behind what we make.

I wrote previously about avoiding creative atrophy: protecting our craft and our thinking. This column is about is the deeper version of that mission. Creative atrophy is losing the ability to do the work. Human atrophy is losing sight of those for whom we do our work. Read More

In 1992, Ward Cunningham introduced a metaphor that gave engineering leaders a new vocabulary. Technical debt, he argued, is what you take on when you ship code that is good enough for today but wrong for the long term. Taking a shortcut is not free. Interest accrues. Eventually, you must pay the principal back with all the compounded charges or the system would collapses under the weight of decisions that no one wants to revisit.

Information architecture (IA) and other UX design practices work the same way, but few organizations use this metaphor for IA debt, which is a problem because IA debt is real, measurable, and is likely growing inside every organization that has been running a digital product for more than a year. IA debt accrues quietly, hidden behind small editorial decisions and well-meaning content drops. IA debt compounds because teams must slot every new piece of content into a structure that has already drifted away from coherence. An organization pays back IA debt eventually, in the form of redesigns, lost conversions, and customers who quietly stop showing up.

Organizations must take IA debt seriously. In this column, I’ll explain where IA debt comes from, what it costs, how to audit it, and how to pay it down without setting fire to your IA roadmap. Read More

Almost every principle of usability encourages UX professionals to make user interfaces faster. We reduce clicks, simplify navigation, shorten forms, and remove friction wherever we find it. We celebrate speed because it usually helps people complete their tasks with less effort. Most of the time, that’s exactly the right goal. But not every user interaction should become faster. Some actions deserve a pause—such as deleting a patient record, sending money to the correct recipient, approving a prescription for a medication, or publishing confidential information. In these moments, hesitation is not a flaw in the user experience. It is part of good judgment.

Yet we often treat hesitation as something to eliminate. When users pause before clicking a button, we might assume the user interface has failed. When users stop to reread a confirmation screen, we might wonder how to simplify it. We have become so focused on removing friction that we sometimes overlook the value of reflection. Read More

When Meta launched Threads in July 2023, it positioned the product as a global competitor to X, formerly Twitter, a text-based social platform with a consistent user interface across all markets. Yet Taiwan quickly became one of Threads’ strongest markets, accounting for an estimated 18 to 26 percent of its global Web traffic, despite having a population of only 23 million. Users adopted the same product for very different reasons across markets.

In the United States, Threads struggled to differentiate itself from X, many perceiving it as a very similar product with a familiar user interface, but few distinct features or clear advantages. In Taiwan, however, Threads filled a gap with a capability that the country’s digital landscape had long lacked.

This raises an important question for UX designers: since Meta had designed the same product for everyone, why did it produce such different user experiences around the world? This column examines how the same UX design affordances, including a chronological-feeling feed, conversation design, reply visibility, and moderation, led to different user outcomes across markets, and what this reveals about designing global products. Read More

Any system’s backend logic shapes its user experience. This article provides an example of how the requirements for a particular business domain—lead-generation and routing requirements—determine the workflow of a software solution and, thus, how its backend logic translates into the user experience.

In this business case, whether a company is a lead generator, affiliate network, or advertiser, it is crucial that the distribution of leads is well thought out and personalized, delivering optimal engagement for every user in the marketing funnel.

The software should take care of this job, enabling flexible workflows for consumers in different locations, each having varying quality and conversion potential. For example, when generating solar-installation leads—or leads in any other market where the customer’s location matters—the software should connect consumers to sales representatives who are aware of the peculiarities of the location in question and target consumers only in the locations where the company operates. Read More