When Not to Build
A written test for deciding whether a model should exist, and how to say no with evidence.
Objective
By the end of this lesson, you can apply a five-question test to a model idea and write a short, evidence-based recommendation to build, change, or stop it.
Saying no is engineering
Many harmful systems were built by capable people who never stopped to ask whether they should. The most valuable thing an engineer can do is sometimes to say, "This should not be a model," and explain why.
The five-question test
Answer each in writing:
- Purpose. What decision does this support, and who makes it?
- People. Who is affected? Were they asked?
- Mistakes. What happens to a person when it is wrong? Can they find out and appeal?
- Data. Does the data fairly represent the people affected? Does any label or proxy carry past unfairness?
- Alternatives. Would a rule, a checklist, or more staff time do the job with less risk?
If you cannot answer one, stop and find out. If the honest answer to question 3 is "serious harm, no appeal," do not build it.
A national example
Practice with an AI reviewer
An AI assistant can act as a tough reviewer. It does not get the final say. You and the people affected do.
Prompt Lab
Get a hard critique of a model idea using the five-question test.
Your prompt
Act as a skeptical ethics reviewer for a community nonprofit. Your task: Apply the five-question test (purpose, people, mistakes, data, alternatives) to my model idea and tell me the weakest answer Format: Five short sections, then one line: build, change, or stop, with the reason
Reflection
Discussion
Ask. Answer. Build together.
Loading…