How to Become a “Stacking Backtimer”

Back in 1962, or thereabouts – when the Smith-Corona mechanical typewriters were still being programmed into young people – I got my first exposure to Back-Timing.

Today, understand, in an age where performance is optional, the Education system doesn’t teach much about PUP – Performance Under Pressure.  Back then?  Oh, yeah.

So the way it worked was this:  You would sit down at the assigned typewriter. Load it with a sheet of paper. Make sure the tabs were set correctly.  Feet on the floor. Posture erect.  You know – the rules that no one follows today.

The teacher would come around, put an exercise  (face-down) on the desk.  And would return to her position at the front of class.  “This morning we have a 2-minute exercise.  I will set the BACK TIMER for two minutes.  When it begins, turn the paper over, place it in your copyholder and time until the timer rings.”

Then you’d sweat for two minutes, fat-fingering every other word and eventually counting (after the “ding!”) that you had gotten only 70-words (three of them misspelled) down onto the S/C. Eighth grade misery was what it was.  Nowhere near the fun of the advanced math classes.

Another Back-Timer

My second encounter with Back-Timing was in my early broadcasting days.  1968 at KRKO in Everett, WA.  Hosting “Garrett’s Graveyard” – an overnight DJ, commentary, with lots of Led Zeppelin, and early top-40.

Back-Timing here was much different.  I was spinning records.  Just before the “top-of-the-hour” though I would read a few news headlines and end by picking up a UPI network feed.

Back-timing this – so the very last part of the weather “in the Jet City it’s 47-degrees” for example – didn’t step on the Network.  That was a BIG no-no in serious rock ‘n roll radio.

Early on, I discovered a back-timing hack for this problem – and I’ve used it off and on in studio work for more than 40-years.  The station had a very nifty Frieze Audio-Pilot in the audio chain.  Essentially, it has two-speeds of automatic volume control.  The slow one would follow signals through a very wide range.  The faster system would do fast compression (20-50 db, in fact) on the averaged signal.

By very slowly turning down my microphone (while reading the headlines and weather) the Audio-Pilot would bring down my average audio level (applying more boost in the AVC) and listening, no one was the wiser – because the apparent volume was unchanged.

BANG! When the network news hit?  It was 20-30 db hotter than me and it sounded smooth and I never stepped on the network.  The program director (fellow named Russ Rebel) was very impressed.  (Russ was a deputy sheriff when he wasn’t doing the morning show and later maced me on the air, but that’s a whole other 3-drink story.)

Is There a Point?

Hell yes there is. Aren’t you paying attention?

One of the most powerful tools in your time-engineering arsenal is learning to back-time major events in your life.

Two quick examples:

Cooking Breakfast

Handle all the items that take the most time first.  On a typical morning?

  • Egg pan goes on the stove first  On low, takes a few minutes to be perfect but not too hot.
  • Bacon goes in the microwave 3 to 2 1/2 minutes, depending on brand and thickness.
  • Toast goes down immediately.
  • Then as the microwave dings the bacon is done, the eggs are ready to turn out and the toast pops.

Being a time-engineer you have already got a thermos of hot coffee so in 10 seconds from plating, you’re ready to eat.

Write a Web Column

I try to limit myself on writing time.  When you’ve been a “production writer” for over half your life, this is easy.  You know (generally) what your Deliverable will be (1-2 pages in a memo, for example).  So you block the time for tomorrow.  Now, if there is information you don’t have, it’s assigned out with hard deadlines to the people who work for you.  Or – in modern times – you tell your AI (assistant mode) I need a report on (fill it in) by  (pick the time.)

Now, when the hole comes up on your calendar that you have saved for this project, you have everything you need.  Files, comments, spredsheets of supporting data.  (Or AI has made up the best “Dog ate my homework story” that ever lived.)

And Example from Today

I had a 15-minute hole in my calendar so I went to the house to have a mid-morning cup of tea with my wife.  As I put on my jacket to wander back to the operating position in my life, I paused – maybe all of 10-seconds for the back-timing and event-stacking plan.

  1. There was a bag of trash to take to the burn barrel.  (We live in the woods and there’s not even a building department of out here.)  By doingd this now, I could stack several events into Flow.  That’s how you “make time.”
  2. Once I got to the shop, a computer hard drive that was rolling onto backup would be done.  And the latest software updates would be ready to install.  Microsoft will give you an estimated time for their updates and you can get a good sense on others.  This is back-timing at it’s finest.

The idea orf back-timing is easy to remember with a simple Sports or Driving analogy.

If you like sports?  “What is on-deck that could turn into a Rain Delay in my Life?”

Picture yourslef a NASCAR or Road Racer? Ask “What are the coming speedbumps and can they be fixing themselves while I have tea?”

Back-timing can be something as simple as the eggs and the bacon showing up done together.  But back-timing works on things like construction sites.  No point having the concrete mixers lining up for a big pour if the fomrs aren’t done yet.

This is another Time-Tool you can use in a massively extensible way.

Until next time, then?

George

 

How to Use AI for Kick Butt Personal Scheduling

We don’t do “productivity porn” around here.  We do, however, crank out a HUGE amount of…um…stuff.  And the fact is, real ballers and hitters DO an incredible amount of output.  They don’t meet to commiserate – they’re on the field kicking it.

There’s a reason for the old saying “If you want something done, give it to a busy man…(or woman – this was a saying in pre-pronoun times, but you get the idea!)

Time Engineering: a Schedule That Actually Runs You

Most schedules fail for one simple reason: They are written about work instead of being engineered around reality. Around DELIVERABLES.

What follows is not a productivity system. It is not a goal list. Nor is it a calendar stuffed with optimism.

It is a time-engineering process — the deliberate construction of a day so that decisions disappear, energy is protected, and life actually gets lived.

This article explains how such a schedule is built, step by step, and why it works — especially when time, energy, and attention are finite resources.  Even if you don’t think they are now, believe me, out here at 77 you will know it in your bones.

There are two or three bedrocks to this that are important to embrace in advance.

  1. The Nature of time has changed.  With the coming of compute at scale, information is no longer just in books, it’s all digital.  What used to take a quarter of credit-hours in college is now in a 30-minute Youtube how-to.  This is leverage.  You literally can do it all in Life.  Just not everything.
  2. AI has destroyed conventional Day Planning.  Planning used to eat 60 minutes a day of my time.  Can I schedule this?  Where will it ripple, what can I push.  You know the dance.  “How can I work that in this week?”  Now, I don’t worry.  I tell my AI (assistant) “Print my day card” and a nifty document (which I will show you in a sec.) tells me what I’m doing almost every minute of the day.
  3. You can become an Action Figure and The Boss in Your own life.  To do so all it takes is a decision to more wisely use our mosdt valuable asset in life: Our time.

The First Rule: The Calendar Is the Machine

A calendar is not a reminder tool. It is a control system.  You are the motor.  Your AI is your “onboard computer.”  You still set where you’re going.  But you don’t meter the fuel (time) any more than your car let’s you meter the fuel injectors.

If your calendar:

  • requires constant renegotiation,
  • spills work into evenings,
  • relies on “I’ll fit it in,”

…then it is not a calendar — it is a stress amplifier.

Time-engineering starts with a different premise:

The calendar runs the human, not the other way around.

That means the calendar must be:

  • explicit,
  • bounded,
  • physically realistic,
  • and enforceable without willpower.

Know why airplanes don’t crash?  All of us who are pilots use knee boards.  They give us all the options. If you lose an engine or you get down to decision altitude and have to divert? Everything is on your lap on the approach plate.  This is the thing to have in mind when you start your day.

  • Know what the Day is starting like.
  • Have a crystal-clear vision of what you want it to be when it’s over.
  • Tell your (AI) assistant your available time.
  • The “Schedule me.

That’s the top-level.  Now let’s reduce this to a deliverable personal workflow.

Step One: Lock the Hard Stops First

Before adding any work, we locked the immovable constraints:

  • A daily hard stop at 4:00 PM
  • Evenings defined explicitly as “drinks and dinner”
  • No work leakage after the stop, ever

This single decision does more than any productivity hack. It creates pressure upstream — forcing clarity earlier in the day.  I know every day of the week I quit work and roll to a glass of wine and cooking dinner and then serious down-time.  Between first food and coffee and then?  I’m on fire!

Without a hard stop, work expands endlessly. With a hard stop, work becomes selective.

Step Two: Engineer for Biology, Not Ambition

Instead of scheduling tasks, we scheduled human limits:

  • Physical work before noon (heat matters)
  • Market-dependent work after market close
  • Writing early, when cognition is strongest
  • Hands-on work distributed to protect dexterity and focus

This is time-engineering’s core insight: You don’t manage time. You manage friction.

When friction is removed, execution becomes easy.

Step Three: Replace “To-Do Lists” With Time Blocks

A to-do list is an argument with yourself. A time block is a decision already made.  You are going to (by-God) do it and finish the deliverable.

Every recurring obligation in my life is first converted into a bounded block:

  • Comments moderation
  • Gardening
  • Ranch work
  • Writing
  • Studio rebuild
  • Shop and electronics work

Nothing was left “floating.” If it doesn’t fit on the calendar, it doesn’t exist.

Step Four: Separate “Must-Do” From “Drop-Safe”

This step is where most schedules break — and where this one survives.

Not all blocks are equal.
Some protect health.
Some protect income.
Some protect sanity.

Others exist to absorb opportunity. Instead of pretending everything is critical, we built drop-safe capacity:

  • Studio time
  • Electronics bench
  • Feature writing
  • Website improvements

This creates slack without chaos.

When energy dips or reality intrudes, something can fall away without guilt.

Step Five: Create the Day Card

The final step was to abandon the weekly planner mindset entirely.

The system runs on day cards:

  • One day
  • One page
  • Time range → activity
  • No rationale
  • No commentary
  • No explanations

This matters.

A day card is not a plan — it is a flight checklist. You don’t argue with it. You execute it.

Why This Works (Especially Later in Life)

This approach is not about doing more. It is about doing without friction.

It works because:

  • Decisions are made once, not repeatedly
  • Evenings are protected
  • Physical movement is embedded, not optional
  • Cognitive load is front-loaded
  • The calendar absorbs chaos instead of amplifying it
  • Most importantly, it preserves agency.

You are never “behind.” You are simply on today’s card.

What Comes Next

At the end of this article, I am including a real, working set of day cards generated using this process — not as a template, but as proof. Yeah…this is how this week will roll.

The specific times don’t matter.  Your life is on a different path, different tasks and deliverables, of course.  But! The structure does.

Time-engineering is not about copying someone else’s schedule. It is about building a calendar that can run you well — day after day — without burning you down.

Here’s How My Week is Rolling

SUNDAY — DAY CARD (from now which is an early Sunday morning)
7:30 AM ShopTalk auto-publish (verify only)
8:30–9:30 AM Ranch maintenance (1 hr)
9:30–10:30 AM Gardening DO hour (1 hr)
11:00–11:10 AM Reader comments check #2
11:10 AM–12:10 PM Office cleaning (1 hr)
12:10–1:00 PM Lunch
2:00–2:10 PM Reader comments check #3
2:10–3:10 PM Shop cleaning (1 hr)
3:10–3:55 PM Studio time (45 min)
3:55–4:00 PM Wheel garbage for Monday pickup
4:00 PM Drinks and dinner (unplugged)

MONDAY — DAY CARD
4:20–4:50 AM Walking pad (30 min)
5:00–5:10 AM Reader comments check #1
5:10–7:30 AM UrbanSur writing → publish
8:30–9:30 AM Ranch maintenance (1 hr)
9:30–10:30 AM Gardening DO hour (1 hr)
10:30–11:30 AM Shop work (1 hr)
11:30–11:40 AM Reader comments check #2
12:00–1:00 PM Lunch
1:30–2:00 PM Reader accounting (30 min)
2:00–2:10 PM Reader comments check #3
2:10–2:40 PM PN Feature research / notes
3:00–4:00 PM Electronics bench (1 hr)
4:00 PM Drinks and dinner (unplugged)

TUESDAY — DAY CARD
4:20–4:50 AM Walking pad (30 min)
5:00–5:10 AM Reader comments check #1
5:10–7:30 AM UrbanSur writing → publish
8:30–9:30 AM Ranch maintenance (1 hr)
9:30–10:30 AM Gardening DO hour (1 hr)
10:30–11:30 AM Shop work (1 hr)
11:30–11:40 AM Reader comments check #2
12:00–1:00 PM Lunch
2:00–2:10 PM Reader comments check #3
3:00–3:30 PM ChartPack work (30 min)
3:30–4:00 PM Studio time (30 min)
4:00 PM Drinks and dinner (unplugged)

WEDNESDAY — DAY CARD
4:20–4:50 AM Walking pad (30 min)
5:00–5:10 AM Reader comments check #1
5:10–7:00 AM Peoplenomics writing → publish
8:30–9:30 AM Ranch maintenance (1 hr)
9:30–10:30 AM Gardening DO hour (1 hr)
10:30–11:30 AM Shop work (1 hr)
11:30–11:40 AM Reader comments check #2
11:40 AM–12:30 PM HadG polish + preload
2:00–2:10 PM Reader comments check #3
3:00–4:00 PM Electronics bench (1 hr)
4:00 PM Drinks and dinner (unplugged)

THURSDAY — DAY CARD
4:20–4:50 AM Walking pad (30 min)
5:00–5:10 AM Reader comments check #1
5:00 AM HadG auto-publish
7:30 AM UrbanSur auto-publish
8:30–9:30 AM Ranch maintenance (1 hr)
9:30–10:30 AM Gardening DO hour (1 hr)
10:30–11:30 AM Shop work (1 hr)
11:30–11:40 AM Reader comments check #2
2:00–3:00 PM Studio time (1 hr)
3:45–3:55 PM Reader comments check #4 (final)
4:00 PM Drinks and dinner (unplugged)

FRIDAY — DAY CARD
4:20–4:50 AM Walking pad (30 min)
5:00–5:10 AM Reader comments check #1
5:10–7:30 AM UrbanSur writing → publish
8:30–9:30 AM Ranch maintenance (1 hr)
9:30–10:30 AM Gardening DO hour (1 hr)
10:30–11:30 AM Shop work (1 hr)
11:30–11:40 AM Reader comments check #2
11:40 AM–1:40 PM ShopTalk Sunday write + preload
2:00–2:10 PM Reader comments check #3
3:00–3:46 PM ChartPack work (46 min)
3:46–4:00 PM Studio time (14 min)
4:00 PM Drinks and dinner (unplugged)

SATURDAY — DAY CARD
4:20–4:50 AM Walking pad (30 min)
5:00–5:10 AM Reader comments check #1
5:10–7:00 AM Peoplenomics writing → publish
8:30–9:30 AM Ranch maintenance (1 hr)
9:30–10:30 AM Gardening DO hour (1 hr)
11:00–11:10 AM Reader comments check #2
11:10 AM–12:10 PM HadG planning (1 hr)
2:00–2:10 PM Reader comments check #3
3:00–4:00 PM Electronics bench (1 hr)
4:00 PM Drinks and dinner (unplugged)

Using this approach has let me dump almost all stress and tension into the AI and tell it (in so many words) “This is what I want to get done this week.  I hate planning, so give me the checklist to get it all done within my constraints.

That’s it.

Except, that when you actually do it?  You enter the Order of Hyper-Humans. Time Engineers.

George

The Farmer’s Clock and Other Stories

[For the late arrivals:

  • Part One (Physics of Done) establishes the why: clocks, compression, deliverables, limits.

  • Part Two (Farmer’s Clock) establishes the when: patience, stewardship, continuity, rhythm.

This is therefore part two.  Try not to be late all the time, ‘K?]

A farmer cannot deep-work a crop into existence.

You can prepare the soil. Plant carefully. Water. Weed. Protect. But once the seed is in the ground, the primary process runs on a clock that does not respond to effort intensity.

No amount of focus makes corn grow faster.

Biological Time Matters

Agriculture operates on biological time. Growth happens continuously, slowly, and mostly without you. The farmer’s role is not creation but stewardship. Short interventions, long waits, repeated attention over months.

This is neither deep work nor shallow work. It is something older and less forgiving.

The farmer’s clock punishes impatience. Try to hurry growth and you damage it. Ignore it and you lose it. Show up inconsistently and yields suffer.

This clock governs far more of life than most modern knowledge workers want to admit.

Biological time happens internally, as well.  Men and women both have “biological clocks”.  As it turns out, there is sometimes no “setting these to income” or waiting for “things to make sense.”  Growing up, to some extent, is learning to be in charge of your biological clockworks.

Life Clocks Are Ticking!

This part is ugly, but plug your nose and keep reading.

Health operates on this clock. Fitness. Healing. Aging. You cannot deep-work your way to cardiovascular health in a weekend. The body responds to repeated, moderate inputs over time.  I’m 77 now.  Ask me how I know?

Relationships operate on this clock. Well, sort of.  (Not the weekend long boff-a-buddy relationships…tehe longer ones.) Trust, familiarity, shared history, emotional safety. None of these can be compressed without distortion.  (OK, all can get in the way of a good boffing, of course!)

Infrastructure out here in the wilds operates on this clock. Gardens, homesteads, systems, routines, habits. Small neglect compounds silently. Small care compounds quietly.  Until the guy up the road gets drunk and starfs unloading an ought-six at 2:20 AM while you’re sleeping and he’s on Planet ETOH.

Markets even operate on this clock at certain scales. Long cycles do not respond to daily attention the way traders wish they would. In economics, we speak of cycles.  (Which we also do at biker bars.)

The mistake is trying to force farmer-clock systems onto deliverable clocks.

People try to “finish” fitness. They try to “complete” relationships. They try to sprint habit formation. They try to deep-work maintenance.

It doesn’t work.

The farmer’s clock demands chunking.

“OK, What’s Chunking?”

Um, besides wehat you hurl after a bottle of Jack?  Or a Chinese food brand?

Chunking (of time) is not a productivity hack. It is acceptance of reality. It says: this outcome emerges from repeated, modest effort applied consistently over time, regardless of how motivated or focused I feel on any given day.

Chunking respects continuity. It respects systems that never finish.  (Excedptd the lo mein.)

This is why production lines never stop. Once a process is in motion, the work is not to complete it but to keep it stable. The line does not care about your schedule, your focus, or your creative energy. It moves.

Trying to impose deep work on a moving line creates friction. The system does not pause because you want to think deeply. It demands presence, not immersion.

Many modern roles operate closer to production lines than to writing desks, even if they involve computers and abstract information.

Customer support. Publishing schedules. Content pipelines. Farm operations. Daily logistics. Household management. These systems reward rhythm, not intensity.

The farmer’s clock also explains why some people feel perpetually behind despite working hard. They are treating continuous systems as if they were deliverables. Every day feels like failure because nothing is ever “done.”

Nothing is supposed to be done.

It is supposed to be tended.

Memory hack:  think of fire.  No fuel means it done.  Nice and still there?  It’s being tended.

This realization is liberating when accepted and maddening when resisted.  Thatr’s OK, because we all are Original Amateur Hour walk-ons.

The farmer does not end the field. The firefighter does not end readiness. The caretaker does not end care.  (Why, even this column may never end…)

Trying to finish what cannot finish creates guilt instead of progress.  No, no.  We create guilt – we don’t shoulder it.  See how much you have to learn about management?

Time engineering is the practice of matching effort to clock.

Our favorite tools as the ‘ations.

  • AUTOmation
  • DELEGation
  • OBFUSCation
  • and if we forget? PROCRASTINation  (We’ll make you C-level ready, yet.)

Deliverables want compression.

Tasks want repetition.

Systems want stewardship.

Emergencies want readiness.

Biology wants patience. (or a nice dinner out and many drinks)

There is no universal productivity method because there is no universal time behavior. (OK, bad is in the running…)

The people who seem calm and effective are not working harder. They have learned which clocks to respect.

They deep-work what can be finished.

They chunk what must be maintained.

They wait where waiting is required.

They stay ready where unpredictability rules.

And they stop blaming themselves for failing to hurry processes that do not respond to hurry.

The farmer’s clock is not slow. It is precise.

Ignore it and effort is wasted. Align with it and small actions compound into durable outcomes.

The physics of done is not about doing more.

It is about knowing what kind of thing you are dealing with before you decide how to apply yourself.

Once you see that, time stops feeling scarce.

It starts feeling structured.

And structure, applied patiently, is how things actually get done.

Leaving you more time to figure out how to feed your biological clock…

Ding! Times up.  You get the tab.

~George

The Physics of Done

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

Deliverables: The Anti–To-Do List That Actually Works

[Note: This is especially important for ADHD and managing ADHD people!]

I had one of those good father-son conversations with G2 this morning — the kind where you think you’re going to talk shop (AI hacks, tools in the farm shop, the latest shiny thing), but you end up talking about how to live a day without getting dragged around by it.

G2’s a lifelong ADHD manager. His coping strategy has been simple and brutal: no more than three major tasks a day. Not three hundred. Not “a list.” Three. That constraint alone keeps a day from becoming a guilt-soaked game of whack-a-mole.

But then he nailed the real problem: “Dad, you get me off my tasks.” And he’s right — not because the conversation is bad, but because the old to-do list is a fragile system. A single interruption and the whole thing collapses into noise. The to-do list is made of easy-to-excuse items: low urgency, vague endpoints, and zero emotional weight. Miss a few and you’re suddenly “behind” on a list that never ends.

So I offered him a strategy that’s helped me more than any productivity app ever has: throw out the to-do list. Replace it with deliverables.

A deliverable is different. A deliverable has an endpoint you can point to. It’s a thing that can be delivered to someone — even if the someone is you. “Draft done.” “Rail section installed.” “Invoice sent.” “Seedlings transplanted.” It’s not “work on…” or “look into…” or “research…” Deliverables don’t let you hide. They force clarity: What will exist when I’m finished?

Manage Deliverables, Don’t Limit Learning

Here’s the key that makes this ADHD-friendly and show-up-every-day practical: even if you only have one or two deliverables on a given day, you’re never so “focused” that you can’t evaluate a new tool — especially a power tool like AI — that might speed every future deliverable. That’s not distraction. That’s capital investment in your own throughput. It’s like trying to build a house while refusing to stop and consider a hammer and nails because you’re “too busy.” The right tool isn’t a derailment — it’s compound interest.

The final piece is what turns deliverables from a philosophy into a life changer: ship time. Every deliverable gets a day (or at least a window) when it ships. Not “someday.” Not “ASAP.” A day. That’s the difference between a dream and a plan. If you don’t assign ship time, deliverables quietly degrade back into to-dos, and your brain goes right back to negotiating with itself.

Try it for a week. Kill the to-do list. Convert every “task” into a deliverable with a visible finish line. Then assign ship time to each one. You’ll find something strange happens: you stop “doing things” and you start producing outcomes. And when outcomes become your unit of measurement, your day gets calmer, your priorities get sharper, and you don’t get knocked off course every time somebody (including your dad) shows you a shiny new tool.

If you’re ADHD-wired, this may be the closest thing to a cheat code I’ve found.

Action Bonus

Being in a “biased to action” family, here’s the application tool:  This is a one-screen Deliverables Board template you can paste into a note, print, or turn into a simple spreadsheet. (Built to match your “3 major outcomes/day” + “tool investment is allowed if it speeds future deliverables” philosophy.)

The Deliverables Board (Daily)

Date: ____________ Day theme (1 sentence): ___________________________________

1) Today’s Deliverables (max 3)

D1 (Must Ship): ______________________________________

  • Ship time (hard): ________ (or Ship day: ________)

  • Definition of DONE (observable): __________________________

  • Next action (5–15 min): _________________________________

  • Blockers / dependencies: _________________________________

D2 (Should Ship): _____________________________________

  • Ship time/day: ________

  • DONE: _________________________________________________

  • Next action: ____________________________________________

  • Blockers: _______________________________________________

D3 (Nice-to-Ship): ____________________________________

  • Ship time/day: ________

  • DONE: _________________________________________________

  • Next action: ____________________________________________

  • Blockers: _______________________________________________

2) Tool Investment Lane (optional, but allowed)

Tool/test that speeds future deliverables (time-boxed): __________________________

  • Time box: ____ minutes (15–30 recommended)

  • What I’m deciding today: _________________________________

  • If “yes,” where it plugs in tomorrow: ______________________

3) Communications Gate (prevents “Dad rabbit holes”)

Before any call/text/chat longer than 2 minutes, ask:
“Does this help ship D1/D2 today?” ☐ Yes ☐ No
If No, park it here: PARKED TOPIC: _______________________

4) Parking Lot (not a to-do list — it’s an intake bin)

  • Parked item 1: __________________________________________

  • Parked item 2: __________________________________________

  • Parked item 3: __________________________________________

5) End-of-Day Closeout (2 minutes)

  • Shipped today: ☐ D1 ☐ D2 ☐ D3

  • If not shipped, new ship day/time: _________________________

  • One sentence learned (keeps compounding): __________________


Weekly Companion (5-minute version)

This week’s Big Deliverables (max 5):

  1. __________________ (ship by /)

  2. __________________ (ship by /)

  3. __________________ (ship by /)

  4. __________________ (ship by /)

  5. __________________ (ship by /)

One tool investment for the week: _________________________

That’s it.  Simple.  More kanban -friendly.

Consider yourself empowered,

George

Comments are always welcome!

We Need to Talk About Workflows

“Workflow” is one of those words people toss around until it means nothing. So let’s pin it down like an engineer would.  Or, a tag team in wrestling, lol.

A workflow is the repeatable path that turns intent into a deliverable. Not motivation. Not “I feel organized.” A workflow is the plumbing between idea and shipped. If that plumbing leaks, you don’t just lose time—you lose trust in yourself, and then the whole machine starts slipping.

Every real workflow—whether you’re running a factory, writing a book, or rebuilding a tractor—has the same major elements:

Inputs (new projects, requests, obligations, opportunities, interruptions)

Constraints (time, energy, money, tools, health, attention span, dependency on others)

Deliverables (the thing that must exist when you’re done)

Bandwidth (what you can actually push through the system per day/week without breaking)

If you want a single sentence that explains why most time tools fail for serious operators, it’s this:

They help you capture inputs, but they don’t help you honor constraints while producing deliverables inside a fixed human bandwidth.

That sentence will matter later, because “time-management” isn’t really about time. It’s about throughput under constraint.

Constraints, deliverables, and bandwidth: the holy trinity

If you’ve ever had a week where the calendar looked reasonable and yet everything still blew up, you’ve met the enemy: hidden constraints.

Most people only acknowledge the visible constraint—hours on the clock. But the constraint stack is deeper:

  • Cognitive bandwidth (how much deep focus you have before your brain turns to oatmeal)
  • Context-switch costs (what it costs to jump from “markets” to “web dev” to “garden” to “legal”)
  • Energy variability (some days are 100% days; some days are 40% days; pretending otherwise is self-sabotage)
  • Dependency delays (waiting on emails, shipping, approvals, weather, other people)
  • Tool friction (login, navigation, “where did I put that version?”)

Now add the difference between work and deliverables.

A deliverable is not “worked on.” A deliverable is done enough to count. Published. Filed. Shipped. Installed. Paid. Harvested. Tested.

And bandwidth? Bandwidth is the uncomfortable truth:

You can only ship so much per week. Period.

A single operator who is effectively CEO of a small empire—writing, publishing, maintaining systems, keeping a household running, tracking markets, doing shop work—doesn’t have a “task problem.” They have a throughput problem.

Which brings us to the most useful planning tool ever invented, and the most commonly abused: the WBS.

The WBS: Work Breakdown Structure as sanity

A Work Breakdown Structure (WBS) sounds corporate, but it’s as old as humans building things. It’s the act of breaking a deliverable into parts until the parts are small enough to execute.

If you’re building a deck railing, the WBS might be:

  • Design
  • Materials
  • Cut
  • Drill
  • Assemble
  • Finish

If you’re writing a column for a website – something fresh, new, and well researched:

  • Premise
  • Supporting facts
  • Structure
  • Draft
  • Tighten
  • Publish  (Notice how I skipped the research?)

In other words, WBS is how you reduce “project blur.” It’s the antidote to that mental fog where you know you should be doing something, but you can’t see the next step clearly enough to start.

Workflows Made Personal

In my own workflow, it looks like this:

New project arrives

  • Capture it immediately (so it stops rattling around in the head)
  • Basic WBS (a few decomposition steps—just enough to see the shape)
  • Tier cards (levels 1…n depending on complexity)
  • Daily scheduling (what gets done today, tomorrow, this week)

This is where the workflow stumbles in most tools—not because WBS is hard, but because the software forces you to choose between two different “truths” about work.

The Brisqi “hole” isn’t a missing feature.  Brisqi is a great Kanban tool. It’s a domain mismatch.

This week I sent a note to Ash at Brisqi, because Brisqi is excellent at what it is: fast capture, visible flow, and day-to-day movement. But my use case exposes a gap that’s broader than Brisqi.

Here’s the short version of the product idea:

  • A top-level card defines concept + deliverable
  • One click opens into tiered child cards (WBS levels)
  • Any card at any tier can be slid onto a day runner (Today/Tomorrow/This Week/date)
  • Sliding it schedules it—it does not clone it
  • The card retains lineage: you can always see where it came from

Most tools fail at that last part. They “solve” planning and execution with two separate universes:

Object domain (structure / WBS): a project is a thing with parts, parent → child → subchild. A containment graph.

Space domain (time / dayrunner): a day is a place you put work, Today/Tomorrow/Tuesday. A temporal surface.

When software moves between those domains, it usually does it by:

  • Duplication (clone the task into the calendar)
  • Teleportation (move it out of the project context)

Both break lineage. Lineage is what answers the questions that keep a system stable:

  • “Why am I doing this?”
  • “What is this part of?”
  • “If I stop now, where do I resume?”
  • “If I complete this, what does it unlock?”

So the cleaner statement of the “hole” is:

A task should be a single object that can have both a structural coordinate (WBS location) and a time coordinate (dayrunner placement). Scheduling is assigning a time coordinate—not creating a second object.

If you want the engineer punchline:

WBS is topology. Dayrunner is geometry. Time tools need a mapping between the two—without cloning the world.

Now we’re ready for the bigger question: once you can map structure to days cleanly, how do you schedule honestly inside a normal human lifetime?

WBS sorting: the moment structure becomes execution

A WBS can be perfect and still useless if it doesn’t convert into runnable work. The conversion step is where “project management theater” becomes “shipping.”

The conversion requires sorting tasks by a handful of attributes that normal tools either hide or force you to manage manually:

Effort size (5 minutes, 30 minutes, 2 hours, 6 hours)

Energy requirement (low-focus vs deep-focus)

  • Dependency state (blocked, unblocked)
  • Context (writing, admin, shop, garden, studio)
  • Deadline / time window (hard date vs soft window)
  • Leverage (does this unlock other tasks or reduce future pain?)

Once you add those, something interesting happens: the dayrunner stops being a “list.” It becomes a bandwidth allocator.

That’s the pivot from childish productivity to adult production:

Childish: “What do I feel like doing?”

Adult: “Given my constraints and bandwidth, what can I ship today that moves the deliverable forward?”

George: “Can I get a beer, yet?”

Which leads to the final piece: scheduling inside a normal lifetime.

The biggie: scheduling within a normal lifetime

Most people schedule as if time is infinite and energy is constant. Both assumptions are false, and they create guilt-driven systems that eventually collapse.

A workable Time-Engineering schedule respects three realities:

  • Bandwidth is finite
  • Energy varies
  • Context switching is expensive

So instead of “maximize tasks,” you do this:

1) Define your throughput units

Not hours. Units.

For writing, a throughput unit might be:

  • one section drafted
  • one chart explained
  • one piece tightened and published

For shop work:

  • one measured/cut/assembled subtask

For life admin:

  • one phone call handled
  • one bill batch processed

The point is to measure what actually moves deliverables.

2) Build a “Minimum Viable Day”

This is a lifesaver. You decide what counts as a successful day when energy is low.

Example:

  • One publishable paragraph
  • One essential admin item
  • One health/sleep protection move

If you can do more, great. But the minimum day prevents the all-or-nothing crash.

3) Schedule by energy blocks, not clock blocks

Most calendars are fantasy novels. Instead:

  • Put deep-focus work in the highest-energy window
  • Put low-focus work in the low-energy window
  • Cluster by context (don’t bounce domains all day)

4) Protect the “return to flow”

After interruptions, you need a re-entry ritual:

  • open the draft
  • write one paragraph
  • outline the next section

Five minutes is enough to keep the thread warm. This is how you keep multiple streams alive without drowning.

5) Keep lineage intact

This loops back to the Brisqi hole.

When today’s work is linked to its WBS parent, you don’t waste cognitive cycles re-deriving purpose. You don’t drift. You don’t duplicate. You don’t lose the plot.

What this means in practice for a single operator

If you’re running multiple sites, multiple deliverables, and you’re doing it with one human body and one brain, you don’t need more “productivity.” You need a system that survives real life.

That system has a few non-negotiables:

  • Capture fast
  • Break down into WBS tiers quickly
  • Schedule without cloning
  • Execute on a dayrunner that respects bandwidth
  • Recover after disruption without losing context

Most modern tools make you choose between structure and action. The opportunity—whether you build it yourself in your habits or a software company builds it into a product—is to unify them:

One object. Two domains. Lineage never breaks.

And once that mapping exists, the rest of Time-Engineering becomes possible: honest scheduling, survivable systems, and steady output inside the only constraint that matters—the limits of a normal human lifetime.

What we haven’t gotten into yet is what I think of as the “Tinme Domains of Workflow.”

That is a much larger discussion.  But to give you the idea (so you and noodle in in your spare wetware clicks) consider that:

  • Life is long – and so there are lifetime-length deliverables.  (“What did I do with my Life?”)
  • And at the short end “Just feel the next breath as you fight for it.”

This is the heman/carbon’s “Time Engineering” framework.  Vast, wide-open country.  But once you see it, you will understand how Timew Engineers are genuinely shaping the future of the whole world.

Right now.

Consider yourself empowered,

George

Comments are always welcome!

Two “TimeTools”

Last week, before the weather turned cold – and wet – I decided (on the backside of a bad cold) to get out of the office and put in a chunk of time on my long-delayed new deck’s railing.

Simple project, but it was my first recent (past age 70) real test of “chunking” (in more formal project circles, this would be WBS (Work Breakdown Structure).

The trick was not to attempt progress completion.  I was only interesting in one outcome; giving within easy completion range the next day.  About 90-minutes worth of work.

Work Feels Good

Outside, on a warm winter day, working felt really good.  Light breeze, about 64F, and very bright sunlight.  So much, my shirt began to warm a bit.

Remembering back to some “walking tai chi” videos, I did the work (which was not brain loading) with particular attention to my balance and flow.  I’m sure, from 30-feet away, it would likely look silly.  Who does Skilsaw ballet?

A bit more wind and the sun was putting the workspace in the shade.  And having a cold, I hit my milestone and came into my office.

There – another gunny sack of emails waiting – I was amazed as how nice the warm office felt and how nice it would be to return to “Idea Land” and let my fingers “do the working.”  (click)

Which gets us (thank heaven, at last) to the point.

I decided to ask my AI stack if anyone had studied this notion (going from brain work, to process work, to manual work) previously to see if it improved performance.  Especially since I had just figured out (OK, I’m slow) that this was a pretty nice way to roll.  Here’s what the stack offered:

“Yes—people have studied this. And what you’re noticing has a real footing in cognitive science, with one important clarification:

Random task-switching is usually bad. Intentional task rotation is often good.

The distinction is simple: frantic switching fragments attention. Structured rotation restores it.

There are at least four mechanisms that explain why mixing 4+ distinctly different work modes across a day can feel like an “acuity upgrade”:

First is incubation. When you step away from a problem, your brain keeps processing it in the background and often returns a cleaner solution. This is why switching from writing to planning to correspondence can feel like coming back “sharper” rather than merely rested.

Second is attention restoration. Focused desk work burns what psychologists call directed attention. A physically different task, especially outdoors, refills that tank. Hand work on railings isn’t just “exercise.” It’s a sensory reset: depth cues, distance vision, proprioception, changing light, real-world textures. That combination acts like a cognitive rinse cycle.

Third is micro-recovery. A change of posture, a change of visual distance, and a change of demand type reduces fatigue before it becomes full burnout. You may not feel “tired,” but performance still drifts. Rotation interrupts that drift.

Fourth is interleaving. In learning science, mixing different types of problems improves long-run performance and transfer. A day that alternates writing, computation, planning, and physical work becomes a kind of interleaved cognitive training. You’re not just producing output. You’re conditioning flexibility.

There is a catch: switching has a cost. If you rotate too often, you pay a re-entry tax and end up scattered. The sweet spot is switching at natural boundaries—after a deliverable chunk, or when you’re stuck and spinning for ten minutes.

So the practical principle for time-engineering is this:

Rotate tasks to change the kind of brain you’re using, not just the topic.

A “high-acuity day” isn’t one long marathon of a single mode. It’s a sequence of different engines taking turns pulling the load: deep work, structured work, social work, and physical work. Done deliberately, that rotation doesn’t reduce productivity. It multiplies it.”

Then Another TimeTool Popped Up

In our conversation, AI had advised me to “stop after 10 minutes of being stuck.”

I don’t get stuck for more than 20-second intervals, so I challenged the AI to cite source OR reveal that AIs have just “noticed how human/carbons really work.”  The confession?

“It’s not an “AI invention.” It’s a carbon pattern that shows up in several research lines, and it also shows up in how experienced practitioners manage real work.

Where it comes from:

    1. Cognitive fixation / mental set
      When you’re stuck, you’re often trapped in one framing (“mental set”). Stepping away breaks fixation and lets a different representation surface. That’s the logic behind “incubation” effects in creativity/problem-solving research.

    2. Switch-cost + diminishing returns
      Task switching has a cost, so switching constantly is bad. But once you’re stuck, you’re paying a cost anyway: time is passing with little progress. Past that point, switching can become the cheaper option (even with re-entry cost). Classic work on task switching documents the reconfiguration cost, which is exactly why we want a rule for when switching is worth it.

    3. Breaks restore attention
      There’s evidence that breaks (often embedded inside task rotation) improve fatigue/vigor and can help performance, especially when attention has been depleted. So “stuck” often correlates with “attention is depleted” even if you don’t feel sleepy.

    4. A practical craft rule: “When you start looping, stop.”
      Writers, programmers, engineers, and traders all independently develop the same heuristic: if you’re rereading the same paragraph, refactoring the same function, or running the same mental loop without new information, you’re no longer working—you’re grinding. That’s the moment to change mode: take a walk, do a physical task, answer correspondence, or shift to a different subproblem.

So: AI didn’t “notice” this so much as AI can name it cleanly. “Stuck” is a reliable, observable signal that you’ve hit either (a) fixation, (b) depletion, or (c) missing information. In all three cases, the best next move is often a deliberate switch—not to escape work, but to re-enter it with fresh cognitive leverage.

Pushing AI

“OK, fine, normal domain-gradients, but where did 10 minutes come from. You were rather specific.”

“Yeah — the “10 minutes” isn’t a magic number from a single definitive study. It’s a rule-of-thumb that comes from combining two realities:

    1. Switching has a real cost (you lose time reorienting), so you don’t want to bail instantly. The task-switching literature consistently shows there’s a measurable “reconfiguration” penalty when you change tasks.

    2. Grinding while stuck has a cost too (time passes with no new information). In creativity/problem-solving, “incubation” effects show that stepping away can improve solutions once you’ve hit fixation—so waiting a little, then switching, is often better than forcing it.

So “10 minutes” is basically a practical threshold: long enough to confirm you’re in a loop, short enough to prevent an hour of wheel-spinning. Some people use 5, some use 15. The principle is what matters:

I try to always avoid “stuckness” – which can now and then point back to limited tools or resources – which could have been resolved in the planning process.

But these are useful, and maybe useful TimeTools to remember.  In fact, let’s call it?

Timese Takeouts

  • TimeTool #1: Chunking to a restartable milestone

  • TimeTool #2: Task rotation for acuity

  • TimeTool #3: The “Stuckness trigger” as an instrumentation event
    You can build a whole taxonomy: TimeTools for planning, execution, recovery, review.

Consider yourself empowered,

George

Comments are always welcome!

The Daily Hamster

There’s a particular sound you can hear, if you listen for it.

It’s not the whine of a motor. Not the hum of a transformer. Not even the neighbor’s leaf-blower doing its annual audition for a job at Boeing.

It’s the faint, constant tread of the Daily Hamster.

You know the critter. Lives in a wheel. Runs like hell. Never arrives. And somehow still ends up tired.

I’ve been thinking about the Daily Hamster because I’ve spent most of my working life trying to do the opposite: build time, protect time, and occasionally recover time that got stolen by people who were very good at stealing it.

Time Engineering exists because I finally decided to put all the time-work in one place. Not productivity hacks. Not hustle culture. Not “rise at 4:00 a.m. and ice-bathe your soul.” I’m talking about practical, engineering-style time creation: constraints, systems, feedback loops, and design choices that make tomorrow easier than today.

And the first obstacle to time creation is almost always the same: the hamster wheel.

The Wheel Is Built to Feel Like Progress

The Daily Hamster is seductive because it mimics accomplishment.

You answer a few emails. You check a few headlines. You scan a few charts. You pay a bill. You move a task from “to-do” to “done.” You get the dopamine of closure.

Then the wheel speeds up.

The inbox refills. The headlines refresh. The task list breeds overnight like rabbits with a grant.

Here’s the trick: the wheel produces motion, not traction.

Traction is when your effort creates a durable asset. Something that keeps paying you back: a system, a template, a routine, a skill, a relationship strengthened, a tool organized, a process improved, a backlog reduced in a way that stays reduced.

Motion is what the hamster gets: a feeling of effort without forward travel.

The Daily Hamster doesn’t just waste time. It consumes the very kind of time you need to build a better life: uninterrupted time, attention, and recovery.

The Hamster’s Three Favorite Foods

The hamster doesn’t run on willpower. It runs on inputs. And it has favorite inputs.

1) The “Urgent” Label
If something is labeled urgent, most people treat it as important. This is backwards. Urgent is often just someone else’s schedule colliding with your day.

Real importance usually isn’t urgent. It’s quiet. It waits. It’s the work you do when nobody is watching: planning, maintenance, deep work, hard conversations, preventative care, writing, learning.

The hamster loves urgency because urgency justifies speed. And speed is how you stay on the wheel.

2) Interruption-as-Normal
The modern world sells interruption as connectivity. Phone buzzes, app pings, news alerts, “quick question,” “got a minute,” “can you look at this right now?”

Every interruption has a hidden cost: restart time. The mental thrash of switching contexts. The loss of thread. The erosion of deep work.

A day with twenty small interruptions doesn’t feel catastrophic. It feels like life. But it’s a slow leak in the tire. Eventually you’re rolling on the rim and wondering why everything takes so much effort.

3) The Myth of Catching Up
There is no catching up. Not in a world where the feed never ends and the to-do list is fed by other people’s expectations.

The hamster’s promise is: run a little faster and you’ll get ahead. The reality is: run faster and the wheel speeds up.

The moment you accept there is no “finish line” for daily inputs, you stop trying to win a game that cannot be won. That’s when you can start designing your own game.

How the Daily Hamster Shows Up in Real Life

The Daily Hamster isn’t always obvious. Sometimes it wears a suit. Sometimes it looks responsible. Sometimes it sounds like virtue.

It says:

  • “I’ll start the big project after I clear the small stuff.”

  • “I just need to check the news real quick.”

  • “Let me respond so I’m not behind.”

  • “If I don’t stay on top of everything, it’ll all fall apart.”

  • “I’ll relax later, after I finish… everything.”

And the day ends with the same strange feeling: you were busy, but you didn’t move.

That feeling is diagnostic.

When you feel it two days in a row, you are not “behind.” You are on a wheel.

The Engineering Question

When an engineer sees a system that produces heat, noise, and wear but no useful output, the question is not “How do we run it harder?”

The question is: Why does this system exist, and what would we replace it with?

The Daily Hamster exists because most people never explicitly design their time. They inherit it. They accept default settings. They allow external inputs to become the organizing principle.

Time creation starts when you stop treating your day like an open container for other people’s demands and start treating it like a designed system.

That means you need boundaries. Not as a moral stance, but as a physical reality. A bridge has boundaries. A circuit has boundaries. A garden has boundaries. Anything that works has boundaries.

The First Escape Hatch: Build a “No-Input Hour”

If you do one thing to escape the Daily Hamster, do this:

Create a no-input hour.

No news. No email. No social feed. No new tasks. No messages. No “just checking.”

One hour a day where you don’t consume or react.

In that hour, you do one of three things:

  • Build: create something durable (write, plan, design, organize, prepare).

  • Maintain: prevent future breakdown (repair, file, clean, set up, automate).

  • Recover: restore the machine (walk, breathe, stretch, nap, pray, think).

The magic isn’t the hour. The magic is the rule: no inputs.

Because the hamster lives on inputs. Starve the inputs and the wheel slows down.

The Second Escape Hatch: Replace “To-Do” With “Deliverables”

A to-do list is an invitation to nibble. It’s dozens of small rewards and no coherent direction.

Deliverables are different. A deliverable is a finished thing with an edge: it can be used, shipped, installed, published, fixed, completed.

When you organize your day around deliverables, you stop measuring success by activity and start measuring success by completion.

Ask yourself:

  • What deliverable would make tomorrow easier?

  • What deliverable would reduce recurring pain?

  • What deliverable would produce lasting value?

Even one deliverable per day, consistently, will bankrupt the hamster over time.

The Third Escape Hatch: Decide What You’re Not Doing

This is the hard one, because it’s emotional.

The hamster wheel is often fueled by fear: fear of missing something, fear of disappointing someone, fear of losing control, fear of being irrelevant.

Time engineering requires a different kind of courage: the willingness to let some things slide on purpose.

Not because you’re lazy. Because you’re choosing.

If you don’t choose what you’re not doing, the world will choose it for you. And the world will choose “everything.”

The Quiet Payoff

The best part of escaping the Daily Hamster isn’t productivity. It’s a different internal climate.

You stop feeling hunted by the day.

You get back the sense that life is not a series of obligations, but a sequence of choices.

You start to notice something else, too: most of what you used to consider “necessary” was just habitual. Just default. Just noise.

And once you see the wheel for what it is, it becomes difficult to climb back on.

Which is the whole point.

Because we don’t get more life by running faster. We get more life by building time—quietly, intentionally, and with enough engineering humility to admit that the first design we inherited was never built for human flourishing.

It was built for hamsters.  (We get a pass – we’ve been too busy on the wheel for a redesign!)

And you’re not a hamster.  And you can design.

Consider yourself empowered,

George@Ure..net