Handbook for Operational Excellence

Methods

Methods

Methods define how we translate technology strategies into practice. They are the ground rules for collaboration between engineering, business, and operations. A consistent set of methods reduces cognitive load in teams and ensures reproducible quality.

This section covers proven frameworks such as the C4 Model for architecture documentation, Site Reliability Engineering (SRE) for stable operations, and agile scaling methods for growing organisations.

Table of Contents

  • Agile Scaling and Descaling: Scaling agile teams without bureaucratic overhead. How Team Topologies and Conway's Law optimise the organisation.
  • Bounded Context: Drawing precise domain boundaries. How Bounded Contexts serve as the foundation for clean microservice architectures.
  • C4 Model and Docs-as-Code: Systematic visualisation of software architectures. How the C4 Model creates clarity across levels and containers.
  • Compliance as Code: Automated checking of regulatory requirements. How Compliance as Code replaces manual audits with continuous, machine-readable controls.
  • DDD (Domain-Driven Design): Mapping complex business logic in software. How Domain-Driven Design bridges the gap between specialist departments and code.
  • FinOps and Cloud Economics: Financial management of cloud usage. How FinOps creates transparency and secures the economic efficiency of infrastructure investments.
  • GitOps and Reconciliation: Infrastructure management via Git. How GitOps uses declarative configuration and automatic synchronisation to ensure consistency.
  • Golden Path: Standardised development paths for fast, reliable results. How Golden Paths improve developer experience without sacrificing autonomy.
  • InnerSource and Code Openness: Applying open-source principles within the organisation. How InnerSource breaks down knowledge silos and scales collaboration.
  • ITIL vs. SRE: Service management in transition. How classic ITIL processes are automated and made more flexible through Site Reliability Engineering (SRE).
  • Nearshoring and Vendor Integration: Managing IT service providers and nearshoring partners. How partner management secures quality through transparency and shared goals.
  • Blameless Post-Mortems: Learning from incidents without blame. How blameless post-mortems improve operational resilience and team trust.
  • Refactoring: Improving code without changing behaviour. How systematic refactoring keeps technical debt under control.
  • RFCs and ADRs: Asynchronous documentation of architecture decisions. How RFCs and ADRs democratise the decision-making process and make it traceable.
  • Strangler Fig Pattern: Replacing legacy systems incrementally. The Strangler Fig Pattern as a safe migration strategy for live production systems.
  • 20% Tech Debt Rule: Managing technical debt in day-to-day work. How the 20% rule and Dependency Bankruptcy preserve the team's ability to act.