Traditional governance could apply ethics after the fact: a decision produced a bad outcome, the board investigated, and it corrected course. That lag worked when organisations moved slowly enough for retrospective correction to matter.
Algorithmic systems remove that luxury. They execute thousands of decisions on whatever values were embedded during design, long before any board reviews the results. By the time governance examines outcomes, the system has already optimised for efficiency over fairness, or speed over care. Ethics applied afterwards becomes damage control, not moral architecture — which forces ethics upstream, into the design itself, before deployment rather than after harm.
The complication is that AI doesn’t arrive value-neutral. Foundation models are pre-trained on judgements made by whoever built them — typically encoding assumptions about fairness, harm, and appropriate behaviour that were never written down as a specification, but are baked into training data, feedback tuning, and safety guardrails. A board can specify its own organisation’s values and still find the underlying system already has different ones, misaligned in ways that often only surface once the system is operating at scale.
The work is therefore twofold. First, understanding what values a model already embodies — not from marketing material, but by systematically testing how it behaves when facing an ethical trade-off. Second, building the additional architecture that constrains or redirects those pre-installed values toward organisational purpose, while accepting that some of what’s baked in can’t be fully overridden without breaking the system.
This gets harder still once an organisation runs several AI systems at once, each optimised for something different — recruitment for throughput, resident tools for engagement, asset management for cost. Each behaves impeccably by its own local measure while the combination produces something morally incoherent that nobody chose. What’s needed isn’t one central authority dictating every system’s behaviour, but a layer of coordination that makes conflicts between systems visible — so that a clash between recruitment efficiency and staff wellbeing becomes a board decision, not a buried trade-off.
No design eliminates drift entirely; embedded values get tested by situations nobody anticipated, so this has to be treated as continuous work, not a box ticked once at build time — ethical questions surfaced where decisions actually happen, not only where risk gets recorded afterwards.
The real test is what happens under pressure. When time is short and incentives pull the other way, does the ethical framework still shape the decision, or does it quietly get bypassed? If it can be ignored when convenient, it was aspirational, not integral. The difference is that architecture holds when nobody’s watching. Aspiration doesn’t.