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 #565

Merged
merged 1 commit into from
Feb 2, 2024
Merged

Update comms-sign-off.mdx #565

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 4 additions & 1 deletion 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 @@ -4,5 +4,8 @@ slug: /comms-sign-off
sidebar_position: 4
---

Under construction 🚧
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