Field Notes
10 AI Pro Tips Most Users Miss
I run my consulting practice, my automations, and most of my working day through AI. These ten habits came out of 900+ real working sessions: the ones that paid back the most for the least effort, ranked. None of them require a specific tool.
The short version: the biggest gains come from treating AI like a system you manage, not a chat you have. Make it prove tasks are complete, write your preferences down once, turn every mistake into a permanent rule, and have it verify its own work in a fresh session. Everything below is a one-sentence habit anyone can start today.
Tip 1 · Highest ROI
Never accept "done." Demand a completion audit
The most common AI failure isn't a wrong answer. It's a silent skip: you ask for 12 things, the AI does 9, and reports the task complete. On short tasks you catch it. On long ones (renaming 200 files, updating every page, processing a spreadsheet) the skip hides in the volume, and you find it weeks later.
The fix costs one sentence. Require a count. Require that skips be named. And require the word "none" when nothing was skipped, because omission is exactly how skips hide. Once the AI has to write "processed 11 of 12, skipped row 84 because the date field was empty," it can no longer wave the task through, and neither can you.
I now end every multi-step request this way, and I build it into every automated workflow I ship to clients. It is the cheapest quality gate that exists.
Copy-paste
"Before saying you're done: report the exact count of items processed vs. requested. Name anything skipped or only partially done, and why. If nothing was skipped, write 'none.' Only say 'complete' if the counts match."
Tip 2
Write your preferences once, in a file the AI always reads
Most people re-type the same corrections for months. "Shorter." "No bullet points." "Always ask before deleting." Every modern AI tool has a place for standing instructions: custom instructions in ChatGPT, project instructions in Claude, a CLAUDE.md file in coding tools. Almost nobody uses it seriously.
Treat that file as your personal operating manual. Mine covers output format, tone, what the AI must always ask before doing (anything irreversible), what it should push back on, and what "good" looks like for my common tasks. One edit upgrades every future conversation, forever. That compounding is why this ranks second: five minutes of writing saves a correction you'd otherwise make hundreds of times.
Start small. After your next three chats, notice what you corrected, and move those corrections into the file.
Copy-paste
"Based on everything I've corrected in this conversation, draft a set of standing instructions I can save so future chats get it right the first time."
Tip 3
Turn every AI mistake into a permanent rule
Correcting the AI in chat fixes today. It does nothing for tomorrow, because the next session starts blank. The habit that changes everything: when the AI gets something wrong, have it update your standing instructions right then, in the same conversation, while the failure is concrete.
I learned this the hard way. For weeks my feedback was "captured" in notes that never made it back into the instructions, so the same mistakes kept returning. The rule that fixed it: feedback isn't done until it's written into the file the AI actually reads. Now each failure happens once, becomes a rule, and stays fixed. My instruction files read like scar tissue, and that's exactly what makes them valuable.
Pair this with tip 2 and your setup gets measurably better every single week, without any extra effort beyond corrections you were already making.
Copy-paste
"You got X wrong. Write a one-line rule that would have prevented this, and add it to my standing instructions now. Show me the exact line you added."
Tip 4
Ask the AI to write the prompt before it does the work
For anything non-trivial, don't start with the task. Start with: "interview me, then write the prompt you'd want for this task." The AI asks you questions you hadn't considered (audience, edge cases, format, what failure looks like), turns your vague intent into explicit requirements, and hands you a prompt you can review before any work happens.
You get three payoffs. The output quality jumps, because ambiguity got resolved up front instead of discovered in draft four. You get a reusable artifact: save the prompt and run it again next month, or on a schedule. And you learn what a good prompt for that job even looks like, which makes you sharper on every future ask.
I keep a folder of these. My weekly review, my daily prioritizer, and my research runs all started as prompts the AI wrote for me, then refined over a few iterations. Prompting the AI to prompt itself is the cheapest quality upgrade there is.
Copy-paste
"Before doing anything: interview me one question at a time about what I actually need. Then write the full prompt you would want to receive for this task, and wait for my sign-off."
Tip 5
Verify in a fresh chat, not the same one
Asking "are you sure?" in the same conversation is theater. The context that produced the answer will reproduce the answer. The same reasoning, the same assumptions, the same blind spots are all still sitting there, and the AI will mostly agree with itself.
Real verification is structural: open a new chat, give it only the source material (not the first chat's conclusions), and ask it to do the check cold. Numbers get re-derived from the source. Claims get re-checked against the document. If the two sessions agree, your confidence is earned. If they disagree, you just caught an error that no amount of same-chat double-checking would have surfaced.
I do this for anything with real stakes: financial figures, client deliverables, anything I'd be embarrassed to get wrong. It takes two minutes and has caught errors that would have cost me far more than two minutes.
Copy-paste (in a new chat)
"Here is a source document and a set of claims someone derived from it. Independently verify each claim against the source. Don't assume the claims are right. Report PASS or FAIL per claim, with the evidence."
Tip 6
Make the AI write to files, not just chat
Chats scroll away and context windows forget. Anything worth keeping (decisions, plans, statuses, research) should land in a durable document the moment it exists: a Google Doc, a Notion page, a markdown file. Have the AI checkpoint as it works, not summarize at the end after the good details have already been compressed away.
The highest-value version of this is the handoff file. Before closing a long session, have the AI write a short brief for its own successor. The instruction that makes it work: synthesize, don't summarize. "We discussed X" is useless. "Decided X because Y, next step is Z, open question is W" lets tomorrow's session pick up in thirty seconds instead of thirty minutes of re-explaining.
Once your projects live in files instead of chat history, switching tools, models, or sessions stops costing you anything.
Copy-paste
"Write a handoff note for a future session: what we decided and why, what's in progress, exact next steps, and open questions. Synthesize what matters for continuing, don't summarize what we talked about."
Tip 7
Buy discipline, not intelligence
When output disappoints, most people reach for a bigger model. Usually the problem isn't intelligence, it's process. A mid-tier model following explicit gates (restate the task, list what you'll check, verify before claiming done) routinely beats a frontier model freestyling.
So give every task a checklist shape: what does done look like, what will you verify, what's out of scope. Then route by difficulty. Expensive models earn their cost on judgment: scoping the problem, attacking a draft, final review. Cheap or fast models handle the mechanical middle: extraction, formatting, first drafts, bulk processing. And regardless of the model, never accept "done" without seeing the output itself, because a confident summary is not an artifact.
This is also the budget answer. Discipline transfers to whatever model you can afford; intelligence you rent by the token.
Copy-paste
"Before starting: restate the task in your own words, list the steps you'll take, and name what you'll check at the end to confirm it worked. Then proceed."
Tip 8
When output quality varies, remove the freehand
If the AI produces a great report on Tuesday and a sloppy one on Thursday, the instinct is to prompt harder on Thursday. Wrong lever. Inconsistency means the AI is improvising something that should be standardized: the structure, the format, the checks.
Build the fixed part once: a template it must fill in, a checklist it must run, a scoring rubric it must apply, an example of "good" it must match. Then the AI's variability gets spent where it helps (the thinking, the analysis, the writing) instead of where it hurts (whether the executive summary exists this week). The judgment stays with the AI; the consistency comes from the harness.
Every recurring output I produce (reports, briefs, reviews) runs through a template with a required-sections check at the end. Quality stopped depending on the AI's mood the day it ran.
Copy-paste
"Turn this output into a reusable template with required sections and a final checklist that verifies every section is present and complete. I'll use it every time from now on."
Tip 9
Automated AI must fail loud
The moment you schedule AI to run without you (daily digests, monitors, report generators), the danger changes. It's not crashing; you'd notice a crash. It's the job that exits cleanly while producing nothing, or half of something, and no one notices for three weeks.
Two rules cover it. First, no silent failure paths: every automation should alert you when something goes wrong, never quietly skip, queue, or retry into the void. Second, add a watchdog: a separate scheduled check that verifies the output actually exists and looks right (the file is there, it's a sane size, today's date is on it). The watchdog catches the case where the job died before its own error handling could run.
I run this belt-and-suspenders pattern on everything unattended, after learning the expensive way that a silently stale automation can do real damage before anyone notices.
Copy-paste (for any scheduled task)
"If any step fails or produces empty output, send me an alert saying exactly what failed. Never skip silently. Also: create a second scheduled check that verifies today's output exists and is complete, and alerts me if not."
Tip 10
Point the AI at yourself, on a schedule
Everyone uses AI to do work. Almost no one uses it to examine how they work. Once a week, have it review your recent activity (task lists, notes, calendar, whatever it can see) and answer questions no productivity app will: What am I avoiding? What keeps reappearing without progress? Where is my effort going versus where I said my priorities were?
The upgrade that makes it bite: an escalation rule. Anything flagged three weeks running stops being an observation and becomes a forced decision: commit to it this week or drop it deliberately. That one rule is the difference between a pleasant weekly summary and a review that actually changes behavior.
Mine has caught patterns I genuinely couldn't see from the inside, including a stretch where most of my effort was going into polishing tools instead of the work the tools were built for. An honest mirror, on a schedule, is one of the most underused things AI can be.
Copy-paste (weekly)
"Review my week. This is an analysis, not a status report: what am I avoiding, what's appeared multiple weeks without progress, and where did my time go vs. my stated priorities? Anything flagged three weeks running: force me to a yes/no decision on it."
Frequently asked questions
What is the single highest-ROI way to get better results from AI?
Demand a completion audit. One added sentence (count what you processed, name what you skipped, write "none" if nothing) catches the most common failure: the AI silently skipping items and reporting the task complete.
Do these tips require a specific tool like ChatGPT or Claude?
No. All ten are tool-agnostic habits that work in ChatGPT, Claude, Gemini, Copilot, and anything else. A few are easiest in tools with persistent instructions or scheduling, but the habits transfer everywhere.
Why verify in a fresh chat instead of asking "are you sure?"
Because the context that produced an answer will reproduce it. A new chat, given only the source material, checks the work cold. Disagreement between the two sessions is a signal you can't get any other way.
Request a Discovery Session ↗