Clarify steps for where to document Actionable Insights
Why is this change being made?
When creating actionable insights for a recent benchmark study, I noticed that the handbook implied the need to document these in both Dovetail and GitLab, in addition to having a report readout. After reviewing with the UXR team, we determined that documenting Actionable Insights in GitLab was necessary and required, but if there was a research report outside of Dovetail (i.e., in Google Slides), those insights did not need to be duplicated into Dovetail.
I've proposed updated wording to clarify the practice of documenting Actionable Insights, ensuring that they do get documented in GitLab, but not necessarily in Dovetail.
Author and Reviewer Checklist
Please verify the check list and ensure to tick them off before the MR is merged.
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - 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
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
For transparency, share this MR with the audience that will be impacted. -
Team: For changes that affect your direct team, share in your group Slack channel -
Department: If the update affects your department, share the MR in your department Slack channel -
Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Edited by Danika Teverovsky