Playbook Validity Index (PVI)

GMI-SWD-032Software DeliveryIntegration-Required

Definition

The percentage of organizational playbooks (enforced coding standards, architectural patterns, and workflow templates) that are verified as current, technically correct, and aligned with the organization's current architectural direction, measured by periodic expert review.

The Measurement Gap

There is no metric that tells you whether the organizational playbooks being enforced are still valid, current, and architecturally aligned, which means high conformance rates can enforce outdated or counterproductive standards.

Formula

Plain language: Take every playbook in the platform's enforced library. Have a senior engineer or architect review each one against three criteria: (1) Is it technically current? (Does it reference current framework versions, non-deprecated APIs, current security patterns?) (2) Is it architecturally aligned? (Does it support the direction the architecture is heading, not just where it's been?) (3) Is it non-conflicting? (Does it avoid contradicting other enforced playbooks?) Score each criterion pass/fail. A playbook is "valid" only if all three criteria pass.

Notation:

PVI = (PB_valid / PB_total) × 100

Variables:

  • PB_valid = playbooks where all three validity criteria pass (count, MANUAL: expert review)
  • PB_total = total playbooks in the enforced library (count, NATIVE from platform configuration)

Validity criteria:

  • Technical currency: references only current (non-deprecated) frameworks, libraries, APIs, and patterns. (pass/fail, MANUAL)
  • Architectural alignment: supports the organization's current target architecture, not just legacy architecture. (pass/fail, MANUAL)
  • Non-conflicting: does not contradict any other enforced playbook in the library. (pass/fail, DERIVED from pairwise playbook comparison + MANUAL verification)

Proposed formula, pending validation pilots.

At a Glance

Category
Playbook Governance Quality

Decision Supported

Are the playbooks we're enforcing still the right standards, or has the playbook library become a source of technical debt: reliably enforcing patterns that are outdated, deprecated, or misaligned with where the architecture is heading?

← Playbook Conflict Density (PCD)Deploy Strategy Exposure Index (DSEI) →

Assess Your Organization

The AI-GPS Assessment evaluates your AI governance maturity and recommends KPIs like this one for your implementation roadmap.

Take the Free AI-GPS Assessment