Communicating direction updates to groups

Why is this change being made?

PMs work on direction pages frequently, but we don't always keep other departments involved when we make updates to our vision.

We should make sure that folks are aware of changes to direction pages by CCing the group on any relevant MRs. We should also take the time to regularly tell others internally about what we're doing; one way of doing this is to host an AMA for your group every month. Another might be to regularly record a video walkthrough of your direction pages on a regular basis.

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per [say-why-not-just-what][transparency]
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in [#mr-buddies][mr-buddies-slack].
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.