By Laini Byfield
The ETHICMAP framework explained
ETHICMAP is a repeatable cycle that turns ethics into operations. It is designed for programs where timing, merging, and edge cases decide real outcomes for real people.
What ETHICMAP is
ETHICMAP is an implementation cycle for Small Data Ethics. It is designed to be used every program cycle — not only during initial design.
Core stance
- Treat data errors as moral events — not technical bugs.
- Design for contestability, traceability, and repair.
- Assume relational exposure — not anonymity.
The cycle — what each step produces
E — Environment
Output: context statement, constraints, power map, data boundaries.
T — Timing
Output: timeline of cutoffs, lags, retroactivity, comms calendar, appeal windows.
H — Harmony
Output: equity and exposure check — who is at risk under errors and edge cases.
I — Incentives
Output: feasibility test — participation pathways that avoid coercion.
C — Calibration
Output: realistic change model — guardrails for what can be claimed and measured.
M — Measurement
Output: metric spec plus uncertainty — error modes, match rates, confidence flags.
A — Application
Output: runbook, standard ops, versioning, reprocessing rules, escalation triggers.
P — Publish
Output: change log and learning memo — decisions, tradeoffs, what changed and why.