Role Expectation Conflict Reconciliation

Make incompatible role expectations visible and govern which duty controls, what must be redesigned, and when a person needs recusal, substitution, support, sequencing, or release.

Essence

Role-Expectation Conflict Reconciliation governs incompatible demands carried by one person, position, team, or agent. It makes role sources, duties, authority, resources, loyalties, boundaries, and affected parties visible, then changes priority, structure, occupancy, support, or expectations so the contradiction is not privately absorbed.

Clarity alone is insufficient. Two expectations can be perfectly clear and still impossible or unethical to satisfy together.

The unit of intervention is the role–expectation system, not the supposedly deficient role-holder. Expectations are produced by laws, contracts, professional standards, managers, clients, communities, families, peers, metrics, identities, and informal norms. When these sources impose incompatible duties, exhorting the person to communicate better or become more resilient merely transfers the cost of organizational contradiction into private strain.

Reconciliation does not mean splitting every difference. Some duties are nonwaivable, some expectations lack legitimate authority, some conflicts can be sequenced, and some require recusal, substitution, boundary change, or release. The archetype makes that judgment explicit, contestable, and operational while preserving continuity for people who depend on the role.

Compression statement

Roles carry expectations about action, availability, loyalty, confidentiality, care, impartiality, performance, and identity. A person or position may be unable to satisfy them simultaneously, or one role may contain contradictory demands from different principals. Role-Expectation Conflict Reconciliation inventories roles and expectation sources; maps time, authority, resource, loyalty, ethical, identity, and boundary conflicts; identifies affected parties and nonwaivable duties; distinguishes negotiable preference from legitimate obligation; chooses priority through declared rules; redesigns scope, sequence, staffing, delegation, recusal, information access, or handoff; protects people from retaliation for surfacing impossible demands; and monitors residual strain, hidden work, quality, safety, and recurrence.

Canonical formula: role_and_expectation_inventory + incompatibility_classification + affected_party_and_duty_map + capacity_and_boundary_evidence + legitimate_priority_rule + redesign_recusal_substitution_options + protected_escalation_and_transition + residual_strain_monitor -> governable_role_commitments

When to Use This Archetype

Use it when roles compete for the same time or resources, demand incompatible loyalty or confidentiality, combine advocacy with impartial review, conflict across care and performance, or receive contradictory instructions from multiple principals. The conflict must have consequences beyond private preference and admit structural choices such as sequencing, delegation, recusal, substitution, added capacity, or role release.

If the only problem is unclear decision authority, use Decision Rights Clarification. If separate actors disagree, use dispute governance. If the sole concern is self-interest bias, use Conflict-of-Interest Management. High but compatible workload is ordinary capacity management.

Strong application signals

Use the full pattern when a person can satisfy expectation A or B but not both within the relevant time, resources, authority, confidentiality, or ethical constraints; when satisfying one principal predictably harms another beneficiary; when a role-holder must advocate and judge the same matter; when formal work depends on invisible caregiving, emotional, or coordination labor; or when conflict is repeatedly surfaced only after errors, illness, exit, or retaliation.

The pattern applies even when nobody is openly arguing. Role conflict can remain intrapersonal or be normalized as dedication. A clinician may privately absorb incompatible care and throughput demands; a manager may hide compliance work to preserve delivery metrics; a community leader may be bound by confidentiality while expected to represent constituents publicly. Absence of a dispute is not evidence of compatibility.

Use a lighter clarification process when expectations are vague but become jointly feasible once specified. Use workload management when the duties are compatible and the only gap is volume. Escalate to this archetype when clarity exposes a structural contradiction or when capacity additions alone cannot resolve duty, loyalty, identity, confidentiality, or authority incompatibility.

Structural Problem

Role conflict occurs when satisfying one legitimate expectation breaches, delays, or undermines another. Organizations often misdescribe it as resilience, productivity, or communication failure. That lets principals externalize impossible demands and makes the individual choose privately which beneficiary will be harmed.

The conflict can concern time, authority, loyalty, ethics, identity, care, information, impartiality, or responsibility without matching resources. It may occur across roles or inside one role with multiple principals.

Map actors, roles, and expectation sources

Separate the actor from the role and the role from each expectation. One actor can occupy several roles; one role can be occupied by several actors; and one role can receive expectations from many sources. For every material expectation, record the source, claimed authority, beneficiary, required action or restraint, quality standard, timing, information boundary, resources, consequence of breach, and route for interpretation or appeal.

Include formal and informal sources. Statutes, professional codes, contracts, job descriptions, delegations, and policies may have explicit standing. Performance targets, team norms, cultural expectations, care relationships, identity commitments, and emergency practices may be less formal but still exert real force. Informality does not make an expectation unreal; it does mean legitimacy and enforceability require careful examination.

Distinguish ambiguity, tension, overload, and conflict

Ambiguity means the expectation or authority is unclear. Tension means duties compete but can coexist with ordinary judgment. Overload means compatible duties exceed available capacity. Conflict means satisfying one material expectation necessarily violates, delays beyond tolerance, compromises, or conceals another under realistic conditions. These diagnoses can combine, but their remedies differ.

Test compatibility at peak conditions and across the complete duty cycle. Two roles may fit average hours yet collide at month-end, emergencies, court deadlines, school pickup, or recovery periods. A duty may be technically sequenced but not ethically sequenced if delay creates irreversible harm. A conflict may also be conditional: confidentiality and reporting are compatible until specified facts trigger a mandatory duty.

Identify incompatible obligation types

Time and presence conflicts are only one class. Authority conflict assigns responsibility without decision power. Loyalty conflict binds the actor to principals with opposed interests. Confidentiality conflict pits information protection against disclosure or reporting. Impartiality conflict combines advocacy, benefit, or prior involvement with independent judgment. Care and performance conflict places relational duty against throughput. Identity conflict makes role performance demand denial or betrayal of a salient community or self commitment. Ethical conflict pits an instruction against law, safety, rights, or professional standards.

Intervention Logic

Inventory roles, principals, duties, beneficiaries, authority, information, time, and resources. Translate vague expectations into observable obligations. Classify the incompatibility and identify nonwaivable duties and affected-party harms. Test simultaneous feasibility and structural options.

Where capacity, sequencing, scope, or interface changes solve the conflict, redesign them. Where judgment integrity is compromised, disclose, recuse, review independently, or separate roles. Where no feasible combination exists, apply an authorized priority rule and explicitly release, transfer, defer, or compensate displaced duties. Protect disclosure and monitor handoffs, retaliation, residual strain, and recurrence.

1. Construct the role–expectation map

Inventory actors, occupied roles, principals, beneficiaries, formal and informal expectations, authority bases, resources, information rights, temporal windows, and accountability. Translate abstractions such as “be supportive,” “deliver,” “remain neutral,” or “protect confidentiality” into observable obligations and tolerances. Record disputed interpretations rather than prematurely choosing one.

2. Test source legitimacy and precedence

Verify whether the source has authority over the role and the type of duty asserted. Distinguish law, rights, safety, professional duty, contract, delegated authority, policy, legitimate managerial direction, beneficiary expectation, custom, preference, and self-imposed norm. Precedence is contextual: a performance target does not override a statutory reporting duty; a manager cannot waive a professional obligation they do not own; and a family or community expectation may carry moral weight without automatically authorizing access to confidential information.

Build a reasoned priority order rather than a universal list. Consider legal force, rights and safety floors, professional independence, mandate scope, affected-party harm, reversibility, urgency, consent, and whether the source created the conflict. Make exceptions visible and reviewable.

3. Diagnose the incompatibility

Pair expectations and test simultaneous feasibility, sequencing, substitution, information separation, and conditional triggers. Estimate realistic time, attention, emotional labor, recovery, authority, competence, and resource requirements. Identify which assumption creates the collision and whether it is necessary. Capture the role-holder's evidence without requiring public disclosure of sensitive identity, health, family, or client information.

4. Generate reconciliation options

Start with expectation clarification and removal of illegitimate demands. Then consider scope reduction, resource addition, deadline or sequence change, interface redesign, joint ownership, delegation, substitute staffing, information segregation, independent review, recusal, role separation, boundary renegotiation, temporary relief, or exit. Options may combine: recusal without a qualified substitute protects integrity but abandons the beneficiary.

5. Negotiate where duties are waivable

When sources have legitimate but negotiable claims, convene an authority-linked negotiation. Make nonwaivable floors explicit first. Compare options by beneficiary harm, role-holder burden, continuity, privacy, reversibility, capacity, and accountability. An agreement must state revised expectations, resources, boundaries, decision rights, displaced duties, owners, dates, and review conditions. Consent obtained under retaliation risk is not reliable settlement.

6. Adjudicate when negotiation cannot resolve

Escalate unresolved precedence or rights conflicts to an authorized, sufficiently independent decision maker. Provide notice, relevant evidence, representation where stakes warrant, a record of reasons, conflict-of-interest controls, and appeal or review. Adjudication is not generic dispute settlement: its question is which role obligation governs and how the displaced obligation will be lawfully released, transferred, or remedied.

7. Transition roles and protect affected parties

Implement handoffs, successor access, confidentiality boundaries, knowledge transfer, consent, continuity coverage, compensation, and communication. Limit disclosure to what each party needs operationally. If the person exits or a role is separated, preserve records and services without carrying prohibited information across boundaries.

8. Monitor and prevent recurrence

Track workload, decision delay, quality, safety, ethical incidents, moral distress, absence, turnover, complaints, workarounds, handoff failure, retaliation, and the informal return of released duties. Feed findings into staffing, role design, source policy, escalation, and leadership review. A resolved case should reduce the structural source of future conflicts, not merely redistribute it to a quieter person.

Key Components

The Role, Expectation, and Principal Inventory establishes the full demand set. The Incompatibility Classifier separates time, authority, loyalty, information, ethical, and identity conflicts. The Affected-Party and Nonwaivable-Duty Map protects less powerful beneficiaries. The Capacity, Authority, and Boundary Test distinguishes ambiguity from impossibility.

The Duty Priority and Release Rule prevents silent dropping. The Redesign, Recusal, Delegation, and Substitution Plan changes structure. Protected Disclosure and Escalation makes early reporting safe. The Transition and Residual-Strain Monitor ensures released work does not return informally.

Component	Description
Role, expectation, and principal inventory ↗	The inventory establishes who occupies which role, who asserts each expectation, who benefits, what authority is claimed, and what resources and information accompany the duty. It includes informal care, identity, and relational expectations only when relevant and with privacy safeguards. Without source mapping, the loudest instruction can masquerade as the legitimate one.
Role-incompatibility classifier ↗	The classifier distinguishes ambiguity, overload, conditional tension, and structural conflict, then tags time, resource, authority, loyalty, interest, confidentiality, identity, care, ethical, and multi-principal modes. Multiple tags are normal. Classification guides options: additional staff can solve capacity conflict but cannot make a conflicted adjudicator impartial.
Affected-party and nonwaivable-duty map ↗	This map prevents priority from becoming a contest among principals alone. It identifies people whose safety, rights, care, confidentiality, access, or livelihood depends on each duty, including parties absent from the meeting. It also names which obligations cannot be casually traded and who, if anyone, can interpret or waive them.
Role capacity, authority, and boundary test ↗	The test checks realistic time, peaks, attention, emotional labor, recovery, competence, decision power, information access, resources, and separation. It also tests boundary permeability: whether information, relationships, or authority from one role improperly crosses into another. A clear assignment fails if its enabling conditions do not travel with it.
Role-duty priority and release rule ↗	The rule records why one duty controls, which authority makes the decision, how harm and reversibility were considered, and what happens to displaced obligations. “Prioritize X” is incomplete unless Y is explicitly deferred, transferred, waived by a competent source, compensated, or ended.
Redesign, recusal, delegation, and substitution plan ↗	The plan turns a decision into a viable structure. Delegation transfers authority, information, resources, competence requirements, capacity, acceptance, and accountability together. Recusal identifies the scope and duration of withdrawal, independent successor, information firewall, handoff, and continuity. Boundary redesign states what the role will no longer own.
Protected conflict disclosure and escalation path ↗	The path offers confidential intake, need-to-know handling, representation, interim protection, nonretaliation, independent routing, response time, and escalation to an authority capable of changing expectations. A complaint channel that forwards the disclosure to the source of retaliation without protection is not a safe path.
Role transition and residual-strain monitor ↗	The monitor observes whether the designed arrangement holds. It compares formal assignments with actual work, samples handoffs and exceptions, and looks for retaliation, moral distress, delay, quality loss, confidentiality leakage, successor overload, and hidden return. Findings trigger redesign rather than renewed blame.

Common Mechanisms

A role-expectation conflict matrix reveals incompatible pairs. Simultaneous feasibility tests compare capacity and timing under peaks. Duty-priority and harm comparison makes displaced obligations visible. Recusal, delegation, or separation gates test continuity and successor capacity. Protected conflict conferences revise expectations through real authority. Recurrence audits test whether hidden strain returns.

Each mechanism is partial. A matrix can document impossibility without changing it, and a meeting without authority can pressure the role-holder to accept the same conflict again.

Use mechanisms in a sequence appropriate to the conflict. A matrix and feasibility test can establish the collision. Source review and harm comparison can narrow legitimate options. A protected conference can negotiate waivable expectations. An independent gate can require recusal, delegation, or separation. A recurrence audit can reveal that the formal resolution never changed actual work.

Mechanisms must be privacy-bounded. Evidence may include client confidences, health information, family circumstances, protected reports, or identity commitments. Use functional descriptions and minimal disclosure where possible; separate the operational fact that a duty cannot be performed from details that are unnecessary to the decision. Restrict records, set retention, and disclose conflicts only to those able to act or provide required oversight.

Power affects mechanism validity. A conference is not genuinely participatory if a supervisor controls pay, scheduling, evaluation, or future opportunity and no nonretaliation control exists. A recusal decision is not independent if the replacement answers to the conflicted principal. Match procedural safeguards to stakes and power asymmetry.

• Duty-Priority and Harm Comparison
• Protected Role-Conflict Conference
• Recusal, Delegation, or Separation Gate
• Role-Conflict Recurrence Audit
• Role-Expectation Conflict Matrix
• Simultaneous Feasibility and Capacity Test

Parameter / Tuning Dimensions

Tune role granularity, time horizon, severity thresholds, authority for priority decisions, strength of nonwaivable-duty floors, disclosure confidentiality, recusal threshold, delegation requirements, transition duration, and recurrence-monitoring cadence.

Role and expectation granularity

Too coarse a role label hides incompatible functions; too fine a decomposition creates administrative noise. Split roles where authority, beneficiary, information boundary, ethical standard, or accountability differs. Specify expectations to the level needed for feasibility and priority without micromanaging legitimate professional judgment.

Conflict and escalation thresholds

Tune which tensions remain with ordinary judgment and which require protected review. Consider severity, frequency, irreversibility, safety, rights, confidentiality, affected-party dependence, and retaliation risk. A low-frequency conflict can merit immediate escalation if consequences are grave; a recurring minor collision may warrant systemic redesign because cumulative strain is high.

Priority and waiver authority

Define who can interpret, modify, waive, or transfer each duty. Authority should follow the source and subject matter, not merely organizational rank. Require independent adjudication where the decision maker benefits from one priority outcome or where professional, legal, or rights duties constrain managerial discretion.

Recusal, delegation, and separation depth

Tune the scope, duration, information firewall, successor independence, handoff, and review of structural remedies. Overbroad recusal can unnecessarily exclude expertise or relationships; narrow recusal can leave the decisive conflict intact. Delegation depth must match the transferred responsibility.

Protection and monitoring cadence

Set confidentiality, interim measures, response deadlines, nonretaliation checks, retention, appeal, and follow-up according to risk. Monitor early after transition, at known peak periods, and after leadership, policy, staffing, or workload changes. Avoid surveillance of the role-holder; measure the role system and consequences.

Invariants to Preserve

• Every material expectation has a source, beneficiary, authority, resource demand, and review path.
• Nonwaivable duties and affected-party harms precede priority selection.
• Conflict disclosure is protected from retaliation.
• Displaced duties are released, transferred, deferred, or compensated explicitly.
• Delegation includes authority, competence, information, capacity, acceptance, and accountability.
• Recusal preserves continuity and lawful confidentiality.
• Hidden work and residual strain remain monitored.

The role-holder retains standing and dignity. They must be able to describe incompatibility, challenge source legitimacy, decline an unsafe or unethical instruction, and contest a redesign that removes opportunity or identity without necessity. Participation does not give them unilateral authority over duties owed to others, but neither are they merely the object of assignment.

Privacy is preserved through purpose limitation, minimal disclosure, access control, and separation of sensitive facts from operational instructions. Informal care or identity roles should not become an invitation for organizational intrusion. The system needs enough evidence to govern the conflict, not a complete account of private life.

Affected parties and less powerful beneficiaries remain visible. A resolution that protects the role-holder by abandoning patients, students, clients, constituents, family members, or junior staff is incomplete. Continuity, remedy, and explicit transfer are part of reconciliation.

Target Outcomes

The pattern should reduce impossible assignments, hidden work, burnout, moral distress, delay, and quality loss while improving duty protection, priority clarity, recusal, delegation, continuity, and accountability.

Measure structural outcomes, not the disappearance of complaints. Useful indicators include incompatible assignment frequency, time to protected review, percentage resolved by source correction or redesign, displaced-duty disposition, handoff quality, confidentiality incidents, retaliation reports, hidden overtime, missed care or service, moral distress, successor overload, recurrence, and whether affected parties received remedy.

Silence after intervention can mean resolution or fear. Pair administrative metrics with confidential follow-up and evidence from actual work. A strong result makes ordinary priority judgments easier while making serious conflicts safer to surface.

Tradeoffs

Role integration conflicts with independence, continuity with recusal, flexibility with bounded responsibility, and resolution evidence with privacy. These tensions require case-specific structural decisions rather than universal separation or consolidation.

Integrated roles can provide context, trust, speed, and relational continuity, yet the same integration can enable self-review, confidentiality leakage, divided loyalty, or chronic overload. Separate only the functions necessary to protect integrity and feasibility, while designing interfaces that preserve legitimate knowledge and service continuity.

Flexible roles allow adaptation when conditions change, but vague flexibility can become unlimited obligation. Bound flexibility with capacity, authority, duration, review, and explicit release. Temporary exceptions need sunset or incorporation into staffing; otherwise exceptional work becomes an invisible permanent role.

Conflict visibility enables legitimate priority decisions but may expose identity, health, family, client, or protected-report information. Use the least revealing evidence capable of supporting the decision. Independent reviewers can sometimes evaluate sensitive facts and provide an operational conclusion without broad disclosure.

Fast recusal can protect integrity but disrupt care or service. Delay for handoff can preserve continuity but extend compromised judgment. Establish interim restrictions, qualified substitutes, emergency coverage, and a time-bounded transition rather than choosing between instant abandonment and indefinite conflict.

Failure Modes

Clarity without feasibility documents impossible work. Powerful principals crowd out less visible beneficiaries. Hollow delegation transfers blame rather than capability. Retaliation silences conflict. Recusal without continuity abandons service. Hidden recurrence returns released duties informally. Feasibility tests, duty floors, transfer gates, nonretaliation, substitute plans, and recurrence audits address these failures.

Ambiguity misclassified as conflict

Detect this when parties attach different meanings, scopes, or deadlines to the same expectation and compatibility returns after authoritative clarification. Clarify before structural separation, but do not let repeated “clarification” become a way to deny an established contradiction.

Conflict misclassified as overload

Adding hours or staff cannot reconcile duties that require both advocacy and impartial judgment, confidentiality and unauthorized disclosure, or incompatible loyalties. Detect when more capacity leaves the normative collision intact. Use source precedence, boundary redesign, independent review, recusal, or separation.

Power-weighted priority

The highest-status or most proximate principal may win even when its demand is discretionary and another party's right or safety is nonwaivable. Detect repeated sacrifice of invisible beneficiaries and decisions without reasons. Require affected-party mapping, subject-matter authority, recorded priority logic, and review.

Retaliation and privacy breach

Disclosure may trigger poor assignments, exclusion, evaluation harm, gossip, credential threats, or pressure to reveal more than necessary. Detect adverse changes after reporting and access beyond need-to-know. Provide interim protection, independent intake, representation, audit trails, remedial authority, and sanctions for retaliation.

Hollow remedy and failed recovery

A decision may order delegation without successor capacity, recusal without continuity, or boundary change without removing old metrics. Detect missed handoffs, repeated exceptions, successor overload, confidentiality gaps, and work returning informally. Reopen the transition, resource the substitute, repair affected-party harm, and correct the source policy.

Recurrence through system design

Conflict often returns because incentives, staffing, escalation, job architecture, or principal behavior remain unchanged. Aggregate recurring cases by source and conflict mode, then redesign upstream mandates, reporting lines, role combinations, staffing ratios, and policy language. Do not treat each recurrence as a unique personality problem.

Neighbor Distinctions

Decision Rights Clarification resolves who decides. Alignment Governance resolves disagreement among actors. Conflict-of-Interest Management protects judgment from divided interest. Decision Load Management reduces cognitive burden. Authority Rotation limits tenure. Role conflict uniquely reconciles incompatible expectations carried by one role-holder or position.

Responsibility assignment creates ownership and accountability for work. It is a component of role design, but assigning responsibility cannot resolve two incompatible obligations and may worsen conflict when authority or resources do not accompany it. This archetype decides which duty remains, which moves, and what conditions make the assignment viable.

Distributed Authority Checks and Balances designs institutions so multiple centers constrain one another. It intentionally separates powers at system level. Role reconciliation may use separation or independent review, but its trigger is incompatible expectations concentrated in an actor or position, including informal and capacity conflicts that are not constitutional checks.

Procedural Fairness governs how decisions are made through notice, voice, reasons, impartiality, and appeal. Those safeguards may be required when adjudicating a role conflict, especially under power asymmetry. The parent archetype additionally diagnoses role-source incompatibility, tests feasibility, and redesigns occupancy, boundaries, resources, or duties.

Generic conflict resolution mediates incompatible interests or perceptions among parties. Role conflict can exist without interpersonal disagreement and may not be negotiable when law, rights, safety, confidentiality, or professional duties set floors. Reconciliation therefore combines negotiation with source legitimacy, precedence, structural remedy, and explicit release.

Cross-Domain Examples

A clinician should not combine confidential treatment with punitive evaluation without separation. A manager responsible for delivery, employee advocacy, compliance, and budget reduction needs priority and redesign, not generic resilience training. A public official with a loyalty conflict may require disclosure, recusal, substitution, and continuity.

Healthcare

A clinician is asked to provide confidential treatment and certify facts for a punitive employment action. The map separates care, confidentiality, reporting, employer, and patient expectations; identifies nonwaivable professional duties; and tests whether limited consent resolves the collision. Where impartial punitive evaluation remains incompatible, an independent evaluator receives only authorized information, the treating relationship continues, and the transition is audited for privacy and care disruption.

Matrix organization

A security lead reports to a product executive on delivery and to a risk executive on release assurance. Both issue mandatory deadlines that cannot coexist. The system verifies authority scopes, quantifies feasibility, protects escalation, adjudicates the release gate, revises shared metrics, assigns capacity, and records which delivery commitment is released. Follow-up checks whether the product leader reintroduces the rejected demand informally.

Education

A teacher is expected to advocate for a student, grade impartially, maintain confidentiality, report specified risks, support family engagement, and meet class-wide workload targets. Conditional triggers and information boundaries are clarified; reporting duties are separated from discretionary disclosure; additional support and independent review handle high-stakes cases; and family communication does not expose protected student information.

Caregiving and employment

An employee with predictable elder-care duties is assigned an on-call role whose peak demands collide with nontransferable care windows. The organization does not demand private clinical detail. It tests schedules, backup, role rotation, compensation, and scope; negotiates a bounded arrangement; transfers specified on-call periods with authority and pay; and monitors team burden and retaliation.

Research and public service

A researcher is principal investigator, supervisor, data custodian, and adjudicator of a complaint involving their own program. The design protects disclosure, moves fact finding and adjudication to independent roles, preserves necessary data access controls, maintains project continuity, and prevents the investigator from evaluating complainants through another role.

Non-Examples

Clarifying one uncontested decision owner is not role-conflict reconciliation. Mediating separate teams is dispute resolution. Reducing a compatible task list is workload management. Asking someone to work harder leaves structural incompatibility intact.

Nor is every uncomfortable decision a role conflict. Ordinary professional judgment can require choosing among compatible priorities within delegated discretion. Personal dislike of a legitimate expectation is not structural incompatibility. The archetype applies when evidence shows simultaneous infeasibility, prohibited boundary crossing, compromised judgment, or unavoidable breach of another material duty.

A disclosure form without independent review and remedy is not reconciliation. Reassigning a person while retaining the same metrics and informal requests is not boundary change. Telling a caregiver to use leave without examining role design may simply privatize the conflict. Creating a committee to discuss the problem without authority to release expectations is procedural theater.

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (4)

• Allocation: Assign a limited supply across competing claimants under a feasibility constraint, independent of which criterion fills in the rule.
• Conflict of Interest: Competing incentives.
• Role: A bundle of expected behaviours attached to a social position.
• Role Conflict: Conflicting roles.

Also references 12 related abstractions

• Accountability: Responsibility for actions.
• Authority: The recognized, legitimate right to issue binding decisions within a defined scope, distinct from raw coercive force or mere persuasive influence.
• Consent: Voluntary agreement.
• Delegation of Authority: Assign responsibility.
• Legitimacy: Accepted authority.
• Normativity: What ought to be.
• Pareto Efficiency: Optimal allocation.
• Procedural Fairness (Due Process): Due process.
• Psychological Safety: Safe environment for risk-taking.
• Social Identity Theory: Identity via groups.

▸ Show 2 more

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Interrole Capacity and Time Conflict · temporal variant · recognized

Reconciles legitimate roles that require incompatible presence, timing, attention, emotional labor, recovery, or resource use under realistic peak conditions.

• Distinct from parent: The primary incompatibility is resource and temporal feasibility rather than divided judgment, confidentiality, or contradictory authority mandates.
• Use when: Multiple roles collide at specific deadlines, emergencies, care windows, or peak periods; Average workload appears feasible while simultaneity or recovery makes it impossible; Informal care, volunteer, identity, or continuity duties materially constrain scheduling; Sequencing, added capacity, substitution, scope change, or release may restore feasibility.
• Typical domains: caregiving, shift work, education, volunteer leadership, emergency response
• Common mechanisms: role expectation conflict matrix, simultaneous feasibility and capacity test, protected role conflict conference, role conflict recurrence audit

Divided Loyalty and Professional-Duty Conflict · governance variant · recognized

Reconciles loyalty, advocacy, confidentiality, impartiality, reporting, care, consent, fiduciary, and professional obligations owed to parties whose interests conflict.

• Distinct from parent: The conflict turns on normative and fiduciary integrity rather than only capacity; some compromises are prohibited and structural independence may be mandatory.
• Use when: One person is expected to advocate and independently judge the same matter; Confidentiality and a reporting or disclosure duty may collide; Professional or legal duties constrain what principals may negotiate or waive; Disclosure alone cannot preserve credible judgment or public trust.
• Typical domains: healthcare, law, research, public service, journalism, fiduciary governance
• Common mechanisms: duty priority and harm comparison, recusal delegation or separation gate, protected role conflict conference, role conflict recurrence audit

Intra-Role Multi-Principal Conflict · governance variant · recognized

Resolves incompatible expectations issued to one role by multiple authorized principals, mandates, beneficiaries, or governance channels.

• Distinct from parent: The conflict occurs inside one named role and concentrates on competing authority sources rather than the actor's separate professional, care, or identity roles.
• Use when: A matrixed or joint role has several principals with overlapping direction rights; Authority hierarchy, mandate scope, or conflict-reconciliation rules are incomplete; The role-holder is accountable for outcomes controlled by different principals; Released expectations repeatedly return through informal instructions or metrics.
• Typical domains: matrix organizations, public administration, joint ventures, platform operations, interagency programs
• Common mechanisms: role expectation conflict matrix, duty priority and harm comparison, protected role conflict conference, role conflict recurrence audit

Near names: Incompatible Role Expectations, Multi-Role Strain, Inter-Role Conflict, Intra-Role Conflict.