1. What This Criterion Is For
Clarity assesses whether a control is understood by the people who are expected to use it, support it, or be affected by it. That includes knowing:
- What the control is
- What it’s for
- How it works
- When it applies
- What role they play in it
Clarity is a foundational element of fit-for-purpose control design. Even well-constructed systems fail when the people in them are confused or misinformed.
This criterion is especially critical in high-risk or uncertain moments, where ambiguity can lead to paralysis, inconsistency, or avoidance.
2. How to Use It
Use the Clarity criterion when:
- Designing a new control (to ensure it’s understandable in context)
- Reviewing a control that is inconsistently applied or misunderstood
- Exploring near misses or confusion during incidents
- Helping teams articulate what they assume is already known
Clarity can be assessed through observation, facilitation questions, document review, or reflective exercises (“What would you do if…”).
3. Examples Across Controls
| Control Type | Example of How Clarity Applies |
|---|---|
| Intake | Are staff and applicants clear about what steps are required, what is being screened, and what will happen next? |
| Training | Do participants understand the purpose of the training, what they are expected to learn, and how it connects to their role? |
| Supervision | Do staff know who they are supervising, when, and what that supervision involves? |
| Incident Response | Do staff, volunteers, and participants know how to report concerns and what will happen after? |
| Reporting | Do teams know what data is collected, why, and how it will be used? |
4. What Strong, Fragile, and Failing Look Like
| Level | Indicators |
| Strong | People can confidently describe the control and their role in it. New staff pick it up quickly. No significant variation in understanding. |
| Fragile | Some roles or teams are clear, but others are unsure. Explanations vary. Staff rely on peer cues or guesswork. |
| Failing | People don’t know the control exists, misunderstand it entirely, or avoid using it due to confusion or fear. |
5. Common Pitfalls
- Assuming that once a control is introduced, people understand it
- Overreliance on written documents without follow-up
- Using technical or policy language that doesn’t translate to real roles
- Forgetting to re-clarify during turnover, change, or crisis
6. Design Prompts
When designing or reviewing a control:
- Would a new team member know what this is for?
- Can people explain the control in their own words?
- Are the steps and expectations obvious in the moment they’re needed?
- Do people know who to ask if they’re unsure?
- Has this control been reviewed for clarity across different roles, literacy levels, and languages?
Clarity is one of the simplest criteria to understand and one of the most commonly overlooked in practice. Strengthening it often requires no new resources — only thoughtful communication, modeling, and follow-up.