When everything is a priority, nothing stabilises. Modern organisations operate under constant demand. Transformation, compliance, optimisation, innovation — all run concurrently. Each initiative is justified. Each is urgent. Individually, they make sense. Collectively, they compete.
Why concurrency feels unavoidable
External pressure rarely pauses. Leaders hesitate to delay necessary change. So new work layers onto existing commitments. Without explicit retirement of prior work, concurrency becomes cumulative.1 Managers sequence informally. Teams negotiate priority locally. The system remains busy. But coherence declines.2
What unmanaged concurrency produces
Unmanaged concurrency produces attention fragmentation, decision delay, escalation repetition, and uneven adoption. Managers buffer overload quietly. Sponsors intervene episodically. Practitioners facilitate alignment sessions. But without explicit portfolio discipline, load accumulates.
The reinforcing cycle
When performance variance increases, the instinctive response is to tighten oversight, expand reporting, and multiply coordination layers. Each addition consumes capacity, which increases variance, which prompts further control. The organisation becomes structurally congested — not because it lacks discipline, but because it lacks trade-off clarity.3
Why this matters
Concurrency is not inherently destabilising. Implicit concurrency is. When leadership does not articulate what pauses under constraint, the system absorbs contradiction downward. That absorption has cost.4 This is one way of understanding how portfolio governance interacts with structural strain and strategic coherence.
-
Samuelson, W., & Zeckhauser, R. (1988). “Status Quo Bias in Decision Making.” Journal of Risk and Uncertainty, 1(1), 7–59. https://doi.org/10.1007/BF00055564. Samuelson and Zeckhauser demonstrate that decision-makers systematically favour maintaining existing commitments over retiring them, even when retirement would improve outcomes, because retiring prior commitments requires acknowledging that the original decisions were suboptimal — a psychologically and politically costly action. Applied to portfolio management, this bias explains why new initiatives are consistently launched without retiring prior ones: launching feels like progress while retiring feels like failure. Concurrency accumulates not through negligence but through the systematic preference for adding over removing. ↩︎
-
Weick, K. E. (1995). Sensemaking in Organizations. Sage. Weick’s framework of sensemaking explains local negotiation of priority as an adaptive response to absent coordination. When formal structures for priority governance are inadequate, people do not simply wait — they construct their own interpretations of what is most important based on available cues (which sponsor is most visibly active, which escalations are loudest, which metrics are tracked most closely). Informal sequencing is distributed sensemaking: the organisation continues to function, but coherence declines because each team’s locally constructed priority map diverges from every other team’s, and from the organisation’s actual strategic sequencing requirements. ↩︎
-
Pfeffer, J. (1981). Power in Organizations. Pitman. Pfeffer’s analysis of resource allocation in organisations establishes that when formal authority fails to make explicit decisions about priority, the decision does not go unmade — it is made through political processes. Competing demands are absorbed downward through informal influence, positional leverage, and negotiated accommodation. The cost of absorbing contradiction downward is not merely efficiency loss; it is the substitution of political outcomes for strategic ones, with the strongest political actors’ priorities winning rather than the organisation’s sequenced strategic priorities. ↩︎
-
Hackman, J. R. (1987). “The Design of Work Teams.” In J. W. Lorsch (Ed.), Handbook of Organizational Behavior, pp. 315–342. Prentice Hall. Hackman’s work on team design identifies boundary management — managing the interface between the team and its external environment — as a structural function that must be explicitly designed into a group’s operating model. When this function is not designed in, individuals informally absorb the boundary management load: managing competing demands, negotiating priority conflicts, interpreting conflicting signals. This informal absorption is the hidden cost of implicit concurrency — it is real work that consumes real capacity, but it appears in no portfolio plan and generates no visible output. ↩︎