The team created this App to be the iOS version of the desktop tool. I worked with the UX team to improve wording after the wireframes were complete.
On this screen, users can pin or favorite a dashboard. But, it isn’t immediately clear the difference between the two (default vs. one of many favorites), so the goal was to clarify this simply.
Bookmarks and Filters
It’s hard to tell from these screens, but the name “Bookmarked Filters” was a huge win. The desktop application uses the word Bookmarks and Filters, but bookmarks are simply saved filters.
We knew new users might not understand the term bookmark. We also knew that long-time users understand what a bookmark is and might be confused by the new language. So, we compromised at “Bookmarked Filters.” That meant we could re-use the wording to “Add to Filter” on some screens, saving work for UX, product, engineering, and the user. We planned to use this as starting point to move to more intuitive naming for “Bookmarks,” like “Saved Filters,” in future iterations.
Error Messages and Tool Tips
Here are a few error messages I wrote at my latest org. Many of these were ad hoc and not part of a particular user flow.
Error message that displayed when a user changed the authentication type for many users at a time. The previous wording was “Unable to change the authentication type for the following users.” I wasn’t able to impact the text in the grey box.
Standardized wording for an Administrator tool (not pictured). Some highlights:
- Changed instances of the field label “Max —” to “Maximum”
- Changed capitalization from Title Case to Sentence case for longer field labels.
- Changed success messages to use a subject-action-verb-adverb model to present primary label and user goal first, like “Folder XYZ imported successfully.” and “Dashboard ABC imported successfully.”
Tour Guide Example
Here is an example of some UX Content Strategy writing I did for a tutorial for a new user using a new Adobe product. The goal were:
- Draw the user to the main features.
- Highlight top use cases.
This product and tour never got to testing or production. If it had I’d like to have:
- Performed user experience testing (A/B, quantitative, qualitative, etc.) to iterate for helpfulness
- Had clarity on prioritized use cases to reduce the number of steps (again, depending on research results)