4.3 The Seven Guiding Principles (Part 2)

Principles 4 to 7: Collaboration, Holism, Simplicity, and Automation

Section 4.2 covered the first three guiding principles. This section completes the set with collaborate and promote visibility, think and work holistically, keep it simple and practical, and optimize and automate. Remember the shared rules: the principles are universal, enduring, and advisory, they are unchanged between ITIL 4 and Version 5, and they are meant to be applied together and continuously.

4. Collaborate and promote visibility

Collaborate and promote visibility has two halves. Collaborate means working across boundaries, between silos, teams, providers, and consumers, because the right people and information produce better decisions and stronger buy-in. Promote visibility means making work, decisions, risks, status, and progress transparent to those who need them. The logic is blunt: hidden work creates hidden failures, while visible work creates shared accountability and surfaces problems early.

Application example: making work, risks, decisions, and progress visible to stakeholders who need to contribute is the textbook application. Notice what the principle is not: it is not simply being friendly. Keeping backlog priorities secret until deployment, letting only one team see operational incidents, or removing feedback channels to avoid disagreement all violate it, even if everyone is polite. Effective collaboration also means choosing the right people to involve, not involving everyone in everything, which would violate keep it simple and practical.

5. Think and work holistically

Think and work holistically states that no service, practice, process, department, or supplier stands alone. The organization and its four dimensions (organizations and people, information and technology, partners and suppliers, value streams and processes) form a system, and outputs suffer when parts are optimized in isolation. Applying the principle means evaluating a change against its full context rather than one narrow lens.

Application example: a change to a mobile app is evaluated for user experience, service desk impact, supplier readiness, security, and release workflow together, not just for whether the code compiles. This principle is the direct antidote to local optimization that harms end-to-end value, and it is the same instinct that motivates the whole Value System. On the exam, a scenario listing several dimensions being considered at once almost always points to think and work holistically.

6. Keep it simple and practical

Keep it simple and practical advises using the minimum number of steps, controls, artifacts, and metrics needed to achieve an outcome, and eliminating anything that does not contribute to useful control, learning, compliance, or value. Complexity is not free: every extra approval, field, or report consumes effort and can slow value. A helpful test is outcome-based thinking, design the process around the result it must produce, then remove everything that does not serve that result.

Application example: removing process steps that do not contribute to useful control, learning, compliance, or value. Keeping every historical approval simply because it once existed, or mandating the most complex workflow tool for every trivial request, both breach this principle. Simplicity is not the same as sloppiness, controls that genuinely reduce risk or meet compliance stay; only waste is cut.

7. Optimize and automate

Optimize and automate is the most order-sensitive principle, and the exam loves to test the sequence. Optimize means making something as effective and useful as possible; automate means using technology to reduce or remove manual intervention. The rule is emphatic: optimize first, then automate. You must understand and improve the work before applying automation, because automating a broken or wasteful process just produces failures faster and bakes the waste in, making it harder to fix later.

Application example: the correct order is to understand and improve the work, then use automation where it increases value. Automating every existing step before checking whether it is useful is the classic wrong answer. Optimization also should follow focus on value (optimize toward what stakeholders value) and use progress iteratively with feedback (improve in steps). If a question asks what to do before automating, the answer is always to optimize, simplify, and understand the process.

Putting all seven together

The seven principles are a coherent decision toolkit, not a checklist. A single improvement often invokes several at once: focus on value sets the goal, start where you are grounds it, progress iteratively with feedback paces it, collaborate and promote visibility runs it transparently, think and work holistically keeps the whole system in view, keep it simple and practical strips out waste, and optimize and automate scales it responsibly. The exam rewards candidates who can read a short scenario and name the single most directly demonstrated principle, so learn each one by its signature cue.

As a memory aid, the seven principles in order spell out a rhythm many candidates chant before the exam: focus, start, progress, collaborate, holistic, simple, optimize. If you can recite that sequence and attach one signature example to each, you can handle both the straight recall questions (which set correctly lists the principles) and the scenario questions (which principle is being applied here), and together those account for a meaningful share of the Value System marks.