Personas and stakeholders
A useful answer begins with the other person’s decision. Confirm their authority and evidence needs rather than assuming every firm uses the same process. STABLE
| Persona | Question to resolve |
|---|---|
| Vendor / deployer CTO | Workflow, integration, identity, tool paths, control scope and effect observations |
| CISO / governance lead | Threat model, bypass, key custody, trust model, verification and incident access |
| Compliance reviewer | Applicable requirements and which artifact answers which question |
| Underwriter / actuary | Exposure definition, data quality, loss relevance and permissible use |
| Reinsurer / portfolio reviewer | Dependencies, aggregation, correlated severity and uncertainty |
| Broker / MGA | Client problem, usable submission, distribution effort and authority |
| Claims reviewer | Timeline, observed effects, corroboration, causation and missing records |
| Procurement / CFO | Workable cost, retention, support, lock-in and measurable business value |
Avoid universal answers: privacy depends on actual fields and exports; verification depends on supplied material and trust; pricing needs more than counts; excluded cover returns only by an authorised contract change. STABLE
Show one artifact, what it establishes, and what remains unknown. Propose a test with the reviewer who can accept or reject the use. See market discovery.
Drill this page →20 bank questions stand behind what you just read. Check it while it’s warm.