Go to NONLINEAR Impact

The Responsible
AI Compass

A design guide when you plan & build AI systems — and a diagnostic map when an AI deployment goes wrong and you need to find out where.

Built on existing research, policy and practice in Responsible AI, and shaped for organisations whose mission is social or environmental — not scale for its own sake.

NESWPurposeTechGovernancePeople& Planet
PurposeTechGovernancePeople & Planet

THE TOOL IMPACT TEAMS NEED IN THE AGE OF AI 

AI decisions happen very fast. This compass helps you make them responsibly.

The Responsible AI Compass is a simple map of the four areas where conscious decisions have to be made when a team uses or builds AI: your purpose, the tech behind it, the governance around it, and its effect on people & planet. It gives you the questions worth asking, before launch and again when something goes wrong.

It exists because there is still no agreed standard for doing AI responsibly, and most harm shows up quietly: a group left out of the data, a team disengaging, a decision nobody can explain, a cost nobody counted. Teams that ask these questions regularly build the kind of trust that beneficiaries, donors, partners, and governments respond to. Responsible AI isn't just risk mitigation — it's how you invest in your long-term impact.

The goal is not perfection. It’s progress, made visible.
Mara Puacz
Innovation & Impact Advisor · Responsible AI Board Member

How to use the Compass

BEFORE DEPLOYMENT

Designing an AI initiative

Before you build: name who this will affect, including people who won't be in the decision room. Say who has access and who is accountable when something fails. Check whether the technology does what you intent it to do. Then ask whether any of this actually serves the communities you exist for. If you can't answer all four, you're not ready.

 AFTER DEPLOYMENT

Diagnosing what went wrong

Don't start with the error log. Start with who was harmed/ or is at risk and then trace it back: what decision allowed this? What governance gap meant no one caught it? What design choice created the condition? You'll usually find the technology did exactly what it was built to do - the problem was built in earlier.

The compass

Four layers of impact — and of diagnosis

PurposeTechGovernancePeople& Planet

Purpose

Before anything else: what is the organisation for, and why does this problem need AI at all? Purpose is the conversation most teams skip — and the one every failure eventually traces back to.

Decisions to work through

  • Mission alignment
  • Problem definition
  • Non-AI alternatives
  • Success criteria
  • Who asked for this
  • Cost of doing nothing

Questions to ask

  • What problem are we actually solving, described without the word “AI”?
  • Who asked for this — our beneficiaries, our staff, a funder, or a vendor?
  • What would a good non-AI solution look like, and why are we not doing that?
  • How will we know this worked, and who decides?
  • What are we willing to stop doing if this succeeds — or if it fails?
  • Does this move us closer to our mission, or only closer to looking modern?

When it goes wrong here

When something goes wrong here, the system usually worked as built - it was simply built for the wrong reason, or with weak understanding of the why..

Sources & further learning

EU AI Act ↗

European Union

The official regulation establishing a risk-based legal framework for AI.

Partnership on AI ↗

Partnership on AI

Research and practical guidance for the responsible development and use of AI.

Your turn

Help us make the Compass even better!

If a question saved you from a bad decision, or a layer failed to catch something real, that belongs here.