Capital Mispricing and Structural Risk

Chapter 9: Who Loses When Clarity Wins

The specific roles whose authority is diminished when structural clarity replaces coordination: programme directors, central data teams, product managers of portfolio labels, and the consulting ecosystem. Their resistance is not cynical but rational; these roles were legitimate responses to a real structural problem.

The preceding chapters named what the dysfunction costs. This chapter names who profits from it continuing.

Between diagnosis and correction, there is resistance. It is predictable, rational, and the single most common reason structural corrections fail. Naming it is a precondition for surviving it.

The roles that lose scope were not mistakes but rational responses to a real problem. The organisation rewarded the visible coordination of complexity rather than its elimination, because complexity itself was invisible to the people who controlled headcount. The structure that created them has changed. The roles have not.

Programme directors and portfolio leads. Their authority derives from coordinating across teams that do not share ownership. When units own processes and interact through contracts, the coordination function disappears. The programme director who manages dependencies between six teams is performing work that versioned contracts and owned boundaries make unnecessary. While the work itself was real, the genuine need for it is not.

Central data teams. Their authority derives from controlling a shared substrate. When units own their data and publish through contracts, the central team's scope shrinks to reporting-layer governance: contract compatibility, cross-unit standards, conflict resolution. This is a smaller, more focused function. For a team that built its identity around controlling the organisation's data, it is experienced as a loss.

Product managers and product owners of portfolio labels. Their role bridges the gap between a portfolio label and the system. When the portfolio label corresponds to an owned process, the bridge is unnecessary. The product manager of “Customer Engagement” exists because Customer Engagement has no coherent boundary in the code. When it does, the role either becomes the process owner or it disappears.

...

See also: Full contents · Preview chapters · Illusions of Work