Journey Creation
When creating a new journey, I'm already receiving an error message right away. This is a bad UX.
When creating a new journey, I'm already receiving an error message right away. This is a bad UX.
Why even say "name is a required field" at all? We should have the button deactivated to prevent the user from creating the journey.
Other improvements:
- [x] Action button should be "Create" instead of "Save". "Save" should be using only when renaming.
- [x] Error message should display only for cases outside of "name is a required field", e.g.: "This Journey name already exists."
- [x] Dialog Title: "New Journey"
- [x] Dialog Description: Name of new Journey inside "Root/Journey Name:"On November 18, 2024, Eduarda Ferreira initiated a Socra titled "Journey Creation." The focus was on enhancing the user experience (UX) and user interface (UI) during the journey creation process. Eduarda pointed out a critical issue where users receive an error message immediately upon attempting to create a new journey, highlighting poor user experience.
To address this, she suggested that the action button should be disabled until the required field for the journey name is filled out, eliminating unnecessary error messages at the outset. Furthermore, several key improvements were implemented:
- The action button was updated from "Save" to "Create," reserving "Save" for renaming journeys.
- The error message functionality was refined to only trigger for specific situations, such as when a journey name already exists, rather than generic required field alerts.
- The dialog title was set to "New Journey," and the dialog description was clarified to display "Name of new Journey inside 'Root/Journey Name:'".
These enhancements were aimed at creating a smoother and more intuitive journey creation process, ultimately improving the overall user experience.By Eduarda Ferreira