1. What This Criterion Is For
Alignment with Objectives assesses whether a control supports the organization’s core goals and values — especially its Swans.
A control that technically functions but doesn’t serve what the organization is trying to achieve is unlikely to be prioritized, funded, or taken seriously. This criterion helps teams ensure that every control contributes directly to the outcomes that matter most.
It also helps prevent systems from becoming fragmented, where compliance activities run parallel to — or even in tension with — the mission.
2. How to Use It
Use the Alignment with Objectives criterion when:
- Designing or reviewing a control during system-building or evaluation
- Staff describe a control as burdensome, disconnected, or bureaucratic
- Aligning prevention with broader strategic goals (e.g., inclusion, participation, trust)
This criterion is especially useful when working with senior leadership or funders, who need to see how controls reinforce (not hinder) mission delivery.
3. Examples Across Controls
| Control Type | Example of How Alignment with Objectives Applies |
|---|---|
| Training | Is training framed as core to safe, values-aligned delivery — or just a legal requirement? |
| Behavior Expectations | Do behavioral guidelines reflect the organization’s values and relational goals? |
| Supervision | Is oversight seen as part of quality service and trust-building — not just risk control? |
| Reporting | Do reporting systems reinforce transparency, accountability, and ethical leadership? |
| Budget | Are prevention-related controls funded in a way that reflects stated safety priorities? |
4. What Strong, Fragile, and Failing Look Like
| Level | Indicators |
|---|---|
| Strong | Controls are clearly connected to what matters. Staff and leadership see them as part of doing the work well. |
| Fragile | The control is functionally helpful but poorly linked to the organization’s mission. People see it as “extra.” |
| Failing | The control is seen as a distraction, punishment, or a compliance-only task. Staff resist or quietly bypass it. |
5. Common Pitfalls
- Implementing controls based on external expectations, not internal purpose
- Failing to connect new prevention measures to values, trust, or impact
- Separating “safeguarding” from “programming” in ways that create silos
- Leaving control justification out of onboarding, communication, or training
6. Design Prompts
When designing or reviewing a control:
- What objective or Swan is this control helping us achieve?
- Would staff or leadership see this as contributing to the mission?
- Does this control reflect and reinforce our values?
- Is this control integrated into the work — or bolted on?
- How do we explain why this control matters in terms of purpose, not just risk?
Alignment with Objectives makes the system meaningful. When people see how controls help achieve what they care about, prevention becomes a shared effort — not just a task to be managed.