Improve discoverability of slash commands in Duo Chat
Problem to solve
Research showed that slash commands in Duo Chat were not discoverable.
The research was conducted with a prototype of the in-product Duo Chat (as opposed to IDE chat). All participants typed in natural language before being directed to use slash commands. Most participants did not notice the text input "type / for slash commands":
Further validation required
The same research showed that participants lack established mental models to effectively utilize the slash commands because they were not heavy adopters of the in-product chat. There was also lack of consensus what commands should be available, in-product.
Before making slash commands more discoverable, it is important better understand the in-product user workflows so we can determine which slash commands can add value. When we have implemented high-value slash commands, that would be the moment to better onboard users to slash commands.
The research was not conducted on the IDE chat, but some participants mentioned using Duo Chat IDE slash commands, and there was more consensus of the commands that could be helpful in the IDE. It's possible that we could do some light validation or desk research on IDE slash commands and design an IDE-specific solution.