Your three-hour focus block was a fantasy from the start

it is 9:00 on a Monday. Lars, a brand strategist with four retainer clients, blocks 9:00 to 12:00 for "deep work, proposal." He sits down with coffee, genuinely believing he will get up at noon with a finished doc.

By 9:47 his attention has slipped. Slack. Inbox. Coffee refill. By 11:00 he has four paragraphs and a feeling that he is not disciplined enough. Eight Mondays in a row. Zero finished proposals.

The frustration is not about distractions. It is the gap between the focus duration he thinks he has and the one he actually sustains. Every block built on the inflated number guarantees a day that ends in shame.

Why does your three-hour focus block almost never last three hours?

Because nobody concentrates for three hours straight. Not Lars, not you, not the author of the book that made you try.

Real concentration runs in shorter windows than the calendar suggests. Forty-five minutes is common. Sixty is a good day. Ninety is the upper edge for most freelancers I have worked with, and it shows up on a specific kind of project: familiar tools, clear scope, no strategy calls in the middle.

A three-hour rectangle is not a focus block. It is a wish.

The real planning failure is self-assessment, not distraction

We blame Slack. We blame kids. We blame the neighbour drilling at 10:15. None of that is the root cause.

The root cause is that we estimate our focus stamina the way we estimate task duration. From imagination, not observation. We picture our best forty-five minutes ever and stretch them into a Monday morning. Then we are surprised when the actual operator, the tired one with three open clients and a tax deadline, cannot hold the same line.

Eight Mondays of unfinished proposals is evidence. The block stays at three hours anyway, because the planning self does not believe the working self. You do not have a discipline problem. You have a self-modeling problem.

How long do freelancers actually concentrate before they drift?

Most freelancers I have talked to follow roughly the same arc, give or take ten minutes.

The first 25 to 45 minutes are sharp. The work moves, the doc grows, the function compiles. Then a soft fade, where the next sentence takes longer to land. By minute 60 or 70, a small interruption (a notification, a thought about lunch) is enough to break it. Getting back to the same depth costs more than the next twenty minutes are worth.

Four out of five freelancers I have watched plan their day will ship one good 45 to 60 minute session before lunch and one more after. That is a normal weekday. The trouble is they had booked 9:00 to 12:00 and 14:00 to 17:00, so a normal weekday reads as a disaster.

What an honest focus block looks like on a Tuesday

Noor is a backend developer with two SaaS retainers. She used to plan three-hour coding mornings, end them at 90 minutes, and call the second half wasted.

She did not waste 90 minutes. She held real focus for 90 minutes, which is roughly the upper edge of what a human sustains on a complex task. The session was good. The block was wrong.

Her Tuesday now reads like this:

• 9:15 to 10:00: write the failing test for the webhook retry logic
• 10:00 to 10:20: walk to the bakery, no phone
• 10:30 to 11:15: make the test pass, push the branch
• 11:30 to 12:00: PR review and Slack

Two scoped 45 to 60 minute windows. Each one has a shipping criterion she can name out loud before she starts. The break between is not optional, it is part of the design. Same amount of work done. She just stopped scoring herself against a fantasy.

How to scope work to the focus duration you actually have

Pick a deliverable that fits the window you have observed yourself sustain. Not the one a productivity book told you was the minimum.

Roos, a copywriter with mixed B2B clients, used to book "two-hour writing blocks" and spend the first 20 minutes on admin because she was "not warm yet." A Slack ping at the 40-minute mark would end the session. By her own count: zero hours of deep work. Honest count: 40 productive minutes that shipped. Not a failed two-hour block. One successful focus window with the wrong label on it.

If you want to do this on purpose:

1. For one week, write down the actual minute you started and the minute you drifted. Just two numbers per session, no judgment.
2. Look at the median at the end of the week. That is your real window, not the one you imagined.
3. Scope the next week's tasks to that number. If your median is 50, plan 50-minute units with a named output for each.
4. Put a break between every two units. A real one. Not "check email."

See what actually fits in the hours you have left today is one way to do step three without doing the math each morning. TaskBerry will not run a timer, silence Slack, or measure your drift. You still do the noticing. It holds the result, in S/M/L units instead of imagined three-hour rectangles.

What changes when you stop planning around the focus duration you don't have

Mees consults hourly for one anchor client. He used to plan Wednesday afternoon as a four-hour research block, then actually do three good 50-minute sessions with breaks, and call the day a failure because it "wasn't four hours of deep work." Three good sessions is a good afternoon. Calling it a failure was the only broken part.

When you stop planning around focus durations you do not have, evenings get lighter, overruns shrink, and the half-finished docs stop piling up. It takes one honest week of paying attention to your own drift, then planning for the operator you actually are.

If your calendar describes a day you have never once finished, the calendar is wrong, not you. Plan a day you can actually finish is the version of this we are trying to make easier.

Lars's Monday block is not going to start working on the ninth try. The honest move is to cut it in half, name what ships in the first half, and let the second half be a different kind of work. A boring fix. Probably the one that gets the proposal out.