Module 5
Productivity
Are You Actually Doing the Work?
Book section: Productivity — Are you actually doing the work?
Core lesson: Productivity is meaningful work completed, not the appearance of effort. Start the hard thing, slow down enough to do it properly, and return after imperfect days.
Learning outcomes
- Spot avoidance disguised as research, preparation, or busy work.
- Use practical starting techniques to overcome initial resistance.
- Define progress in tangible outputs rather than hours or activity.
Lesson
1. Separate movement from progress
It is possible to spend a whole day learning about writing without writing, researching an app without making it, or refining a task manager without completing a task. The book names this pattern repeatedly: learning and organisation can become procrastination. Learning is useful when it serves the next piece of work. A productive question is not “How busy was I?” but “What exists now that did not exist before?”
This does not mean every creative hour must produce a polished artifact. Sketching, experimenting, and trying something that fails can be meaningful. What matters is whether the activity moves your capability or project forward rather than helping you feel busy while avoiding the central task.
2. Make starting smaller than your resistance
The book suggests counting backwards from five and physically moving toward the task. It also suggests committing to five minutes. These are ways to interrupt the internal negotiation that often precedes avoidance. Open the file. Draw the first line. Write a bad sentence. Do not ask for motivation first. Often action makes the next action easier; if you stop after the planned five minutes, you have still honoured the minimum.
3. Do the important, difficult thing first
“Eat the frog” recurs throughout the book. The idea is to face the most consequential avoided task before the day is swallowed by trivial demands. The first action must be small enough to execute. “Finish my novel” cannot be a morning task; “rewrite the first page” can be.
4. Use productive avoidance carefully
The author also notices that when one task feels impossible, doing another worthwhile thing is better than drifting into meaningless distraction. This is a fallback, not an excuse to avoid the main project indefinitely. Record which task you avoided and ask why. Confusion, excessive scope, fear of producing weak work, and plain fatigue require different responses.
5. Keep returning without punishment
One heroic day followed by two weeks of inactivity is less useful than steady work that fits your life. The book argues against all-or-nothing thinking. Miss a day, then begin again. Reduce the scope if needed. Do not spend more energy judging the lapse than restarting.
Practical exercise — The avoidance audit (15 minutes)
Write down the last three things you did while postponing your main project. For each, mark necessary preparation, useful secondary work, or avoidance. Then write the smallest next action for the task you have been resisting. Make it possible to start in under a minute.
Example: “Learn about podcasting” becomes “Record two minutes of unscripted audio on my phone, listen once, and note one improvement.”
Assignment — Five deliberate starts
On five separate days, complete one five-minute start on the main project. Continue if appropriate, but track starts separately from duration. Record the resulting artifact or insight. At the end of the week, choose the technique that helped you begin most reliably.
Reflection
1. Which tasks leave me feeling productive without bringing anything closer to completion?
2. What am I protecting myself from when I avoid the important work?
3. What is a realistic amount of progress on an ordinary day?
Module takeaway: Start something real, work on the most important piece, and start again tomorrow.