Hermes Bot
135 lines
11 KiB
Markdown
135 lines
11 KiB
Markdown
## SHURA / CONSENT
|
||
|
||
**ORG_DESIGNER:**
|
||
Consent is not consensus. Consensus demands everyone agrees. Consent asks: *“Is this proposal good enough for now, safe enough to try?”* One objection blocks a proposal in consent—but only if the objection is reasoned, not preference. In practice: circle meetings use a round-robin “consent round.” Each member states their tension, then a proposal is formed. Then a round of quick objections: “Any objection? If none, consent. If yes, we integrate the objection.” This keeps decision speed high and psychological safety intact.
|
||
|
||
**KHALIFAH:**
|
||
Classical *shura* was never a vote. The *khalifah* consulted experts (*ahl al-hall wa al-aqd*), listened, then decided. But the decision was binding only if it aligned with the *shari’ah* (purpose). The *shura* was consent-based: no one could override the purpose. Umar ibn al-Khattab consulted widely on the *diwan* (registry) before adopting it. Consent meant: no participant was silenced; no decision violated the *mithaq*. Our modern parallel: each role-holder gives consent to proposals that align with the organizational *maqsad*. If a proposal violates purpose, it is an objection—not a whim.
|
||
|
||
**Action for this Sprint:**
|
||
- Replace all majority-vote meetings with consent rounds.
|
||
- Train every circle: “Objection = reason based on purpose, not personal taste.”
|
||
- Use a simple tool (e.g., Loomio or physical cards) for asynchronous consent.
|
||
|
||
---
|
||
|
||
## STEWARDSHIP / AMANAH
|
||
|
||
**ORG_DESIGNER:**
|
||
Ownership is a liability, not a prize. Stewardship means: the role-holder is a temporary guardian of the domain. In Holacracy, each role has a *purpose*, *domains*, and *accountabilities*. The person filling the role has *authority* to act within those constraints—but they do not *own* the role. They steward it for the organization’s evolutionary purpose. This dissolves entitlement: no “my team,” no “my budget.” Everything is held in trust.
|
||
|
||
**KHALIFAH:**
|
||
*Al-mal amanah*—wealth is a trust. The *baitul mal* is not the ruler’s private treasury. Umar ibn al-Khattab walked the streets at night to check on a widow’s provision. He was the *khalifah*, but he saw himself as a *mustakhliif* (one entrusted). In our organization, every budget allocation, every strategic decision, every hire—all are *amanah*. The steward must be able to account for resources and decisions. The *hisbah* (accountability) ensures no one hoards power or wealth.
|
||
|
||
**Action for this Sprint:**
|
||
- Write a one-page “Stewardship Pledge” for every role-holder: “I hold this role as *amanah*; I will act within its domains and accountabilities.”
|
||
- Link each role’s budget to a measurable outcome (OKR).
|
||
- Create a public ledger (simple spreadsheet) showing who spent what and why.
|
||
|
||
---
|
||
|
||
## CONFLICT / SULH
|
||
|
||
**ORG_DESIGNER:**
|
||
Conflict is a signal of unprocessed tension. In Teal organizations, conflict is not suppressed or escalated to a boss. It is processed by the people involved using a structured process: the *Conflict Resolution Protocol*. Step 1: The person with the tension shares it directly with the other role-holder. Step 2: If unresolved, a facilitator mediates. Step 3: If still unresolved, the circle uses a consent-based ruling. No drama. No HR police.
|
||
|
||
**KHALIFAH:**
|
||
*Sulh* (reconciliation) is the preferred Islamic method. The Prophet ﷺ said: “Make peace between you, for enmity is a razor.” The *qadi* (judge) would first attempt *sulh* before ruling. The goal is not to assign blame but to restore relationships and enable cooperation. In our organization, we assign a *sulh* facilitator for every circle—someone trained in neutral facilitation. They do not judge; they guide the parties to a mutual agreement that honors the *mithaq*.
|
||
|
||
**Action for this Sprint:**
|
||
- Designate one person per circle as *sulh* facilitator (rotating monthly).
|
||
- Write a simple “Conflict Canvas”: What is the tension? What is the underlying need? What proposals resolve it?
|
||
- No conflict goes unresolved for more than one week.
|
||
|
||
---
|
||
|
||
## SUCCESSION / ISTIKHLAF
|
||
|
||
**ORG_DESIGNER:**
|
||
Succession is not an emergency plan—it is a continuous pipeline. Every role should have a *backup role-holder* who shadows, learns, and can step in. In Sociocracy, each circle elects a *delegate* and a *substitute* to the next circle. This creates natural succession. We also maintain *role documentation*: a living handbook that captures decisions, policies, and context.
|
||
|
||
**KHALIFAH:**
|
||
*Istikhlaf* means to appoint a successor with care. Abu Bakr appointed Umar after extensive *shura* and observation. Umar knew the weight: he said, “If I fail, may Allah have mercy on Abu Bakr who appointed me.” Succession is a trust, not a popularity contest. In our organization, every leader must identify and mentor at least one potential successor. The *mithaq* requires that no key role remains without a named backup for more than 30 days.
|
||
|
||
**Action for this Sprint:**
|
||
- For every role with budget authority or client responsibility, identify a backup role-holder.
|
||
- Create a “Succession Record” (one page per role): key decisions, current tensions, pending proposals.
|
||
- Schedule a monthly 15-minute handover practice: backup runs the role for one day.
|
||
|
||
---
|
||
|
||
## HISBAH / ACCOUNTABILITY
|
||
|
||
**ORG_DESIGNER:**
|
||
Accountability is not surveillance. It is *observability*. In modern orgs, we use transparent metrics, open dashboards, and regular retrospectives. The *hisbah* is a built-in feedback loop: each circle reviews its own metrics and tensions weekly. No external police needed. The system is self-correcting.
|
||
|
||
**KHALIFAH:**
|
||
*Hisbah* was the institution of public accountability—not spying, but guidance. The *muhtasib* (inspector) would check markets for fraud, but also advise and remind. The goal was *amr bil ma’ruf wa nahi an al-munkar* (enjoining good and forbidding evil). In our organization, every circle elects a *muhtasib* (rotating quarterly) whose role is to check: Are we living our *mithaq*? Are we spending in line with purpose? No punishment—only a gentle nudge back to the covenant.
|
||
|
||
**Action for this Sprint:**
|
||
- Appoint a *muhtasib* for each circle (quarterly rotation).
|
||
- Publish a “Health Dashboard” with 3–5 key indicators (e.g., consent decision backlog, budget variance, role fulfillment).
|
||
- The *muhtasib* holds a 15-minute weekly “Check-in” with the circle: “What is out of alignment with our *mithaq*?”
|
||
|
||
---
|
||
|
||
## LEGACY / WAQF
|
||
|
||
**ORG_DESIGNER:**
|
||
Exit is not the goal. Most startups build for acquisition. Teal organizations build for *perpetuity*. Legacy means the organization outlives its founders. We design *waqf-like* structures: profit is reinvested, ownership is distributed or held in a foundation, and intellectual property is open-sourced when possible.
|
||
|
||
**KHALIFAH:**
|
||
*Waqf* is the ultimate Islamic legacy. The Prophet ﷺ said: “When a person dies, their deeds cease except three: ongoing charity, beneficial knowledge, or a righteous child who prays for them.” *Waqf* endows property for perpetual benefit—no one can sell it, inherit it, or divert it. In our organization, we create a *waqf* for our core asset (e.g., code, content, methodology). A trust board holds it for the *ummah*. Founders can still earn, but they cannot liquidate the purpose.
|
||
|
||
**Action for this Sprint:**
|
||
- Identify one core asset (e.g., your playbook, software, curriculum) that could be “endowed.”
|
||
- Draft a simple *waqf* deed: “This asset is held in trust for the benefit of the Muslim community, never to be sold.”
|
||
- Form a *waqf* board of three trusted advisors (outside the org) to oversee the endowment.
|
||
|
||
---
|
||
|
||
## THE PRINCIPLE (HUKM)
|
||
|
||
**HUKM:** We establish a constitutional covenant (*mithaq*) that defines our organizational purpose, principles, guardrails, and amendment process, and all decisions and actions must be consistent with this covenant.
|
||
|
||
**DALEEL:** The classical *khilafah* was founded on a *mithaq* (pact) between the ruler and the ruled—the *Bay’at*. Abu Bakr’s inaugural speech was a constitutional moment: “Obey me as long as I obey Allah and His Messenger; if I disobey, you owe me no obedience.” Modern Teal organizations use a similar constitution (e.g., Holacracy’s Constitution) to distribute authority and protect purpose. The *shari’ah* itself is a divine covenant; our organizational covenants mirror that trust.
|
||
|
||
**MAQSAD:** Hifz al-Din (Preservation of Purpose). The *mithaq* ensures the organization’s *din* (way/ purpose) is not hijacked by individuals, short-term profit, or external pressure. It also serves Hifz al-Mal (Preservation of Wealth) by preventing misallocation, and Hifz al-Aql (Preservation of Intellect) by embedding clear decision-making rules.
|
||
|
||
**SHURUT:**
|
||
- The *mithaq* must be written, reviewed, and consented to by every member.
|
||
- Any amendment requires a super-majority consent (two-thirds or unanimous) and a one-week cooling period.
|
||
- The *mithaq* must explicitly state the organization’s *maqsad* (purpose) as non-negotiable.
|
||
- A *majlis al-shura* (advisory council) of at least three people must be established to interpret the *mithaq* in case of ambiguity.
|
||
|
||
**MUNKATHIRAT:**
|
||
- If the *mithaq* is violated by a founder or leader and no corrective action is taken within 30 days, the covenant is invalidated and a new one must be drafted.
|
||
- If the purpose is altered without proper amendment process, the organization loses its *teal* status and reverts to conventional hierarchy.
|
||
- If any single person holds veto power over the *mithaq* (i.e., can block any amendment unilaterally), the covenant is null.
|
||
|
||
---
|
||
|
||
## THE PROTOCOL
|
||
|
||
**STEP 1: Draft the Mithaq (This Sprint — Week 1–2)**
|
||
Gather all current members for a 2-hour workshop. Use the “Constitution Quadrant” framework:
|
||
- **Purpose:** Why do we exist? (Write one sentence.)
|
||
- **Principles:** 3–5 non-negotiable values (e.g., *amanah*, *shura*, *tazkiyah*).
|
||
- **Guardrails:** What is forbidden? (e.g., debt, interest, secrecy, unilateral power).
|
||
- **Amendment Process:** How will we change this? (e.g., 80% consent + 7-day notice).
|
||
|
||
**STEP 2: Consent Round & Signing (Week 3)**
|
||
Present the draft in a circle meeting. Use a consent round: “Any objections?” Integrate all reasoned objections. Once consent is reached, each member signs (physically or digitally) the *mithaq*. Post it publicly on the org’s wiki or wall.
|
||
|
||
**STEP 3: Embed & Test (Week 4)**
|
||
Create a “Mithaq Check” ritual: every Monday morning, the first 5 minutes of stand-up is reading one line of the *mithaq* aloud. Every decision with a budget > X (set a threshold) must cite the relevant principle. After 30 days, hold a retrospective: “Did the *mithaq* help us? What needs amendment?”
|
||
|
||
---
|
||
|
||
## MUHASABA (RETROSPECTIVE)
|
||
|
||
**Where did we shortcut the covenant because it was inconvenient?**
|
||
|
||
One piercing question: *When did we override our own *mithaq* to get a deal done faster—and how did we justify it to ourselves?*
|
||
Reflect without shame. Write it down. Then ask: *What structural change (not just a promise) would prevent that shortcut from recurring?*
|
||
If no one can remember a single violation, you haven’t tested the covenant yet. Next sprint, invite a real pressure test. |