Part III - Physics You Can Feel

Activation Energy and Starting Routines

A blank page. A blinking cursor. They can be as intimidating as a 10-foot wall in front of a runner.

Chapter 11 13 minute read 2,887 words

A blank page. A blinking cursor. They can be as intimidating as a 10 - foot wall in front of a runner. Scientists use the term activation energy to describe the initial energy needed to start a chemical reaction. Think of lighting a match to start a fire - a little spark to overcome the barrier, then the fire sustains itself. In work, starting a task is often the hardest part, requiring that metaphorical spark. Once you’re in motion (as we saw with momentum), things flow more easily. But how many minutes (or hours) have we spent avoiding that first step because it felt hard to begin? Procrastination often isn’t laziness; it’s our natural aversion to the discomfort of starting, of facing uncertainty or potential imperfection in the first moments. The secret to productivity often lies not in pushing yourself through entire tasks by willpower, but in engineering your environment and habits to make starting almost automatic and trivially easy. Imagine if beginning your work felt as simple as rolling out of bed onto your feet in the morning - no thought, just happen. This chapter is all about lowering that activation energy: designing cues, rituals, and environments that essentially put the first 60 seconds of a task on rails, so you slip into it without an internal battle.

Treat the start as a separate, designable step. Instead of focusing on finishing a task, focus first on designing how you will start it. Often we commingle the idea of “doing X task” with the entire burden of it. Instead, break out Step 0: starting. Identify exactly what the first tiny action is, and plan/make that as easy as possible. For example, if the task is to write a report, the first action might be “open a new document and write the report title and my name.” That’s not hard. Or even smaller: “Open the doc where I have notes.” The key is to define the threshold activity that moves you from not doing to doing. Then, optimize everything around that moment. One trick is to use the “2 - minute rule”: commit to just 2 minutes of the task. Tell yourself you can stop after 2 minutes if you want. Two minutes is so small it requires minimal activation energy. And 99% of the time, once you start, you’ll continue, because the barrier was overcome. It’s like convincing yourself “I’ll just tie my running shoes and step outside for a minute” on a reluctant day; often you end up running a decent run once out there. So, for every important task, identify: What’s the 2 - minute version of this? For coding, maybe it’s “open the IDE and write a pseudo - code outline for one function.” For drawing, “sketch a rough shape on canvas.” For email backlog, “reply to just one email.” By doing this, you separate the daunting size of a task from the tiny start, making it psychologically manageable. Design your environment to support this: if writing, maybe have the document template open and ready (as said, pre - position materials - tying to previous chapter). If you do morning workout, lay out your clothes and shoes the night before right by your bed (environment engineered so the start is literally one step: get dressed). If you have to analyze data, open all relevant data files and the analysis software at end of previous session, so starting next time is as simple as looking at what’s already open. Essentially, remove any barrier like “I need to fetch or arrange stuff” by doing it in advance when you’re not in procrastination mode (like at the end of day or week prior). Often, just having that context ready lures you in. Treat your “start” like a tiny ritual separate from the task’s main body.

Create a quick starting ritual. Many productive individuals have a consistent routine that signals their brain “time to start now.” It might be as simple as making a cup of tea and clearing their desk, or more elaborate like a specific music playlist or a breathing exercise. The content of the ritual matters less than the consistency and the association it builds. Over time, your brain learns: hearing that instrumental soundtrack or sitting in that particular chair position means we’re about to focus on task X. A two - minute ritual can include: closing unrelated tabs/apps (creating a clean slate), setting up your workspace (window arrangement or tools needed), maybe a short mantra or writing down your top intention, then diving in. For example, a programmer might have a ritual: refill water bottle, put on noise - cancelling headphones, open code editor, review yesterday’s last few lines of code - and go. This string of actions, if done habitually, reduces the friction to start because it becomes automatic. It also gently warms up your mind. Make part of the ritual something enjoyable if possible, as a Pavlovian carrot. If you like a certain scented candle or a specific location (like working from a cafe), incorporate that to make starting pleasant. Even something like “I get to play one motivating song while I set up” can turn initiation into a mini treat rather than burden. The key is not to allow diversions sneak in disguised as ritual. E.g., if checking one news site is part of your routine, that might spiral into 30 min reading. Better to keep ritual steps directly related to priming for work. Some do a “mind dump” journaling for 2 min to clear any distracting thoughts, then jump in - that can be helpful if minds cluttered. Keep it short - the ritual should not become an elaborate procrastination technique. It’s meant to cue and ease you in, not replace the work.

Pre - commit and schedule your start specifically. We are more likely to follow through if we’ve made a concrete plan and told someone or put it on our calendar. So leverage that: schedule a block of time for the task’s start explicitly, and better yet, tell a colleague or friend “I’ll start X at [time] and get you a draft by [time].” This externalizes accountability. If you tell your team “I’ll begin testing at 2 PM and update you by 3,” you’ve created a social incentive to not put it off - your word is on the line. Or find a “start buddy” - someone also needing to start their own task; agree to message each other at start time that you’re beginning and then check in after 30 minutes. This is akin to having a gym buddy so you both show up. Just knowing someone is expecting you to say “I started at 9 as planned” can nudge you past that initial hump. On scheduling, be granular: instead of generic calendar entry “Work on Project”, make it “9:00 - 9:15 gather data for Project (start)”. That precise piece looks easy (15 min to gather data) and once you’re doing it, you likely continue into analysis. Additionally, use positive constraints like the “send proof in 25 minutes” approach: e.g., email a colleague “I’m going to draft the introduction of report now; will send it to you in 30 minutes just to show progress.” Now you have a deadline that forces a start (and some work). This technique, often recommended by productivity coaches, can dramatically cut procrastination - suddenly you have publicly committed and time - bound the initial output, so you just dive in. Another trick: if big tasks scare you to start, pre - commit by actually starting a tiny part whenever you think of it. Example: if you’ll have to write a proposal tomorrow, open the doc today and title it “Proposal for X” and jot one bullet idea. Save. Now tomorrow it’s already “started” in a sense, and often our brains see an open loop and want to continue. Pre - committing also means maybe leaving an easy bit unfinished intentionally so you’re drawn to complete. That’s an Ernest Hemingway trick: always stop writing when you know what’s next, so you’re eager to get back to it to finish that thought - it’s easier to resume than start anew. That’s like leaving a door slightly ajar so it’s not a full push from rest next time.

Use a timer and no - judgment initial pass. Perfectionism is a huge activation energy increaser. We stall because we want the first attempt to be good. Remove that pressure by explicitly granting yourself a garbage first draft or a rough initial attempt with no expectation of quality. One way is to set a timer for a short burst (say 15 minutes) and say “I will work on this and I don’t care what state it’s in at the end of 15 minutes, I’m just going to hack at it.” The timer does two things: it gives you an end point (so starting feels safer - you know it’s not endless), and it nudges you to focus for that sprint. Knowing you only have 15 minutes might also bypass your inner critic - you simply don’t have time to both do and critique simultaneously. For instance, open a blank page and set 10 min timer to brain - dump any relevant content or ideas, promising yourself you won’t edit. Often, you end with raw material to refine but crucially, you have started, and that raw stuff is infinitely easier to shape than a blank page. The no - judgment rule means consciously telling yourself: “This code or outline might be messy, that’s fine, I’m just laying scaffolding.” It squashes the inertia caused by fear of imperfection. Many professionals use the “bad first draft” technique - writing anything to get flow going, then later editing heavily. It’s easier to drive a moving car even in a bit wrong direction than to get a stationary car to full speed - so get moving without worrying if direction is perfect; you can steer afterwards. If you have trouble not judging, literally turn off your monitor (if typing) for a few minutes and type blind, so you can’t go back and fix typos - forces you into just producing mode. Or use tools that don’t allow deleting easily in the draft phase. These artificially remove friction of self - correction at start. Remind yourself that a mediocre start is still far better than no start, because you can always improve something that exists. For tasks not creative, say cleaning a big garage, similar approach: set 10 min timer “I’ll gather all items on floor into one corner, no need to organize yet.” That’s an unstructured, low - pressure start. Once 10 min passes, you might be like “eh, I’ll keep going a bit, maybe I’ll sort this pile now.” If not, at least you did something which makes re - start later easier (less to do = less intimidating).

Design an environment that triggers focus. Sometimes we rely solely on willpower to start, but environment cues can do a lot of heavy lifting. For example, if you always have to clear a bunch of clutter to use your workspace, that friction might lead you to say “later.” Instead, tidy up before leaving prior day, or dedicate a particular spot that is always clean and ready for deep work (maybe a library or a conference room, etc.). Some people have “focus mode” tricks: a certain hat they wear or lamp they turn on that tells their brain “we’re in work mode now.” It’s a bit gimmicky, but it can help partition mental states. Consider digital environment too: if opening your computer leads you straight to distractions (news sites, social media), that environment is booby - trapped with high - friction diversions. Adjust settings: maybe set work browser home to an internal dashboard, while leaving the news for your phone in off hours. Use full - screen mode or Distraction - free writing apps when starting on writing task so even if your brain tries to wander, the environment gently keeps it on track (no flashy multi - tabs visible). Some folks do “internet off” for first hour of work to force focus - that’s an environment constraint boosting starting focus. Relatedly, pair environment with time: identify your peak energy time and schedule your hardest - starting tasks then, because natural momentum from alertness helps. If you know at 3pm you always slump, that’s not ideal time to schedule a painful start. Instead use morning or whenever you’re most fresh to do that activation requiring work. Save the more mechanical tasks for low energy times. Also, if in an office, maybe start difficult solo tasks before colleagues arrive or when it’s quiet to avoid initial interruptions (the friction of immediate distraction can kill a start). Or if working from home and you find starting is hard amidst home chores, maybe go to a coffee shop purposely to begin a writing sprint somewhere environment signals “we’re here to work quietly.” Essentially, craft both a physical and digital space conducive to focus and free of common roadblocks at the start line.

Place a “start card” or visual cue. The outline mentions a start card listing first 60 seconds of actions. This is a clever hack: physically writing on an index card or sticky note, “When I sit down at 9am, I will: 1) open code project X, 2) run test suite, 3) fix first failing test.” That card sits on your keyboard or monitor so you see it. In the moment of starting, you don’t even have to think what to do - you just follow the card. It’s like giving future - you instructions. It’s oddly effective because it reduces mental load (no decision needed at start, just action), and it leverages commitment (you wrote it, so you feel obliged to do what it says). Another example: if procrastinating on an expense report, your start card might say, “Open spreadsheet, enter receipts #1, #2, #3.” That’s it. Once you do those, maybe inertia is overcome to keep going, but even if not, you’ve begun. Visual cues to start might also be something like if you need to remember to start a task at certain time, put a big sticky on your desk edge “2 PM: call client.” That physical reminder prevents you from drifting past the start time. Also helpful is leaving something in a “in your way” place - e.g., if you must take a file tomorrow to work on, put it on your chair so you must pick it up (triggering you to do it first). A start card is essentially an if - then plan externalized: “If it’s Monday 10am, then do [these steps].” It’s been shown that encoding implementation intentions (“if X happens or time Y, then I do Z”) increases follow - through because it gives your brain a specific cue and action to latch onto without re - deciding anew.

Practice an immediate start routine tomorrow. As a concrete exercise, pick one important thing you’ve been putting off and design a blast - off for it next time you’re at work. Write down tonight what you’ll do in the first 5 minutes of that task. Gather any materials now. For instance, “Tomorrow at 10, I’ll spend 5 min starting project research: I’ll open the research doc, copy the first reference link, skim it, and jot 3 bullet notes.” Prep: keep the doc open in your computer, place any needed files in one folder, put a sticky “10am - project research: 3 bullets.” When 10am comes, follow that script. Once you do the 3 bullets, see how you feel. Many times, you’ll just continue out of momentum. If truly you don’t, fine - you at least started and can resume later with lower activation energy (you have an outline begun now, easier to add to). Reflect on whether this felt easier than your usual approach of “uh, should start that sometime today.” If yes, try adopting similar structure for other tasks. The difference in productivity and stress can be huge: you replace dithering with doing, and doing even a bit alleviates the anxiety cloud of an undone task. Over days, you might realize tasks you dreaded aren’t so bad once you’re rolling regularly on them. The consistent start routine also builds confidence: you trust yourself to get going - in the same way athletes trust that their warm - up gets them into performance mode. Starting is a skill and habit, and now you have the toolkit to master it: clear triggers, minimal barriers, and no shame in taking baby steps.

By engineering your starts, you transform the hardest part of work into something almost automatic. Instead of standing at the foot of a mountain each day, you’ve built a little stair step or conveyor belt that lifts you onto the trail before you notice. As a result, you’ll find many tasks simply get done because you’re finally consistently beginning them - half the battle. With activation energy tackled, our next focus in “Physics You Can Feel” will be the big picture flow of work items through your system: how to identify where things clog up (bottlenecks) and how to maintain a steady throughput without overload. That ties everything together, ensuring once started tasks actually move to completion efficiently.

Listen
Checking audio...