Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update comms-sign-off.mdx #566

Merged
merged 2 commits into from
Jan 23, 2025
Merged

Update comms-sign-off.mdx #566

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b0b641c
Update comms-sign-off.mdx
shell1 Feb 2, 2024
45d8b20
Merge branch 'main' into shell1-patch-86
jaredlockhart Jan 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/workflow/implementing/risk-mitigation/comms-sign-off/comms-sign-off.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,11 @@ title: Comms Sign-off
slug: /comms-sign-off
sidebar_position: 4
---
If your experiment includes ANY message, make sure you had an [in-product message consult](https://mozilla-hub.atlassian.net/wiki/spaces/FIREFOX/pages/208308555/Message+Consult+Creation) and filed an [FXE Jira ticket](https://mozilla-hub.atlassian.net/jira/software/c/projects/FXE/boards/543) that was triaged via the Desktop or Mobile messaging leads (Venetia and Courtney).

Ideally work with your comms or PR contact for your area to let them know the details of the experiment and why a risk has been identified. If you don’t know where to start for Comms help for your area - #cccc is a channel where you can get help. That channel also has a runbook document linked that has some more information on ways to engage with the Comms team.
This is to ensure we are using a consistent voice with users - and also to make sure we don’t inadvertently send multiple messages that don’t flow together to the user.

It is very rare for any pro-active comms to come for an experiment - but we have had “reactive comms” ready around several user visible feature changes or messages. Having reactive comms prepared and flagging the experiment for the support team makes responding to any incident quicker and less likely to escalate badly.

Ideally work with your comms or PR contact for your area to let them know the details of the experiment and why a risk has been identified. If you don’t know where to start for Comms help for your area - #cccc is a channel where you can get help. That channel also has a runbook document linked that has some more information on ways to engage with the Comms team.

It is very rare for any pro-active comms to come for an experiment - but we have had “reactive comms” ready around several user visible feature changes or messages. Having reactive comms prepared and flagging the experiment for the support team makes responding to any incident quicker and less likely to escalate badly.
Loading