QEEPP Assessment Checklist
The QEEPP Assessment Checklist is a structured worksheet used to score structural integrity across the five interdependent dimensions of the framework: Quality, Effectiveness, Efficiency, Performance, and Productivity.
It organizes the assessment into 25 structural controls, with five controls under each dimension, aligned to the QEEPP progression from Stabilize to Scale.
The checklist supports both initial and recurring assessments and is intended to strengthen scoring consistency across initiatives, platforms, portfolios, and operating models.
QEEPP Cube assessment structure
The QEEPP assessment model follows a structured architecture referred to as the QEEPP Cube.
The cube represents the three structural layers of the assessment:
How to use the checklist
QEEPP maturity scale
| Score | Maturity State | Structural Meaning |
|---|---|---|
| 1 | Ad hoc | Reactive, unstable, and inconsistent practices |
| 2 | Emerging | Initial structures exist but remain inconsistent |
| 3 | Defined | Processes and controls are established and repeatable |
| 4 | Managed | Execution is measured, monitored, and actively governed |
| 5 | Institutionalized | Practices are embedded, standardized, and self-sustaining |
Quality | Stabilize
Structural integrity before velocity.
| Structural control | Diagnostic prompts |
|---|---|
| Architecture baseline | Is a clear target architecture defined and used to guide transformation decisions? |
| Security guardrails | Are security controls and guardrails embedded into design, delivery, and deployment practices? |
| Data foundations | Are data ownership, governance, quality expectations, and stewardship responsibilities clearly established? |
| Reliability engineering | Are reliability expectations, resilience mechanisms, and recovery procedures defined and tested? |
| Technical debt and risk | Is technical debt identified, quantified, prioritized, and governed alongside delivery pressure? |
Effectiveness | Align
Relevance before optimization.
| Structural control | Diagnostic prompts |
|---|---|
| Strategy alignment | Are transformation initiatives directly linked to strategic business objectives? |
| Capability mapping | Are business capabilities mapped to technology initiatives, dependencies, and transformation scope? |
| Value streams | Are value streams clearly defined and used to organize change, ownership, or investment focus? |
| Outcome definition | Are measurable business outcomes or OKRs defined for the initiatives being assessed? |
| Portfolio prioritization | Are initiatives prioritized according to business value, impact, and structural readiness? |
Efficiency | Optimize
Lean before expansion.
| Structural control | Diagnostic prompts |
|---|---|
| Operating model | Is the operating model clearly defined with understood roles, responsibilities, and decision ownership? |
| FinOps discipline | Are cloud, infrastructure, or platform costs actively baselined, monitored, and optimized? |
| Application rationalization | Are redundant systems being reduced and platform sprawl being governed intentionally? |
| DevSecOps flow | Are delivery pipelines standardized, automated, and consistently applied across teams? |
| Automation | Are repetitive delivery and operations activities automated through approved tooling and infrastructure as code? |
Performance | Measure
Measurement before momentum.
| Structural control | Diagnostic prompts |
|---|---|
| KPI framework | Are transformation KPIs clearly defined and used to monitor structural integrity and execution health? |
| Service metrics | Are service expectations expressed through SLA or SLO definitions and reviewed consistently? |
| Execution cadence | Are governance reviews, delivery checkpoints, and accountability rhythm established and followed? |
| Risk reporting | Are risk, compliance, and delivery exceptions surfaced, tracked, and communicated proactively? |
| Operational transparency | Are dashboards and performance signals visible to decision-makers and relevant delivery stakeholders? |
Productivity | Scale
Scale without degradation.
| Structural control | Diagnostic prompts |
|---|---|
| Platform enablement | Do internal platforms or shared services help teams deliver faster with stronger consistency and control? |
| Self-service infrastructure | Can teams provision approved infrastructure or platform capabilities through governed self-service mechanisms? |
| Reusable components | Are templates, patterns, services, and components reused to reduce duplicated effort? |
| Delivery enablement | Do teams have the standards, tooling, and support needed to deliver consistently at scale? |
| Scalable capacity | Can delivery capacity expand without increasing fragmentation, instability, or loss of governance control? |