State vs Status: What Engineering Leaders Should Report

Status measures progress on specific tasks. Is the feature done? Are we on schedule? It's transient and surface-level. State measures the internal health of the technical asset. Is our capacity to change increasing or decreasing? Is the system getting healthier or rotting? The CTO monitors State. The CEO must value State over temporary Status.

All metrics must flow automatically from the code and deployment pipeline. Zero manual reporting. Connascence degree, fan-out, and regression rates should be visible to anyone who looks. Once the data is visible, hiding problems becomes impossible.