Low-Context DevOps

This paper introduces the concept of “Low-Context DevOps” as a way to improve DevOps and SRE team culture. Author Thomas Limoncelli contrasts high-context cultures, where a lot of implicit background knowledge is required to operate effectively, with low-context cultures, where knowledge is made explicit and codified.

The paper argues that DevOps environments should strive to be low-context by minimizing the amount of tacit context required to be productive. This improves efficiency, reduces frustration, and increases morale.

Five key techniques are presented for achieving a low-context DevOps culture:

1. Streamlining onboarding of new employees
2. Encouraging compliance with best practices by making them the path of least resistance
3. Designing systems to be low-context from the start
4. Using ubiquitous documentation to capture and share context
5. Continuously working to reduce required context over time

The author concludes by emphasizing that everyone can demonstrate leadership in moving their organizations toward low-context DevOps, even without explicit managerial authority. Small individual efforts to streamline, document, and share knowledge can drive significant cultural change.