You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A couple of users have been puzzled about how to access the gate column and find the button to generate a draft intent. They might not see the gate chips, or not realize that they can click on them to open the gate column, or not realize that the draft intent button is in the gate column. Part of this usage failure might arise strictly from the UI implementation (e.g., the gate chips could be assumed to be status indicators only rather than clickable buttons) and part of it might be because of a mismatch of expectations about the scope of the tool relative to the process (e.g., "I just want to generate an intent" vs. "We want feature owners to follow the whole process, with generating an intent being a step near the end of that process").
I can look at a variety of ways to improve discoverability. Since most users seem to have successfully discovered how to access the gate column, the fix for the remaining users might need to be pretty prominent so that they don't miss it. E.g., I could add a word-bubble to the gate chips. I had previously implemented a word-bubble call-out for the old process overview page. Such word-bubbles are common in Google products like GSuite. Such bubbles could even be part of a UI tour where a first-time user works through a series of 3 or 4 bubbles, but it is probably best to focus on just this individual point.
The text was updated successfully, but these errors were encountered:
A couple of users have been puzzled about how to access the gate column and find the button to generate a draft intent. They might not see the gate chips, or not realize that they can click on them to open the gate column, or not realize that the draft intent button is in the gate column. Part of this usage failure might arise strictly from the UI implementation (e.g., the gate chips could be assumed to be status indicators only rather than clickable buttons) and part of it might be because of a mismatch of expectations about the scope of the tool relative to the process (e.g., "I just want to generate an intent" vs. "We want feature owners to follow the whole process, with generating an intent being a step near the end of that process").
I can look at a variety of ways to improve discoverability. Since most users seem to have successfully discovered how to access the gate column, the fix for the remaining users might need to be pretty prominent so that they don't miss it. E.g., I could add a word-bubble to the gate chips. I had previously implemented a word-bubble call-out for the old process overview page. Such word-bubbles are common in Google products like GSuite. Such bubbles could even be part of a UI tour where a first-time user works through a series of 3 or 4 bubbles, but it is probably best to focus on just this individual point.
The text was updated successfully, but these errors were encountered: