iran-product-benchmark
Iran Product Benchmark
Compare observable behavior for one task. Apply the evidence policy; a convenience sample is not an industry ranking.
For Iranian projects, read the Iranian task comparison checks section in the task reference when money, payments, phone/SMS, fulfillment or local dates affect the request. Apply relevant checks only; keep other Persian regions and the user’s scope intact.
For articles or content interfaces, read the editorial section of the task reference when the request concerns local cultural fit, article comparison or reading/card usability. Apply only the relevant checks.
Workflow
- Bound the comparison. Define task, audience, device, locale, products and why each belongs. Keep conditions comparable; identify differences preventing a fair comparison. Finish with task and sampling rationale.
- Inspect the flow. Follow the task where authorized access permits; use supplied artifacts for other states. Record URL/artifact ID, date, viewport/device, version when known, and observed steps. A screenshot supports only its visible state. Mark hidden/login-only steps unobserved; do not complete purchases or contact sellers merely to benchmark.
- Record evidence. Use the benchmark method for dimensions, records and uncertainty. Separate visible evidence from interpretation. If ratings help the decision, define a rubric and show missing data separately rather than scoring unknowns as failures.
- Compare trade-offs. Select dimensions relevant to the task: discovery, decision support, price/currency clarity, fulfillment information, recovery, accessibility or copy. For transaction flows use the benchmark method’s local service/payment states, matching city and order conditions. Finish with a dated table, evidence for each finding and comparability limitations.
- Transfer findings. Recommend patterns for the target product with supporting observations, audience fit and validation needed. Adapt interaction ideas while preserving the target brand and constraints. Finish with actionable design implications.
Deliverable and completion
Return scope/conditions, comparison table, observation references, patterns/trade-offs, unobserved steps and next design checks. All scored or categorical judgments must trace to observations and a stated criterion. Distinguish static appearance from tested interaction and reported features from observed behavior.