Hermes Bot
8.8 KiB
SPRINT 5: SHURA — DECISION MAKING AT SCALE
MAQSAD: Hifz al-Nasl (Preservation of Community)
Consultation at Scale — Because a community that cannot decide together cannot survive together.
1. THE CHARTER (Mithaq)
We the people of this organization establish this covenant: that all decisions affecting the whole are made through Shura—genuine consultation rooted in trust, not performance. We distinguish consent from consensus: a decision is valid when no one present has a reasoned objection, not when everyone agrees. We reject performative consultation where leaders have already decided. The Prophet ﷺ consulted his companions on matters as small as battlefield tactics (Uhud, Khandaq) and as large as succession (Saqifah). He listened, he changed course, he bound himself to the outcome. We do the same. Authority to decide is a trust (amanah), not a privilege. Every decision carries the weight of community preservation—Hifz al-Nasl. We will not fracture what we are building by ignoring voices or forcing unanimity. Shura is the method; consent is the discipline; community is the purpose.
Our Mithaq: We consult before we command. We consent before we proceed. We inform before we implement.
2. SPRINT STRUCTURE (Hikma / Architecture)
ORG_DESIGNER:
Stop treating every decision like a referendum. You need a decision-making quadrant. Draw four boxes:
| INFORM | CONSULT |
|---|---|
| Decide → Notify | Gather input → Decide alone |
| CONSENT | CONSENSUS |
| Propose → No objection → Adopt | All agree unanimously or block |
Each domain in your organization gets a default quadrant. Operational decisions (e.g., sprint task assignments) → Consent of the role holding the domain. Tactical decisions affecting a circle (e.g., tooling budget) → Consent of that circle. Strategic decisions affecting the whole organization (e.g., pivot product) → Consent of the full governance circle. Existential decisions (e.g., dissolution, merger) → Consensus or supermajority with safeguards.
The mistake most orgs make: they default to Inform (top-down) or Consensus (paralysis). The sweet spot is Consent—fast enough to act, safe enough to protect.
KHALIFAH:
The Prophet ﷺ operated a multi-level shura system. Draw three circles:
-
Inner Circle (Ahl al-Hill wa al-Aqd – the people of binding and loosening): senior companions consulted on state matters. Their consent was binding for appointments of caliphs. Example: Abu Bakr's selection at Saqifah.
-
Outer Circle (general public): consulted on matters affecting everyone, but not binding. Example: Prophet consulting the army at Uhud about whether to fight inside or outside Medina.
-
Executive Circle (wulat – governors, judges): delegated authority to decide within their domain, but subject to review and removal if they violated shariah.
Modern mapping:
- Inform = announcement of a decree that cannot be changed (e.g., shariah ruling). Rare.
- Consult = istishara: leader gathers input, decides. Prophet did this at Badr for positioning the army.
- Consent = ijma' of qualified representatives: the inner circle's no-objection. Binding.
- Consensus = ijma' of all believers. Practically impossible except for foundational matters (e.g., Quranic text).
Your sprint structure: assign each decision type to one of these four modes. Document it. Test it. If you default to Inform for decisions that affect others, you are not practicing Shura—you are practicing tyranny, no matter how benevolent.
3. AUTHORITY MAP (Ikhtiyar / Delegation)
ORG_DESIGNER:
Authority in a Teal org is distributed by consent, not command. Every role has a domain: the exclusive right to make decisions in that area, unless someone raises a reasoned objection. This is not consensus—it's "I can act unless someone shows me this will harm the organization." The authority map for Shura looks like this:
- Who proposes? The person with the tension or the role responsible for the domain.
- Who consents? The circle members whose domains are affected. They can object only with a reasoned argument (not preference) showing harm to the purpose.
- Who informs? Everyone else affected gets notification after the decision.
Example: A product manager proposes a feature change. Domain: product roadmap. The consent group: engineering, design, customer success. If no one objects, she proceeds. If engineering objects (e.g., "this breaks our architecture"), the proposal is modified or tabled. If customer success objects (e.g., "this confuses users"), same process. No one votes. No one forces consensus. Objections are data, not obstruction.
This is radically different from command hierarchy: "I decide, you execute." And different from pure democracy: "Everyone votes, majority wins." Consent respects the expertise of the role holder while protecting the whole.
KHALIFAH:
The classical principle of ikhtiyar (delegation of authority) mirrors this. The khalifah does not decide everything. He delegates to governors, judges, and commanders—each with a defined domain. The condition: the delegate must act within shariah and consult when their decision affects others.
The Prophet ﷺ delegated authority to Mu'adh ibn Jabal as governor of Yemen. He gave him a domain: judge according to Quran, then Sunnah, then his own reasoning (ijtihad). Mu'adh was not required to consult the Prophet for every case. But he was required to consult local scholars and community leaders for complex matters.
The authority map for your organization:
- Domain holder decides within domain, subject to consent of those affected.
- Circle decides matters affecting the circle, subject to consent of all members.
- Organization-wide decisions require consent of the governance circle (the modern Ahl al-Hill wa al-Aqd).
No one has absolute authority. Authority is bounded by purpose (maqsad), shariah, and the community's welfare. If a leader violates these bounds, the community has the right to object—and if ignored, to remove.
The danger of performative Shura: when a leader consults but has already decided. The Prophet ﷺ rejected this. At Hudaybiyyah, he consulted, then accepted the treaty despite many companions' emotional objections. He had genuinely listened; he made the decision based on revelation and strategic insight. But he never pretended to consult when the decision was already made. Performative Shura destroys trust faster than no consultation at all.
Your authority map must make explicit: who decides, who consents, who informs. If you cannot write it down, you are not practicing Shura—you are practicing politics.
4. TREASURY (Baitul Mal / Trust)
ORG_DESIGNER:
Money decisions are the most sensitive. The Baitul Mal is not a private purse—it is a public trust. Every allocation must be transparent and consented by those who contribute or are affected. Use the Shura Quadrant for treasury:
- Operational expenses (e.g., software subscriptions, rent) → Consent of the finance role or circle. Inform the organization.
- Program budgets (e.g., marketing campaign, event) → Consent of the circle that owns the program. Consult the finance circle.
- Major capital (e.g., hiring, acquisition, large investment) → Consent of the full governance circle. Full transparency: all data open to anyone who asks.
The rule: no one can spend money that belongs to the community without the community's consent—either directly or through delegated representatives. This is not charity; it is fiduciary duty.
KHALIFAH:
Umar ibn al-Khattab established the diwan (registry of stipends) after consultation with the senior companions. He did not decide alone. He consulted on who should receive, how much, and in what order of priority. The Baitul Mal was managed by a trusted treasurer (like 'Abdullah ibn al-Arqam) and accounts were publicly reviewed.
Key principles:
- Transparency: Umar would announce the state of the treasury in the mosque. No secrets.
- Consultation on distribution: The spoils of war were distributed after shura. The Prophet consulted before dividing the war booty of Hunayn.
- No private use: The khalifah's personal expenses were separate. Abu Bakr took only what he needed from the treasury, and when he fell ill, he returned his stipend.
Apply these to your org: every treasury decision goes through the Shura Quadrant. Publish the budget. Publish actuals. Let anyone raise an objection. If you hide financial data, you are not practicing Shura—you are practicing embezzlement, even if unintentional.
This sprint: map your current treasury decisions to the quadrant. Find one decision that should move from Inform to Consent. Change it this week.
End of Part 1. Next: Part 2 — The Principle, Protocol, and Muhasaba.