MOMCI 2026

Before any operational pattern can be correctly interpreted, the instrument must establish the distribution of expertise, the structural composition of the team, and the degree to which critical knowledge is concentrated in individuals rather than embedded in systems or documentation.

This domain captures seniority distribution, primary role classification, and team architecture — integrated, segmented, or siloed. It also captures practitioner-defined areas of deepest expertise in open-text form. That last construct is analytically significant: free-text expertise mapping surfaces knowledge concentration risk that a fixed taxonomy would obscure. When two or three engineers across an organization share a single specialization, that pattern is a platform risk — whether or not it appears in any workforce report.

Toil is the operational labor that is reactive, manual, and tactically necessary but strategically inert. Its accumulation is the primary signal of a platform organization under systemic stress. It does not appear in uptime metrics. It is not reported upward. It is, by definition, dark data — generated continuously, never collected.

This domain quantifies the practitioner's time allocation between reactive firefighting and proactive engineering, and the frequency of direct terminal-level manual intervention to resolve alerts. The intervention frequency construct is a specific proxy for automation deficit — measuring not whether automation exists in principle, but whether it is available at the actual moment of operational demand. The gap between those two conditions is where toil accumulates.

Workload distribution across mainframe teams is rarely uniform and rarely documented accurately. This domain examines how operational responsibilities are allocated across roles, where informal workload accumulates beyond what any workforce plan accounts for, and whether practitioners consider their current load sustainable. Unsustainable workload is a direct retention risk — and a barrier to bringing new practitioners into the field, as the conditions experienced by existing staff shape how the role is perceived and whether it can realistically be filled.

Organizational culture is not what an organization says about itself. It is the aggregate pattern of decisions made under operational pressure. Self-reported culture assessments produce the culture the organization wishes to have. Scenario-based instrumentation produces the culture it actually operates under.

This domain uses scenarios to assess how improvement efforts are received — whether automation proposals move forward or stall, whether modernization is structurally supported or organizationally resisted, and what friction practitioners encounter when they identify a better way to operate the platform.

The Index closes with a single open construct: given total operational autonomy, what one technical process change would most improve platform resiliency? This is the instrument's most analytically significant domain.

Practitioners who operate a system under pressure daily possess diagnostic knowledge that no external audit, vendor assessment, or management report can replicate. The gap between what they would prioritize and what the organization has chosen to address is a direct measure of organizational alignment risk. When that gap is wide and consistent across respondents, it is not an opinion. It is a finding.

Responses are coded and synthesized using Substrata Research Methodologies to surface systemic patterns without attribution. The result is the qualitative core of the published findings — the practitioner voice, surfaced systematically, analyzed without identity.