VeriSM Essentials study materials
VeriSM Essentials study resources

VeriSM Essentials: Service culture and organizational behaviour

VeriSM Essentials · Work through your exam, one topic at a time.

All guide sections

Service culture and organizational behaviour

Domain 2 - Service culture and organizational behaviour

Service culture is the set of shared values, beliefs and behaviours that determine how people treat consumers and each other. The exam tests whether you can separate culture from climate and perks, explain how culture is shaped and measured, and apply organisational behaviour ideas - motivation, team development, change - to service scenarios.

Core rules

  • Culture is learned behaviour, not a poster. A service culture exists when people at every level understand what value means for consumers and act on it unprompted. Values statements are artefacts; behaviour under pressure reveals the real culture.
  • Three levels (a widely used model): visible artefacts such as tools, rituals and language; espoused values, what the organisation says it believes; and basic assumptions, the unspoken beliefs taken for granted. Change fails when only the first two are touched.
  • Leaders shape culture through what they pay attention to, what they reward and punish, and how they react to failure. A blame response to an incident teaches hiding; a blameless review teaches learning.
  • Motivation is intrinsic (autonomy, mastery, purpose) as well as extrinsic (pay, recognition). A service desk measured only on handle time erodes the intrinsic motivation to help.
  • Teams develop through forming, storming, norming, performing and adjourning. Cross-functional service teams need shared goals and time before they perform.
  • Change needs unfreezing, movement and refreezing, or a structured step model, plus reinforcement so new behaviour sticks.

Worked example: an organisation wants developers to join an on-call rota so knowledge shifts left. Training is delivered but nothing changes. Reasoning: the artefacts still reward shipping features only, and operations still circulates a blame list after incidents. The fix is to change the system - shared incident metrics, joint retrospectives, recognition for reliability work - so that the espoused value of owning the service together becomes a basic assumption.

Traps that cost marks

  • Confusing culture with climate, engagement scores or office perks.
  • Assuming a values statement or a training course changes culture.
  • Blaming individuals for behaviour the reward system produces.
  • Treating culture change as a finite project with an end date.