4 min read - AI Made in Morocco: How SMEs Can Select Their First High-Value Use Case

In March 2026, the Morocco RamadanIA programme supplied the dated context for assessing business friction. The announcement sets the external boundary. Your own evidence must establish whether the idea fits your organisation.

Decide how to handle business friction

Proceed only after verifying Business friction, Data feasibility, Review effort, Local operating fit before committing budget.

Treat this as a portfolio decision. Rank the options, name the owner, set an evidence threshold and record the condition that would stop the work. Apply that rule to business friction and data feasibility.

Start with business friction. That check determines which evidence will be useful for the other dimensions.

What the Morocco RamadanIA programme source contributes to business friction

Morocco RamadanIA programme was reviewed on 27 August 2026 for its treatment of business friction. Check the current source before a procurement, architecture or compliance decision. An announcement describes the offer or initiative. Your internal evidence determines whether it meets the need. This operational framework is not legal advice.

Examine business friction, data feasibility, review effort, local operating fit

1. Business friction

For business friction, record the current state, the owner and the decision that depends on this dimension. Keep the inventory limited to verifiable facts.

2. Data feasibility

For data feasibility, map the dependencies, data and affected people. Test any assumption that could invalidate the initiative before investing further.

3. Review effort

For review effort, choose observable evidence and a minimum threshold. The test should tell you whether to proceed; an impressive demonstration is not enough.

4. Local operating fit

For local operating fit, set the boundary, escalation path and exit condition. The team must be able to stop, replace or return the solution to manual operation.

Decision matrix for business friction

Leadership, business, technology and security teams should assess the same evidence on business friction and data feasibility before deciding.

Test business friction in five steps

1. Scope business friction. Write down the question, owner and date by which an answer is required.
2. Establish the data feasibility baseline. Measure the current process, including quality, incidents and review effort.
3. Test review effort. Limit data, users, permissions and duration so the change remains reversible.
4. Review local operating fit. Examine errors, manual rework, escalations and effects on affected people.
5. Answer the original question. Record proceed, change or stop, together with the evidence supporting that choice.

Evidence to retain for data feasibility

The evidence pack keeps the findings on business friction with the other material needed for the decision:

• the decision, its owner and consulted stakeholders;
• the inventory associated with business friction;
• the baseline and test results for data feasibility;
• the access, risks and approvals connected to review effort;
• the rollout, monitoring and exit plan for local operating fit.

If this initiative stops, retain its findings on business friction and local operating fit so the next review does not repeat the same assumptions.

Mistakes that weaken review effort

Avoid:

• starting with the most visible use case instead of the most valuable constraint
• approving a pilot without a baseline or a decision date
• treating adoption volume as proof of business value

A 30-day plan for local operating fit

• Days 1 to 5. Name the owner of business friction, define the boundary and collect available sources.
• Days 6 to 12. Map data feasibility, including its data, access, dependencies and failure scenarios.
• Days 13 to 20. Test review effort against a baseline and pre-agreed stop criteria.
• Days 21 to 26. Ask the responsible functions to review the findings on local operating fit.
• Days 27 to 30. Compare the four findings with the decision above and define the next required proof.

Record the decision on business friction

Keep a short record with the owner, evidence reviewed and decision. Add the condition that would trigger another review of business friction or local operating fit.