3.3 Think and Work Holistically, Keep It Simple and Practical, and Optimize and Automate

Think and Work Holistically

Think and work holistically states that no service, practice, process, department, or supplier stands alone. To deliver value, the organization must work as an integrated whole — the service value system (SVS) is greater than the sum of its parts, and a change in one area has effects elsewhere. The principle is the antidote to silo thinking, where each team optimizes its own piece while the end-to-end outcome suffers.

Applying it means recognizing the interdependencies between the four dimensions of service management (organizations and people, information and technology, partners and suppliers, value streams and processes) and across the whole value chain. A decision that looks good for one team but degrades the overall service violates the principle.

Recommendations for Think and Work Holistically

• Recognize the complexity of the systems — but do not let that paralyze action.
• Collaboration is key to thinking and working holistically — it links directly to the collaborate principle.
• Where possible, look for patterns in the interactions between system elements.
• Automation can facilitate working holistically by connecting and coordinating parts.

A common exam scenario shows two teams hitting their own targets while the customer's overall experience gets worse. That conflict of local goals against the whole is the signal to apply think and work holistically.

Keep It Simple and Practical

Keep it simple and practical advises using the minimum number of steps needed to accomplish an objective. Apply outcome-based thinking to produce practical solutions, and design processes, services, and practices to do their job and no more. The principle explicitly says to eliminate anything that produces no useful outcome — if a step, control, metric, or activity adds no value, remove it.

A frequent misunderstanding is that "simple" means "low quality" or "do less than needed." It does not. The goal is value-creating simplicity: achieve exactly the service quality stakeholders need — neither over-engineering nor under-delivering. ITIL also notes that simplicity and accessible language build customer trust and reduce friction, time, and cost. Beware, though: even something that seems like waste from one viewpoint may produce value from another — always check before deleting.

Recommendations for Keep It Simple and Practical

• Ensure value — every activity should contribute to a valuable outcome.
• Simplicity is the ultimate sophistication — start simple and add complexity only when it is truly justified.
• Do fewer things, but do them better.
• Respect the time of the people involved — over-complex processes waste it.
• Easier to understand, more likely to adopt — simple solutions get used.

Optimize and Automate

Optimize and automate is the most heavily tested ordering on the exam: you optimize first, then automate. Optimization means making something as effective and useful as it can be before introducing technology. Automation then uses technology to perform steps without human intervention, freeing people for higher-value work. The critical rule: do not automate a broken process — automating an inefficient or wasteful process simply makes the waste happen faster and at larger scale.

ITIL describes a path to optimization that you should be ready to recognize:

1. Understand and agree the context in which the proposed optimization exists, including the overall vision and objectives.
2. Assess the current state of the proposed optimization — what is to be optimized and why.
3. Agree what the future state and priorities should be, focusing on simplification and value.
4. Ensure the optimization has the appropriate level of stakeholder engagement and commitment.
5. Execute the improvements iteratively — break the optimization into manageable steps with feedback.
6. Continually monitor the impact of optimization and adjust.

Notice how this path reuses earlier principles — focus on value, progress iteratively with feedback, and keep it simple. Only when a process has been optimized to its simplest valuable form should you ask which parts can be automated economically. ITIL frames automation as a way to maximize the value of human work, and stresses assessing the feasibility and cost before automating, so the automation is economically viable.

Recommendations for Optimize and Automate

• Simplify and optimize before automating — automation of a poor process locks in the problem.
• Define your metrics so you can tell whether optimization actually improved things.
• Use the other guiding principles when applying this one.
• Automate what can be automated economically — not everything that can be automated should be.

Why the Order Matters

The optimize-before-automate sequence is one of the most reliable exam points in this chapter. Automation is fast and scales easily, which is exactly why automating an unoptimized process is dangerous: every flaw is reproduced at machine speed and volume. Optimizing first removes redundant steps, clarifies the desired outcome, and standardizes the process so that whatever is automated is genuinely worth running. Automation then delivers its real benefit — maximizing the value of human work by removing repetitive manual effort and letting people focus on judgment, exceptions, and improvement.

Before committing, ITIL says to weigh the feasibility and cost of the automation so it is economically justified; an automation that costs more than the toil it removes fails the test.