Reporting, culture and a capstone case

Principles, governance and improvement models only work if people use them, and people use them when the culture supports it. This final lesson covers three linked topics. First, reporting: how to present measures through scorecards and objectives so they inform decisions, and how measures can backfire when they become targets. Second, culture: what it is, why it matters for service management, and how leaders shape it. Third, a capstone case that brings the whole course together by applying the principles, governance and the continual improvement model to a struggling service desk.

Reporting that informs decisions

Measurement (lesson 11) produces data; reporting turns data into information people can act on. Good reports answer a question that matters to their audience, compare results with targets and trends rather than presenting isolated numbers, and highlight what needs attention. Lesson 5 warned about information overload: a report that nobody reads or acts on is waste.

Two widely used reporting structures are the balanced scorecard and objectives and key results (OKRs).

The balanced scorecard

The balanced scorecard, developed by Robert Kaplan and David Norton in the 1990s, presents measures from four perspectives so that no single view dominates: financial, customer, internal process, and learning and growth. Applied to an IT service organization, it prevents a focus on cost alone or on technical measures alone.

Objectives and key results

OKRs pair a qualitative objective with two to five measurable key results. They are typically set quarterly, are public within the organization and are often deliberately ambitious, so achieving around 70 % is considered good. OKRs suit improvement work because they connect a clear direction with measurable progress. They differ from KPIs: a KPI tracks ongoing performance, while an OKR describes a change the organization wants to achieve in a period.

When measures become targets

Goodhart's law, named after the economist Charles Goodhart, is often summarized as: when a measure becomes a target, it ceases to be a good measure. People respond to targets, and if a target can be met in ways that do not deliver the underlying value, some people will meet it that way. Service management offers many examples:

• A target for average call handling time leads agents to end calls before problems are solved.
• A target for tickets closed leads to tickets being closed and reopened, or split into several.
• A target for change success rate leads teams to avoid making needed changes, or to classify failures as "partial successes".
• A target for meeting service levels leads to the clock being paused on technicalities.

Defences include pairing measures so that gaming one harms another (handling time with first-contact resolution, for example), measuring outcomes rather than activity, reviewing measures regularly, and above all building a culture where people understand the purpose behind each measure and feel safe reporting honest results.

The cost of poor quality

One way to make the value of improvement visible to governing bodies is to estimate the cost of poor quality (COPQ): the costs that would disappear if every process worked right first time. COPQ includes internal failure costs (rework, repeat incidents), external failure costs (lost customers, penalties, compensation) and some appraisal costs (extra checking needed because processes are unreliable).

Culture and service management

Organizational culture is the set of values, beliefs and behaviours shared by people in an organization. It shapes how people act when nobody is checking. The same process can succeed in one organization and fail in another because of culture: honest reporting, collaboration and improvement thrive where people trust each other and feel safe, and wither where mistakes are punished.

The sociologist Ron Westrum described three types of organizational culture based on how information flows. Pathological cultures are power-oriented: information is hoarded and messengers are punished. Bureaucratic cultures are rule-oriented: information flows through formal channels and responsibilities are narrow. Generative cultures are performance-oriented: information flows freely, failures lead to inquiry and new ideas are welcomed. DevOps research has found generative cultures are associated with better delivery performance.

Psychological safety, a shared belief that people can speak up, ask questions and admit mistakes without being punished, is a key feature of generative cultures. It matters for service management because incident reviews, problem analysis and improvement all depend on people being honest about what went wrong. Blameless post-incident reviews, which focus on how the system allowed an error rather than on who made it, are one practical expression. Workload and wellbeing are also part of culture: a service desk under constant pressure is prone to burnout. HSE-109 covers psychological health and safety at work, including stress, burnout and supportive conversations, in depth.

How leaders shape culture

Culture cannot be changed by announcement. It changes as people see what is actually rewarded, tolerated and punished. Leaders shape culture through what they pay attention to, how they react to bad news, what they measure, whom they promote and how they behave themselves. A leader who thanks someone for reporting a mistake does more for visibility than any policy. ITIL's guiding principles describe a culture as much as a method: valuing outcomes, honesty, collaboration and learning.

Agile, Lean and DevOps all emphasize culture. Agile values individuals and interactions and responding to change. Lean emphasizes respect for people and continuous improvement by those doing the work. DevOps emphasizes shared responsibility between development and operations, learning from failure and automation that frees people for valuable work. Service management that draws on these approaches is more likely to succeed when its culture matches its methods.

Capstone: improving a struggling service desk

A regional health authority's IT service desk supports 6,000 staff. Complaints are rising, and the governing body has asked the CIO for an improvement plan. The service desk handles 12,000 contacts a month. Measures from the last quarter: first-contact resolution 52 %, average speed to answer 9 minutes, 14 % of incidents reopened, user satisfaction 3.1 out of 5, and staff turnover of 35 % a year. Agents are targeted on average handling time of 6 minutes.

The capstone shows the course's main ideas working together: the principles guided each decision, governance set expectations and monitored results, the continual improvement model structured the work, measures were chosen to avoid Goodhart's law, and culture changed through what leaders rewarded.