Module 15 · Tier 6 — Critical Evaluation

Personal AI Operating System

Design your own system. How to run your work with AI as an integrated co-pilot.

12 min Tier 6 — Critical Evaluation

Why This Matters

Individual AI tools and workflows are useful. An integrated personal AI operating system is transformative. The difference: instead of reaching for AI when you remember it exists, you've designed a system where AI is the default for specific categories of work. This module is about designing that system — your personal stack, your documented workflows, your decision criteria for when to use what.

A personal AI operating system has four components:

Most practitioners end up using 3-5 tools regularly, with one primary conversational AI and specialized tools for specific use cases. Design criteria:

Document your stack as a simple decision table: "For [task type], I use [tool], because [reason]."

Full access is for AIQ members

Unlock all 56 lessons, the certificate pathway, and the SociA|~ community.

56 lessons across all three course tracks
AIQ certification on completion
SociA|~ Society community access

Unlock full access →

The Concept

What a Personal AI OS Looks Like

A personal AI operating system has four components:

Your stack: The specific tools you use for specific task types — not every tool that exists, but the specific ones that work best for your work.
Your workflows: Documented, named processes for your most frequent AI-assisted tasks.
Your decision criteria: Clear rules for when to use AI versus when not to — based on task type, stakes, and time available.
Your prompt library: Proven prompts for recurring tasks, in a place you can find them.

Designing Your Stack

Most practitioners end up using 3-5 tools regularly, with one primary conversational AI and specialized tools for specific use cases. Design criteria:

Which tasks make up 80% of my AI use?
Which tool performs best for each task category?
What are my data privacy requirements?
What integrates with the tools my team uses?

Document your stack as a simple decision table: "For [task type], I use [tool], because [reason]."

The Decision Criteria Framework

A personal AI OS includes explicit criteria for when AI is and isn't the right choice:

Use AI by default: First drafts, research synthesis, structural analysis, generating options, format conversion, document summarization.

Use AI with verification: Factual research, anything that will be used externally, analyses that inform decisions.

Use AI for input only: Sensitive communications, high-stakes decisions, anything where your unique context is irreplaceable.

Don't use AI: Situations where the thinking process itself is the value (building your own judgment), genuinely confidential information in non-approved tools, tasks where authenticity of voice is verified (some academic, some professional contexts).

The Weekly AI Review

The habit that keeps a personal AI OS healthy: a 15-minute weekly review.

What AI-assisted work am I most proud of this week? Why did it work?
What AI output disappointed me? What would I change?
Did I use AI for anything I shouldn't have? Or miss using it somewhere I should have?
Is there a new prompt worth adding to my library?

This review takes 15 minutes and produces the continuous improvement loop that separates compounding practitioners from stagnating users.

A personal AI OS snapshot

An example stack for a marketing professional:

Primary AI: Claude — complex writing, analysis, long documents
Search AI: Perplexity — current information, research with citations
Content AI: ChatGPT — image generation, varied content formats
Workspace AI: Notion AI — internal documents, meeting notes, knowledge base
Automation: Zapier — 3 recurring automations (weekly report, lead email drafts, content calendar)

Prompt library: 22 entries across 5 categories. Decision criteria: documented on one page in Notion. Weekly review: Friday afternoon, 15 minutes.

This took about 6 months to develop. It compounds every month as new workflows are documented and new prompts are captured.

Hands-On Exercise

Document your personal AI OS

NotionObsidianGoogle DocsAny notes system

This is the most important exercise in the Workflows track. Set aside 45 minutes. Document your personal AI OS: 1. Your stack (one table): Task type → Tool → Reason 2. Your top 5 workflows (one paragraph each): Name, trigger, steps, output, pitfalls 3. Your decision criteria (one page): When you use AI by default, with verification, input only, and not at all 4. Your prompt library status: How many entries do you have? What's missing? 5. Your weekly review habit: When will you do it? What format? Share this with one person — a colleague, a coach, anyone who can hold you accountable to using it.

Done is better than perfect. A rough personal AI OS that you actually use is worth 10x a perfect one you never complete.

Active Recall

Before moving on — close this lesson and answer these from memory. Then come back and check. Testing yourself (not re-reading) is how this sticks.

1 What are the four components of a personal AI OS? Why does each one matter?

2 What is the weekly AI review and why is it the habit that separates compounding practitioners from stagnating users?

Reflection

What is the current state of your personal AI OS? What's the most important missing piece? What would your system look like in 6 months if you maintained the weekly review habit?

Key Takeaway

A personal AI OS has four components: stack, documented workflows, decision criteria, and prompt library. The weekly review habit is what makes it compound. Done is better than perfect — start with what you have and iterate.