Context map
Country relevance starts with the person holding the device.
A useful Ghana brief does not paste national facts into a generic proposal. It asks which conditions change the user journey, the operating relay, or the evidence required for release.
| Field question | What the team must learn | What changes in the build |
|---|---|---|
| Who arrives? | Role, device, language, accessibility needs, support access, and the task that brought the person here. | Content order, interaction weight, help route, and acceptance devices. |
| What can interrupt them? | Connection changes, expired sessions, missing documents, provider delays, shared devices, or staff handoffs. | Save states, retries, clear errors, re-entry, and alternate support. |
| What information moves? | Fields, documents, analytics, staff access, vendors, storage, exports, and deletion ownership. | Data minimisation, access rules, notices, logs, and response procedures. |
| How does value change hands? | Approved payment route, currency display, provider account, confirmation, refund, fulfilment, and reconciliation. | Transaction states, evidence, customer messages, and finance handoff. |
| Who can say “ready”? | Business, language, privacy, payment, technical, and release owners. | Review packet, test plan, approvals, rollback, and monitoring. |
Local knowledge boundary
The client supplies the operating reality. Sources help challenge it.
- Observe: document the current journey before prescribing software.
- Verify: use the official body closest to each question.
- Assign: name who is qualified to interpret the result.
- Translate: turn accepted decisions into requirements and tests.
- Recheck: revisit provider and authority material before release.