Why DCO Competency Areas Cannot Mature in Parallel

The Question

Most digital maturity models score an organization's capability areas on parallel scales, then recommend investing in whichever scores lowest. That framing assumes the areas are substitutable and additive: strengthen automation this quarter, experience design next quarter, and the aggregate maturity score rises accordingly. Capability-sequencing research complicates this assumption. Do Digital Cognitive Organization (DCO) competency areas — governance and coordination, automation and execution, experience design, and workforce capability — mature as independent, parallel investment tracks, or does the evidence support a dependency sequence in which governance capacity must stabilize before the others can compound?

The evidence favors dependency over parallelism, though not an absolute or universal one. Research on organizational capabilities, management practices, and staged maturity models converges on a consistent pattern: coordination and governance capacity functions as a leading, binding constraint, while workforce capability behaves as a trailing one that cannot be usefully front-loaded. Organizations that fund all four areas evenly, on the assumption that balance signals commitment, more often produce fragmented capability than compounding maturity.

Context and Definitions

This note uses "DCO competency area" to mean a distinct organizational capability that a Digital Cognitive Organization must develop: governance and coordination (the function that translates strategy into digital capability requirements and owns cross-functional decision rights), automation and execution (the operational capacity to deploy and run AI and process automation reliably), experience design (the consistent design of digital interactions for customers, workers, and partners), and workforce capability (the skills and role redesign needed to operate the resulting system).

"Maturity sequencing" refers to the order in which an organization builds these competencies, as distinct from the level it eventually reaches in each. A sequencing claim is a claim about dependency, not about final capability ceilings: an organization could, in principle, reach high maturity in all four areas regardless of order, but the evidence below concerns how reliably and efficiently that maturity accumulates depending on sequence.

The scope here is enterprise-level digital transformation programs in large and mid-sized organizations, drawing on management-practice research, organizational capability theory, staged maturity frameworks, and large-sample digital transformation surveys. The note does not address early-stage ventures, where formal governance structures are often deliberately minimal, nor does it claim a single mandatory sequence applies identically across sectors and regulatory contexts.

What the Evidence Shows

Staged maturity models treat sequence as structural, not optional. The Capability Maturity Model, developed at the Software Engineering Institute to assess software process capability, defines five maturity levels in which each level's practices assume the disciplines of the levels below are already in place; an organization cannot meaningfully practice "optimizing" behavior without first having a "managed" and "defined" process foundation (Paulk et al., 1993). The model's staged structure has been influential well beyond software engineering precisely because it formalizes an intuition many transformation practitioners hold informally: some organizational capabilities are prerequisites for others, not peers to be developed on independent tracks.

Management and coordination capacity is itself a measurable, foundational capability. Bloom and Van Reenen's cross-country study of management practices found substantial, persistent variation in structured management practices across firms, and that this variation predicted productivity, profitability, and growth more reliably than many other firm characteristics (Bloom & Van Reenen, 2007). Their finding is not specific to digital transformation, but it supports a broader claim this note relies on: coordination and management capacity is a distinct, foundational organizational capability rather than an incidental byproduct of investment in visible technology.

Large-sample digital maturity research finds leadership and coordination capability, not technology adoption, separates mature organizations from the rest. In a global survey of roughly 3,700 executives and managers, Kane et al. (2017) found that digitally maturing organizations were distinguished less by which technologies they had adopted and more by leadership behavior: a clear digital strategy, cross-functional collaboration structures, and a culture that tolerated experimentation. Organizations at earlier maturity stages frequently owned comparable technology but lacked the coordinating structures to convert it into consistent value. Westerman et al. (2014) reached a related conclusion using a two-axis model of digital capability and leadership capability, finding that organizations strong in digital capability but weak in leadership capability underperformed both peers strong in neither and peers strong in leadership capability alone.

Recent enterprise AI evidence reinforces the same ordering for automation specifically. McKinsey's 2025 global AI survey found that workflow redesign, senior oversight, and clear ownership structures had a stronger association with realized value than the number or sophistication of AI use cases deployed; the survey also found that organizations more often centralize governance, risk, and data functions while distributing adoption and talent decisions closer to the business (Singla et al., 2025). This is consistent with automation capability compounding once a coordinating layer exists, rather than substituting for one.

Counterevidence: sequencing is not a universal law. Vial's (2019) systematic review of digital transformation research found considerable heterogeneity in transformation pathways; structural and organizational change frequently precedes or accompanies technology-driven disruption, but the review does not support a single mandatory sequence applying identically across all organizational contexts. Some organizations pursue effective automation or experience improvements through decentralized, product-led initiatives before formal governance structures exist, particularly in smaller or less regulated environments. The dependency pattern described above is a strong tendency in enterprise-scale, cross-functional transformation, not an invariant law.

What Deeper Analysis Reveals

The evidence above supports more than a restatement of "governance matters." It suggests a specific mechanism and a boundary condition that most balanced-scorecard maturity models miss.

The mechanism is that governance and coordination capacity functions as a binding constraint on the other three competency areas, in the economic sense: below some threshold of coordination capacity, additional investment in automation, experience, or workforce development does not convert into proportional maturity gains, because there is no mechanism to translate local capability into cross-functional, repeatable value. This is why Bloom and Van Reenen's structured-management findings and Kane et al.'s leadership findings, though drawn from different literatures and methods, point the same direction: both identify a coordinating capacity that determines how much of an organization's other investments actually compound.

The boundary condition, visible in Vial's (2019) review and in the counterevidence above, is that the binding constraint applies most strongly at enterprise scale and across functional boundaries. A single product team can automate a workflow or redesign an experience without waiting for enterprise-wide governance, because the coordination problem it faces is small enough to solve informally. The constraint becomes binding specifically when an organization tries to make several such efforts compound into an enterprise capability, because that compounding is precisely the coordination problem governance capacity exists to solve. This distinction, between local capability improvement and enterprise-level compounding, is missing from parallel-scale maturity models that score all four areas as if they answered the same question.

A further distinction worth making explicit: governance capacity is not the same as a named governance structure. An organization can establish a Digital Office, steering committee, or CDO function and still lack governance capacity if that structure holds no real cross-functional decision rights. This explains a pattern practitioners often observe and existing maturity models struggle to account for: organizations with a formally documented governance function that nonetheless show the same fragmentation as organizations with none. The relevant variable is decision authority, not organizational chart position.

Through the D2 Digital Cognitive Organization lens, this reframes governance not as one competency area competing for budget alongside the others, but as the organizational mechanism that determines how much of the budget allocated elsewhere converts into compounding capability. The D4 Digital Transformation 2.0 lens adds the portfolio-design implication: a transformation portfolio that allocates capital evenly across competency areas is optimizing for the appearance of balanced commitment rather than for the sequence that actually produces enterprise-level maturity.

Implications for Leaders

Diagnose coordination capacity before allocating capital. Before funding automation, experience, or workforce initiatives at scale, leaders should assess whether a coordinating function exists with genuine cross-functional decision rights, not merely a named office. Where that assessment is negative, the highest-value initial investment is establishing real decision authority, even though this produces no visible technology output in the short term.

Expect an early-phase speed cost and a later-phase compounding benefit. Sequenced investment is typically slower in its first phase than parallel investment, because governance work produces no immediately visible deliverable. Leaders should set expectations accordingly and resist reallocating capital away from coordination work toward more visible initiatives before it has had time to compound.

Distinguish local wins from enterprise capability. A successful automation pilot or experience redesign in one business unit is evidence of local capability, not enterprise maturity. Leaders should ask specifically whether the initiative depended on informal workarounds that would not survive being replicated across the organization; if so, it is not yet evidence that automation or experience competency has matured at enterprise scale.

Treat workforce investment as a trailing, continuous activity, not a front-loaded program. Because workforce capability is most useful when applied against a stable, redesigned operating environment, large reskilling investments made before governance and automation have stabilized are at higher risk of producing skills that have no immediate application.

Audit named governance structures for actual authority. Where a governance function already exists, leaders should verify it holds real budget and decision authority over the initiatives it is meant to coordinate, rather than assuming its existence on an organization chart is sufficient evidence of coordination capacity.

Conclusion

The evidence does not support treating DCO competency areas as parallel, independently fundable tracks. Governance and coordination capacity behaves as a binding constraint: below a threshold of real cross-functional decision authority, automation, experience, and workforce investments compound poorly regardless of their individual quality. This is a strong tendency in enterprise-scale, cross-functional transformation, not a universal law; smaller, decentralized initiatives can succeed without waiting for formal governance to mature first.

The main limitation is that most evidence connecting governance capacity to digital maturity is correlational, drawn from surveys and case research rather than controlled comparison. The next useful step is longitudinal: tracking transformation portfolios over time to test whether organizations that establish real governance authority first show measurably better compounding than those funding all four areas simultaneously.

Limitations

This note draws primarily on cross-sectional executive surveys, a widely cited staged process-maturity model developed outside the digital transformation context, and a systematic literature review. None of these establishes causation, and management-practice and digital-maturity research both show meaningful variation by sector, firm size, and regulatory environment. The sequencing pattern described here should be read as a strong, well-evidenced tendency at enterprise scale, not a formula that applies identically to every organization regardless of context.