CARE Loop
From Chapter 9 of AI and the Art of Being Human
What it is
A team practice that scales individual clarity into organizational compassion and systematic care.
Where you would use it
When your team needs to embed care and dignity into AI systems and their use
When implementing AI that affects employees, customers, or other stakeholders
When organizational speed conflicts with human care
When you need to build care into company culture, not just compliance
The Tool
Four Movements for teams
Context: Map the whole system—who’s affected, what assumptions exist, how different worlds collide in one space
Acknowledge: Name impacts honestly in team settings—make the invisible visible to everyone, not just leadership
Respond: Act at two scales—immediate adjustments in the present, systemic changes in the near future
Evaluate: Review patterns using both metrics and stories—schedule regular “Reflection Hours” to ask what’s working
How to use it
Make this a weekly team practice. Pick one AI process affecting people. Spend 30 minutes running the complete loop together. Document what you discover. Implement at least one immediate fix and identify one systemic change.
See it in practice: The Schedule Was Legal, Efficient, and Wrong →
FAQ
Add paragraph text. Click “Edit Text” to update the font, size and more. To change and reuse text themes, go to Site Styles.
The CARE Loop is a practical way to keep care and human impact in view when working with AI. It encourages people to make care an active part of how they design, use, and evaluate technology-supported work.
Use it when designing an AI-supported experience, changing a process, or deciding how an AI tool should interact with people. It is particularly relevant when the work affects customers, students, colleagues, or communities.
Build time for care-focused questions into planning and review. Discuss whose needs may be overlooked, how people will experience the process, and what should change when the impact is not acceptable. Revisit those questions as the system or situation evolves.
