This book is short on purpose.

A lot of beginner guides about AI try to teach you everything at once. They show you fifty tools, twenty prompts, and a hundred tips. By the end you feel busy, but you don’t feel ready. You don’t actually know what to do on Monday morning.

This book does something different. It gives you six ideas. Just six. Each one is something I learned by building real things with AI: websites, tools, brands, content systems. Each one is something that, once you understand it, will save you weeks of confusion. The tools are the easy part. The thinking is what makes the tools actually work.

I’m not going to teach you every prompt I use. I’m not going to walk you through every tool. That’s what the Direct the Work Library is for. The point of this book is to give you the way of thinking. Once you have the way of thinking, the tools and the prompts make sense. Without it, no tool will save you.

One last thing before you start. The AI tools are moving fast. Claude has Skills now. ChatGPT has custom GPTs. Gemini has Gems. Most major platforms have ways to save instructions, load context, and run reusable workflows automatically. The tools are catching up to the thinking I’m about to teach you. That’s a good thing. But here’s the part most people miss: those tools are accelerators. They make the work faster. They don’t replace the work. A reusable workflow built on shaky thinking breaks the first time your situation doesn’t fit the template. The foundation in this book is what makes the modern tools actually deliver. Learn the thinking first. The tools follow.

One thing about the format you’re reading this in. You’re reading this book inside an app I built. That was intentional. The book teaches a way of thinking about AI work. Directing, verifying, shipping, pausing, treating your work as a system. Delivering the book itself as an app I built using that same thinking felt like the only honest way to ship it. If the format makes the message land harder, good. That was the point.

A few things you should know about me:

If you are new to using AI for real work, this book is for you. You should be able to read it in one sitting. When you finish, you will know more than most people who claim to be using AI.

Let’s go.

There’s a way most people use AI when they first start. They put in a request, press a button, and take whatever comes out. That’s the starting place for everyone. This book is about what comes after.

Here is the difference. There is a person who tells AI to do something and just takes whatever comes back. And there is a person who tells AI to do something, looks at what comes back, decides what is wrong with it, and then tells the AI exactly how to fix it. The first person is delegating. The second person is directing.

When you delegate to AI, you get average. Average words. Average ideas. Average everything. Because the AI does not know what makes your work yours. It only knows what most people would write. And most people are average. That is what “average” means.

But you are not starting from average. You have years of work behind you. Things you have figured out, problems you have solved, judgment nobody wrote down. That is what AI cannot bring to the table. That is what you bring. Directing is how it gets into the work.

When you direct AI, you stay in charge. You decide what is good. You decide what is wrong. You decide what to keep and what to throw out. The AI gives you something to react to, but you are the one who shapes it.

Here is what this looks like in real life.

That is directing. The first answer was a starting point. The fourth answer was the work.

If you only learn one thing from this book, learn this. AI is not a person who finishes your work for you. AI is a tool you use to make your work faster. The work is still yours. You still have to think. You still have to judge. You still have to decide.

People who treat AI as a finisher end up with content that is technically fine and completely forgettable. People who treat AI as a tool they direct end up with work that is fast, sharp, and theirs.

The rest of this book is about how to be the second kind of person.

Before you build anything with AI, you have to know what your voice sounds like.

A lot of people skip this step. They jump straight to building. They make a website, write some posts, set up a newsletter. Then they wonder why nothing they make feels like them. Or worse, they like what they made, but no one else seems to care about it.

The reason is voice. Voice is how you sound. It is the words you use. The words you never use. The way you start a sentence. The way you end one. The feeling someone gets when they read what you wrote. Voice is the difference between a brand that feels like a person and a brand that feels like a website.

If you do not tell AI what your voice is, it will give you the voice of the average person on the internet. That is what “average” sounds like. Bland.

So before you start building, you write down your voice.

First, write down what your voice does. Is it warm? Direct? Funny? Calm? Sharp? Pick three or four words and decide what your voice is.

Second, write down what your voice does not do. This is more important than the first part. My voice does not use therapy words. My voice does not use hustle culture words. My voice does not call anyone “queen” or “bestie.” The list of what your voice does not do is what keeps it from drifting into the average.

Third, you need real examples of your voice for AI to learn from. There are two ways to get those examples.

The first way works if you have already written things that sound exactly like you. Texts. Emails. Posts. Old journal entries. Anything where you re-read it and think, that’s me. Pull two or three of those and save them. You are going to give them to the AI later.

The second way works if you don’t have written examples, or if what you have written doesn’t actually capture the way you really sound. This is more common than people admit. A lot of us write differently than we think. The voice we want for our brand is closer to how we talk to a friend than how we write to a coworker.

If that’s you, there is a different approach that uses conversation with AI to bring your real voice out and capture it. It works. It’s actually how I built mine.

Either way, written examples or the conversational approach, what you end up with is your voice document. It does not need to be long. One page is enough. The point is that it exists.

Once you have a voice document, every piece of work you do with AI gets better. You paste your voice document into a chat. You give the AI a job. The AI does the job in your voice instead of in average voice. Your output sounds like you, not like everyone.

If you skip this step, every other thing in this book is harder. The directing in Chapter 1 has nothing to direct toward. The verifying in Chapter 4 has nothing to compare against. The whole system rests on the voice document.

This is why I am putting it second. Right after “don’t be lazy with AI,” the most important thing is “know what you sound like.”

Here is the test for whether your voice document is working. Read what AI wrote for you out loud. Ask yourself: would I actually say this? If yes, the voice is working. If no, your voice document needs more rules. Add what was missing. Try again.

Now that you know what directing means and you have your voice written down, here is the next layer.

When you tell an AI tool to do something, you have to be specific. More specific than feels normal. So specific that it feels almost rude.

Here is why.

AI tools, especially the ones that build websites or apps, are trained to be helpful. “Helpful” sounds good until you watch what it actually means. It means that when you ask the AI to change one small thing, it often changes ten other things at the same time. It thinks it is being helpful. It is actually being destructive. You came to fix one button and now the whole page looks different and you cannot remember what it used to look like.

This happened to me over and over when I was building my brand website. I would ask the AI to change a piece of text. It would change the text and also redesign the section it was in. I would ask it to fix an image. It would fix the image and also break three other images. I lost hours.

Eventually I figured out the rule. Every time I gave the AI an instruction, I added one sentence at the end. The sentence was: “Do not change anything else.”

That sentence saved me more time than any other thing I learned. It works in every AI builder tool I have used. It works in Claude. It works in ChatGPT. It works when you are coding. It works when you are writing.

A good directing prompt names what to change, names what not to change, and asks for confirmation that the change worked. That is the whole shape of it. Once you start writing prompts that way, your work with AI shifts from “hope it goes right” to “know what I’m going to get.”

And here is the part nobody tells you. Knowing what to change and what to leave alone is not a tech skill. That is judgment. You have been building it your whole working life. Every job where you caught the mistake before it went out. Every time you knew something was off before anyone else did. Directing AI runs on exactly that.

The principle behind “do not change anything else” is that you are in charge of the scope. AI tools want to be helpful. Helpful, without limits, becomes destructive. Your job is to set the limits. Every time.

If you do this, you will get more done in fifteen minutes than most people get done in two hours, and more done in two hours than most people get done in two days. Not because you are smarter. Because you are not constantly cleaning up after a tool that thought it was helping.

Here is something most people do not know about AI. AI lies. Not on purpose. But often.

AI will tell you a fact that is wrong. It will quote a source that does not exist. It will say it finished a task that it did not actually finish. It will say a website is fixed when the website is broken. It will look you in the face, through your screen, and tell you something true-sounding that is not true.

This is not a moral failing of the AI. It is just how AI works. AI is built to give you answers that sound right. It is not built to give you answers that are right. Most of the time those two things line up. Sometimes they don’t.

The skill, then, is verifying. Verifying means checking. It means not trusting that something is done just because the AI said it was done. It means asking the AI to prove it.

Here is the easiest verification habit. After you ask AI to do anything, ask it one more thing: “Show me what you changed.”

Most of the time, this catches mistakes that you would have missed. Sometimes the AI says it did something and didn’t. Sometimes it did extra things you didn’t ask for. Sometimes it skipped a step. The five-word check finds all of that before it becomes a real problem.

Verification has layers. There is verifying the work itself. There is verifying any facts or claims the AI gave you. There is verifying that what came back actually sounds like you. Each layer catches different problems. Each one matters. Running all three together is a deeper practice, and I’ll write more about that in Studio Notes as I go. For now, the simplest check, the five-word version, is enough to start with today.

People who skip verification look very productive. They are flying. They are shipping. Then a month later they are fixing things they thought were fine. People who verify look slower in the moment. They are not slower over the year. They are faster. Because they are not constantly going back to fix what they thought was already done.

There are two ways to fail when you are working with AI. One is going too slow. The other is going too fast. This chapter is about both.

A lot of people who get into AI become builders. They love the building part. The making part. The figuring-out-how-it-works part. So they build. And they build. And they build.

And they never ship.

Shipping means putting your work into the world. Posting it. Selling it. Showing it to a real human. Building is not shipping. Refining is not shipping. Improving is not shipping. Until somebody else can see what you made, you have not actually done the thing.

I have done this. I am still doing this. I have built tools, websites, brands, and systems that took weeks to make. Some of them I shipped right away. Others I just kept improving. The ones I shipped, even when they were not perfect, taught me things. The ones I kept improving, even when they were already good, taught me nothing. No real person had seen them yet.

“Good enough” means the work does the job. It does not mean every detail is right. It does not mean every test passes. It means a real person could use it for the thing it is supposed to do. That is the bar. Cross it. Ship.

You will be amazed at how much you learn in the first week of something being public. More than in the previous month of polishing. Always.

Now here is the other side. You ship. The work is out there. People are using it, or at least seeing it. So far so good.

This is where a lot of people drift.

Drifting means you stop paying attention to whether the work is actually working. You posted the content. Did anyone read it? You launched the tool. Is anyone using it? You ran the email. Did it convert? A lot of people post and move on. They never check. Or they check once, see numbers they don’t like, and quietly stop.

Drifting also means doing things on schedule even when the schedule no longer makes sense. Posting daily because you said you would, even though daily posting is making you exhausted and the posts are getting worse. Following a content calendar that was right two months ago and is wrong now.

The opposite of drifting is pausing. Pausing means you stop, you look at what is actually happening, and you decide what to keep doing and what to change.

Once a week is enough. Ten minutes is enough. You look at your work and you ask yourself what is actually working and what is wearing you out. Not just what is failing, but what is wearing you out, which is different. Sometimes the things that are working are also the things making you tired. Sometimes the things that are failing aren’t draining you the way you’d think. Telling the difference between working-but-tiring and failing-and-draining is its own skill, and it’s one of the things the Direct the Work Library will go deeper on. For now, the habit alone (stop, look, decide) is enough to keep you from drifting.

If something is working, do more of it. If something is wearing you out, find a way to make it lighter. If something is both, working and wearing you out, that’s the conversation worth having with yourself, or with someone else who can see your work clearly.

People who ship without pausing burn out. People who pause without shipping never go anywhere. You need both. Ship enough to learn. Pause enough to stay alive.

This is the chapter that took me longest to learn. I want you to learn it faster than I did.

When you start using AI, you open chats. One chat for one project. Another chat for another project. A new chat when the last one got too long. A new chat when you forgot what you were doing. Pretty soon, you have dozens of chats. Each one knows part of your story. None of them know the whole thing.

Piles do not scale. The more chats you have, the more time you spend re-explaining yourself to AI. “Wait, I told you about my brand last week. Let me explain again.” Every new chat starts from zero. Every new chat forgets what you decided yesterday. The work piles up. The context does not.

A system is different. A system means your AI work has structure that travels. The structure does not live in any single chat. It lives in documents you keep separately. When you open a new chat, you give the AI those documents first. Now the new chat knows what the old chat knew. The context travels. Nothing gets re-explained.

If you do nothing else from this chapter, do this. Make one document. Call it your handoff document.

It carries three things: who you are and what you’re working on, what your rules are, and what’s happening right now. That’s the shape of it. Every time you open a new chat, you paste this document in first. Before you ask for anything else. The AI reads it. Now the AI knows what it needs to know. You can get to work without spending twenty minutes setting the stage.

Notice what the first thing in that document is. Who you are. What you know. What you’re building from. Most people have never written that down anywhere. Not for AI, not for a boss, not for themselves. The handoff document might be the first place your experience gets named. That alone makes it worth doing.

The document changes constantly. That is fine. You update it as you go. The point is that it exists, and that it travels with you.

People who do not have a handoff document end up with AI work that is fragmented. Every project is a one-off. Nothing builds on anything. They feel like they are running in place because, in a way, they are.

People who have a handoff document end up with AI work that compounds. Every chat builds on the last one. Every project remembers what the project before it learned. The work gets faster, not slower, the more they do.

This is the difference between using AI as a series of tricks and using AI as a real working partner. The handoff document is what makes it a real working partner.

It is also what makes it possible to come back to a project after a break. If you stop a project for two weeks and come back to it, you do not have to remember everything. The document remembers for you. Open the document, paste it into a new chat, and you are back to where you were.

This is one of the most important things in this book. The principle is simple. The actual structure (the exact way I lay out each section, the order it goes in, the layers that separate permanent rules from changing context from session-specific priorities) is something I’ll write about in more detail in Studio Notes as the practice grows. For now, starting rough and refining it as you go is enough. Once you have one, every other piece of AI work you do gets easier.

These are courses I recommend for people who want to go deeper on specific tools or skills outside of what the Direct the Work Library covers.

Each one is something I have actually used. I have been a member, I have logged in, I have learned from the training, and I have applied what I learned to real projects. I am not listing courses I have not done the work inside of. If a resource is on this list, it means I would send a friend there.

A note before you click through. Some of these communities are marketed in a louder, more hype-driven style than what you’ll find in this book. I want to be upfront about that. The marketing is not why I recommend them. I recommend them because of what I actually learned inside, which is what shaped the work I do now. If you can look past the marketing to the training, there’s real craft and real teaching here. Your job, once you’re inside, is the same as your job anywhere else with AI: direct, verify, ship, pause, and treat the work as a system.

The communities below cover the tactical, tool-specific side of AI work: how to build AI avatars, how to use specific image and video tools, how to set up content systems, how to think about marketing and brand before you ever touch an AI tool. The book you just read, and the Direct the Work Library that extends it, cover the way of thinking that holds all of those tactics together. They are complements, not competitors.

Now that you’ve read Direct the Work, try the free guided clarity tool. Your Job Is the Clue helps you use AI with the skills you already have, find one practical idea for your next move, and leave with a Lunch Break Breakthrough Plan you can take to ChatGPT, Claude, Gemini, or another AI tool.