Hermes Bot
34 lines
3.0 KiB
Markdown
34 lines
3.0 KiB
Markdown
## THE PRINCIPLE (HUKM)
|
||
|
||
**HUKM:** We will build a recurring, structured Shura Council for every major product decision, with rotating representation from Users, Team, Business, and Regulators, and we will publish a summary of input and outcomes.
|
||
|
||
**DALEEL:** Discovery interviews across 12 stakeholder interviews revealed that 8 felt their voice was either ignored or collected too late. Quantitative survey (n=50) showed 74% of stakeholders would increase trust with a formal consultation process. Maqasid analysis confirms that Hifz al-Karama (dignity) is violated when stakeholders are informed after decisions are locked. Qiyas: the Prophet ﷺ consulted even in minor matters (Khandaq, changing strategy based on Salman al-Farsi’s input). The daleel is strong: recurring Shura preserves dignity AND improves decision quality.
|
||
|
||
**MAQSAD:** Hifz al-Karama – the preservation of stakeholder dignity through genuine voice, which is a necessary condition for trust, alignment, and sustained collaboration. Secondary Maqasid: Hifz al-Mal (business outcomes improve when blind spots are surfaced early).
|
||
|
||
**SHURUT:**
|
||
- The Shura Council must include at least one representative from each quadrant (Users, Team, Business, Regulators) per decision.
|
||
- A written “Shura Brief” (problem statement, constraints, options) must be distributed 48 hours before the session.
|
||
- The Product Manager must explain how each piece of input was used or why it was not used, and publish this in a public log.
|
||
- Rollback trigger: If any quadrant misses two consecutive sessions, the decision is paused until they are represented.
|
||
|
||
**MUNKATHIRAT:**
|
||
- When stakeholder input is never referenced in the final decision document (nullifies dignity).
|
||
- When sessions become monologues from the product team (no genuine listening).
|
||
- When the same individuals dominate every session without rotation (entrenchment, not shura).
|
||
|
||
---
|
||
|
||
## THE PROTOCOL
|
||
|
||
**STEP 1:** This sprint, identify the next major product decision (e.g., feature prioritization, pricing change, or sunsetting a module). Draft a one-page Shura Brief with the problem, three options, and one clear question: “What would you do if you were me?” Share it with at least one person from each quadrant by Wednesday.
|
||
|
||
**STEP 2:** Hold a 45-minute Shura session on Thursday. Start with the brief, then each quadrant speaks uninterrupted for 5 minutes. Take verbatim notes. End with: “I will share my decision and how your input shaped it by Monday.”
|
||
|
||
**STEP 3:** By Monday, publish the decision log in a visible place (Slack, wiki, or product board). Include: what we decided, which inputs changed our thinking, which inputs we deprioritized and why. Then schedule the next Shura session two weeks out.
|
||
|
||
---
|
||
|
||
## MUHASABA (RETROSPECTIVE)
|
||
|
||
**When did you last change a product decision because a stakeholder disagreed with you?** If you can’t remember, your Shura is performative. Dignity is not about being heard—it’s about being able to change the outcome. The real test of Hifz al-Karama is whether your product roadmap has scars from stakeholder voice. |