Digital Ethics Frameworks
A digital ethics framework is a working set of principles and checks for the specific decisions data, AI and algorithms actually make, so a team catches harm before a customer or regulator does.
Six steps run in sequence, from naming the decision the system makes to giving someone real power to stop it.
Reach for this when…
- You're deploying an AI or automated decision system and 'we'll be responsible' isn't a plan.
- A team member has flagged a use case that feels wrong but nobody can say exactly why.
- A regulator, customer or journalist could reasonably ask 'how did this system decide that', and you don't have an answer.
How to run it
- List the actual decisions the system makes about people, not the technology in the abstract.
- Name who could be harmed and how, including groups not in the room when it was built.
- Set concrete checks: what data is used, what's excluded, and who can override the system.
- Build in a human review point for consequential decisions, not just a general policy.
- Monitor after launch, the system's behaviour will drift as data and use change.
- Give someone real authority to say no or pause it, not just an ethics statement.
A worked example
Situation. Grace Nakato was building an AI triage tool at AfyaLink Health, a digital health startup in Kampala, Uganda, meant to flag which patients should be seen fastest. Early testing showed it consistently deprioritised patients from neighbourhoods with lower historic clinic attendance.
Applied. Rather than publishing a general AI ethics statement, her team named the specific harm, proxying neighbourhood for likely no-show, penalising patients who'd struggled to attend before, removed that variable, and set a rule that any low-priority flag triggered mandatory human review.
Result. The tool shipped three weeks later than planned but without the bias, and the mandatory review point caught two further edge cases in its first month that the original design hadn't anticipated.
The catch
A framework written as a values statement changes nothing if it isn't attached to specific checks on specific decisions, most 'AI ethics' documents fail here. It's also genuinely hard to spot harms to groups not represented on the building team, the framework needs to actively seek that input, not wait for it. Principles agreed at launch need monitoring after, since a system's real-world behaviour can drift from what was tested.
If your digital ethics framework can't name a specific decision it would stop the system from making, it isn't a framework, it's a mission statement.