Values checks help people bring shared principles into the decisions they make every day, not just into mission statements. This guide is for individuals and teams who want practical checks that fit real workflows without turning every task into a lengthy ethics review. The key is to add a short pause at moments when a choice can affect people, trust, or responsibility.
Key takeaways
- Use checks at consequential decisions, handoffs, exceptions, and approvals, not automatically at every task.
- Ask who is affected, which value is at stake, and what responsible action follows.
- Make ownership and escalation clear so a concern can change the decision.
- Review what the checks help people notice and improve, not simply how many boxes they complete.
What does a values check add to a workflow?
A values check connects a principle to a specific action. It asks whether the way work is being done reflects commitments such as honesty, fairness, care, or accountability. It is not the same as a data validation, which checks whether an entry meets a defined format or range.
For example, a customer support workflow might meet its response-time target while repeatedly denying reasonable exceptions. A values check can help the team notice that tension before the response is sent. The goal is not to replace expertise or policy, but to make the human consequences of routine decisions visible.
Values become more useful when people can translate them into shared actions and expectations. A check should therefore name the principle, connect it to the decision at hand, and leave room to explain a conflict.
Where should you place checks in daily work?
Put checks at workflow junctions where judgment matters or an outcome may be hard to reverse. Mapping a process helps reveal these points before adding prompts. Start with one recurring workflow, then trace what triggers it, who makes decisions, where work changes hands, and what happens when the usual path does not fit.
- Prioritization: Could urgency or convenience unfairly push someone’s needs aside?
- Handoffs: Is the next person receiving enough context to act responsibly?
- Exceptions: Does the standard rule need a thoughtful review in this case?
- Approval or delivery: Is the outcome accurate, respectful, and ready to stand behind?
This kind of mapping supports daily decisions aligned with values by showing where a small pause can make a meaningful difference. Low-impact, reversible tasks may need no extra step. Focus first on choices that affect access, workload, trust, or someone’s opportunity to respond.
How can you make a values check brief and useful?
A short routine works best when it helps someone choose a next step, rather than simply confirm that a value exists. Try a three-question check at a relevant decision point:
- Who is affected? Consider people beyond the person completing the task.
- Which value matters here? Name the principle and the specific tension, if there is one.
- What action can I take? Proceed, adjust the plan, ask for input, or raise a concern.
For instance, before assigning a late task, a manager might consider who absorbs the extra work, whether the same people are repeatedly asked, and whether the deadline can be renegotiated. A useful check-in routine should make these questions feel like part of the work, rather than a test of someone’s character.
For teams, agree on what happens when a check reveals a conflict. People need a clear way to pause, ask for a second perspective, or document why a decision was made. Simple daily leadership routines can help make reflection and follow-through part of normal collaboration.
What does a values check look like in practice?
Keep the prompt close to the decision it is meant to improve. The examples below show how a principle can become a practical question without adding a long approval process.
| Workflow moment | Check prompt | Possible next step |
|---|---|---|
| Shortlisting applicants | Are we assessing people against relevant criteria consistently? | Review the criteria and compare evidence before finalizing. |
| Assigning team work | Is the workload distribution reasonable and visible? | Redistribute tasks or discuss capacity and deadlines. |
| Responding to a complaint | Have we understood the person’s concern before deciding? | Ask a clarifying question or seek a second review. |
| Using automated recommendations | Can we explain the recommendation and identify who may be affected? | Check the rationale and escalate uncertain or high-impact cases. |
For automated or AI-supported work, the NIST AI RMF Playbook organizes suggested actions under Govern, Map, Measure, and Manage. NIST describes it as a voluntary resource, not a mandatory checklist. That distinction is useful: teams can adapt appropriate safeguards to their context instead of treating compliance with a form as proof of good judgment.
How can teams keep checks from becoming box-ticking?
Review whether the process helps people notice tensions and respond to them, rather than counting completed prompts as the outcome. In a regular team review, discuss a small number of examples: What concern came up? Could someone raise it safely? Did the decision or workflow change? What did the team learn?
Use feedback from people affected by the process, and protect sensitive details when recording examples. Track practical signals such as recurring exceptions, decisions revised after review, or unclear ownership. These are prompts for learning, not standalone proof that a team acts ethically.
If people repeatedly describe a gap between stated principles and group behavior, treat it as a pattern to examine. Early signs of value misalignment can point to a workflow or team norm that needs attention. Then make a small change, assign responsibility for reviewing it, and return to the question of whether the change improves the experience for those involved.
Frequently asked questions
What is a values check in a workflow?
A values check is a short pause at a decision point to ask whether the next action reflects the principles the team claims to follow. It turns broad commitments, such as fairness or care, into observable choices. It is different from checking whether a number or data field is valid.
Where should values checks be placed?
Place checks where decisions can meaningfully affect people or outcomes: when work is prioritized, handed off, changed to handle an exception, approved, or delivered. A check is most useful before an action becomes difficult to reverse. Routine, low-impact steps usually need fewer prompts than consequential decisions.
What are the three basic components of a workflow?
A useful practical model is a trigger, a decision, and an action: something starts the workflow, someone chooses what to do, and work moves forward. Some methods describe workflows as inputs, processes, and outputs instead. These are complementary ways to map work, not one universal definition.
How do you develop a workflow process?
Start by choosing one recurring process and describing its trigger, decision points, handoffs, and outcome. Identify where a choice could conflict with a stated value, then add a brief prompt, an owner, and a way to raise exceptions. Test the change with the people who perform the work.
How can teams tell whether values checks are working?
Review whether teams are surfacing conflicts early, documenting exceptions, and changing decisions when a value is at risk. Pair these process signals with feedback from affected people. Avoid judging success by the number of boxes completed, since a completed check does not prove that a decision was fair or responsible.
