Building a Shariah-Compliant AI Product Playbook for a Malaysian Islamic Bank

The situation

An enterprise of this profile is a licensed Islamic bank operating in Malaysia under the Islamic Financial Services Act 2013, with a Shariah Committee that opines on every product structure and a Shariah Risk function that monitors operational compliance. The bank may be a stand-alone Islamic institution or the Islamic banking subsidiary of a universal banking group with conventional and Islamic operations side by side. The retail line covers personal financing, home financing, credit cards and digital channels. The SME line covers term financing, working capital and supply chain products built on Murabahah, Tawarruq, Musharakah and Ijarah structures.

The team that triggers the engagement is the product and digital function, working with the head of risk, the head of Shariah review and the head of compliance. The pressure is the same as the conventional banks, but with an extra constraint. AI must not only satisfy the Bank Negara Malaysia FEAT-equivalent expectations on fairness, ethics, accountability and transparency. It must also satisfy Shariah principles around uncertainty, speculation and the prohibition of riba. The Shariah Committee is therefore not an obstacle to be routed around. The Shariah Committee is the most important reviewer the AI feature will face.

Engagements of this archetype begin when the head of product and the head of risk recognise that the team cannot continue to invent the Shariah-AI conversation from scratch on each product. They want a playbook. The playbook has to be defensible to the Shariah Committee, the Shariah Risk function, Bank Negara Malaysia in supervisory dialogue, and the internal audit function. That is the brief.

What we observed

1. The Shariah review is being asked after the AI design is finished

The Shariah review team is consulted after the PRD. This produces a familiar pattern. The Shariah review rejects an element that the product team thought was settled. The product team rebuilds. The engineering team rebuilds. The release slips. Nobody is happy.

2. AI risk is being framed as a separate workstream

The technology risk function and the Shariah Risk function each have their own framing of the AI feature. The two framings are not yet reconciled. Each new product has to reconcile them from scratch.

3. The product team does not know how to write a Shariah-AI brief

The single highest leverage artefact is the brief that the product manager writes describing how an AI augmented workflow respects Shariah and AI risk principles in the same document. Most banks do not have that artefact yet.

4. The Shariah Committee is willing to engage earlier

The Shariah Committee is often more willing to engage earlier in the design process than the product team assumes. Reframing the cadence of engagement is itself a useful intervention.

The engagement approach

Engagements of this archetype run as an eight to twelve week capability build with a single deliverable. The Shariah-compliant AI product playbook the bank can use on every future AI feature.

Discovery, weeks one and two

The founder, Prashant Shinde, an HRD Corp Train-the-Trainer certified founder, runs a discovery with the head of product, head of risk, head of Shariah review, head of compliance and a delegate from the Shariah Committee secretariat. Output is a draft table of contents for the playbook, a sponsor map and a cadence with the Shariah Committee.

Foundation, weeks three and four

The cohort takes the AI for Islamic Finance Malaysia module and the Agile Product Ownership module. The AI-Native Agile Operating Model is taught as the underlying operating reference.

Playbook build, weeks five to nine

The team co-writes the playbook. Sections include the Shariah-AI brief format, the AI risk and Shariah risk reconciled review template, the human-in-the-loop convention for Islamic finance products, the documentation standard for the Shariah Committee, and the supervisory dialogue checklist for Bank Negara Malaysia. The founder reviews each section before it is finalised. The Shariah Committee secretariat reviews each section in parallel.

Certification and showcase, weeks ten to twelve

Senior participants complete ICP-APO. The cohort closes with a Shariah-AI showcase where two live product candidates are walked through the new playbook end to end, in front of the Shariah Committee. The Committee signs off on the playbook as the working standard.

What changed

1. Time from product idea to Shariah Committee review

The cycle from a product idea being articulated to a clean Shariah Committee review compresses, because the team now has a written format the Committee recognises.

2. Rework after Shariah review

The rework that used to follow Shariah review reduces. The product team and the Shariah review function are in the same conversation earlier.

3. Defensibility of the AI posture

The bank can show Bank Negara Malaysia, internal audit and the Shariah Committee a coherent written posture on AI. This is not a marketing claim. It is an operating asset.

4. Cross-functional respect

Product, risk, Shariah review and engineering all report that the conversation about new AI products is more productive. This is the qualitative outcome the head of product cares about most.

Lessons that transfer to other Malaysian Islamic banks and takaful operators

• Treat the Shariah Committee as a design partner. The relationship is most productive when the Committee sees the design early.
• Reconcile AI risk and Shariah risk in one template. Parallel templates produce parallel debates.
• Invest in the brief format before the tooling. The brief is the durable artefact.
• Document the supervisory dialogue checklist. Bank Negara Malaysia engagement is easier when the bank has a written reference.