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 COPYPrompting 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
The difference isn't politeness or length — it's that the second version hands over a finished task, not a question.
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.
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.
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.
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.
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.
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?
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:
| Tool | What it offers | How it works |
|---|---|---|
| Gemini | Library | Saves generated docs/images/video, links back to the original chat, can turn saved material into quizzes or study guides |
| ChatGPT | Library | Saves every uploaded/created file in a sidebar tab; "Add from Library" reuses it in any new chat; storage scales with your plan |
| Claude | Projects + Artifacts + Memory | Same problem solved with three separate tools instead of one: a persistent knowledge base (Projects), revisitable/editable outputs (Artifacts), and auto-summarized context (Memory) |
| DeepSeek | None | No cross-session memory or file library — every chat starts from zero. Widely flagged by users as its biggest gap |
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
| Task | Reach for |
|---|---|
| Quick fact-check, everyday question | Any tool — no meaningful difference |
| Long project you'll return to over days/weeks | Whichever has the strongest persistence feature for your plan (see table above) |
| Image generation | ChatGPT or Gemini — Claude doesn't generate images |
| Precise document/spreadsheet formatting | Whichever tool your workplace already standardizes on — consistency beats marginal quality gains |
| Sensitive or high-stakes work | Read 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?
Delegating Real Work
Writing, research, and documents — with before/after prompts you can copy directly.
Writing: From "Help Me Write" to "Here's My Draft, Fix It"
The biggest quality jump in AI writing help comes from giving it a rough draft to improve rather than a blank request to generate from nothing. Your own voice and specifics are worth more than the AI's default phrasing.
Even a two-sentence rough draft anchors the output in your actual situation instead of a generic template.
Research: Ask It to Show Its Sources
AI research tools with web access can save real time — but only if you build in a verification step instead of trusting the first answer.
If a tool can't browse the web, treat anything about current events, prices, or recent developments as a starting point to verify — not a final answer.
Documents and Spreadsheets: Delegate the Structure, Not Just the Words
Most people ask AI for content and then manually build the document around it. Skip that step — ask for the finished, formatted deliverable directly.
Slides and Presentations
Ask for the outline first, review it, then ask for the full slides — this two-step approach catches structural problems before you've generated all the content.
Quick-Reference Checklist
- Did I give it a rough draft or real notes instead of a blank request?
- For research, did I ask for sources and confidence flags?
- Did I ask for the finished, formatted deliverable — not just raw content I'll assemble myself?
- For anything long or structural, did I review an outline before generating the full thing?
Automating the Repeatable
Turning recurring tasks into set-it-up-once workflows.
NOT YET DRAFTEDWorking With AI on a Team
Multi-agent thinking, made simple, for group projects and shared work.
NOT YET DRAFTEDWhen AI Gets It Wrong
Verification habits, outage resilience, and avoiding overconfidence in AI output.
NOT YET DRAFTEDA Starter Toolkit
Cheat sheets, prompt templates, and quick-reference tables to keep at hand.
NOT YET DRAFTED