Chapter 35: Shrink the Task

Month nine. The externals were handled, and that was the problem.

Maya had a team of three, a scoreboard she reviewed on Fridays, a lead engine that ran without her begging, and eighteen thousand dollars a month coming in like weather. The fires were out. For the first time since the layoff, nobody was forcing her to do anything. And the thing she most needed to do, the one big move that would put the whole next year on a different curve, sat untouched in a document called signaturecoursev1 that she had opened forty times and built zero percent of.

The course was the move. She knew it. A productized version of her method, sold to the founders who couldn't afford her one-on-one, the asset that would finally let her sell while she slept. She had said this out loud to Renata. She had the outline in her head, fully formed. She had everything except a single recorded module, and the reason she had nothing was that every time she sat down to start, the task arrived at full size: forty lessons, a sales page, a platform decision, an email sequence, a launch. She would look at the whole mountain, feel the familiar weight settle in her chest, decide she wasn't in the right headspace, and go answer Slack instead.

This is the avoidance that survives success. You stop waiting for permission and start waiting for motivation. You tell yourself you'll begin when you feel ready, when the calendar clears, when you've thought it all the way through. The over-planning looks like rigor. Maya had a Notion board for the course with fourteen columns and not one published thing. She had spent three weeks "architecting" it. The architecture was just the font week wearing a CEO's clothes.

Marcus had, finally, launched his course. She'd seen the post. Then she'd seen the next post, two weeks later, where he admitted he was drowning, doing every fulfillment task by hand for nine students because he'd never built the system, only the dream. He was still the mirror. He just stood on the other side of the launch now, equally stuck, having skipped the boring part both directions.

She closed Slack and went back to the council, because she recognized the shape of what she was doing, and she was tired of being fooled by her own diligence.

They went straight at the size of the thing. The most-repeated move in the whole corpus, the one that doesn't belong to any single person:

If you know that there's something that you have to do and you're not doing it, one tactic that's extremely useful is to shrink the task. You can shrink the task until you'll find a step forward that you will take, and if you're sophisticated you could find a step forward that you would take happily.

Happily. That was the word that caught her. She'd been waiting to start the forty-lesson course. Nobody on the council told her to muscle through the forty lessons. They told her to find the version of the task small enough that starting felt good, and Leila Hormozi was blunt about why that mattered, why the size itself was the trap:

We want to make our tasks so achievable that we feel good after we've done them. And then if we do something and feel good after we do it, then we want to do it again because we like doing things that feel good.

She had been training her own brain to avoid the course for three weeks. Every time she pictured the mountain and walked away, she'd reinforced the flinch. The problem was never that she didn't know how to make a course. She knew exactly how. Ali Abdaal, who Maya had watched to death, names this disease by its real name. The cure he keeps repeating is the smallest possible action, taken right now:

If you're thinking of getting started on YouTube then just do it. You could literally pause this video right now, get your phone out, switch on the camera, turn on selfie mode on your phone, and just upload it using the YouTube app on your phone. It is that simple. We all overthink this so much, like my first video has to be good and has to be perfect, but no one cares. No one's going to watch your first video.

Now, not how. The how was never her blocker. She owned the how. The fear of starting had dressed itself up as a need for more planning, a better platform, a clearer outline, the right headspace, and she had believed the costume because it flattered her. Kagan's point, the companion to everything Myron Golden had told her at the very beginning, was that the smallest action taken right now beats the perfect plan taken never. The course didn't need architecting. It needed one ugly recorded lesson today.

The council kept going, away from motivation entirely, toward something she could actually control. A voice in the corpus said the quiet part: stop waiting on the right moment and execute now.

One thing that stood out to me is execute, execute, execute. So I want you to execute right now.

And Ali Abdaal handed her the mechanism, the thing that replaces motivation with a target she couldn't fail by accident:

The main strategy for consistency is to set input goals, goals that are within my control. It's not within my control whether I hit 10,000 subscribers or whether I get a million views on a video. But it is within my control: can I show up every week and share something authentically that would add value to my target audience?

Not "launch the course." She couldn't control the launch. She could control recording one module a week. The outcome was a lottery. The input was a decision.

Three real forks, the kind where serious people split, and she had to resolve each by where she actually stood at month nine.

The first camp said the answer was systems and discipline. Build a boring machine and run it whether you feel like it or not, because the feeling isn't coming and the work is the work. Alex Hormozi, who has made a religion of this, put the whole tedious gospel in one line:

Charlie Munger, in one of his seminal speeches, talks about how to guarantee failure. One of the ones he has is consistency. He's like, "You have to make sure that you're inconsistent, because it's very tough for people who are consistent to not be successful.

The second camp said discipline alone is a burnout trap, and the real fix is to reconnect the work to why it ever mattered. Run the why-chain until you hit the motivation underneath the obligation, because forcing yourself through resentment doesn't compound, it cracks. That camp wasn't wrong. Maya had watched founders grind themselves hollow on pure willpower.

The third camp said stop deliberating at all, just sprint. Plan less, act more, let fast cheap failures show you where you're wrong before you've over-engineered the whole thing. That camp was loud, and on her worst over-planning days, correct.

She sat with all three and asked the honest question. Which one was she? She wasn't in the why-chain camp. Her why was intact. She didn't resent the course; she wanted it, badly, which was exactly why the not-starting hurt. And she wasn't quite in the pure-sprint camp either, because she'd already proven she could act under pressure all year. Her constraint at month nine was none of those. It was that the externals were finally calm enough to let her hide behind planning, and the only thing that would beat that was a boring system she ran on the days motivation didn't show. The deciding variable was the calm itself. Past the novelty, past the survival adrenaline, the work only happens if the system carries it. Chris Williamson said the part that made it land:

A lot of times you have to learn to perform without motivation. You have to learn to perform without purpose.

Systems, then. Built around an input she controlled, run when the kindling was gone.

She paid the toll, and the toll was almost embarrassingly small, which was the whole point.

She did not architect anything. She set a timer for two minutes, opened her phone camera, and recorded the worst possible first take of lesson one: "Hi, this is the messaging audit, here's the first question I ask." Forty seconds. She fumbled the open. She didn't redo it. She saved the ugly file, named it module01raw, and dragged it into a folder. Then, because the rule was an input she could repeat, she put one line on her Friday scoreboard: record one module. Not finish the course. Record one. The two-minute version of the thing she'd been dreading for three weeks took less time than the dread had taken that morning.

The fourteen-column Notion board, she archived. It had produced nothing but the feeling of producing something.

By the next Friday there were three raw modules in the folder, none of them good, all of them real. By the Friday after that, seven, and the early two were already re-recorded better, because starting badly had taught her things the planning never could. The course was not done. It had started, and the starting had broken the spell. The mountain turned back into a stack of two-minute decisions, which is all it had ever been.

Then the system met its first real test, and Maya found her next wall. In week three of recording, a flagship client emailed to end their retainer, no warning, twelve thousand dollars a year walking out the door, and the boring machine she'd just built did nothing to stop the floor from dropping out of her stomach. The systems handled the inputs. They did not yet handle the gut-punch of a setback she didn't see coming, and she spent the rest of that day not recording anything, just spiraling, exactly the way she'd promised herself she'd stopped doing.

My verdict. Waiting for motivation is the most respectable way to never start, because it disguises fear of beginning as wisdom about timing. You are not under-informed. You know the how. You're hiding inside the planning because an unstarted thing can't be bad yet, and Kagan's three words are the whole cure: now, not how. Shrink the task until starting it feels good, anchor it to one input you control, and run that input on the days you don't feel a thing. The four-word version of this entire chapter: shrink it, then start. The mountain you've been architecting for three weeks is a two-minute recording you're afraid to make badly. Make it badly. Today.