Capability Levels
Five levels of Everything-as-Code transformation maturity, progressing from ad-hoc processes to continuous innovation.
Key Principle: Levels are defined by capabilities (what you can do), not outcome percentages (what you've achieved).
Level 1: Initial
Chaotic and unpredictable - Success depends on individual heroics.
Characteristics
- Manual compliance activities dominate work
- No version control for compliance artifacts
- Audits require extensive last-minute preparation
- Issues discovered late (pre-production or production)
- No automation, scattered requirements
Moving to Level 2
- Secure executive sponsorship and establish pilot team
- Begin version controlling artifacts
- Implement basic automation
- Document current processes
Level 2: Managed
Repeatable processes - Core capabilities established but not standardized.
Characteristics
- Git workflow exists for some artifacts
- Basic CI/CD pipelines running
- Some automated testing and evidence collection
- Processes documented but vary by team
- Practices in "learning" state
Moving to Level 3
- Standardize processes across all teams
- Implement comprehensive automation
- Enforce standards through tooling
- Create training programs
Level 3: Defined
Standardized organization-wide - Comprehensive, mature capabilities.
Characteristics
- All artifacts in version control (100%)
- Full CI/CD with quality gates
- TDD practiced consistently, comprehensive test coverage
- Automated evidence collection (90%+)
- Traceability auto-generated
- Continuous compliance validation
Moving to Level 4
- Implement comprehensive metrics collection
- Establish quantitative quality goals
- Apply statistical process control
- Build predictive analytics
Level 4: Quantified
Measured and controlled - Data drives optimization.
Characteristics
- Metrics collected automatically
- Statistical analysis of performance
- Predictive analytics for risk
- Quantitative quality goals tracked
- ROI of practices measured
- Data-driven decision making
Moving to Level 5
- Establish innovation budget and experimentation framework
- Build feedback loops for continuous learning
- Share learnings across organization and industry
Level 5: Optimizing
Continuous innovation - Setting industry standards.
Characteristics
- Regular experimentation with measured results
- Proactive optimization opportunities identified
- Industry leadership (conference talks, papers, open source)
- Continuous learning culture
- Innovation encouraged and rewarded
Maintaining Level 5
- Stay current with research
- Active community participation
- Regular experimentation cycles
- Measure and share innovation impact
Progression Timeline
Typical Timeline (without focused effort):
- Level 1 → 2: 6-12 months (pilot team)
- Level 2 → 3: 12-18 months (org rollout)
- Level 3 → 4: 6-12 months (metrics infrastructure)
- Level 4 → 5: 12-24 months (culture change)
Total: 3-5.5 years to Level 5. With focused effort and executive support, timelines can compress by 30-50%.
Not Linear: Organizations may be at different levels for different practice areas. Recommended: Achieve Level 2 across all areas before advancing any to Level 3.
Regression Possible: Can occur if key personnel leave, leadership changes, budget cuts, or organizational restructuring. Prevention: Document practices, automate enforcement, build organizational capability.
Determining Your Level
You're at a level when:
- ✅ You possess the capability (not just working toward it)
- ✅ You have evidence supporting capability claims
- ✅ Organization-wide (not just one team)
- ✅ Sustainable (not dependent on heroes)
Key Question: "Can we do X?" not "Have we achieved Y%?"
When in doubt, use the lower level. Conservative measurement is better.
Tutorials | How-to Guides | Explanation | Reference
You are here: Explanation — understanding-oriented discussion that clarifies concepts.