← All guides

The first ten minutes: a script for starting anything

Ankora Guides · 5 min read

Here's the thing almost nobody tells you about hard tasks: you don't have to do the task. You have to do the first ten minutes. For most stuck people, once you're actually moving, momentum takes over and finishing stops being the problem. The entire battle is the gap between not-started and started. So stop trying to will yourself through the whole thing, and run a script instead.

Why ten minutes

Ten minutes is a deliberately chosen number. It's long enough to get you past activation energy, the mental cost of beginning that's separate from the task itself. And it's short enough that your brain doesn't throw up the wall of dread it saves for "spend your whole afternoon on this." Ten minutes is small enough to say yes to and long enough for momentum to catch. You are not committing to the task. You're committing to ten minutes, and letting momentum make the next decision.

The script

Run these in order. Don't jump ahead; each step exists to lower the cost of the next one.

  1. Name it in one sentence, out loud. Not the whole project, the single next thing: "I'm going to start the client email." Saying it externalizes the task and cuts through the fog in your head.
  2. Shrink it to a ten-minute move. Ask what piece you could actually finish in ten minutes. Not "do the taxes." "Open the folder and find last year's return." If it still feels heavy, it's too big. Cut it again.
  3. Set a timer for ten minutes. A visible countdown turns open-ended dread into a short, bounded game. Give yourself genuine permission to stop when it goes off.
  4. Clear one piece of friction. Just one, the biggest: phone in the other room, the right tab open, the blank doc created and named. Don't "get set up" for an hour. Remove a single obstacle and go.
  5. Tell someone or something you're starting. A body double, a friend, Ankora. Announcing "starting now" to a listener who'll ask how it went adds just enough gentle weight to tip you into motion.
  6. Do the ugly version. Lower the bar to the floor. A bad first draft, a rough list, two sentences. The goal of these ten minutes is motion, not quality. You can make it good later; you can't make nothing good.
  7. At the buzzer, choose. Stop with a clear conscience, or ride the momentum if it showed up. Both are wins, because both started, and starting was the entire point.

The pocket version, short enough to memorize: Name it out loud. Shrink it to ten minutes. Set the timer. Clear one thing. Tell someone you're starting. Do it badly. At the buzzer, stop or keep going, guilt-free.

Make it a ritual, not a rescue

The script works best when it stops being an emergency measure and becomes your default way of starting things. Same sequence every time, boring and repeatable, so your brain learns that "starting" has a known shape instead of being a fresh cliff every morning. The wall gets shorter when the first move is always the same familiar move. A rescue you reach for in a panic helps once. A ritual you run daily rewires the whole approach.

The part where you don't do it alone

If you read that script and thought "I know all of this and still won't do it," that isn't a personal failing. It's the whole reason external structure exists. A script is much easier to run when something runs it with you: hands you the ten-minute step, starts the timer, and is still there at the buzzer to ask how it went. Knowing the steps was never the hard part. Having something hold them steady while you begin is.

Want the script run with you?

Tell Ankora what you're staring at. It hands back a ten-minute first step, stays with you while the timer runs, and checks in after. The first ten minutes, done together.

Try Ankora free