WebOps Principles

These principles are an overview of the culture, practices and motivations driving teams working in the WebOps profession.

Software and platforms are constructed around the needs of our users.

Systems and tools exist to enable our users to deliver, and that is where their value lies.

The quality of a system is in it’s end-user performance in totality, rather than it’s component parts.

We have a culture of continuously experimenting with new approaches and technologies.

Risks and failures are opportunities to learn from, and a natural part of evolving high-quality systems.

Our users rely on our services, so we push towards highly reliability and availability.

We have tight feedback loops with our users, making iteration and improvement a constant and highly reactive process.

The tools and the systems we deliver are in constant motion, as user experiences drive design changes and improvements.

We focus on automating any manual tasks, freeing up users from time-consuming, repetitive jobs.

Building from configuration so that all systems and environments are identical and reproducible.

We are always looking to share our experiences and knowledge.

Our systems, code and practices are documented in a way that helps people to easily understand and use them.