Context matrix
Break “India” into product decisions small enough to verify.
Country scope should narrow uncertainty, not decorate a proposal. This matrix asks which audience and operation each observation affects and what evidence would justify changing the design.
| Matrix row | Questions for the selected audience | Product evidence |
|---|---|---|
| Region and language | Where are the users and staff? Which journeys and terminology do they need? Who writes, reviews, and supports each language? | Segment definition, content owner, reviewed screens, support route. |
| Device and access | Which devices, browsers, assistive technologies, connection conditions, identity steps, and shared-device risks apply? | Acceptance matrix, performance runs, access and recovery tests. |
| Data and systems | Which fields, documents, events, providers, regions, staff roles, exports, retention, and rights procedures exist? | Data register, provider decisions, access review, response evidence. |
| Payments and tax handoff | Which provider/account, currency display, payment states, invoice or receipt, GST/tax review, refund, fulfilment, and reconciliation are approved? | Provider proof, transaction tests, customer copy, finance acceptance. |
| Security and scale | What volume and concurrency are evidenced? Which abuse, queue, rate-limit, incident, backup, recovery, and support conditions need protection? | Load assumptions, threat notes, alerts, rollback and incident contacts. |
Evidence discipline
No row passes because it sounds plausible.
- Exact audience and affected task are named
- Observation comes from a user, system, provider, or maintained authority
- Qualified owner accepts the interpretation
- Decision changes a requirement, exclusion, or test
- Important assumptions carry a recheck date
- Unresolved items remain visible in the release packet