Broadcast message for upcoming breaking changes in 14.0
Request for recruting customers via In App Messaging
Ensuring a positive user experience for our users is the most important factor to consider when deploying messaging in our product. With that goal in mind, we have put in place the following procedures to ensure that in-app messaging does not result in any negative user sentiment.
What is the purpose of your proposed messaging?
We want to announce the breaking changes ahead of %14.0. Some deprecations will hit GitLab.com before the 22nd (Release day) and some users may not be reading the blog post. The blog should explain Why are we deprecating.
We want to initiate an In app messaging campaign - telling people to go to the blog post In app message campaign should only target SaaS users. This is important because some features may land in GitLab.com before the 22/06 and users will not know why some of their workflows may break.
We might want to cross link this blog post from the 13.12 & 14.0 blog post
How will you define success?
Number of users reading the blog
Number of users taking corrective actions as mentioned in the blog
What type of users do you want to target? (be as specific as you can)
Only SaaS GitLab.com users
How many impressions you are targeting for your desired user type(s)?
What pages do you plan to deploy your message on?
- 13.12 release blog post
- Feature flags page
- API documentation
- Branches page
- Authorization doc page https://docs.gitlab.com/ee/api/oauth2.html#supported-oauth2-flows
- Code quality page
- Browser performance
- AutoDevops templates page
- https://docs.gitlab.com/ee/api/tags.html#create-a-new-release
- GitLab pages settings
- GitLab CI templates page
- dependency scanning
- https://docs.gitlab.com/ee/user/project/clusters/protect/web_application_firewall/
What is the average total of unique users accessing those pages per day?
What is the average unique users matching your desired user type(s) accessing those pages per day?
What type of message is needed:
- Informational (no CTA)
- Link (copy & CTA)
- Survey (copy & in-line question)
Informational
What is the desired content of your message?
A blog post stating all the upcoming breaking changes to expect
If your message contains a survey (either in-line or linked), you’ll need to fill out a problem validation research request issue in the UX Research project where a UX Researcher will review and approve your survey. Include a link to your research issue.
The VP of Product Management will review and prioritize as needed, and then assign to Senior Growth Product Manager (for deployment/monitoring) and Senior UX Researcher (for reviewing messaging content/number of impression, etc.)
General in-app messaging guidelines
- Messages must be approved by VP of Product Management @adawar in order to run.
- We run a maximum of 2 in-app messages at any given time in order to limit the number of messages a user sees in quick succession.
- Messages run for the shortest amount of time possible.
- Messages are limited to a single page on the site unless there is a business reason to put it on multiple pages.
Transparency around decision making criteria
The goal will be weighed against in-app message fatigue. Will we have made significant progress on outcomes or will we have frustrated our users?