Focus on value, collaborate, work holistically

What a guiding principle is, before any of the seven

A guiding principle is a recommendation that holds whatever the organisation is doing — it does not change when the goals, the strategy or the structure change. That universality is the definition being tested, and the wrong answers usually describe something narrower: a mandatory rule, a step in a process, something that applies only to improvement work, or something an organisation picks when it suits.

They are also not a sequence and not a menu. There is no prescribed order, no mapping of one principle to one value chain activity, and no supported reading in which an organisation adopts three and ignores the rest. The one internal ordering worth remembering is inside "optimize and automate".

Focus on value

Everything the organisation does should link back, directly or indirectly, to value for a consumer or a stakeholder. The examinable failure is elaborate work that nobody asked for and that helps nobody achieve anything — an ornate self-service portal feature built because it was buildable. The work may be well engineered and the principle still broken.

It also covers the case where the provider is measuring the wrong thing about itself. A provider that reports excellent technical availability while users describe the service as frustrating is not looking at value; it is looking at a component metric and calling it the service. That is the same gap service level management later names the watermelon effect, and at principle level it is a focus-on-value failure.

Collaborate and promote visibility

Involve the people who ought to be involved, and make the work visible so decisions can be made on what is actually happening. Two teams each keeping a private backlog and a private status spreadsheet, duplicating work and losing urgent items because leadership cannot see them, is the standard scenario — it is a visibility failure first and a collaboration failure second.

The correction question is worth rehearsing because it appears in some form on most papers. Collaboration does NOT mean consensus. An improvement lead who insists every decision be agreed by every stakeholder before anything moves has misread the principle: the aim is to involve the right people so decisions are better informed, not to give everybody a veto.

Think and work holistically

Nothing stands alone. A service is the product of services, practices, teams, information, technology and suppliers working together, so a change designed by one team in isolation is a change designed without most of the relevant facts. The recurring scenario is a change planned by the application team alone that ships, breaks a downstream reporting service and leaves the support team without documentation.

The line against "collaborate and promote visibility" is the one to hold. Holistic thinking is about the SYSTEM — the parts and their interactions. Collaboration and visibility is about the PEOPLE and the transparency of the work. Duplicated effort between two teams who cannot see each other is a visibility failure; a technically correct change that broke something nobody thought about is a holistic one.