Harm Audit

The Hardest Question: How Could This Hurt Someone?

This is the most important question a builder can ask. Not "does it work?" but "could it cause harm?"

Most harm from technology isn't intentional. It comes from builders who didn't think through how their creation could be misused, who it might exclude, or what unintended consequences it might have.

The good news: a structured audit catches most potential harms before they become real problems. That's what you'll do in this lesson.

The Harm Audit Framework

For each question, think about your project specifically:

• 1. Misuse: Could someone use your project in a way you didn't intend? Could it be used to bully, deceive, stalk, or harm? Even simple tools can be misused — a location-sharing feature could enable stalking.
• 2. Exclusion: Who can't use your project? People with visual impairments? Slow internet? Old devices? Non-English speakers? Every excluded user is a person your project doesn't serve.
• 3. Misinformation: Could your project spread false information? If it uses AI-generated content, is that content verified? If it displays data, is that data accurate and up to date?
• 4. Psychological impact: Could your project make someone feel bad? A habit tracker that shames users for missing days. A comparison tool that triggers unhealthy competition. Design for encouragement, not guilt.
• 5. Data exposure: What happens if your project's data leaks? Is there anything stored that could embarrass or endanger someone?

Accessibility: Can Everyone Use It?

Accessibility means making your project usable by people with different abilities. Here are the basics every project should meet:

• Text is readable: Sufficient font size (at least 16px) and color contrast
• Images have alt text: Descriptions for screen readers
• Buttons and links are large enough: Tap on mobile without frustration
• The project works without relying solely on color: Color-blind users can't distinguish red from green
• Interactive elements are reachable with a keyboard: Not just a mouse

You don't need to be an accessibility expert to make your project work for more people. Even implementing 2–3 of these basics makes a significant difference.

The Responsibility of Shipping

When your project was on your computer, you were the only person affected. Now that it's deployed, it touches other people's lives — even in a small way.

That's a responsibility, and it's one worth taking seriously. Not because you need to be perfect, but because thoughtful builders make the world better. Every time you ask "could this hurt someone?" and adjust accordingly, you're building something worth being proud of.