3 UX considerations for a multi-agent system
This chapter covers
- Examining how the user interface landscape has evolved from the command line to multi-modal, multi-agent systems
- Tracing the shift in software engineering practices from traditional development to autonomous multi-agent systems
- Discerning between end user and developer personas in understanding the user
- Comparing interactive versus offline multi-agent scenarios
- Spelling out UX design principles for multi-agent applications, including capability discovery, cost-aware action delegation, interruptibility, observability and provenance.
The ultimate goal of building a multi-agent system (or any software tool) is to solve a specific problem for a user. This system may be utilized as components by developers (such as software developers via SDKs or APIs etc.) to create larger systems or directly used by end-users to accomplish particular tasks. Regardless of the target user, it is crucial that we develop systems with an optimal user experience - systems that are effective, meaning they help users achieve their tasks with minimal friction or effort, and enjoyable, making them engaging and delightful to use. To achieve this, we must understand the user and their behaviors, motivations, attitudes, and goals, and then design systems that cater to these needs.