The chat box is not a universal interface. It is a default, and a lazy one. This article from Smashing Magazine argues that UX and product teams are force-fitting AI capabilities into conversational UI because LLMs were trained on dialogue, not because chat is the right tool. The result is measurable user failure: a traveler in a loud airport forced to type a booking reference into a chat field with one hand, then read a paragraph to find a gate number. The interface was smart. The modality was wrong.
The article builds its case around two failure modes. First, the input problem: a blank text box creates choice paralysis, forcing users to become prompt writers when a slider, button, or drag-and-drop interaction would execute the same intent faster and with less cognitive load. Second, the output problem: text is a serial medium. Reading three paragraphs to find one status update is slower and more error-prone than a color-coded dashboard. A doctor needs a numerical display, not a narrative. A trader needs a line graph, not a written description of price movement. The article frames both failures as a cognitive tax, one that compounds under professional stakes.
The full piece is worth reading for two concrete tools it introduces: a Task Audit and an Input/Output Alignment Matrix. It also includes a taxonomy of input and output modalities mapped to the contexts where each performs best, with explicit notes on accessibility requirements when visual formats are the primary output. If your team is currently defaulting to chat for any AI feature, this taxonomy will force a harder conversation about why.
[READ ORIGINAL →]