Role-Conflict Recurrence Audit¶
Test or assessment — instantiates Role-Expectation Conflict Reconciliation
Samples workload, decisions, handoffs, exceptions, distress, and harm after redesign.
The Role-Conflict Recurrence Audit is a scheduled look-back that returns weeks or months after a role conflict was supposedly resolved and samples the person's actual work to see whether the fix held — or whether the duty that was formally released has quietly crept back. It is the only mechanism in the set that operates on a closed case, and its question is temporal rather than diagnostic: not "is there a conflict?" but "did the resolution survive contact with daily reality, or did informal pressure reinstate the old arrangement while the org chart still says it's gone?"
Example¶
A regional grocery chain resolves a recurring conflict for its store managers, who had been both running the sales floor and personally building the weekly staff schedule — two duties that collided every Sunday night and produced chronic unpaid overtime. The redesign moves scheduling to a centralized workforce-planning team; the release rule records that store managers no longer own scheduling. Case closed.
Three months later the recurrence audit samples eight stores. It pulls actual clock-in records, interviews two managers confidentially, and reads the scheduling system's edit logs. In five of the eight stores, managers are still overriding the central schedule on Sunday nights — because district directors kept holding them personally accountable for labor-cost targets that only the schedule controls. The formal duty moved; the informal accountability did not, so the released duty returned under a new name. The audit's output is not blame for the managers but a finding that the source policy — how district directors are measured — reinstated the conflict. That routes the case back to redesign, not to the individuals who were quietly absorbing the strain.
How it works¶
- Sample actual work, not self-reports of compliance. Pull records, logs, and schedules; interview confidentially; look at what happens, not what is claimed.
- Compare designed duties to real duties, watching specifically for the released duty reappearing in a new guise.
- Read the fingerprints of recurrence — hidden overtime, workarounds, exceptions hardening into routine, successor overload, retaliation, and moral distress.
- Attribute to the source, not the person. Aggregate across cases to find the structural driver behind repeated returns.
- Route findings to redesign, feeding staffing, role architecture, and source policy — not to discipline.
Tuning parameters¶
- Look-back timing — how long after resolution, and at which peaks, the audit runs. Too soon and the fix hasn't been stress-tested; too late and harm accrues unseen.
- Sampling breadth and depth — how many sites or cases, and how far into each. Broad-and-shallow catches drift; narrow-and-deep catches how it hides.
- Evidence-source mix — administrative metrics versus confidential follow-up; silence after intervention can mean resolution or fear, and only the second source tells them apart.
- Attribution grain — whether findings are pinned to individuals or to the source system that reproduces the conflict.
- Trigger sensitivity — how much drift counts as recurrence worth reopening the case for.
When it helps, and when it misleads¶
Its strength is that it is the guard against hollow remedy — the resolution that looks finished on paper while the work never changed — and it is the one mechanism that can prove a redesign either held or quietly failed.
Its failure mode is that what you measure, they manage: once role-holders know which indicators are watched, a returned duty simply hides better rather than disappearing, and the audit records compliance instead of reality. This is Goodhart's law[n1] operating on the audit itself. A related misuse is letting the audit become surveillance of the role-holder rather than of the role system, which both violates privacy and teaches people to conceal. The guarding discipline is to pair announced metrics with confidential evidence from actual work, measure the system rather than the person, and treat recurrence across cases as a mandate to redesign the source — not to re-discipline the quieter people who ended up carrying the strain.
How it implements the components¶
The audit realizes the archetype's after-the-fact verification work — confirming a resolution held, not diagnosing or resolving one:
role_transition_and_residual_strain_monitor— it is this monitor operating on a live case: comparing formal assignment against actual work and sampling for hidden return, retaliation, moral distress, and successor overload.role_duty_priority_and_release_rule— it re-checks each duty the release rule marked transferred, deferred, or ended, verifying the disposition actually stuck rather than reverting informally.
It does NOT implement role_expectation_and_principal_inventory or affected_party_and_nonwaivable_duty_map — cataloguing the demand set and mapping exposure is the Role-Expectation Conflict Matrix's; nor role_capacity_authority_and_boundary_test or role_incompatibility_classifier, the peak-capacity verdict owned by the Simultaneous Feasibility and Capacity Test.
Related¶
- Instantiates: Role-Expectation Conflict Reconciliation — supplies the evidence that a resolution durably reduced the conflict rather than redistributing it.
- Consumes: Recusal, Delegation, or Separation Gate — it audits the redesigned occupancy that gate approved, checking whether the change survived; and the release recorded by Duty-Priority and Harm Comparison.
- Sibling mechanisms: Role-Expectation Conflict Matrix · Simultaneous Feasibility and Capacity Test · Duty-Priority and Harm Comparison · Recusal, Delegation, or Separation Gate · Protected Role-Conflict Conference
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Role-Conflict Recurrence Audit operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it samples workload, decisions, handoffs, exceptions, distress, and harm after redesign.
Independent corroboration: The frozen evidence defines Role-Conflict Recurrence Audit as 'Samples workload, decisions, handoffs, exceptions, distress, and harm after redesign', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Post-redesign auditing of workload, decisions, exceptions, and harm is organizational design evaluation.
Related originating lineages:
- Psychology — Occupational stress and role-conflict research independently supply distress measures.
- Statistics & Experimental Design — Sampling and longitudinal comparison materially test recurrence.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: samples workload, decisions, handoffs, exceptions, distress, and harm after redesign.
Review resolution: Both blind reviewers agree that organizational_management is the primary historical origin. Explicit reconciliation of alternate origin disagreement, origin mode disagreement starts from reviewer_a’s mechanism-specific evidence: Post-redesign auditing of workload, decisions, exceptions, and harm is organizational design evaluation. Reviewer A proposed alternates=psychology, statistics_experimental_design, origin_mode=cross_disciplinary_synthesis, domain_reach=multi_domain, and encyclopedia_synthesis=true; reviewer B proposed alternates=systems_cybernetics, origin_mode=single_lineage, domain_reach=multi_domain, and encyclopedia_synthesis=true. The final record retains every independently supported alternate from either review (psychology, statistics_experimental_design, systems_cybernetics) without an arbitrary cap, selects origin_mode=cross_disciplinary_synthesis to represent the combined lineage evidence, and keeps domain_reach=multi_domain and encyclopedia_synthesis=true from the more mechanism-specific assessment. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] The principle associated with economist Charles Goodhart — "when a measure becomes a target, it ceases to be a good measure." Applied to a recurrence audit, once role-holders know which indicators are watched, a returned duty can be made invisible in exactly those indicators, so the audit must also sample actual work and confidential experience, not only the metrics it announces. ↩