Defining the Desired Experience

To define the desired experience, the first decision is which experiences demand attention. This is the prioritization discussion started in the last chapter. Knowing where these use cases are to appear helps with scope, planning, and follow-through. Some require building traditional conversational experiences; shockingly, these can be called classic now! Others will use channels (such as Slack, Teams, or a web experience) that can handle interactive elements, such as GUI components. Some will extend features within existing channels to include LLMs in the workflow to solve a limited use case. That last one is a powerful incremental approach. Others will build single-purpose bots or voice-only interfaces. Each of these experiences has unique and general considerations.

This chapter will cover the highest-priority enterprise user experiences one can develop with ChatGPT, along with three overarching design elements: accessibility, internationalization...