Skip to content

Reorganize and reword some tenets in Shared Reality and Decision Velocity

Juan Silva requested to merge master-patch-23c2 into master

Why is this change being made?

After some discussions during the "Train the Trainer" pilot workshop, we identify a misalignment for two of the tenets with their respective guiding principles.

This MR proposes a reorganization and rewording or expansion of the tenets' definitions.

The following changes can be observed in this MR:

  1. Move Collaboration Codification tenet to the Shared Reality principle section. Most of the tenet actually speaks about shared reality and documenting how teams collaborate. So the argument is that Shared Reality is a better fit for it.
  2. Update the wording of the Collaboration Codification first paragraph to make a stronger connection to the Shared Reality so it is consistent with the other paragraphs.
  3. Move Situational Leadership tenet to Decision Velocity principle section. Situational leadership is hard to connect with Shared Reality and it has a more natural fit to the speed of decisions principle.
  4. Update the definition of Situational Leadership with a new paragraph that warns against falling into contradictory behaviours that deviate from the TeamOps principles and tenets (as discussed during the workshop). Eventually, we could also move away from the loaded term "Situational Leadership", but for now this addition can prevent people to think that any managerial or leadership tactic is fair game.
  5. Update the definition of Situational Leadership with a new paragraph to make a clearer and stronger connection to the Decision Velocity
  6. Move up the tenet of Bias for action to be the first one within the Decision Velocity section since it is likely the strongest one in this principle.

For more clarity here is a screenshot that depicts the updates applied to (2) above:

Screen_Shot_2023-01-06_at_3.10.02_PM

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.
  • 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
  • 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 Laurel Farrer

Merge request reports