GitLab's guidance says failure investigations should focus on situational aspects and the decision-making process that produced the failure rather than blaming a person or team. It describes blameless root cause analyses and retrospectives as settings where stakeholders can speak up without fear of punishment or retribution.

Blameless Root Cause Analysis and Retrospectives

GitLab describes the Fundamental Attribution Error as a double standard in which people explain their own mistakes by circumstances but explain others' mistakes by the individual. To reduce this bias, the handbook advises assuming positive intent, respecting others' expertise, and giving grace when a perceived mistake occurs.

Google

GitLab presents effective collaboration as necessary for achieving results. It says helping others is a priority even when the help is not immediately tied to one's own goals, and it expects people to rely on others for help and advice.

Collaboration in GitLab's Stated Values

GitLab public handbook values page describing CREDIT values, public values, reinforcement mechanisms, remote-work culture, transparency, collaboration, iteration, diversity, inclusion, belonging, and results for customers. https://handbook.gitlab.com/handbook/values/

GitLab Handbook: Values

GitLab says anyone may contribute suggestions on any subject, including people outside the company. The person responsible for the work decides how to proceed, while taking suggestions seriously and explaining why suggestions may or may not be used.

Open Input and Decision Ownership in GitLab Collaboration

GitLab values caring for others and treats care as a basis for direct challenge and feedback. It says kindness does not require avoiding disagreement or withholding feedback, and that people can criticize work while remaining respectful toward the person.

Caring Directness in GitLab Feedback

GitLab encourages recognizing people who helped and says open, frequent recognition can increase team engagement. At the same time, the handbook notes that public praise may feel awkward or uncomfortable, so thanks should be sincere, explain the reason for recognition, and can happen in venues beyond a single channel.

Public Recognition Norms in GitLab's Values Handbook

Assuming Positive Intent to Mitigate Fundamental Attribution Error

In a disagreement, a steel-man approach means responding to the strongest good-faith version of the other person's position instead of attacking a weak or imaginary version. A good steel-man representation is one the other person feels fairly represents their view, even if they still disagree with the assumptions or conclusion.

Steel-Manning Disagreements

GitLab's guidance says people should be more accepting when others take initiative to improve things. Because decision-making can slow as companies grow, it encourages people to have short toes and feel comfortable letting others contribute to their domain.

Learn Before

Related

Learn After