| Not in this article, but Don Norman also frequently rails against complex conceptual models. The other day, my mom was complaining that her phone was not ringing and it took me forever to figure it out. I had to go to Google to find a troubleshooting guide. The problem is that there are multiple ways to prevent a phone call from ringing. You can switch the hardware button (silent mode), you can set focus mode on (or have it set automatically), and you can mute individual people in the address book. Or you can add people to a group so that they ring even if the phone is in focus mode (but not in silent mode). There are probably other ways I've forgotten. Already we've introduced a bunch of concepts: silent mode, focus mode, muting individual people, exceptions to focus mode, etc. And the user has to figure out these concepts just from looking at the UI. But if you don't understand the entire conceptual model, you may not know why something is not working. This problem can't be solved with better affordances or more text labels, unfortunately. Maybe LLMs will eventually save us. Instead of the user having to figure out the capabilities and UI of the device, the device tries to figure out the intent of the user. |
> What is a feature interaction?
> A feature interaction is some way in which a feature or features modify or influence another feature in defining overall system behavior. Feature interactions are especially common in telecommunications, because all features are modifying or enhancing the same basic service, which is real-time communication among people.
> Features are popular because they are easy to add and change. The dark side of features is feature interaction, which is implicit in feature composition and therefore difficult to understand. [emphasis added]