Plus three exercises to run before you write yours
On Wednesday, the Communicators Club spent a session on AI. Across the group, no person, church, or organization had an AI policy. Some of us use AI regularly and some avoid it on purpose, and in both cases the decision exists only in someone’s head.
Everyone who communicates on behalf of an organization needs clarity on this, for themselves and for the people they work with. A policy should fit on a single page. Simplicity is what makes it work. A page can be read in two minutes, remembered, and followed, while a long document gets filed and forgotten.
A policy of any length needs to answer three questions:
- What do you use AI for? Name the tasks where it is welcome, such as subject line options, alt text, meeting summaries, or proofreading.
- What always gets human review? Treat everything AI produces as a first draft. A person owns the final version.
- What never goes into it? Name the information and the kinds of writing that stay out of AI entirely.
A policy that skips one of these leaves a gap that someone will eventually fall into.
Before you write that page, you need to know what belongs on it. You cannot set boundaries around something you have not thought through. The exercises below are meant to start that thinking. They help you see how you already use AI in your work, and where it could support you, so the policy you write reflects your actual practice and your actual comfort level.
- Read your announcements as a first-time visitor. Ask AI to read your Sunday announcements as someone who has never been to church and list every word or reference it finds confusing. It is a quick way to find insider language, and it shows you what the tool does well.
- Hold a staff exercise. Each person writes down one thing AI is welcome to do and one thing it never will. Compare the lists. The overlap becomes the start of your policy, and the gaps become the conversation you need to have.
- Go AI-free for one week on one channel. Pick email or social posts. Note what gets slower, what gets better, and what nobody misses. You will learn where AI earns its place in your workflow.
Go disrupt something,
Christen

