Suggesting changes to Assembly in context of team member touchpoints
Why is this change being made?
This MR suggests a change to the Assembly timeline and how we think about it in relation to other team member touch points to further clarify how different touch points keep team members informed in different ways.
By separating Assembly from Earnings week, it allows us to bring in a broader range of content (i.e. values awards, AI updates) by lessening the expectation that this is purely a financial update.
To answer questions related to our earnings releases, we will set up a separate post-Earnings Recap & AMA for the CEO & CFO to answer questions and provide any additional clarity our team members may need.
Author Checklist
-
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
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Devin Rogozinski