I85PREP
⌘ K
VeriSM Essentials study materials
VeriSM Essentials study resources

VeriSM Essentials: Management practices and the management mesh

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

All guide sections

Management practices and the management mesh

Domain 5 - Management practices and the management mesh

The management mesh is VeriSM's flexible set of capabilities used to create and run a product or service. The exam tests its four elements, your ability to select and tailor practices for a given context, and the argument that VeriSM combines practices rather than picking one.

The four mesh elements

  • Resources - people, money, information, technology, infrastructure, suppliers.
  • Environment - the context the service runs in: regulatory, cultural, organisational, cloud or on-premise, in-house or outsourced.
  • Emerging technologies - capabilities that change what is possible, such as cloud, AI and machine learning, IoT, analytics and automation.
  • Management practices - the methods used: ITIL, ISO/IEC 20000, COBIT, SIAM, Agile, Scrum, Kanban, Lean, DevOps, TOGAF, CMMI, plus non-IT practices from HR, finance and risk.

Rules for using the mesh

  • The mesh is defined per product or service, not once for the organisation, and it changes as the service and its context change.
  • Practices are selected, combined and tailored to fit outcomes, environment, culture and regulation - not adopted wholesale, and not chosen for fashion.
  • Overlap must be managed: two practices both owning change or incident flow create duplication and conflicting metrics.
  • Each practice brings its own vocabulary; VeriSM's job is to align them to one value stream.

Worked example: two services in one company. A claims service in a regulated insurer builds its mesh from COBIT for control, ITIL for incident and change flow, stage-gated approvals for audit evidence, and on-premise resources. An experimental customer app uses Scrum, DevOps automation, cloud resources and light product analytics. Same organisation, different meshes, because environment and outcomes differ. Answering with a single enterprise-wide framework stack would be wrong.

Traps that cost marks

  • Treating the mesh as a fixed framework stack or a maturity ladder.
  • Assuming more practices mean a better mesh.
  • Copying another organisation's mesh without its context.
  • Forgetting that environment and emerging technologies are mesh elements, not background.
  • Reducing VeriSM to a single framework such as ITIL.