Answer yes/no for each indicator. Mostly "yes" answers in this section, with few in later sections, suggests a Reactive baseline.

• Documentation — Is documentation mostly absent or so outdated it can't be relied on during an incident?
• Change Management — Do changes happen without a defined process, on an as-needed basis?
• Incident/Problem — Are incidents resolved individually with no pattern tracking across recurrences?
• Monitoring — Is monitoring minimal or limited to a few systems, with problems typically discovered by users first?
• Asset Management — Is there no reliable current inventory of hardware, software, or cloud assets?

• Documentation — Does documentation exist for major systems, even if inconsistently maintained?
• Change Management — Is there an informal but generally followed process for reviewing changes before implementation?
• Incident/Problem — Are incidents logged, even if problem tracking (recurring root cause analysis) is inconsistent?
• Monitoring — Are critical systems monitored, even if alert thresholds are mostly vendor defaults?
• Asset Management — Does an inventory exist, even if it is not regularly reconciled against reality?

• Documentation — Is documentation standardized, centrally located, and assigned to named owners?
• Change Management — Is there a formal, consistently followed change process with risk classification and rollback planning?
• Incident/Problem — Are recurring incidents formally tracked as problems with root cause investigation?
• Monitoring — Are alert thresholds tuned to the environment, with a defined escalation path by severity?
• Asset Management — Is the asset inventory reconciled on a defined, recurring cadence?

• Documentation — Is documentation reviewed and updated proactively after changes, not just periodically?
• Change Management — Are change trends analyzed to identify risky patterns before they cause incidents?
• Incident/Problem — Are problem trends used to drive infrastructure or process improvements, not just tracked?
• Monitoring — Is monitoring used to detect and address emerging issues before they become incidents?
• Asset Management — Are lifecycle and end-of-support risks addressed proactively based on asset data?

• Documentation — Is documentation quality and currency itself measured and continuously improved?
• Change Management — Is the change process itself periodically reviewed and refined based on outcome data?
• Incident/Problem — Is there a continuous feedback loop from incidents and problems into architecture and process design?
• Monitoring — Is monitoring coverage and alert quality continuously tuned based on operational feedback?
• Asset Management — Is asset data integrated across change, incident, and monitoring processes to inform decisions?

For each capability area (documentation, change management, incident/problem management, monitoring, asset management), identify the highest stage where most indicators are answered "yes." Most organizations will land at different stages across different capability areas — that unevenness is itself useful diagnostic information.

• IT Operational Maturity Model — /knowledge-center/it-operations/it-operations-service-management/it-operational-maturity-model
• IT Operations Fundamentals — /knowledge-center/it-operations/it-operations-service-management/it-operations-fundamentals