5.4. Value Chain
💡 First Principle: The value chain is the set of interconnected activities an organization performs to convert demand into value — and this topic also defines the operational vocabulary (incident, problem, release, observability, and more) that those activities work with, because you can't reason about running services without naming their moving parts.
Why care: the value chain is where the organization's actual operational work lives, and the terms defined here are the everyday language of service operations. Misnaming an incident as a problem, or confusing continuous delivery with continuous deployment, causes real operational confusion. The mental model: the value chain is the organization-level engine of activities, and these terms are the parts it handles.
⚠️ Common Misconception: That a problem and an incident are the same thing. An incident is the unplanned interruption you feel; a problem is the underlying cause behind one or more incidents. This boundary is tested directly.
