Protected Role-Conflict Conference¶
Protocol — instantiates Role-Expectation Conflict Reconciliation
Brings principals and affected parties into nonretaliatory resolution with authority and written outcome.
The Protected Role-Conflict Conference is the live event where a role conflict is actually settled. It convenes the principals and the affected parties in front of someone with real authority to change the expectations, runs under explicit nonretaliation guarantees, and ends in a binding written outcome. Its distinctive feature is authority plus protection: unlike a diagnostic grid or a paper ranking, the conference is the moment revised expectations get agreed and recorded — but it only works if the convener can genuinely alter the mandate and the role-holder can speak without fear of reprisal. A meeting with neither is theater.
Example¶
A city building inspector keeps being pressured by a council member to fast-track occupancy permits for a politically important downtown development, while the building code and her professional duty require her to withhold sign-off until fire-egress deficiencies are corrected. She has quietly absorbed this for months — slow-walking rather than confronting a council member who influences the department's budget.
A protected role-conflict conference is convened by the city manager, who (unlike the council member) holds authority over both the inspector's assignments and the permit process and can bind the outcome. The council member, as a principal, is at the table; so is a representative of the building's future tenants, an affected party usually absent from such rooms. The inspector receives an explicit nonretaliation assurance and the option of bringing a representative. The conference does not relitigate the fire code — that floor is fixed going in — but it resolves the reconcilable part: the council member's legitimate interest in speed is met by a committed remediation timeline and a parallel-track inspection, while the inspector's sign-off duty is protected and the pressure to shortcut it is formally lifted. The outcome is written down — revised expectations, who owns the remediation, dates, and a review condition. What made it real was that the person in the room could change the mandate and the inspector was safe enough to describe the conflict plainly.
How it works¶
- Convene with authority. The chair must be able to actually change expectations, not merely hear them — otherwise the room can only pressure the role-holder to re-consent.
- Fix the nonwaivable floors before negotiating. Only genuinely waivable expectations are placed on the table; the floors are declared, not bargained.
- Bring the absent affected party into the room — in person or through a representative — so resolution is not a deal struck over their head.
- Guarantee nonretaliation and offer representation. Consent extracted where a principal controls pay, scheduling, or evaluation is not reliable settlement.
- Produce a binding written outcome — revised expectations, resources, decision rights, displaced-duty owners, dates, and review conditions.
Tuning parameters¶
- Convener authority level — how much mandate-changing power the chair actually holds. Too little and the conference is advisory theater dressed as resolution.
- Nonretaliation strength — from a verbal assurance to enforceable interim protection and defined sanctions for reprisal; match it to the power asymmetry in the room.
- Affected-party representation — whether and how absent beneficiaries get voice, versus being spoken for by the principals.
- Floor-setting rigor — how firmly nonwaivable duties are excluded from negotiation before anyone starts bargaining.
- Outcome bindingness — advisory minutes versus an agreement with named owners, dates, and a scheduled review.
When it helps, and when it misleads¶
Its strength is that it is the only mechanism here that can actually revise an expectation rather than merely document or rank it, and its protection lets impossible demands surface before they cause harm — an application of psychological safety[n1] to a specifically adversarial moment.
Its failure mode is that a conference without real authority or without protection is procedural theater: it pressures the role-holder to re-consent to the same conflict, and consent obtained where a principal still controls the person's pay, schedule, or evaluation is not a settlement. The classic misuse is convening a committee "to discuss" with no power to change the mandate, which launders an unresolved conflict as participation. The guarding discipline is to seat a convener who can genuinely change expectations, install nonretaliation protection and representation scaled to the power gap, and require a written outcome with owners and dates — genuine voice backed by authority, in the sense procedural-justice research means, not a meeting held for its own sake.
How it implements the components¶
The conference realizes the archetype's protected-negotiation-and-settlement work — the live decision event, not the prior diagnosis:
protected_conflict_disclosure_and_escalation_path— the conference is that path made live: protected intake, nonretaliation, representation, and routing to an authority able to change expectations.role_duty_priority_and_release_rule— the written outcome records the revised priority and the explicit disposition of displaced duties, with owners and dates.redesign_recusal_delegation_and_substitution_plan— where the settlement changes structure (a parallel-track inspection, a reassigned remediation duty), the outcome commits that redesign.
It does NOT implement role_expectation_and_principal_inventory or role_incompatibility_classifier — cataloguing and typing the conflict is the Role-Expectation Conflict Matrix's and Simultaneous Feasibility and Capacity Test's; it does not run role_capacity_authority_and_boundary_test; nor role_transition_and_residual_strain_monitor, the after-the-fact check the Role-Conflict Recurrence Audit runs to confirm the outcome held.
Related¶
- Instantiates: Role-Expectation Conflict Reconciliation — supplies the authority-backed, protected settlement the reconciliation turns on.
- Consumes: Duty-Priority and Harm Comparison — it negotiates around the nonwaivable floors and priority that comparison has already established, resolving only the waivable remainder.
- Sibling mechanisms: Role-Expectation Conflict Matrix · Simultaneous Feasibility and Capacity Test · Duty-Priority and Harm Comparison · Recusal, Delegation, or Separation Gate · Role-Conflict Recurrence Audit
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: The authorized conference resolves waivable role conflicts with affected parties present and issues a written binding outcome under nonretaliation.
Nearest alternative: Communication, Facilitation & Learning — Facilitation is essential, but the gathering's primary purpose is a bounded resolution decision.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Protected Role-Conflict Conference is most plausibly rooted in the organizational_management tradition because its characteristic form depends on the coordination, governance, learning, and redesign of organized work. The assignment tracks that formative lineage, not the many settings in which the mechanism can now be applied.
Related originating lineages:
- Law & Governance — The law_governance tradition materially shaped Protected Role-Conflict Conference through its own practice of formal rights, duties, remedies, review, and procedural constraint.
- Psychology — The psychology tradition materially shaped Protected Role-Conflict Conference through its own practice of individual cognition, motivation, judgment, and behavior.
- Sociology & Anthropology — Role theory supplies the analysis of conflicting expectations from multiple principals.
Review resolution: Both blind reviewers agree that organizational management is the primary origin. Explicit reconciliation resolves reported ambiguity, alternate origin disagreement, origin mode disagreement, encyclopedia synthesis disagreement. Formative alternate lineages are retained as law_governance, psychology, sociology_anthropology; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Attribution caveat: The named conference is synthetic, while role-conflict resolution is established organizational practice.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] Amy Edmondson's term for a shared belief that a setting is safe for interpersonal risk-taking — that one can raise a problem or admit a conflict without fear of punishment or humiliation. A role-conflict conference depends on it: without credible nonretaliation, a role-holder will re-consent to an impossible demand rather than name it aloud. ↩