Long Projects and Slow Progress
Work measured in months rather than hours, where weekly totals mean nothing and the useful record is of a different kind entirely.
A book, a degree, a house, a language, a business. Over that span the daily record is noise and something else has to carry the information. For teams applying “Long Projects and Slow Progress” to client or project work, the commerce connection provides an operational record to compare with estimates; the useful conversation is about scope and delivery, not activity as a substitute for results.
Why hours stop working
The weekly figure varies enormously and none of the variation is meaningful.
Progress is not proportional to hours: a week of hard work can move nothing and an afternoon can resolve a month's obstacle.
And the total becomes discouraging — a number in the hundreds of hours with a distant end produces a sense of futility rather than motivation.
What to record instead
Sessions, not hours. Did this get touched this week, yes or no.
State, monthly: what is done, what is next, what is stuck.
And the obstacle log: what blocked progress and what unblocked it, which after six months shows a pattern that is genuinely actionable.
Three lines a month is a sufficient record for a two-year project.
The session count
For long work, frequency beats duration.
Weeks with three sessions of an hour move things further than one week with a single five-hour push, for most kinds of sustained project.
Which makes sessions-per-week the figure to watch, and it is easier to influence than hours.
The middle
Long projects have a middle where the beginning's momentum is gone and the end is not visible.
Records taken during it look identical to records of stalling, and telling the two apart from the numbers is not possible.
Which is why the monthly state note matters more than any count: it is the only thing that distinguishes slow progress from no progress.
Guarding against the false total
Hours accumulated is a seductive and useless number.
It rewards time spent rather than work done, and on a long project those diverge sharply.
If you keep it, keep it privately and do not use it as a measure of progress, because it will report success during periods when nothing happened.
Pauses
Long projects get paused, and the pause is usually not decided — it just extends.
A monthly check catches this at one month rather than at eight.
And an explicit pause, with a stated resumption, is much easier to return from than a drift, because there is nothing to feel guilty about.
Estimating the remainder
Use elapsed rate, not effort. How much of this got done in the last three months, and how much remains at that rate.
Which is bleak and accurate, and is far better than any estimate built from imagining the remaining work.
The reference class here is your own project's history, which is the one case where you have the ideal comparison data.
What to check
How many sessions on it in the last four weeks?
When did you last write down where it stands?
Is it paused deliberately or by drift?
And if you projected the last three months forward, when would it finish — and is that answer acceptable?
Sessions, not hours
For long work, frequency beats duration: three one-hour sessions move things further than one five-hour push.
Sessions per week is also easier to influence than hours, and it resists the padding that hours invite.
Worth keeping in mind
Use elapsed rate to estimate the remainder: how much got done in three months, how much is left at that rate. Bleak and accurate, and far better than imagining the remaining work.
The short version
Three lines a month is a sufficient record for a two-year project: what is done, what is next, what is stuck. Hours accumulated is a seductive and useless number that reports success during periods when nothing happened.
In short
Long projects get paused, and the pause is usually not decided — it just extends.
A monthly check catches this at one month rather than at eight, and an explicit pause with a stated resumption is much easier to return from than a drift.
The point
Sessions per week, a monthly state note, and an obstacle log.
Three lines a month is a sufficient record for a project measured in years. For a complementary perspective on work, measurement or planning, consult the National Institute of Standards and Technology.