Question Pack — Humanitarian & NGO
Pack (fixed)
| Field | Value |
|---|---|
| Respondents | Humanitarian organisations, multilaterals, NGOs, implementation intermediaries |
| Primary gates | Use cases · Counterparties · Delivery model · Adoption |
| Secondary gates | Regulation · Infrastructure · Cross-RFP handoffs |
Assemble (fill before the interview)
| Field | Value |
|---|---|
| Cluster | |
| Use case (this play) | |
| Play one-liner | |
| Hypothesis status | hypothesized / desk-supported / revised |
| Desk claims to test | |
| What would falsify this play | |
| Respondent name / role | |
| Access basis | Interviewed / Warm Access / Referred / Desk-Identified |
| Session goal | confirm / falsify / upgrade confidence |
| Date |
Then run Interview Conduct opening. Keep every probe anchored to this play.
Run — primary gates
Use cases
- Is the failure behind this use case acute enough in this cluster that your organisation would consider a new rail — not just a demo?
- Have you evaluated blockchain or digital-asset tools for something like this play before? What was decided and why?
- Would Cardano-specific properties (deterministic settlement, credentials, public auditability) matter for this play, or would any compliant digital system suffice?
Counterparties
- Who inside your organisation can sponsor a pilot of this play (mandate + budget + decision rights)?
- Which government or regulator relationships are required before this play can proceed in this cluster?
- Which local partners do you already trust for last-mile delivery or beneficiary access on this play?
Delivery model
- Who would implement and operate a pilot of this play day-to-day — your team, a local integrator, a global vendor, or a consortium?
- What delivery capacity is missing locally that has killed or delayed similar projects?
Adoption
- What counts as real adoption for this play: recurring beneficiary payments, institutional dependency, audited workflow integration, or something else?
- Which “pilot” announcements near this play should be treated as weak signals?
- If an adoption signal is claimed: propose a CASS tier and evidence rationale.
Run — secondary gates
Regulation
- What compliance or donor constraints govern this play (payments, data, digital assets)?
- Where is the regulatory path unclear enough that you would not proceed without counsel?
Infrastructure
- What must exist before this play is credible: mobile reach, identity, off-ramp, offline capability, privacy?
- Which of those are unmet in this cluster?
Cross-RFP / adjacent issues
- Which blockers of this play are liquidity, wallet UX, or enterprise-compliance issues rather than regional entry strategy?
Capture (fill during / after)
| Field | Value |
|---|---|
| Gates addressed | |
| Play status after call | confirmed / revised / rejected / inconclusive |
| Counterparties named | |
| Access basis updates | |
| Regulatory certainty | Clear / Evolving / Uncertain |
| Adoption signal (if any) | |
| Proposed CASS tier | |
| CASS rationale | |
| Referrals | |
| Notes / ingest link |
Last updated on