Files
2026-08-16 06:08:04 +08:00

8.2 KiB
Raw Permalink Blame History

Principle #8: Growth Metrics — Barakah vs Vanity Metrics

Maqsad: Hifz al-Nasl (Preservation of Lineage/Continuity) → Sustainable Growth


1. THE SCENARIO

Youre the Product Lead at a fast-growing fintech startup. Your CEO bursts into your office: “Why are we spending two sprints on a retention feature when we could be acquiring new users through paid ads? We need to hit 500K signups by Q4.” You open your notebook. The Mujtahid in you asks: What is the hukm of this growth? What is the maqsad? Is this Barakah or vanity? The Product Lead in you pulls out the AARRR funnel and an Opportunity Solution Tree. You know the CEO is chasing a vanity metric. But you need evidence—and a ruling—to redirect the ship. This is Principle #8.


2. DISCOVERY (ISTIQSA')

PRODUCT_LEAD:
Lets run Continuous Discovery. First, map the Opportunity Solution Tree. The desired outcome is sustainable growth—users who stay, invite their families, and build long-term financial health. The opportunity is: Users who reach their first savings goal have 80% retention at 6 months. The problem were solving is not “more signups” but “more users who complete the activation loop.”

We use Jobs-to-be-Done: What job is the user hiring our product to do? For our fintech app, the core job is “Help me save consistently for my familys future without stress.” Thats Hifz al-Nasl—preserving continuity of lineage by protecting wealth and family stability. Growth that undermines that job (e.g., incentivizing debt or gambling-like features) is not Barakah.

So our discovery question: What does growth with Barakah look like? We interview 10 long-term users. They say: “I only recommend this app to my siblings because it actually helped me stop late fees.” “I dont care about the referral bonus—I just want my brother to get out of debt too.” These users are our North Star. Their behavior shows that Barakah growth is organic, trust-based, and aligned with family well-being.

MUJTAHID:
Istiqsa (exhaustive inquiry) begins with defining the problem space through the lens of Maqasid al-Shariah. The maqsad here is Hifz al-Nasl—preserving lineage and continuity. For a fintech product, this means the growth strategy must not lead to harm that breaks families (debt cycles, gambling, exploitation of the vulnerable).

Vanity metrics—total signups, raw MAU, paid acquisition numbers—are gharar (uncertainty) because they dont reflect genuine benefit. They are like counting seeds that never sprout. Barakah growth is increase that carries blessings—it multiplies benefit without corrupting the intention.

We must map the problem space using the five Maqasid as filters:

  • Hifz al-Din Does this metric encourage ethical behavior?
  • Hifz al-Nafs Does it protect users from financial stress?
  • Hifz al-Aql Does it promote sound decision-making?
  • Hifz al-Mal Does it preserve wealth (not waste it on acquisition)?
  • Hifz al-Nasl Does it sustain family continuity?

Acquisition-only metrics fail Hifz al-Mal (waste) and Hifz al-Nasl (no continuity). Retention and referral metrics that come from genuine value—those have Barakah. Our istiqsa reveals that the real opportunity is not “more users” but “more users who stay and bring their family.” That is growth with Barakah.


3. EVIDENCE (ISTIDLAL)

PRODUCT_LEAD:
Lets gather daleel—evidence. Quantitative: We pull cohort analysis. Users acquired through paid ads have a 30% 90-day retention. Users acquired through organic referrals have 70%. The median lifetime value (LTV) of a referred user is 3x higher. The paid users churn faster and cost more to acquire. Thats quantitative daleel that paid acquisition is less Barakah for this product.

Qualitative: User interviews reveal a pattern. “I downloaded because of a discount code, but I never used it after the first month.” “My sister told me this app helped her save for hajj—so I trust it.” The qualitative daleel confirms: Barakah growth is rooted in trust and real outcomes, not incentives.

We also look at negative evidence: churn spikes after promotional campaigns. Users who joined via paid ads are 50% more likely to delete the app within 7 days. This is sad al-dharai—blocking the means to harm. The harm here is wasted resources (israf) and misleading metrics that cause product teams to optimize for the wrong thing.

MUJTAHID:
Now we apply the daleel hierarchy from Usul al-Fiqh.

  • Qati al-Thubut (certain in transmission) We dont have revelation, but we have reliable analytics data from our own backend. That is strong evidence, albeit zanni (speculative) in interpretation.
  • Qati al-Dalala (certain in meaning) The meaning is clear: referred users stay longer. Thats a qiyas (analogy): if organic referral leads to higher retention, then investing in referral features is analogous to preserving wealth (Hifz al-Mal) and lineage (Hifz al-Nasl).
  • Istishab (presumption of continuity) We presume that the current pattern (paid users churn) will continue unless proven otherwise. So we should not scale paid acquisition without stronger evidence.
  • Maslaha (public benefit) Sustainable growth benefits the community: users save money, families are less stressed, the company survives long-term. Vanity growth harms the company (burnout, wasted budget) and users (poor experience).

What is “churn” in spiritual terms? Churn is inqita—a severing of the relationship. The user leaves the blessing. A metric that measures “users who leave” is good, but more important is “users who stay and refer.” That is iltizam—commitment. The Barakah filter asks: Does this metric measure genuine commitment or fleeting attention?

Evidence conclusion: The daleel stack points away from paid acquisition as a primary growth lever. The strongest evidence (quant + qual + qiyas) supports investing in referral programs, activation improvements, and retention loops. Those metrics survive the Barakah filter.


4. SHURA

PRODUCT_LEAD:
Time for Shura—structured consultation. I schedule a 90-minute cross-functional sync. Attendees: CEO, VP Marketing, Head of Engineering, Customer Support Lead, and two user researchers. I frame the decision: We need to choose between doubling down on paid acquisition or building a referral + retention engine.

First, I present the evidence from Discovery and Istidlal: the cohort data, user interview clips, and the Barakah filter. Then I open the floor.

  • CEO argues: “We need scale to raise Series B. Paid ads are proven. Referrals take time.”
  • VP Marketing pushes back: “Our paid CAC has risen 40% this quarter. The quality is dropping.”
  • Customer Support Lead shares: “Most complaints come from paid users who dont understand the product.”
  • User researcher shows a clip: “I only used it because of the $5 bonus—now I forgot I even have the app.”

I weight the inputs based on proximity to evidence and expertise. The CEOs opinion is important but based on a fear of missing growth targets. The Support Lead and researcher have direct daleel from users—their voices carry more weight. I record all opinions, including dissent.

MUJTAHID:
Shura in Usul is not a democratic vote. It is a structured process to surface the strongest daleel and reach a ruling that serves the maqsad. The methodology:

  1. Identify the stakeholders Everyone present has a right to speak, but we weight their wilaya (authority) based on knowledge and proximity to the truth. The user researcher and support lead are the shuhud (witnesses) to reality.
  2. Record each opinion with its daleel CEOs daleel: “We need speed to survive.” That is a maqsad of Hifz al-Mal (company survival), but it conflicts with Hifz al-Nasl (sustainable growth). We note the tension.
  3. Seek consensus (ijma) We dont have full consensus. The CEO dissents. We document that dissent as mukhalafa (opposition) but proceed based on the preponderance of evidence.
  4. Issue the ruling The Shura concludes