Language and direction
Define who writes, translates, and approves Arabic; test direction changes, numerals, punctuation, inputs, icons, and mixed-script records on real devices.
Operating brief / not market-entry advice
Put the Jordan operating facts where the product team can use them.
This brief converts country context into design and acceptance questions. It does not claim that every Jordan user, business, network, or regulated situation behaves the same way.
Working checkpoints
Treat variation as a product requirement, not a footnote.
A useful brief marks what is verified, what belongs to a local owner, and what must be tested against the actual audience before launch.Contact and identity fields
Collect only necessary identifiers. Confirm +962 phone handling, names, addresses, and any national or provider identity fields with the operator.
Mobile and network behavior
Prioritize the core task, compress assets, preserve entered work, show progress, and provide a safe retry when a request or callback is interrupted.
Government and vendor context
Treat Sanad, payment rails, messaging, hosting, and other external services as maintained dependencies whose access and terms must be verified.
Route
Build a living operating record.
- 01
Date every source
Record the authority, page, review date, and exact decision it informed so stale guidance can be found later.
- 02
Separate facts from choices
A regulator fact, a client policy, a design choice, and an unresolved question must not be blended into one sentence.
- 03
Test with representative content
Use long and short names, mixed scripts when scoped, realistic amounts, validation errors, empty states, and support escalation.
- 04
Assign a review trigger
Recheck the brief when audience, provider, data, transaction, regulation, or release scope changes.
Jordan is the context, not a stereotype.