A Practical Guide — Not a Strategy Book

Tactics for using AI to actually get your work done.

Short chapters. Concrete prompt templates. No jargon. Built for professionals and students who want to use AI as a working tool, not a novelty.

DRAFT — REVIEW COPY
CHAPTER 01

Prompting Fundamentals

From asking questions to delegating work.

Most people use AI like a search engine with better manners. They ask a question, get an answer, and move on. That's not wrong — but it's leaving most of the value on the table.

The shift that matters isn't learning clever "prompt hacks." It's a mental shift: from asking AI things to delegating work to it. Once you make that shift, the same tool that used to save you five minutes starts saving you five hours.

1. Say What You Want Done, Not What You Want to Know

Weak Prompt "What should I include in a project status report?"
Strong Prompt "Write a one-page project status report for my team's Q3 rollout. Use these three updates: [paste your rough notes]. Flag anything that sounds like a risk. Keep it to bullet points, no fluff."

The difference isn't politeness or length — it's that the second version hands over a finished task, not a question.

Try This Next time you're about to Google "how to write X," stop and instead ask an AI tool to draft X directly, using whatever raw material you already have. It's faster to edit a draft than to write one from a blank page.

2. Give It the Materials, Not Just the Instructions

AI tools are only as good as what you hand them. A request without source material forces the tool to guess — and guessing is where generic, off-target output comes from.

Strong Prompt "Here's our launch plan doc [paste it]. Summarize the three biggest risks in plain language, and for each one suggest a one-line mitigation."

If you have real data, a real document, a real spreadsheet — paste it in or upload it. Don't make the AI invent context you already have sitting in a file.

3. Set the Format Before You Need to Fix It

Getting the right format the first time saves more editing time than almost anything else.

Template "[Task]. Format it as [bullet points / a table / a short email / three short paragraphs]. Keep it under [length]. Tone should be [formal / casual / direct]."

Example: "Draft a follow-up email to a client who hasn't responded in two weeks. Format as an email with subject line. Under 100 words. Tone: friendly but direct."

4. Ask for the Reasoning When the Stakes Are Higher

For low-stakes tasks, just take the output. For higher-stakes ones — a financial decision, a technical fix — ask the tool to show its reasoning before you act on it.

Try This "Before you answer, walk through your reasoning step by step, then give me your recommendation."

5. Correct in the Same Conversation, Not From Scratch

If the output isn't right, don't start over — tell the AI what's wrong and let it revise. This habit alone separates people who feel AI "doesn't get it" from people who get consistently good results.

Correction "This is too formal — make it sound like I'm talking to a colleague, not writing a memo."

6. Delegate the Whole Task, Not Just a Piece of It

Instead of asking for a paragraph or an idea, hand over an entire deliverable and let the tool own it end to end.

Full Delegation "Here's my raw sales data [attach]. Build me a complete one-page summary report with a short narrative at the top, a table of the numbers, and three recommendations. Make it ready to send to my manager as-is."

The more complete the deliverable you ask for, the more time you actually save.

Quick-Reference: The Prompt Checklist

  • Did I ask for a finished thing, not just information?
  • Did I give it the actual materials it needs?
  • Did I specify format, length, and tone?
  • For anything high-stakes, did I ask it to show its reasoning?
  • Am I ready to correct and iterate, rather than accepting the first draft?
SHEET 01 / 07 THE AI PLAYBOOK — REV A
CHAPTER 02

Choosing Your Tool

A practical matrix for knowing which AI assistant to reach for — and when free tools are genuinely enough.

The Persistence Problem — Why Redoing Work Is the #1 AI Time-Waster

A tech reviewer recently described losing hours of work in Gemini simply because there was no easy way to pick up a past project — every session felt like starting over. That single complaint points at the most underrated feature category in AI tools: not raw intelligence, but whether the tool remembers where you left off.

Every major AI assistant has now taken a swing at this problem — but they've landed in very different places. Here's the honest, apples-to-apples comparison:

ToolWhat it offersHow it works
GeminiLibrarySaves generated docs/images/video, links back to the original chat, can turn saved material into quizzes or study guides
ChatGPTLibrarySaves every uploaded/created file in a sidebar tab; "Add from Library" reuses it in any new chat; storage scales with your plan
ClaudeProjects + Artifacts + MemorySame problem solved with three separate tools instead of one: a persistent knowledge base (Projects), revisitable/editable outputs (Artifacts), and auto-summarized context (Memory)
DeepSeekNoneNo cross-session memory or file library — every chat starts from zero. Widely flagged by users as its biggest gap
Try This Before starting any multi-session project — a report you'll revise over weeks, a client deliverable with several drafts — check whether your tool has a persistence feature and turn it on deliberately. Don't rely on scrolling back through old chats to find your own work.

Free vs. Paid — What You Actually Need

Free tiers of every major assistant can draft emails, summarize documents, and answer everyday questions competently. Paying unlocks three things specifically: longer memory/context, higher usage limits, and access to the strongest reasoning models for genuinely hard problems. If your work is mostly quick, everyday tasks, free is enough. If you're doing sustained project work — the kind this book is about — a paid tier on at least one tool pays for itself within the first real deliverable it saves you from redoing.

The Task-to-Tool Matrix

TaskReach for
Quick fact-check, everyday questionAny tool — no meaningful difference
Long project you'll return to over days/weeksWhichever has the strongest persistence feature for your plan (see table above)
Image generationChatGPT or Gemini — Claude doesn't generate images
Precise document/spreadsheet formattingWhichever tool your workplace already standardizes on — consistency beats marginal quality gains
Sensitive or high-stakes workRead the tool's data policy first — this matters more than model quality

Quick-Reference Checklist

  • Do I know which tool I'm using has a persistence/library feature, and is it turned on?
  • Am I paying for capability I actually use, or just habit?
  • For this specific task, does the tool I'm using actually matter — or am I overthinking a simple question?
SHEET 02 / 07THE AI PLAYBOOK — REV A
CHAPTER 03

Delegating Real Work

Writing, research, and document generation — with before/after prompt examples.

NOT YET DRAFTED
SHEET 03 / 07THE AI PLAYBOOK — REV A
CHAPTER 04

Automating the Repeatable

Turning recurring tasks into set-it-up-once workflows.

NOT YET DRAFTED
SHEET 04 / 07THE AI PLAYBOOK — REV A
CHAPTER 05

Working With AI on a Team

Multi-agent thinking, made simple, for group projects and shared work.

NOT YET DRAFTED
SHEET 05 / 07THE AI PLAYBOOK — REV A
CHAPTER 06

When AI Gets It Wrong

Verification habits, outage resilience, and avoiding overconfidence in AI output.

NOT YET DRAFTED
SHEET 06 / 07THE AI PLAYBOOK — REV A
CHAPTER 07

A Starter Toolkit

Cheat sheets, prompt templates, and quick-reference tables to keep at hand.

NOT YET DRAFTED
SHEET 07 / 07THE AI PLAYBOOK — REV A
Recent Changes — Chapter 2
MAR 23, 2026 OpenAI launches Library in ChatGPT — saves all uploaded/created files in a persistent sidebar tab, reusable across chats.
2026 Google's Gemini Library lets users resume past generated work directly, avoiding the redo-from-scratch problem covered in this chapter.