Hermes Bot
10 KiB
SPRINT 7: CONFLICT — SULH AS ORGANIZATIONAL RETROSPECTIVE
Maqsad: Hifz al-Nafs (Preservation of Wellbeing) → Conflict as Growth
1. THE CHARTER
We the people of this organization covenant that conflict is not a breakdown of order but a signal of growth waiting to happen. We reject the silent wound—the grudge buried in a meeting, the resentment that becomes policy by neglect. We commit to Sulh (reconciliation) over mere compromise. Compromise leaves both parties smaller; Sulh restores fitrah—the original balance where each role, each soul, returns to its amanah undiminished.
The Prophet ﷺ said, “Sulh is permissible among the Muslims, except a sulh that makes lawful what is unlawful or makes unlawful what is lawful” (Abu Dawud). He resolved the Black Stone dispute by inviting each tribe to hold the cloth—not by splitting the stone. He did not avoid the tension; he elevated it into shared honor.
Our retrospective (Muhasaba) is the mirror of Sulh. We do not blame; we uncover the tension that was trying to speak. Every objecting voice is a nasihah (sincere advice) wrapped in friction. We protect Hifz al-Nafs—the wellbeing of every member—by making conflict safe, structured, and sacred. We do not fear the fire; we build a forge.
2. SPRINT STRUCTURE
ORG_DESIGNER:
Modern teams treat conflict as a personal failure or a distraction. That’s a waste. In Teal and Sociocracy 3.0, conflict is a governance tension—a gap between current reality and the organization’s purpose. The structure to harvest it is the Conflict Quadrant:
ACCOMMODATE COLLABORATE
(Yield) (Sulh)
| |
LOW ASSERTION HIGH ASSERTION
HIGH COOPERATION HIGH COOPERATION
| |
-----------+--------------------+-----------
| |
AVOID COMPETE
(Flee) (Fight)
LOW ASSERTION HIGH ASSERTION
LOW COOPERATION LOW COOPERATION
Most teams live in Avoid (silence, email chains) or Compete (politics, power struggles). We need a Sulh Sprint—a structured, time-boxed process that moves from any quadrant to Collaborate. The sprint is 2 weeks. First week: raise tensions as objections (not complaints). Second week: facilitated Shura session where each objection is processed with consent, not majority vote. Output: a Sulh Agreement (a written amendment to a circle’s domain or role). This is not therapy; it is governance.
KHALIFAH:
The Prophet ﷺ institutionalized conflict resolution at multiple levels. In Madinah, every tribe had its own hakam (arbiter), but the final authority was the Shura of the Sahabah. The principle: al-Sulh khayr (reconciliation is better)—not because conflict is bad, but because fitnah (division) destroys ummah. The classical Hisbah system had muhtasib who mediated marketplace disputes—not with punishment first, but with nasihah and sulh.
Map this to your org:
- Circle-level conflict → handled by the circle’s lead link (like a qadi of that domain)
- Cross-circle conflict → escalated to a Sulh Committee (two representatives from each circle + one neutral hakam appointed by the Shura council)
- Constitutional conflict → goes to the Mithaq review—does the tension reveal a flaw in the charter? That’s Muhasaba.
The sprint structure mirrors the Sulh of the Prophet ﷺ in the Treaty of Hudaybiyyah:
- Identify the tension (the violated amanah or domain boundary).
- Name the haqq (right) that was harmed.
- Propose a restoration—not a compromise that dilutes purpose, but a sulh that returns each party to their fitrah.
Visual for this sprint:
Draw a circle. Inside, a smaller circle labeled Circle Sulh. From that circle, draw three arrows:
- Arrow 1: Tension → Objection (formally logged in a Sulh Register)
- Arrow 2: Objection → Shura Session (consent decision, not vote)
- Arrow 3: Shura → Domain Amendment (updated in the Governance Record)
Sprint length: 2 weeks. No conflict is “too small.” The smallest tension is the dharrat (atom) of a larger pattern.
3. AUTHORITY MAP
ORG_DESIGNER:
Authority in conflict resolution must be distributed, not hoarded. In Holacracy, any role can raise an objection to a proposal. The Facilitator holds process authority—not content authority. The Lead Link holds domain authority—but cannot override a consent objection. The Secretary holds record authority—the Sulh Agreement must be documented.
The problem: most orgs give the CEO or manager the final say. That’s command conflict resolution—fast, but brittle. The ikhtiyar (delegated authority) must be clear:
- Who can raise a tension? Anyone. No permission needed.
- Who can facilitate a Sulh session? A trained Hakam (neutral facilitator) elected by the circle. Not the manager.
- Who can veto a Sulh Agreement? No one. The circle gives consent. If consent cannot be reached, the tension stays open; the Hakam calls a Shura of the next higher circle.
This is consent-based authority—not unanimous love, but no reasoned objection. If one person says, “This agreement harms our ability to serve the purpose,” the facilitator does not override; the group integrates that objection into a new proposal.
KHALIFAH:
Classical Khilafah never gave the Khalifah unilateral power over disputes. The Qadi (judge) was independent; the Khalifah could not overrule a Qadi’s ruling on a private dispute. The Shura council acted as a check. The Hisbah had its own ikhtiyar—the muhtasib could confiscate fraudulent goods without needing the ruler’s approval.
Map this to your org’s authority map:
- Role of Hakam (Facilitator) → elected by the circle for a 3-month term. Cannot be the Lead Link. Must be trained in Sulh principles (listen, name the haqq, propose restoration).
- Role of Shahid (Witness) → a recorder who documents the Sulh Agreement and ensures it aligns with the Mithaq (charter).
- Role of Mujbir (Enforcer) → only for agreements that require action. The Mujbir is the Lead Link of the circle where the agreement lands—but they cannot amend the agreement; they execute it.
The key: Authority to resolve conflict comes from amanah, not rank. The Hakam has authority because the circle consented to their facilitation. The Shahid has authority because the Mithaq says every agreement must be recorded. The Mujbir has authority because the Sulh gave them a clear domain.
Visual authority map:
Draw three concentric circles:
- Outer circle: Mithaq (Charter) — holds the principles that no Sulh can violate.
- Middle circle: Shura (Circle Governance) — holds the consent process.
- Inner circle: Sulh Agreement — holds the specific restoration.
Arrows:
- From Hakam → Shura (facilitation authority)
- From Shahid → Mithaq (alignment authority)
- From Mujbir → Sulh Agreement (execution authority)
No single person holds all arrows. Authority is distributed amanah.
4. TREASURY / BAYTUL MAL
ORG_DESIGNER:
Conflict has a cost. It costs time, energy, and sometimes money. But unresolved conflict costs more—it leaks talent, erodes trust, and creates shadow power (backchannel decisions). The treasury must allocate a Sulh Budget: 5% of each circle’s operational budget reserved for conflict resolution. This covers:
- Facilitator time (if external).
- Training in Sulh facilitation (mandatory for every Hakam).
- Muhasaba tools (digital platforms for logging tensions, recording agreements).
- Compensation for time spent in Sulh sessions (treat it as sacred as any product sprint).
No one should fear that raising a conflict will “waste money.” The Baitul Mal exists to serve the Maqasid—and Hifz al-Nafs (wellbeing) is a primary Maqsad. If a conflict is ignored, the Baitul Mal will later pay in turnover, lawfare, or silent disengagement.
Transparency rule: All Sulh Agreements are recorded in a public Sulh Register (accessible to all members, not the public). The register shows:
- Date of tension
- Circle
- Summary of objection
- Sulh Agreement (redacted for privacy if needed)
- Cost (time spent, facilitator fees)
This prevents Baitul Mal from being used to buy silence. If a circle spends its Sulh Budget without producing a recorded agreement, the Hisbah reviews.
KHALIFAH:
The Prophet ﷺ said, “The wealth of a Muslim is not lawful unless given willingly” (Ahmad). The Baitul Mal in early Khilafah had a specific allocation for Sulh: the Qadi’s salary, the Muhtasib’s expenses, and the Sulh fund for compensating harm (e.g., if a dispute required returning property or paying diya). This was not discretionary; it was a line item in the public budget.
Your org’s Baitul Mal must have a Sulh Fund—separate from operational budget. Any member can request a withdrawal from the Sulh Fund for:
- Mediation services (internal or external)
- Research to understand the tension (e.g., analyzing data that reveals the root cause)
- Muhasaba retreats (if the conflict is systemic, not interpersonal)
The Khalifah (CEO / Lead Link) cannot block a Sulh Fund withdrawal that the Shura council has approved. The treasurer reports the Sulh Fund usage in every Muhasaba (retrospective). If the fund is unused, it is not a sign of peace—it is a sign of avoidance. Sulh is an investment, not an expense.
Visual for Treasury:
Draw a jar labeled Sulh Fund with an arrow from each circle’s budget. Inside the jar, three compartments:
- Hakam fees
- Muhasaba retreats
- Compensation for harmed parties (if applicable)
Below the jar: “We spend on Sulh because Hifz al-Nafs is priceless.”
End of Part 1. Continue to Principle, Protocol, and Muhasaba in Part 2.