Here’s the Tutorial You’ve Been Asking For

If you’ve been following along for a while, you already know that I don’t gatekeep. When something works, I share it. When I figure out a process that saves me hours of frustration, I write it down and hand it over. That’s the whole point of this space. And today, I’m finally delivering the tutorial that has been sitting in my drafts, half-finished, while my inbox and comment section kept filling up with the same question over and over again.

So here it is. The full breakdown. No fluff, no unnecessary padding, just everything you need to know laid out in the order you need to know it.

Why I Kept Getting Asked This

Before I get into the actual steps, I want to take a second to explain why so many of you have been asking for this specific tutorial. Because I think the context matters.

A while back, I posted a quick behind-the-scenes clip that showed a tiny slice of my workflow. It wasn’t even the main point of that post. But something about it resonated. People started tagging friends, sharing it, and sliding into my DMs asking if I had a longer video or a written guide that explained the whole thing from start to finish.

The honest answer was no, I didn’t. Not yet. I had been doing this process so automatically, so intuitively, that I hadn’t thought to document it. It had become second nature, the way tying your shoes becomes second nature. You stop thinking about the steps and you just do it.

But you can’t teach someone to tie their shoes by just showing them a finished bow. So I made myself slow down, go back to the beginning, and rebuild the whole thing from scratch with fresh eyes. I pretended I was learning it for the first time so that what I wrote would actually make sense to someone who is learning it for the first time.

That’s what you’re getting today.

What This Tutorial Actually Covers

This guide is going to walk you through the entire process from the very beginning. We’re starting at zero. Whether you’ve never attempted this before or you’ve tried a few times and hit a wall somewhere in the middle, this tutorial is designed to meet you where you are.

Here’s a rough overview of what we’re covering:

We’ll start by talking about the mindset and preparation phase, because so many people skip this and then wonder why they keep running into the same problems. Then we’ll move into the actual setup and the specific steps I take in order. After that, we’ll get into the part that most other guides gloss over — what happens when things don’t go the way you expected and how to troubleshoot without losing your momentum. And finally, I’ll share some of the advanced tweaks and personal adjustments I’ve made over time that have made the biggest difference in my results.

By the time you finish reading this, you should have a clear enough picture that you could sit down and execute this on your own. That’s the goal.

Step One: Preparation and Getting Your Foundation Right

The single biggest mistake I see beginners make is jumping straight into the execution without preparing properly. I get it. The excitement kicks in, you want to dive in, and the prep work feels like it’s slowing you down. But skipping it almost always costs you more time in the long run.

Preparation is not glamorous. It is not the part anyone screenshots and shares. But it is the part that determines whether everything that comes after it actually works.

So what does proper preparation look like here?

Start by getting completely clear on your goal. Not a vague, general sense of what you want, but a specific, concrete outcome you are working toward. The more specific you can be at this stage, the easier every decision that follows becomes. When you know exactly what you’re aiming for, you stop second-guessing yourself mid-process.

Next, gather everything you need before you start. There is nothing more frustrating than getting halfway through something and realizing you’re missing a key piece. Go through the requirements ahead of time, make a checklist if that helps you, and confirm that you have access to everything before you take your first step.

Finally, give yourself enough uninterrupted time to get through at least the first major phase without stopping. Starting and stopping constantly breaks your momentum and makes the whole thing take longer and feel harder than it needs to be. Even setting aside ninety minutes of focused time makes a noticeable difference.

Step Two: The Setup Phase

Now we get into the actual doing. This is the part most people think of as “the tutorial,” but I want you to carry everything from Step One with you as you move through this, because a rushed setup creates problems you’ll be cleaning up later.

The setup phase is about creating the right conditions for everything else to work. Think of it like laying the foundation of a house. The foundation doesn’t look impressive from the outside. You can’t see it once the rest of the structure is built. But if it’s off, even slightly, it affects everything that sits on top of it.

During setup, focus on getting the core elements aligned correctly before you add anything on top of them. Don’t rush through this to get to the more interesting parts. Check your work. Adjust as needed. It is much easier to correct something at this stage than after you have built ten more steps on top of it.

One practical tip I always give here: document what you’re doing as you go. You don’t have to write a formal record, but even quick notes or screenshots that show what each stage looked like at completion will save you enormous time if you ever need to retrace your steps or recreate this process later.

Step Three: Execution — Moving Through the Process

This is where most of the visible work happens and where most tutorials spend all their time. But now that you’ve done your prep and your setup properly, this phase should actually feel more straightforward than you might expect.

Work through each step in sequence. I know that sounds obvious, but the temptation to jump ahead or to skip steps that seem redundant is real, especially once you start feeling confident. Resist it. The sequence exists for a reason, and even if an individual step seems small or unnecessary, it is often doing something that isn’t visible until three steps later.

Pay attention to the details at each stage. Little things that seem insignificant early in the process can compound into larger issues as you go. If something looks slightly off, pause and address it before moving on. Developing the habit of doing a quick self-check at each stage before progressing is one of the things that most separates people who get consistently good results from people who feel like they’re always chasing problems.

Don’t multitask during this phase. I know that goes against everything hustle culture tells you, but focused single-tasking during execution produces better outcomes than splitting your attention. Give this your full attention until you reach a natural stopping point.

Step Four: The Part Other Guides Skip

Here’s where I want to be really honest with you, because most tutorials end somewhere around Step Three and leave you with a very incomplete picture.

Things will not always go perfectly. Sometimes a step won’t produce the result you expected. Sometimes you’ll get halfway through and realize something in your setup phase wasn’t quite right. Sometimes you’ll follow every step correctly and still get an outcome that doesn’t match what you were going for.

This is normal. It happens to everyone, including people who have been doing this for years. The difference between someone who gives up here and someone who figures it out is not talent or natural ability. It’s a willingness to troubleshoot methodically rather than emotionally.

When something isn’t working, the first thing to do is stop and resist the urge to start making random changes. Random changes make diagnosis impossible because you can’t tell which thing actually fixed the problem, and they sometimes introduce new problems while masking the original one.

Instead, go back to the most recent point where everything was working correctly. Identify what changed between that point and the point where things stopped working. Then test changes one at a time, checking the result after each one before making another change.

This process is slower in the moment, but it produces faster overall resolution because you’re actually solving the problem rather than just hoping something you do will accidentally fix it.

Also worth noting: the documentation you made during setup becomes extremely valuable here. If you noted what things looked like at each completed stage, you have a reference point to compare against.

Advanced Adjustments That Have Made the Biggest Difference

Once you’ve got the core process down and you’re getting consistent results, this is where you can start experimenting with refinements. I want to share a few of the adjustments I’ve made over time that have moved the needle most significantly for me.

The first is iteration speed. When I first started, I would go through this process slowly and cautiously because I was afraid of making mistakes. Over time I realized that getting faster at the early stages freed up more time and mental energy for the later stages where thoughtfulness and care actually matter more. I got faster by repeating the process enough times that certain early steps became genuinely automatic.

The second is working in batches where possible. Instead of starting from scratch every single time, I began creating reusable templates and starting points that let me skip the parts that don’t need to change from one execution to the next. This alone cut my total time per cycle significantly.

The third is keeping a running log of what works and what doesn’t. Not just notes on process, but notes on outcomes. Over time, patterns emerge. You start to notice that certain approaches consistently produce better results than others, or that problems tend to cluster around particular steps. That pattern recognition is genuinely hard to develop without deliberately tracking it.

What Consistent Practice Actually Looks Like

One thing I want to address directly, because I see a lot of frustration around this: getting good at this takes repetition. Not infinite repetition, but enough to move from conscious effort to something more like muscle memory.

The first time you do this, expect it to take longer than it should. Expect to check back on this guide more than once. Expect to make at least one mistake that you have to go back and correct. All of that is part of the learning process and not a sign that you’re doing anything wrong.

The second time, you’ll notice you move through certain parts more fluidly. The third time, you’ll probably identify at least one point where your earlier approach wasn’t as efficient as it could be, and you’ll naturally adjust. By the fifth or sixth time, the core process will feel genuinely manageable.

I’m not saying any of this to lower your expectations. I’m saying it because I think a lot of people give up during the first or second attempt because they expected it to be easier than it was, and they interpreted that difficulty as evidence that they couldn’t do it. That interpretation is wrong. The difficulty early on is just friction, and friction reduces with repetition.

Following for More: What’s Coming Next

If this tutorial gave you what you needed, I hope you’ll stick around, because this is one piece of a larger series I’m building out. The follow-ups are going to go deeper into specific aspects of this process that deserve their own dedicated treatment.

I’m also planning to address some of the most common questions I get that are adjacent to this topic, because a lot of what people struggle with isn’t the core process itself but the related pieces that feed into it and come out of it.

If there’s a specific part of this tutorial you want me to expand on, drop it in the comments. I read every single one, and the topics I cover next are genuinely shaped by what you tell me you need. That’s not something I say to fill space — it’s how I’ve always built this.

Thanks for being here, thanks for the patience while I put this together, and I’ll see you in the next one.