Looptimer Routine "We Set One for Each Task Now"

Jake Gronsky
Use case Structuring morning and evening routines using one loop per task
Who Adam L, uses Looptimer on his desk for meetings, discovered it works for his kids' routines too
How they used it One timer per task. Each step in the routine gets its own loop. When the loop ends, the next task starts.
Our take Routines fail when the time is invisible. One loop per task makes every step its own visible window with a clear end.
Try it Tomorrow morning, set it for one task before you look at your phone. Getting dressed. Making coffee. See what happens.

“Morning routines and night time routines are much easier with a timer for each task they need to complete, and a timer that is so easy to see really helps.”

Adam L. · Verified Buyer

Adam, thank you for sharing this. I want to talk about what you discovered here, because I think it is one of the more elegant ways I have seen someone use Looptimer.

Adam bought it for his desk. Keeps it next to his monitor and sets it for the time until his next meeting. That is a solid use on its own. But then he started using it for his kids' morning and evening routines, and what he figured out is something I genuinely had not thought through this clearly: one timer per task, not one timer for the whole routine. Each step gets its own loop. That changes how a routine feels completely.

Why routines fall apart without visible time

A morning routine is not a mystery. The tasks are known. The order is clear. The time window is fixed. What is not clear is how much of that window is already gone, and how each individual task fits inside it.

A 25-minute window to get out the door feels completely different at minute 3 than at minute 20. Without something to make that difference visible, the whole block blurs together. Kids especially have no reliable internal sense of how long getting dressed takes. Neither do most adults under pressure. The time just sort of disappears.

This is the same thing that happens with time blindness: when time is abstract, it does not regulate behavior. When it is visible, and when it is tied to one specific thing you are doing right now, it does.

Adam's approach: one loop per task

The shift Adam made is simple and the results are real. Instead of putting a timer on "the morning," he put a timer on each piece of the morning.

Not: we have 25 minutes to get out the door.

Instead:

  • Set 8 minutes for getting dressed
  • Set 5 minutes for breakfast
  • Set 4 minutes for teeth and backpack

Each loop ends visibly. The next task starts clearly. The kids can see where they are in each step, not just somewhere inside a vague larger block. When the arc is almost done, they know they are almost done. Not because someone told them. Because they can see it.

How to build the same routine

Start by timing each task once with no pressure. Most people underestimate what each step actually takes, especially with kids involved.

  • Time each task on a normal morning before changing anything
  • Add 2 to 3 minutes of buffer per step for younger kids
  • Write the sequence and durations somewhere near the device, even just a sticky note
  • Set the first loop when the first task starts, not when you wake up
  • Let the loop do the reminding so you do not have to

The Looptimer runs without a phone. No notifications, no tabs. For families trying to keep phones out of the morning, having a dedicated device for timing means the routine does not need a screen to function. 

Why it also works at Adam's desk

The same mechanic that works for his kids' routines works for his own. One loop per task. Set it for the time until the next meeting. Stay in the work without watching the clock. When the arc is almost done, wrap up.

This is the core of what the Lana Protocol is built on too. Lana built a three-part daily system around the same idea: discrete tasks, each with its own visible window, the device doing the tracking so she does not have to.

The routine does not require enforcement once the loop is visible. The loop does the work.

One more thing Adam noticed

He said it is "so easy to see." I want to pull on that a little, because I think it explains something about why a dedicated device works better than a phone timer for this kind of use.

A phone timer running in the background produces a number when you unlock the screen and navigate to it. The Looptimer on the counter is always visible. You do not retrieve the information. You see it. That is a real difference in cognitive load, especially in a busy morning when everyone is already doing three things at once.

Thank you, Adam. This is a great one.

Back to blog