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:

• Streamlining onboarding of new employees
• Encouraging compliance with best practices by making them the path of least resistance
• Designing systems to be low-context from the start
• Using ubiquitous documentation to capture and share context
• 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.

What's inside

• Deep Dive — This paper provides a deeper understanding and guidance for helping companies scale shared services for success.
• Key Takeaways — Learn 5 techniques to create a low-context culture, from onboarding to system design.
• Clear Guidance — Discover how to encourage best practices by making them the path of least resistance.
• All Levels — Drive change from any level - you don't need to be a manager to build a low-context culture.