Concept 1 of 2

Responsible AI in practice

6 questions test this

Responsible AI is the set of properties a system has to hold for it to be defensible to the people it affects, and the practice of measuring and acting on them. It is often discussed as ethics and examined as engineering. Six properties are named on most lists, and both the AWS and the Google Cloud exam guides use a version of the same six, so a candidate is expected to know how each is detected and what is done about it.

The sections below define the six, explain where bias comes from and why the formal definitions of fairness conflict, separate statistical bias from the social kind, cover the dataset characteristics that matter, list the legal exposure that arrives with generative output and name the tooling on each platform.

The six properties

Bias is systematically different treatment of groups. It arrives from the training data, from how the problem was framed and from who was in the room.

Fairness is whether that difference is defensible. The formal definitions conflict, so this stays a judgement about the situation and never becomes a threshold.

Inclusivity is whether the system works for the range of people who will use it, including those poorly represented in training data.

Robustness is whether it holds up on input it was not designed for, and under deliberate attempts to break it.

Safety is whether it can cause harm, directly through its output or indirectly through what people do with it.

Veracity is whether the output is true, which for generative systems is a property that has to be engineered and cannot be assumed.

Where bias comes from

The first property is the one with the most machinery behind it, and bias enters from four places.

The data. Historical records encode historical decisions. A hiring model trained on who was hired before learns who was hired before, including the reasons nobody would defend.

Representation. Groups thin in the training data get worse results, and an aggregate accuracy figure hides this completely.

Proxies. This is the one that catches people. Removing a protected attribute does not remove its influence, because other fields correlate with it. Postcode carries ethnicity, first name carries gender and purchase history carries both. Dropping the column removes the ability to measure the gap while leaving the gap.

Feedback loops. A model that predicts where problems will be found sends people there, they find problems there, and that becomes tomorrow's training data.

The way to see any of it is by measuring performance separately for each group. A model at 94 per cent overall can be at 97 for one group and 71 for another, and the aggregate number will never say so.

Why fairness has no single definition

Measuring by group produces numbers, and the next question is which numbers have to match, which is where fairness stops being a threshold. Three definitions are in common use. Demographic parity asks that each group receive the favourable outcome at the same rate. Equalised odds asks that the error rates match across groups. Calibration asks that a score of seventy per cent mean the same thing whichever group it was given to. Research published in 2016 and 2017 showed that where the groups differ in the underlying rate of the outcome, no classifier can satisfy all three at once, except in trivial cases.

So a team has to choose, and the choice is about the situation. A screening tool where a missed case is the serious harm wants matched false negative rates. A lending decision that a regulator will read as a rate of approvals wants parity. Writing down which definition was chosen and why is what a review will ask for, and a team that never chose has chosen by accident.

Bias and variance

The word bias also has a statistical meaning, which the exam guides name alongside the social one. High bias is a model too simple for the pattern, underfitting and doing poorly everywhere. High variance is a model too sensitive to its training data, overfitting and failing on anything new. Both damage subgroups first, because that is where the data is thinnest, which is the link between the two meanings.

The dataset characteristics that matter

Since most bias enters through the data, the dataset is where most of the improvement is available. The characteristics that matter are inclusivity, diversity, curated sources and balance. The practical reading is that curation is unglamorous work done before any model exists, and it is where the money is best spent.

Legal exposure

Generative AI brings risks that both exam guides list directly, and each has a legal form.

Intellectual property. Models trained on scraped material can produce output resembling their training data, and who owns generated output is unsettled in several jurisdictions.

Biased output creates discrimination liability where the system touches employment, credit, housing or insurance.

Hallucination becomes misrepresentation once a customer relies on it. In 2024 an airline was held liable in Canada for a refund policy its chatbot had invented, and the tribunal rejected the argument that the chatbot was a separate entity responsible for its own words.

End user risk is what somebody does with confidently wrong advice.

Loss of trust is the one with no legal remedy and the longest tail. A system caught being wrong in public rarely gets a second hearing.

The tooling on each platform

Four capabilities matter and every major platform has its own name for each, so the capability is the thing to hold and the product name is a detail.

Bias measurement, before and after training, broken down by subgroup. AWS calls this SageMaker Clarify, Azure has Responsible AI dashboards within Azure Machine Learning, and Google exposes it through the evaluation tooling in Agent Platform. Open source alternatives such as Fairlearn and AIF360 do the same job and run anywhere.

Drift and quality monitoring after deployment. SageMaker Model Monitor, Azure Monitor for machine learning, Agent Platform model monitoring, or Evidently and WhyLabs for a team that would sooner not be tied to a platform.

Content filtering on both input and output. Guardrails for Amazon Bedrock, Azure AI Content Safety, and Google's safety settings and Model Armor. All of them filter categories at configurable thresholds, and where the threshold sits is a product decision.

Routing to a person where confidence is low. Amazon Augmented AI is the named service, and most teams build this themselves, because it is a queue and a rule.

Sustainability belongs here too, as a responsible AI consideration. Model size, training runs and inference volume all carry an energy cost, and choosing a smaller model that does the job is the decision that follows.

Practise this

The exercise needs one feature that is already live, a blank page and fifteen minutes.

Name the groups the feature could treat differently, being specific about its own users, with no list of protected characteristics to reach for. Then answer three questions for each group in full sentences. Write the third one last and slowly, because an answer describing what somebody would have to work out for themselves is no route to appeal.

Feature ..........................................
What it decides or produces ......................

Group 1 ..........................................
  1. How could this group end up worse off than the others?
  2. How would we find out, from which measurement, broken
     down by what, and who reads it?
  3. If it happened to one of them, what could that person
     do about it, and who would answer them?

Group 2 ..........................................
  1. ..............................................
  2. ..............................................
  3. ..............................................

Groups worth naming
  people the training data holds least about, people whose
  input is phrased unusually, people working in a second
  language, people the decision matters most to

The third question is where this exercise usually stops. Most teams can name a group and can describe a measurement they would run, then discover the affected person has no route at all, or a route into a support queue with nobody in it who can overturn an automated decision. Question two fails a close second, since measuring by subgroup needs the group recorded somewhere, and a team that dropped the attribute in order to be fair has removed its own ability to check.

Written out for one real feature, responsible AI stops being six abstract properties and becomes three questions with names and gaps attached to them.

Common misconceptions

“Removing protected attributes from the training data removes bias.”

Other fields stand in for them. Postcode carries ethnicity, first name carries gender, purchase history carries both. Dropping the column removes the ability to measure the disparity while leaving the disparity in place.

“Fairness is a threshold a model either meets or fails.”

The formal definitions of fairness conflict with each other, and it has been shown that several cannot hold at once except in degenerate cases. Which definition applies is a decision about the situation, and no setting can make it.

“Responsible AI is a review that happens before launch.”

Bias appears as populations shift, so a system fair at launch can drift. It is a monitoring commitment with a named owner, and a gate passed through once does none of that work.

6 questions test this concept

A lending model is found to approve applicants from one postcode group at a much lower rate. The team removes ethnicity from the training data and retrains. Approval rates remain skewed. What is the most accurate explanation?

  • AThe model needs more training data before the disparity will resolve.
  • BThe remaining skew reflects real differences and is therefore fair.
  • CThe model is underfitted and needs a more flexible architecture.
  • DOther fields act as proxies, so removing the attribute removed the ability to measure the disparity rather than the disparity itself.
Check whether it stuck.

One per page, with a worked explanation.

Start the set
Related material
Book
Weapons of Math Destruction, On models that scale harm quietly.
Book
Data and Goliath, On data collection and the asymmetry it creates.
Template
Experiment brief, The belief being tested, a hypothesis with a threshold and a date, how long the test runs and on how much traffic, and a table saying in advance what you will do with each possible result.