The Physics of Done

by

Ever Wonder Why Some Work Finishes—and Some Never Does?  Buddy, we have you covered!

Part One: The Physics of Done

Most productivity discussions start with techniques. Lists. Schedules. Blocks. Rituals. Tools. Apps. Philosophies. Deep work. Shallow work. Focus. Flow. Discipline.  Or, if it’s me, l wonder if “kanban” is the “sharpest stick” to use (and point to https://brisqi.com). If you’re still inert, I’ll scream about how you need to read Cal Newport’s books.

See, he’s a rockstar among time engineers.   Three must-read books for time ownership?  Easy!

Newport’s book “So Good They Can’t Igdnore You” is also “triumph over Life” stuff.  But it goes off more in the Tom Peters (“In Search of Excellence“) direction.  Nope, we stay in the Time Lane.

Now let’s roll back to the top: Most productivity discussions start with techniques. Lists. Schedules. Blocks. (blah, blah, blah…)

That’s backwards.

Before techniques, there is physics.

Not metaphorical physics. Real constraints. Real clocks. Real limits on what effort can do to matter. In so many device clicks.  Might be a clock, an app, a pomodoro timer…

Some things can be finished. Some things can only be tended. Some things punish delay. Some things punish haste. Some things reward intensity. Others ignore it completely.

Until you understand which category your work belongs to, all productivity advice sounds reasonable—and fails intermittently enough to keep you blaming yourself.

The central mistake people make is assuming that “work” is a single category. No. No. No. It isn’t. Work comes in fundamentally different classes, each governed by a different time behavior.

This is why one person swears by deep work while another rolls their eyes. They are not disagreeing about effort. They are living on different clocks.

The real question is not “How should I work?”
The real question is “What kind of thing am I trying to get done?”  (Remember our “deliverables matter” grounding?)

Because done has a physics.

Some outcomes can be compressed. Some cannot. Some can be scheduled. Some arrive only when ready. Some exist independently of you once finished. Others vanish the moment you stop attending them.

This distinction matters more than discipline, motivation, or intelligence. It determines whether effort accumulates or evaporates.

The fastest way to waste time is to apply the wrong kind of effort to the wrong kind of outcome.

To see why, we need to separate two ideas that are often mashed together: deliverables and tasks.

A deliverable is something that exists independently of your ongoing effort. An article, a book, a report, a built structure, a finished design, a completed system. Once created, it persists. You can hand it off. Archive it. Ship it. Walk away.

A task is something that only exists while you are doing it. Feeding animals. Checking systems. Monitoring markets. Watering plants. Responding to messages. Maintaining equipment. The moment you stop, the task disappears and waits to be done again.  Grab a pencil or pen and write this down:

Deliverables have endpoints. Tasks have continuity.

This sounds obvious, but most modern work environments are designed to blur the distinction. Email chains turn into pseudo-projects. Dashboards masquerade as outcomes. Meetings create the illusion of forward motion without producing artifacts.

People stay busy, not productive.

The physics of done begins by asking: does this thing want to be finished, or does it want to be maintained?

I have a nearly huge shop:  Where it screams at me “get done cleaning me!”  I yell back “If I did that,I wouldn’t be throughputting deliverables, would I?”

Deliverables behave like compression problems. They benefit from sustained attention, uninterrupted thought, and the accumulation of internal state. Once you’re “inside” the work, progress accelerates. Interruptions are expensive. Re-entry takes time.

Tasks behave like flow problems. They benefit from regularity, consistency, and low friction. They tolerate interruption. They punish neglect. They do not reward intensity nearly as much as they reward showing up again tomorrow.

Deep work exists because deliverables resist fragmentation. If you try to write a serious piece of thinking in five-minute intervals between interruptions, the overhead eats the output. Most of your energy goes into re-establishing context rather than creating anything new.

This is not a character flaw. It is cognitive physics.  See if you can remember this concept:

“You can only pee for so long”

In other words, deep work has limits. It works only when compression is possible and useful. Apply it where continuity is required, and it backfires. Apply it where interruption is inevitable, and it creates frustration instead of progress. (Besides, eventually, you’ll run out of water…)

This is why certain professions struggle with modern productivity advice. Long on pronouns but they skipped the common sense curriculum.

Emergency responders do not control their interruptions. Their value lies in readiness, not immersion. Trying to carve out deep focus in an environment designed for unpredictability misunderstands the mission. The system must remain interruptible by design.  (Son G2 is a firefighter, incident commander, EMT turned construction site safety boss.  He promises more on this down the road…)

Operations roles function the same way. Network monitoring, facilities management, security, infrastructure, caregiving. These jobs are not about finishing; they are about keeping things from breaking.

Trying to deep work maintenance is like trying to sprint a heartbeat.  You can only put so many coats of wax on a floor before running into Stupidsville.

At the other extreme, creative and analytical work collapses under constant task switching. Writing, system design, research, planning, synthesis—these are fragile processes. They depend on uninterrupted internal continuity. Break that continuity too often and nothing crosses the finish line.

At 77, I had to cut back on 14-hours in the chair immersed in deep work because of the risk of deep vein thrombosis.

This is why people confuse being busy with being productive. Tasks create motion. Deliverables create results.

The danger zone is when deliverables (“Hey Ure, when are you finishing the book?“) get treated like tasks.

Writing becomes “working on” instead of finishing. Projects turn into permanent status updates. Planning replaces execution. Refinement replaces completion.

This is where deep work becomes a corrective. It forces a boundary. It says: during this block, the only acceptable outcome is forward movement toward done.

That constraint is powerful. But it is also specific.

Deep work is not a moral upgrade. It is a tool for a particular physics problem: compressing cognitive effort into a bounded outcome.

Use it everywhere and you’ll start resenting reality for interrupting you.

The real skill is not focus. It is discrimination.

Before committing to a work strategy, ask what kind of thing this is. Does it end? Does it tolerate interruption? Does progress accumulate without me? Does consistency matter more than intensity?

If the answers point toward compression, deep work fits.

If they point toward continuity, it doesn’t.

And this is where most people get stuck, because a large portion of life belongs to a third category entirely.

Which brings us to the farmer’s clock.

Which I would explain right now, but we don’t have time.  Details of the Farmer’s Clock next week.

Which is an engineering challenge, huh?

~George

Leave a Comment