
Define clear boundaries for emotional vs. task-focused AI interactions in your workflow
You'll have a personal protocol document specifying which types of work conversations you'll have with AI and which you'll explicitly avoid, protecting your judgment and focus.
What you'll make
Personal AI Protocol
- Task Zone Definitions: which conversations belong with AI vs humans
- Dependency Indicators: warning signs you've crossed emotional boundaries
- Provider Switching Procedure: how you'll avoid lock-in
- Protocol Testing Results: evidence your boundaries work in practice
Paste your protocol document text directly — should be 2-3 pages you'd actually reference when deciding whether to ask AI something
The 4 parts
Each part ends with a check you can see.
Map Your Current AI Conversations
Audit your recent AI chats to identify which conversations were task-focused versus advice-seeking or emotional.
Done when
You have a categorized list of your last 20 AI conversations with clear patterns about where you cross into non-task territory
Test Consensus Bias Across Providers
Ask the same controversial question to multiple AI providers and compare how they pull toward different versions of center.
Done when
You have evidence of how 3+ AI providers handle the same edge-case question, with your own judgment about when their consensus-pulling helps versus hurts
Build Provider Independence
Set up accounts and export capabilities across multiple AI providers so you can switch without losing work history.
Done when
You can export your conversations from your primary provider and successfully import them elsewhere, plus you have backup accounts ready
Write Your Interaction Protocol
Draft specific rules about which conversations you'll have with AI versus humans, then test the protocol for a week.
Done when
You have a written protocol covering task zones, dependency warning signs, and switching procedures, plus evidence it works in practice
Capstone: you put together your Personal AI Protocol.
About this lesson
What you'll be able to do
- Create a personal protocol document defining which conversations you'll have with AI and which you won't
- Test your current AI usage patterns for emotional dependency indicators
- Establish clear boundaries between AI-assisted work and human-only decision zones
- Build switching capability across multiple AI providers to avoid lock-in
Who it's for
- Knowledge workers who use AI chat daily but haven't defined usage boundaries
- People who've noticed they're asking AI for advice beyond its competence
- Anyone who wants to stay in control of their AI relationships rather than drift into dependency
What it won't cover
- How to build or configure AI models
- Technical prompt engineering
- Comparing AI model capabilities
- Industry predictions about AI development
Skills you'll practise
- Boundary setting for AI interactions
- Emotional dependency pattern recognition
- Multi-provider workflow design
- Personal protocol development