AI & Automation · Resource 09 of 15
The AI-Pilled CoS
Five ways to demonstrate genuine AI mastery — and the structural case for why no agent can replace a human Chief of Staff.
Instruction Manual · Chief of Staff · Claude Edition
The AI-Pilled Chief of Staff
A concrete, step-by-step manual for building an AI-powered CoS practice using Claude — including exact prompts, governance templates, and a trust-building protocol you can deploy this week.
ai-pilled, adj.
A rite of passage where an individual becomes fully awakened to AI's possibilities — moving from casual observer to fervent adopter. Skepticism and detachment give way to enthusiastic engagement, even evangelism.
Evolved from "red-pilled" internet slang, the term signals revelation rather than disillusion — the moment when AI stops being a headline and starts reshaping how you think about every domain you work in.
The prompts in this manual involve uploading strategic documents into Claude. Ensure your organization is using Claude for Work (Team or Enterprise) — the plan tier where proprietary data is not used for model training. See Appendix D for details →
Pillar 01
Build your custom AI thought partner
Most people use Claude as a search engine with better sentences. An AI-pilled CoS builds a persistent, contextualized intelligence layer that knows your organization — its strategy, its language, its tensions, and its priorities. BCG research confirms that the gap between AI adopters who see results and those who do not comes down to how systematically they embed AI into their actual work context, not how frequently they use it. BCG, January 2026
Create a dedicated Claude Project for your CoS work
30 minutes · Tool: Claude.ai Projects
In Claude.ai, navigate to Projects and create a new project titled something like 'CoS Operating System — [Your Org Name].' Projects give Claude persistent memory across conversations. Every conversation inside the project inherits your system instructions and uploaded documents.
Why this matters
Without a Project, every Claude conversation starts from zero. Your AI thought partner has no idea what your CEO cares about, how your org speaks, or what decisions are already in flight. A Project is the difference between a generic assistant and an institutional intelligence layer.
You are the strategic thought partner for the Chief of Staff at [Organization Name]. ORGANIZATIONAL CONTEXT: - Our mission: [1-2 sentence mission] - Current strategic priorities (from CEO): [list 3-5 priorities] - Our stage: [e.g., Series B startup / 200-person nonprofit / Fortune 500 division] - My CEO's communication style: [direct/collaborative/data-driven/narrative-driven] YOUR ROLE: - Think like a McKinsey senior partner with deep knowledge of our sector - Communicate in the register our leadership team uses - Flag when a question requires expertise beyond your knowledge - Always distinguish between what is strategic vs. operational - When I share a document or situation, lead with implications before description CONSTRAINTS: - You do not have access to real-time data or live systems - Do not fabricate metrics, names, or quotes - When uncertain, say so explicitly and offer a structured way to think through it DEFAULTS: - Responses under 300 words unless I ask for a full document - Lead with the "so what" before the detail - Use our org's terminology (I will add a glossary below as I learn what matters)
Upload your five foundational documents
45 minutes · Tool: Claude Project file upload
Upload these five documents to your Project's knowledge base. They are the minimum viable context that separates an intelligent assistant from a generic one.
Important
Do not upload documents containing personal employee data, legal privileged communications, or board-only materials. When in doubt, summarize in plain text rather than uploading the source document.
| Document | What to upload | Why it matters |
|---|---|---|
| CEO priorities memo | Most recent all-hands, strategic memo, or board update from the CEO | Claude answers every question through this lens, not a generic corporate lens |
| Team org chart | Names, titles, reporting lines (a simple text version is fine) | Claude can draft communications knowing who reports to whom and flag stakeholder gaps |
| Current OKRs or goals | This quarter's objectives, key results, and owners | Every recommendation Claude makes can be tested against current priorities |
| Glossary of internal terms | Acronyms, product names, initiative names, internal jargon | Prevents Claude from describing your flagship product as "a software solution" |
| One sample CoS deliverable | A memo, briefing, or executive summary you are proud of | Claude calibrates to your voice and format before you type a single prompt |
Run your first five thought-partner sessions
1 week · Frequency: Daily
Use these five prompts in your first week to calibrate your thought partner and stress-test its usefulness. Each one surfaces a different kind of value.
I'm about to spend significant time on [initiative or project]. Based on our CEO's priorities and current OKRs, rate the strategic alignment of this work on a scale of 1-5 and explain the gap or overlap. Then tell me which of our current priorities this most directly serves.
We are making a decision about [decision]. Based on our org chart and team context, who are the five stakeholders most likely to have a strong opinion on this, and what is each person's likely concern or objection? Flag anyone I might be overlooking.
I have a meeting with [name/role] in 30 minutes about [topic]. Write me a one-page briefing with: (1) the three things they most care about, (2) two potential landmines in this conversation, and (3) the single clearest ask I should make.
Here is our current plan for [initiative]: [paste plan]. Take the strongest possible position against this plan. What are the three most credible objections a skeptical board member or senior leader would raise? Do not soften them.
I need to make a recommendation to the CEO on [decision]. The two main options are: Option A: [describe] / Option B: [describe]. Draft a one-page decision memo in my voice using our standard format. End with a clear recommendation and the one condition under which I'd choose the other option.
Pillar 02
Architect the AI Triad and make adoption stick
BCG research found that AI adoption failure is almost entirely psychological — not technical. Fear, habit, and not knowing what is possible are the real barriers. BCG, 2025 The CoS is the only role positioned to solve all three simultaneously.
Convene the AI Triad in its first 60-minute working session
60 minutes · Who: CEO + CoS + CTO
The AI Triad is not a committee. It is a three-person decision-making unit with a clear division of labor.
We are a [type of organization, size, sector]. I am preparing a 60-minute working session with our CEO and head of technology to align on AI adoption. Generate a one-page pre-read that covers: 1. The three decisions we need to make in this session (use, governance, resourcing) 2. A simple RACI for AI adoption: who owns what between CEO, CoS, and CTO 3. The single most important question we need to answer together 4. Two examples of organizations similar to ours that have done this well Keep it under 400 words. Use plain language, not AI hype.
- □Which AI tools are approved for use by which roles
- □What data can and cannot be entered into external AI tools (the "never list")
- □Who has authority to approve new AI use cases — and how fast that decision gets made
Run a department-by-department adoption sprint
4 weeks · One department per week
Do not try to roll out AI to the whole organization at once. Start with the least risky and most motivated teams.
I need to introduce AI tools to the [department name] team. Their primary work involves [describe what they do]. Their leader is [describe personality/priorities] and is [skeptical / cautiously optimistic / enthusiastic] about AI. Draft a 5-minute verbal pitch I can give this leader that: 1. Leads with a benefit specific to their team's actual work (not generic productivity) 2. Addresses the most likely fear without being condescending 3. Proposes one specific low-stakes pilot they can run this week 4. Ends with a clear, small ask Do not use the words "streamline," "leverage," or "synergy."
Research grounding
BCG research found that employees who are seeking advancement may see AI as a career stepping stone, while those who find pride in their existing work may see it as a threat. Tailoring the pitch to these two different profiles is not optional — it is the primary lever of adoption. Source →
Build a living AI use case registry
Ongoing · Owner: CoS
The CoS owns a shared document — a one-page, continuously updated registry of AI use cases across the organization.
Create a simple AI use case registry template for our organization. Include columns for: - Department - Use case description (one sentence) - AI tool used - Time saved per week (estimate) - Risk level (low / medium / high) - Status (piloting / scaled / paused) - Owner Format it as a markdown table. Add three hypothetical example rows using a [sector] organization as the context.
Pillar 03
Design the AI operating rhythm
The AI operating rhythm is a deliberately designed system where AI handles pre-work and post-work so that every meeting starts informed and ends accountable. NTT DATA's 2026 Global AI Report found that organizations embedding AI into operating processes are 2.5× more likely to exceed 10% revenue growth. NTT DATA, 2026
Implement the pre-meeting briefing system
30 min setup · 10 min per meeting thereafter
For every significant meeting on the CEO or exec team calendar, generate a structured briefing 24 hours in advance.
Meeting: [title] Date/Time: [date] Attendees: [list with roles] Purpose: [decision / update / alignment / relationship] Context: [paste any relevant background] Generate a pre-meeting briefing with exactly these sections: 1. OBJECTIVE — What does a successful outcome look like? (2 sentences max) 2. BACKGROUND — What does the CEO need to know walking in? (5 bullet points max) 3. WATCH FOR — What tensions, sensitivities, or landmines should be on their radar? 4. THE ASK — What is the single clearest decision or commitment we need? 5. OPEN QUESTIONS — What are we still uncertain about? Format for reading in under 3 minutes. No fluff.
Build the post-meeting action capture system
15 minutes after each meeting
This eliminates the 'what did we decide?' conversation that happens two weeks later.
Why this matters
After 90 days, your post-meeting captures become an organizational memory. When someone asks 'what did we decide about X six weeks ago?' — you have an answer in 30 seconds instead of 30 minutes.
Here are my rough notes from today's meeting on [topic]: [paste your notes, transcript, or bullet points] Generate a clean post-meeting summary with these four sections: DECISIONS MADE — What was agreed? Be specific and unambiguous. ACTIONS — Who is doing what by when? Format: [Name] → [action] → [due date] OPEN ITEMS — What was raised but not resolved? Who owns follow-up? CONTEXT FOR NEXT TIME — One sentence summary for anyone who missed this meeting. Flag any action item that has no clear owner or no clear deadline.
Build a weekly operating rhythm using Claude
45 min per week · Best day: Monday morning
Each Monday, use this four-part weekly setup sequence to prime your thinking and the CEO's week.
It's the start of the week. Here is what I know: Current OKRs: [paste or reference uploaded doc] Open decisions needing CEO attention: [list] This week's key meetings: [list with dates] Anything that slipped last week: [list] Generate a Monday morning frame for the CEO in three sections: 1. THIS WEEK'S PRIORITY — the single most important thing to get done 2. THREE DECISIONS IN FLIGHT — status and what needs to move 3. WATCH — one thing that could go sideways this week if we are not paying attention Keep it to half a page. Write it in a tone the CEO will actually read.
Monday — Week frame
- – Generate weekly priorities brief
- – Flag decisions that need CEO attention this week
- – Surface anything that slipped from last week
Wednesday — Pulse check
- – Draft midweek status note to CEO
- – Generate agenda for standing meetings
- – Flag emerging issues before they become crises
Friday — Lookback
- – Summarize week's decisions and outcomes
- – Draft CEO weekend reading (2-3 items max)
- – Update action item tracker
Ongoing — Horizon scan
- – Monitor industry signals for CEO briefing
- – Draft talking points for upcoming external meetings
- – Maintain AI use case registry
Pillar 04
Become the organization's AI sense-maker
The sense-maker function is the highest-leverage thing a CoS can do with AI. Trust in AI systems is shaped more by human actors than by the system's own features. ACM CHI 2024 You are that human actor.
Build a stakeholder translation matrix
1 hour setup · Ongoing use
Different leaders need AI framed through a completely different lens.
I need to make the case for AI adoption to our [role: e.g., General Counsel / CFO / VP of HR / VP of Sales]. Their primary concern is [describe: e.g., risk and liability / cost and ROI / talent and compliance / pipeline and revenue]. Their relationship to technology is [describe: e.g., skeptical but pragmatic]. Write a one-page brief for this leader that: 1. Opens with a problem they already feel (not one we are introducing) 2. Shows how AI solves that specific problem — use a concrete example from their domain 3. Addresses the single biggest risk they will raise before they raise it 4. Ends with one specific, reversible action they can take in the next two weeks Do not use generic AI benefit language. Make it feel like it was written for them.
| Stakeholder | Their lens | Lead with | Most likely objection |
|---|---|---|---|
| General Counsel | Risk & liability | AI governance reduces compliance exposure | "We don't know what data is being sent where" |
| CFO | Cost & ROI | Hours saved × fully-loaded cost = concrete number | "We have no way to measure this" |
| CHRO / VP HR | People & culture | AI augments staff, reduces burnout on rote work | "This will scare our people" |
| VP Sales | Pipeline & speed | Faster proposals, better research, more at-bats | "My team won't use another tool" |
| VP Engineering | Quality & scale | Code review, documentation, test coverage | "We can build this ourselves" |
Run a monthly AI capability briefing
20 minutes monthly · Audience: Full leadership team
This is not a tech update — it is a strategic signal that the organization is paying attention and moving with intentionality.
Generate a 20-minute leadership team AI briefing for [month/year]. Our organization: [type, size, sector] Current AI use cases in flight: [list from use case registry] One thing that worked well this month: [describe] One thing we tried that did not work: [describe] Structure the briefing as: 1. WHAT WE LEARNED (5 min) — one internal win, one honest failure, one lesson 2. WHAT IS CHANGING (10 min) — two external AI developments relevant to our sector 3. WHAT WE ARE DECIDING (5 min) — one governance or adoption question needing leadership input Tone: direct, evidence-based, no hype. Assume the audience is intelligent and skeptical.
Pillar 05
Build your personal AI feedback loop
BCG's research on "trailblazer" AI organizations found that the highest performers share one defining behavior: they test AI ambitiously, reach its limits deliberately, and update their strategy based on what they learn — repeating the cycle faster than competitors. BCG, January 2026
Keep a personal AI observation log
5 minutes per day
Create a second Claude Project titled "My AI Learning Log." After each significant AI-assisted task, spend five minutes capturing what happened.
Today I used Claude for: [task] What the AI did well: [describe] Where I had to override or correct it: [describe] What it could not do at all: [describe] Time saved (estimate): [minutes] Would I use AI for this task again? [yes / yes with modification / no] Based on my log entries to date, what patterns are emerging about where AI is and is not useful in my specific role? Identify three categories where I should lean in more, and one where I should add more human oversight.
Research grounding
UNC Kenan-Flagler research found that AI mistakes carry a disproportionate trust cost. Your log is how you build a calibrated sense of exactly when human oversight is non-negotiable. Source →
Run a quarterly AI capability audit on yourself
90 minutes quarterly
This is the CoS equivalent of a performance review — except you are evaluating both yourself and the tools.
Here is a summary of how I have used AI this quarter: Tasks: [list the main categories of work you used AI for] Biggest wins: [describe 2-3] Biggest failures or corrections needed: [describe 2-3] Current Claude model limitations I've hit: [describe] Answer these four questions: 1. Which tasks am I still doing manually that AI could handle if I invested 30 minutes in a better prompt? 2. Which tasks did I delegate to AI that should have more human oversight? 3. What is one AI capability I have not tried yet that is probably relevant to my role? 4. Based on my pattern of use, what does a more advanced version of my AI practice look like next quarter? Be direct. I want a 90-day improvement plan, not a compliment.
Appendices
Appendix A
Why a Human in the Loop Is Not Optional
"The DNA of work is being rewritten by AI. CEOs must go beyond deploying tools and help their organization reimagine the nature of work itself."
— BCG CEO Survey, January 2026 · bcg.com
Accountability
Agents produce outputs. A Chief of Staff owns outcomes. Organizations need a named human who will raise their hand when an AI is confidently wrong — and who absorbs the accountability when a recommendation fails.
Research from UNC Kenan-Flagler found that AI mistakes carry a disproportionate trust cost. When an agent produces a flawed board document, stakeholders question the entire AI practice.
↗ UNC Kenan-Flagler — Decision-Making Beyond AIPolitical intelligence
Organizational power, informal alliances, unspoken tensions, and undisclosed agendas are invisible to any AI trained on documents. The CoS navigates the organization as a social system.
Fortune's reporting found that orchestration roles managing human-agentic workforces require "the core skills of logic, ethics, rhetoric, and communication" — competencies that describe a seasoned CoS, not an agent.
↗ Fortune — AI is Changing the Corporate Org ChartEthical judgment
Peer-reviewed research is unambiguous: AI systems can produce more or less ethical outcomes depending on design, but they cannot be ethical decision-makers in their own right.
This is not a technology gap that a better model will close. It is a category distinction: ethics is a human accountability, not an AI capability.
↗ PMC / NUS Business SchoolTrust transmission
Research from the 2024 ACM CHI Conference found that trust in AI-integrated systems is shaped more by other human actors than by the system's features.
Replace the CoS who built the governance, ran the trust ladder, and narrated the corrections with an agent — and the trust infrastructure collapses.
↗ ACM CHI 2024 — Trust in AI-Assisted Decision MakingThe direct argument for your CEO or C-suite leader
The C-suite instinct to replace a CoS with AI agents usually rests on a misdiagnosis: equating the CoS role with its most visible outputs — meeting agendas, briefings, action logs. Agents can handle those. But those outputs are not the job.
The job is judgment under ambiguity in a social system. It is knowing which stakeholder meeting is really about something else. It is being the person the CEO calls at 8pm when a board relationship is fraying and they need to think out loud with someone they trust.
The AI-pilled CoS is not the person agents replace. They are the person who makes agents worth having — directing them, quality-checking them, and translating their outputs into decisions that real organizations are willing to act on.
Appendix B
AI Governance Template for the CoS
| Governance area | Policy decision | Owner | Review cadence |
|---|---|---|---|
| Approved tools | Claude (Anthropic) and [list others] are approved. All others require CoS + CTO sign-off before use. | CoS + CTO | Quarterly |
| Data classification | Internal documents: permitted. Personal employee data: never. Legal privileged comms: never. Board materials: summarize only. | CoS + General Counsel | Bi-annual |
| Output review | All AI-generated content going to the board, external parties, or the CEO must have human review. Internal drafts may go direct. | Content owner | Standing |
| AI disclosure | Teams disclose AI assistance in documents for external publication. Internal use requires no disclosure. | Dept heads | As needed |
| Incident reporting | Any AI output that caused a significant error is reported to the CoS within 24 hours. No blame — learning only. | CoS | Ongoing |
| Experimentation permission | Any employee may test approved AI tools on internal, non-sensitive work without permission. Pilots involving external parties require CoS approval. | CoS | Quarterly |
Important
This template is a starting framework, not legal counsel. Before circulating as policy, have it reviewed by your General Counsel — particularly the data classification section.
Appendix C
The Trust Ladder
The CoS earns trust not by proving AI is perfect, but by being the person who ensures AI outputs are honest, accountable, and correctable.
Action
Start with one high-visibility, low-stakes task. Pick something the team sees regularly — a weekly meeting agenda or a department update — and improve it visibly using AI.
Trust outcome
Team sees the output is better. No one had to change their behavior. Curiosity replaces skepticism.
Action
Narrate one correction publicly. When Claude gives you something wrong or tone-deaf, tell the team: "AI drafted this, I caught this issue and changed it."
Trust outcome
Team learns that AI is supervised, not autonomous. Fear of runaway AI drops significantly.
Action
Invite one skeptic to co-create. Find your most vocal AI skeptic and ask for their help improving a prompt. Credit them publicly when it works.
Trust outcome
The skeptic becomes an advocate — or at minimum, stops being an obstacle.
Action
Establish a "no AI zone" with credibility. Declare explicitly which decisions will never have AI involvement — performance reviews, sensitive HR matters, crisis response.
Trust outcome
People trust AI more in the zones where it operates because you have proven you know where it should not.
Action
Publish one honest failure. After 60-90 days, share a brief internal retrospective: "Here is where AI helped us this quarter, here is where it did not, here is what we changed."
Trust outcome
Organizational trust reaches a new equilibrium. AI is a supervised, bounded, continuously improving tool with a named human accountable for it. That human is you.
Appendix D
Claude Enterprise & Protecting Your Data
Free / Pro / Max — Consumer tier
Personal consumer plans. Since September 2025, Anthropic allows optional data use for model training. Employees on personal accounts create "shadow AI" — proprietary data governed by weaker consumer protections.
Not recommended for organizational data.
Claude for Work — Team & Enterprise ✓
Operates under Commercial Terms which explicitly prohibit using your inputs to train models. The Enterprise plan adds audit logs, custom data retention, SCIM, and HIPAA-readiness.
Recommended for all workflows in this manual.
What Claude Enterprise includes
Sources & Further Reading
- BCG — When Companies Struggle to Adopt AI, CEOs Must Step Up (2025)
- BCG — As AI Investments Surge, CEOs Take the Lead (January 2026)
- Fortune — AI is Already Changing the Corporate Org Chart (August 2025)
- UNC Kenan-Flagler — Decision-Making Beyond AI (January 2026)
- PMC / NUS Business School — How AI Can and Cannot Help Organizations Become More Ethical
- ACM CHI 2024 — Trust in AI-Assisted Decision Making
- LSE Business Review — AI Can't Replace Human Leaders (January 2025)
- NTT DATA — 2026 Global AI Report (2,567 executives, 35 countries)
- Anthropic Help Center — Enterprise Plan details
- Anthropic — Consumer Terms Update (September 2025)
- Anthropic Trust & Compliance Center