Skills on AI

Verism

Download raw SKILL.md

Use when asked to apply VeriSM, an organization-level approach to service management that combines several management practices (such as Agile, DevOps, Lean, and ITIL) across the whole business. Distinct from [[itil-5]] (one framework), [[agile-principles]] (one practice), and [[cobit-2019]] (governance framework).

VeriSM is an organizational-level approach to service management. It is best for enterprises that combine multiple management practices, such as Agile, DevOps, Lean, and traditional ITIL, across the whole business. VeriSM calls the chosen combination a "management mesh".

Input required

  • The organization, its services, and its business goals.
  • The management practices already in use across teams.
  • Governance arrangements and risk appetite.
  • The official VeriSM material the user holds.

Questions to ask first

  1. Which practices do different teams use today?
  2. What are the organization's governance rules and principles?
  3. Which emerging technologies or business changes matter?
  4. Where do practices conflict or leave gaps?
  5. Who decides how services are delivered?

Method

  1. Start from organizational governance. Identify the rules, direction, and risk appetite the organization already has.
  2. State service management principles. Define how the organization wants services to be produced and managed, consistent with governance.
  3. Build the management mesh. For each service or product, choose the combination of resources, environment, practices (for example Agile Delivery), and emerging technologies that fits.
  4. Develop capabilities. Check that the organization has the skills and structures to run the mesh.
  5. Deliver and learn. Produce services, gather feedback, and adjust the mesh.

Output format

  • Principles statement.
  • Mesh table: service or product, practices chosen, why.
  • Capability gaps and actions.

Ground rules

  • Do not state VeriSM's model elements beyond what the user supplied or official material confirms.
  • Do not force one practice on all services; the point is to choose deliberately.

Self-check before answering

  • Does each mesh choice trace to governance and principles?
  • Are conflicts between practices addressed?

Common pitfalls

  • Treating VeriSM as a process set — it is an approach that combines others.
  • No governance link.
  • Mesh chosen by team preference alone.

Example prompt

"Design a VeriSM management mesh for a company where the platform team uses DevOps and the support team uses ITIL."

Learn more

View verism/SKILL.md on GitHub