Agreement 5 - Blocking Work

Why is this change being made?

This is Agreement #5 from the AI Offsite in January to be documented and started in the handbook because it is ultimately uncontested and still valid feedback.

Statement of Intent: Blocking or Critical Work Response Time Targets (RTT)

Why: To empower team members to be able to drive progress and move forward

Action/Timeline:

• R&D AI teams agree to responding to inquiries with ETA to resolve within the designated time frame below:
  • High Priority - Within 1 business day
  • Medium Priority - <= 5 business days
• For all inquiries, impact of no/delayed decision needs to be communicated to ensure that team members understand the “why” and context behind the importance (i.e slipped timelines, confidence reduction)
• It there is a delay, AI Leads ping in the #ai-leadership channel
• If the RTT is missed, then a few sentence S-B-I reflection statement should be shared with your Director to provide context and learning to see if we need to change/optimize the process.

Measure of Success: The # of S-B-I (Situation, Behavior, Impact) reflection statements

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
• 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
  • Division: If the update affects your division, share the MR in your division 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

Commits

• Agreement 5 - Blocking Work

---