Most people who try an AI assistant fall into one of two traps.

The first trap: they use it for trivial tasks. Writing a quick email. Looking something up. Drafting a paragraph. Useful, but not transformative. The tool becomes a novelty rather than infrastructure.

The second trap: they try to hand over things that require judgement, relationships, or accountability. The AI produces something plausible but wrong. They lose confidence. They scale back. The tool sits unused.

The value of an AI Chief of Staff comes from knowing exactly where the line is — what it should handle completely, what it should support, and what should stay with you.

Delegate Completely: The Operational Overhead Layer

These are tasks where the output is routine, the value is in consistency, and human judgement adds little.

The morning briefing. Every day, Steve builds your operational picture: weather, news relevant to your industry, tasks due today, calendar items, portfolio or business metrics, and one suggested priority. This is information assembly — time-consuming for a human, trivial for an AI with the right data. You read it; Steve builds it.

Task tracking and overdue flagging. The open loops — proposals sent, commitments made, projects started — accumulate faster than any one person can track without a system. Steve holds them all and surfaces what's overdue. You don't have to remember to check. Steve tells you when something needs attention.

Contact logging. After a meeting or call, tell Steve who you met, what was discussed, and what's next. Steve stores it, timestamps it, and flags the relationship when it's been too long since contact. The follow-up happens because Steve remembers, not because you do.

First drafts of structured documents. Reports, memos, competitive analyses, briefing documents, research summaries. Steve produces a well-structured first draft that reflects what it knows about you, your context, and what you need the document to accomplish. Your time goes to editing for accuracy and judgement, not building structure from scratch.

Information synthesis. "Give me a summary of everything we've discussed about Project X." "What were the key points from my intake about the business?" "What tasks are overdue and what's the pattern?" Steve answers from the context it holds. You don't have to dig.

Delegate With Review: Where AI Supports Human Judgement

These are tasks where Steve does the analysis and preparation, but the final call is yours.

Strategic options. "What are three ways to approach the pricing decision?" Steve can lay out frameworks, trade-offs, and implications. But the decision — which involves culture, relationships, timing, and things Steve doesn't fully know — is yours to make. The briefing is AI; the call is human.

Communication drafts that carry weight. Steve can draft a difficult email, a client response, or a negotiation position. But anything that carries your name and involves real stakes — a client you're trying to save, a partnership you're building — needs your eyes before it goes. Use Steve to avoid the blank page; don't use Steve to replace your voice.

Risk identification. "What could go wrong with this plan?" Steve is useful for surfacing second-order consequences and common failure modes. It's not a substitute for the industry-specific risk knowledge you've built. Use the prompts, test them against your experience.

Meeting preparation. Steve can pull together what you know about someone before a meeting — their background, your previous conversations, what you know about their business. Useful. But the meeting itself, the reading of the room, the relationship — that's yours.

Keep for Yourself: What Should Never Be Delegated

Decisions with significant downside. Any decision where being wrong is costly — people decisions, major capital allocation, legal choices — should be made by you. Steve can inform the decision. Making it is not Steve's job.

Relationship management at depth. Steve can log your contacts and flag when it's time to reach out. But the actual relationship — the call, the meeting, the conversation that builds trust — requires a human being. AI manages the logistics of relationships. It doesn't build them.

Accountability. Steve tracks your tasks. It doesn't own them. The commitment you made, the outcome you're responsible for — that's yours. Steve is the system that reminds you. You're the person who delivers.

Judgement under uncertainty. When the data is ambiguous, the situation is novel, and there's no clear answer — that's when human judgement earns its keep. Use Steve to structure the thinking. The call is still human.

How to Think About the Division of Labour

A useful heuristic: delegate anything where the primary value is not forgetting, not missing something, or building something from structure rather than insight.

Keep anything where the primary value is judgement, relationships, or accountability.

In practice, this means Steve handles your operational infrastructure — the briefings, the tracking, the documents, the synthesis — while you handle the decisions, the relationships, and the outcomes.

That division is what a Chief of Staff is for. AI has made it accessible to people who never had one.