complexity can make it difficult for both domain novices and experts alike to learn how to use the interface. LLMs can help reduce this barrier by being leveraged to prove assistance to the user if they’re trying to accomplish something, but don’t exactly know how to navigate the interface.The user could tell the program what they’re trying to do via a text or voice interface, or perhaps, the program may be able to infer the user’s intent or goals based on what actions they’ve taken so far.Modern GUI apps are slowly starting to add in more features for assisting users with navigating the space of available commands and actions via command palettes; popularised in software iA Writer and Superhuman.

for executing a sequence of tasks as part of a complex workflow, LLM powered interfaces afford a richer opportunity for learning and using complex software.The program could walk them through the task they’re trying to accomplish by highlighting and selecting the interface elements in the correct order to accomplish the task, along with explanations provided.

Expert interfaces that take advantage of LLMs may end up looking like they currently do - again, complex tasks require complex interfaces. However, it may be easier and faster for users to learn how to use these interfaces thanks to built-in LLM-powered assistants. This will help them to get into flow faster, improving their productivity and feeling of satisfaction when using this complex software.

unlike Clippy, these new types of assistant would be able to act on the interface directly. These actions will be made in accordance to the goals of the person using them, but each discrete action taken by the assistant on the interface will not be done according to explicit human actions - the goals are directed by he human user, but the steps to achieve those goals are unknown to the user, which is why they’re engaging with the assistant in the first place

as I’ve wrestled with writing this, it’s clear that many just don’t see the problem, as they assume a cheap button is nearly as good as a proper dial. They’ll openly admit a dial is indeed better but a cheap button is “good enough” and that a dial is “just too expensive.” That actually may be true! There are cases when using a push button is the right choice. But not always. We need to understand when to try a bit harder. Yes, you’re spending a tiny bit more on hardware, but you’re creating a product that is usually much easier to use, reduces returns, and builds your brand which improves sales. Is this positive outcome a given? Of course not, nothing is guaranteed but we need to stop pretending there is NO COST to cheaping out on buttons.

The dial changes the frequency with a simple twist. The push button device “Deconstructs” the twist dial into two up/down buttons. Each press increments the frequency a tiny amount. This means a twist is replaced with many button presses. Again, they are ‘functionally equivalent’ but the expression and ease of use are quite different.

“Adding a feature” is never free. Always start with the user’s problems first. If pressed into using one of these four abuses, make sure to fully appreciate its impact, the friction it creates, and what you can do to work around it.  Adding a feature shouldn’t also “add a problem.”

As a professional UX Designer, I want devices to offer more. But UX Design isn’t about cramming everything into your product in the vague Hail Mary hope it’ll ship a few more units. That’s the sales team speaking, not the user. It’s the wrong motivation and creates monsters.