The division, and the part that makes it work

Rate = total ÷ working periods available

Write an 80,000-word book in six months. Six months is about 26 weeks or 182 days:

Six hundred words is roughly an hour of writing. The transformation here is not mathematical, it is psychological: an 80,000-word book is intimidating and unschedulable, while an hour before work is a decision you can make today. Nearly every large goal becomes tractable at this step and nowhere else.

Some worked conversions

GoalTimeframeDaily requirement
Read 24 books1 year~21 minutes of reading
Run a 42 km marathon18 weeks~30 km a week, 4 sessions
Save 12,0002 years500 a month
Learn 2,000 vocabulary items6 months11 new items a day
Clear 3,000 emails30 days100 a day, ~40 minutes

The reading row is worth unpacking, because it looks impossible and is not. An average book is around 80,000 words; at a typical 250 words a minute that is about 5.3 hours. Twenty-four books is 128 hours a year, which is 21 minutes a day — less than most people spend deciding what to watch.

Build in slack, or the plan fails on week three

Dividing by every available day produces a plan with zero tolerance for illness, travel, a bad week, or the ordinary friction of a life. The first missed day then puts you permanently behind, and being permanently behind is the most reliable cause of abandonment.

Plan for about 80% of nominal capacity. For the book, that means treating the target as 550 words a day rather than 440, which builds in roughly 36 spare days across the six months. You will use them.

This is a specific defence against the planning fallacy — the robust finding that people systematically underestimate how long tasks take, and do so even when they have done the identical task before and know they underestimated it last time. The most effective correction is not to think harder but to look at your own historical rate on similar work and use that number instead of your estimate.

Where linear division is simply wrong

The formula assumes progress accumulates at a constant rate. Several important goals do not behave that way:

Rate against system

The number is a diagnostic, not the mechanism. What actually produces the outcome is a scheduled, protected block attached to an existing routine, and a visible record of whether it happened. The daily rate tells you how big the block needs to be; it does nothing to make you sit down in it.

And check the rate for feasibility before committing. If the arithmetic demands three hours a day and you have one, the honest response is to extend the deadline or shrink the goal — not to write down the impossible number and feel bad in five weeks.

Questions people actually ask

Daily or weekly targets?

Weekly is usually more robust. It absorbs a bad day without creating a failure, and most people lives do not distribute evenly across seven days. Daily works well for small habit-shaped goals.

What if I fall behind?

Recalculate on the remaining amount and remaining days rather than trying to repay the debt in one heroic session. If the recalculated rate exceeds what you can sustain, move the deadline. A missed goal with a moved date still finishes; an impossible rate does not.

Should I share the target?

Evidence is mixed and worth knowing. Some research suggests announcing a goal to an audience whose approval you value can produce a premature sense of completion. Committing to someone who will check on the process, rather than admire the intention, holds up better.

Is my goal data stored?

No. Everything you enter stays in your browser and nothing is transmitted or saved.

Keep exploring Gen Code Tools

Every tool comes with a written guide, and every category is one click away.