← Back to all free guides Save This

Train Your Brain
To Get Good At AI

Smooth practice feels productive and teaches you almost nothing. Five ways to practice so it sticks, plus the 30-day plan.

Here is the finding that should change how you practice: how well you perform while you are learning and how much you actually learn are two different things. They can even run in opposite directions.

That comes out of decades of work by Robert and Elizabeth Bjork at UCLA on what they named desirable difficulties. When you make practice smooth, your performance in the moment looks great and your retention later is poor. When you make practice harder in specific ways, you look worse today and you keep it.

Which explains something you have probably felt. You watch a tutorial, copy the prompt, get a great result, and feel like you learned something. A week later you cannot rebuild it. You did not learn it. You watched someone else learn it.

Below are the five ways to practice, the named effect behind each one, and a 30-day plan you can actually run.

The Five Moves

One

Train One Thing, Not Everything

Your brain adapts to what you repeatedly ask it to do, so asking it to do twelve things builds twelve shallow paths.

How to do it: pick one capability and commit to twenty reps of it. Writing ads. Cleaning and reading data. Building an agent. Turning a call into a plan. The test: if you cannot name your one thing in four words, you have not picked one. People who spread across five tools for a month end up with five logins and no skill.

Two

Keep The Struggle In

This is the generation effect. Attempting something before you see the answer builds a stronger memory than reading the answer first, even when your attempt is wrong.

How to do it: before you copy anyone's prompt or skill, write your own version first. Badly is fine. Then compare. What you get: the comparison teaches you something the finished prompt never could, which is why yours fell short. Copying first deletes that entirely.

Three

Space The Reps

The spacing effect. The same total practice time spread across days beats the same hours crammed into one sitting, and it is one of the most replicated findings in learning research.

How to do it: thirty minutes a day beats a four-hour Saturday binge, and it is not close. Why it works: the small amount of forgetting between sessions is the point. Retrieving something you had half-lost is what strengthens it. A binge never lets you forget anything, so nothing gets strengthened.

Four

Force Retrieval

The testing effect. Pulling something out of your head builds the memory. Reading it again mostly builds confidence.

How to do it: close the tutorial, open a blank chat, and rebuild the thing from memory. The uncomfortable part: you will get it wrong and it will feel like failing. A meta-analysis across 29 studies found retrieval practice and spacing improved learning with an effect size of 0.74, which in this field is large. The discomfort is the mechanism, not a sign it is not working.

Five

Turn The Gap Into The Lesson

Reps without review just make you fluent at your own bad habits.

How to do it: when you finally get a result you like, put your first attempt and your final one side by side and make the AI name what changed. What you get: the difference between the two is the actual lesson, and it is the only part worth writing down. The exact prompt for this is in the plan below.

The Trap

Everything on this list feels worse than watching a tutorial. That is how you know it is the right list. Smooth practice is the feeling of your short-term performance going up while your actual learning goes down.

The 30-Day Plan

Thirty minutes a day, five days a week, four weeks. One capability the whole time. Each week changes what kind of hard it is, on purpose.

The 30-Day AI Practice Plan
DAY 0: PICK YOUR ONE THING (10 minutes) Finish this sentence in four words or less: "I am getting good at ______." Good: writing cold emails. Reading ad data. Building one agent. Turning calls into plans. Too broad: using AI. Getting better at prompting. Automating my business. Then write down where you are today, honestly: - What can I do right now without help? - What do I always need a tutorial or a copied prompt for? - What would "good at this" look like in 30 days, in one observable sentence? Keep a single file called reps-log. Every session gets three lines: what I tried, what broke, what I would do differently. That file is the whole system. WEEK 1: ATTEMPT BEFORE YOU LOOK (the generation effect) Rule for the week: you are not allowed to look at anyone else's prompt or skill until you have written your own version first. Daily, 30 minutes: 1. Pick one real task from your actual work. Not a practice exercise, a real one. 2. Write your prompt cold. No searching, no examples. 10 minutes, then stop. 3. Run it. Save the output. 4. NOW go find how someone else does it, or ask AI directly: "Here is my prompt and the output it produced. Rewrite the prompt the way an expert at [YOUR ONE THING] would write it. Then list the specific differences between mine and yours, and for each difference explain what it changes about the output. Do not be polite about it." 5. Three lines in the reps-log. End of week: you should have 5 side-by-side comparisons. Read them in one sitting and write the three mistakes you made more than once. WEEK 2: BUILD IT FROM MEMORY (the testing effect) Rule for the week: nothing open. No tabs, no notes, no old chats. Daily, 30 minutes: 1. Open a blank chat. 2. Rebuild last week's best prompt or workflow entirely from memory. It will be worse. That is expected and it is the point. 3. Only after you have finished, open the original and compare. 4. Ask: "What did I leave out of my rebuild, and which of those omissions actually mattered to the output?" 5. Three lines in the reps-log. Twice this week, do a cold recall with no building at all: "Quiz me on [MY ONE THING]. Ask me one question at a time, wait for my answer, and tell me what I got wrong before the next question. Ask the things a person would actually need to know to do this well, not trivia." WEEK 3: CHANGE THE CONTEXT (interleaving and varied practice) Rule for the week: same skill, different situation every single day. Do not let it get comfortable. Daily, 30 minutes: 1. Same capability, new context. If you are practicing cold emails: a different industry, a different length, a hostile audience, a follow-up instead of a first touch, a version for someone who already said no. 2. Halfway through the week, add a constraint that removes your crutch. Half the words. No examples given. A tool you do not usually use. 3. Ask once this week: "Give me five situations where the approach I have been using for [MY ONE THING] would actually fail. Then have me try the hardest one." 4. Three lines in the reps-log. WEEK 4: SHIP IT AND TEACH IT Rule for the week: it has to leave your computer. Days 1 to 3: use it on something real with a consequence. Send the email. Run the analysis your team sees. Deploy the agent on a real task. Day 4: teach it. Write the explainer, record the voice memo, or walk a coworker through it. Teaching is retrieval with stakes, and it will expose every gap you have been sliding past. Day 5: the review. Open the reps-log and paste this in: "Here is my full practice log from 20 sessions learning [MY ONE THING]. Compare my earliest attempts to my most recent ones. Tell me: 1) what specifically improved, with evidence from the log, 2) what mistake I am STILL making that shows up more than twice, 3) the one habit that produced the biggest jump, and 4) what my next 30 days should focus on, and why that and not something else. Be direct. I want the pattern I cannot see." THE RULE THAT MAKES OR BREAKS IT A day where you copied someone's prompt and it worked is not a rep. A rep is a day where you tried, it fell short, and you found out why. Twenty of those beats a hundred tutorials.
What This Will Not Do

This will not make you good at AI in general. It makes you good at one thing, and the reason to accept that trade is that one real capability is worth more at work than a shallow familiarity with nine tools.

It also will not feel good for the first two weeks. Week two is where most people quit, because rebuilding from memory feels like going backwards while copying a working prompt feels like progress. That feeling is exactly backwards, and knowing that in advance is most of what it takes to push through it.