Microsoft
Azure Stack notification blade
To decrease supportability requests, and improve overall UX, I was in charge of improving the notification blade that can be used throughout the Azure Stack portal
Benchmark research findings
· Low engagement with self-help (deflection) articles
· Most of self help appears after requesting support, outside of the alert blade and the portal · Alerts have similar titles and steps, and the voice is robotic
· Alerts lead customers to create a support request
· Public support content covers sunny-day scenarios but not rainy-day scenarios
· Customers perceive alert help and steps as irrelevant to their issue
· Customers need logs for troubleshooting and working with support
Current notification blade
Crammed content
Guides users to create a support request for all notifications
Improved notification blade
Improved UX so that the users can focus on how to fix the problem and can submit a support request as the last option
Brought in the log collection experience within the notification blade
