digital-mujtahid/chapters/Fatwa_03_Part2.md

THE FATWA (HUKM)

HUKM: We will institutionalise a mandatory Shura process for all product decisions above a defined threshold (impacting >10% of users or >$50k revenue), requiring documented consultation from all four quadrants (Users, Team, Business, Regulators) before any fatwa is issued, with a clear escalation mechanism for unresolved conflicts.

DALEEL: PRODUCT_LEAD: “Continuous discovery teaches us that decisions made in isolation fail to capture the full opportunity space. Our user interviews revealed three features that were deprioritised because the team assumed they were low-value, but when we finally asked, users rated them as critical. That’s a dignity failure — we assumed their voice without giving them a seat.” MUJTAHID: “Usul al-fiqh requires istiqsa’ (comprehensive investigation) before ruling. The Shura quadrant is a tool for istiqsa’ of stakeholder reality. Daleel from the Quran (Surah Al-Shura 42:38) commands consultation in affairs. The sunnah of the Prophet ﷺ in the Battle of Uhud shows that even when the leader held a strong opinion, he honoured the Shura outcome. Here, our quantitative data showed that 70% of product failures in the last quarter were attributable to a single quadrant being ignored — usually Regulators or Team. That is a pattern of injustice (zulm) that must be remedied.”

MAQSAD: Hifz al-Karama (Preservation of Dignity) — the primary maqsad. Every stakeholder is created with inherent worth; their perspective is a trust (amanah) that must be heard and weighed. Without structured Shura, we reduce people to data points. Secondary maqsad: Hifz al-Mal — avoiding rework that costs 3x initial development; Hifz al-Aql — incorporating diverse reasoning to prevent groupthink; Hifz al-Nasl — building a culture where future product teams inherit a tradition of consultation, not dictatorship.

SHURUT:

• Threshold clarity: The Shura process is mandatory for any decision on the product roadmap that affects a critical metric (e.g., North Star, OKR) or requires >2 sprints of engineering effort. Lower-impact decisions can use a lightweight version (15-min async poll).
• Quadrant weighting: Each quadrant’s voice is weighted by relevance to the decision, not by seniority. A junior engineer’s technical constraint may outweigh a VP’s preference. Weighting is documented before the session and shared openly.
• Time-bound: Shura sessions must conclude within 5 working days for standard decisions, 48 hours for time-sensitive ones. If no consensus, the facilitator (typically the PM) issues a fatwa with a documented rationale based on maslaha (public benefit) and istihsan (juristic preference), explicitly stating which quadrant’s input was overridden and why.
• Transparency: The fatwa must be published to all participants within 24 hours of the session, including a summary of how each quadrant’s input shaped the decision. If a quadrant’s input was set aside, the rationale must cite a specific qa’idah fiqhiyyah (e.g., “al-darar yuzal” — harm must be removed — if overriding a user request to prevent a broader harm).

MUNKATHIRAT:

• If any quadrant’s documented input is ignored without a written istihsan or maslaha justification in the fatwa, the decision is void and must be reconvened within one sprint.
• If the Shura process is bypassed for a decision that meets the threshold (e.g., due to “urgency” that turns out to be false), the fatwa is nullified, and the responsible PM must present a tawbah (corrective action) plan to the team.
• If new daleel emerges within two sprints that contradicts a key assumption used in the Shura, the fatwa is suspended and a mini-Shura (30-min session with the same quadrants) is called to reassess.

THE PROTOCOL

STEP 1: Map your NEXT product decision to the Shura Quadrant. Within 48 hours, open a simple document (Google Doc or Notion) with four sections: Users / Team / Business / Regulators. For each quadrant, list the specific person or data source you will consult. If you cannot name at least one voice per quadrant, that is a red flag — escalate to your product lead. Example: Decision to add a new payment feature — Users: interview 3 power users; Team: lead engineer and designer; Business: CFO and sales director; Regulators: compliance officer and Shariah advisor (if fintech). Deadline: end of third day.

STEP 2: Run a 60-minute Shura session using the structured agenda. Invite all identified stakeholders. Agenda: (a) Context setting — the problem and opportunity (5 min), (b) Each quadrant presents their input in turn, uninterrupted (4 min each = 16 min), (c) Facilitated discussion — highlight trade-offs, identify conflicting daleel (20 min), (d) Decision or escalation — if consensus, document fatwa; if not, assign a decision-maker to issue a fatwa with rationale within 24 hours (19 min). Use a timer. Record all input on a shared board.

STEP 3: Issue the fatwa and define Munkathirat. Within 24 hours of the session, publish the fatwa using the five-part format (Hukm, Daleel, Maqsad, Shurut, Munkathirat). Include a one-paragraph summary of how each quadrant’s input was considered. Then, add a calendar entry for one sprint later to review the Munkathirat triggers. Example trigger: “If user adoption of the new payment feature drops below 20% in two weeks, the decision is null and we