The CHRO Lens: When People Absorb Structural Ambiguity

People compensate before they complain

Where accountability is ambiguous, capable employees do not stop working — they absorb. They coordinate across a handoff no one owns, they rebuild a report the system should produce, they manage a relationship the structure failed to assign. The work gets done, so the defect stays invisible.

Absorption has a cost curve. It is free for a while, then it shows up as discretionary effort declining, then as the strongest performers leaving first, because they are the ones with options. By the time attrition is on a slide, the organization is a year past the point where the design should have been corrected.

The diagnostic error is treating the exit as a market event. Compensation benchmarking and employer branding are the reflex. Neither touches the reason the role was unbearable.

The strongest people leave a badly designed role first, because they are the only ones who can.

Four instruments, one direction

A people system reinforces the operating model only when four instruments point at the same behavior: the role as written, the capability the role requires, the manager who supervises it, and the recognition that follows performance.

Misalignment is easy to detect and rarely examined. A role written for ownership, supervised by a manager who reviews activity, is a contradiction the employee resolves personally — usually by reverting to activity. A capability model that names judgment, paired with recognition that rewards volume, teaches the organization what actually counts within a fortnight.

The chief people officer's structural contribution is not program delivery. It is holding the four instruments in agreement, and refusing to launch a fifth program into a contradiction the first four have not resolved.

The manager is the smallest unit of the operating system

Nothing in the operating model reaches an employee except through a manager. Where the manager layer is untrained, the operating design terminates one level above the work — which is precisely where most transformations quietly stop.

The practical test is whether a first-line manager can state the outcomes their team is measured on, name the decisions they may make without escalation, and describe what they would stop doing if capacity was short. Three questions, answered inconsistently, explain most execution variance in an enterprise.

Exhibit — The role reinforcement check

Run this for the three roles under the most pressure. Fill each column from the actual artefacts — the job description, the capability framework, the manager's review agenda and the last recognition or bonus decision.

Where the four columns disagree, the employee resolves the contradiction personally. That personal resolution — not the strategy — is what the enterprise actually runs on.

Signals the people system is carrying a design defect

• Attrition is concentrated in the strongest performers rather than distributed.
• Exit conversations describe frustration with clarity, not with pay.
• First-line managers cannot state the decisions they are permitted to make.
• Recognition rewards a different behavior from the one the operating model requires.
• Capability development is a calendar of programs rather than a response to a named gap.

Before the next recruiting campaign is funded, it is worth establishing whether the roles being filled are designed to be survivable. A vacancy is easy to measure; an unbearable role is not.

Behavior is never read outside the system that evokes, rewards or tolerates it.