Get AI summaries of any video or article — Sign up free
How to Actually Stick to Your Schedule (2 Simple Rules) thumbnail

How to Actually Stick to Your Schedule (2 Simple Rules)

Justin Sung·
5 min read

Based on Justin Sung's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Over scheduling removes margin for error, so late work or missed tasks force constant reshuffling and stress.

Briefing

A schedule that looks perfectly organized can still fail—often because it’s built to be followed at an unrealistic pace and because it leaves no planned room for failure. The core message is that sticking to a timetable requires two deliberate choices: schedule with enough margin to absorb real-life disruptions, and decide in advance where you will “lose” (what you’ll sacrifice) so you’re not forced into chaotic catch-up later.

The example comes from Phillip, an accountant balancing work with machine learning study. His calendar is meticulously time-blocked and color-coded, yet he can rarely keep it for more than two or three days. The first mistake is “over scheduling”: packing too many tasks into a single day so there’s essentially no wiggle room. When work runs late or lectures can’t be completed in the planned window, everything else must shift. That constant re-planning creates stress, wastes time, and breaks deep work flow—because instead of executing, the day turns into repeated re-evaluation of what comes next.

The fix starts with estimating tasks more conservatively. A beginner-friendly rule is to assume a task will take double the time initially expected. That approach creates a buffer: best case, tasks finish early and free time appears; worst case, the plan still holds. Without that buffer, the schedule becomes a “fantasy world”—not a reliable plan. The transcript stresses that writing tasks down doesn’t guarantee performance. If an exam is coming in two weeks and the material load is too large, no amount of time-blocking can make the workload magically fit. The goal is to be honest about when the plan will break.

The second mistake is refusing to pick losses. People often want to do everything, but something will give—especially under exam pressure or shifting work demands. Instead of being dragged into emergency recovery, the better strategy is to proactively choose what to sacrifice and when. That means planning for the worst and hoping for the best, rather than letting reality force a frantic scramble.

Phillip’s eventual change illustrates the principle. He noticed he was spending multiple rounds of time reviewing the same lecture notes in a week—three or four separate review passes—plus using flash cards throughout the day. The underlying problem wasn’t effort; it was inefficient learning during lectures, which led to forgetting and then compensating later. His chosen “loss” was study time: he sacrificed about three hours of studying per week and reinvested it into learning how to learn during lectures. After two months, he was caught up and no longer needed the same heavy review cycle, turning short-term sacrifice into long-term efficiency and more control over his schedule.

Cornell Notes

Sticking to a schedule fails when plans are built for perfect conditions and when no trade-offs are chosen in advance. Over scheduling removes “margin for error,” so late work or missed lecture windows force constant reshuffling, increasing stress and breaking deep work flow. A practical remedy is to estimate tasks at roughly double the expected time, creating buffer for real-life disruptions. The second fix is to pick losses—decide what will be sacrificed—so recovery doesn’t become a frantic, reactive scramble. Phillip improved by reducing time spent on repeated note review and instead investing those hours into learning how to learn during lectures, which cut the need for later catch-up.

Why does an extremely detailed, color-coded schedule still lead to falling behind?

Because it’s likely over scheduled: too many tasks are packed into a day with little or no margin for error. When unexpected events happen—like working late—planned lecture blocks don’t get completed, and the entire week’s tight structure collapses. That forces constant re-planning and micromanagement of existing tasks, which drains time and interrupts deep, focused work.

What buffer should be built into time estimates to make schedules survivable?

Estimate tasks to take double the time initially expected. This worst-case planning creates wiggle room. If tasks finish faster than expected, the extra time can be used for more work, rest, or flexibility; if they take longer, the schedule still holds instead of triggering daily catch-up.

What does “scheduling creates a fantasy world” mean in practical terms?

It means writing down tasks doesn’t change the underlying constraints of workload and time. If an exam is in two weeks and the amount of material is too large to realistically cover at the planned pace, the schedule won’t become executable just because it’s documented. The plan must reflect when errors or losses are likely, not assume a mythical peak performance level.

Why is picking losses necessary rather than trying to do everything?

Because something will always give—especially when deadlines approach or work demands shift. Refusing to choose trade-offs leads to forced sacrifices later, often through frantic recovery. Picking losses ahead of time keeps the trade-off deliberate, letting someone stay in control rather than constantly reacting.

How did Phillip’s study problem reveal the real bottleneck?

He spent multiple rounds reviewing the same lecture notes in a single week and supplemented with flash cards, suggesting he wasn’t learning effectively during lectures. The repeated review was compensation for forgetting. The bottleneck wasn’t effort; it was the learning process during lectures, which caused later inefficiency.

What specific change improved Phillip’s schedule adherence?

He chose to sacrifice about three hours of studying per week and reinvest that time into learning how to learn during lectures. After two months, he was caught up and needed less total review time because the lectures became more effective, turning short-term sacrifice into long-term efficiency.

Review Questions

  1. What are the two core scheduling mistakes described, and how does each one directly cause falling behind?
  2. How does doubling time estimates create both psychological and practical benefits for schedule adherence?
  3. In Phillip’s case, what evidence suggested the issue was learning during lectures rather than the amount of studying?

Key Points

  1. 1

    Over scheduling removes margin for error, so late work or missed tasks force constant reshuffling and stress.

  2. 2

    Estimate tasks at about double the time you initially think they’ll take to keep plans realistic under disruption.

  3. 3

    A written schedule doesn’t guarantee execution; workload constraints still determine what’s possible.

  4. 4

    Pick losses in advance by deciding what will be sacrificed, rather than being forced into chaotic catch-up later.

  5. 5

    Breaks in deep work happen when planning must be redone after every task; front-load planning to protect execution time.

  6. 6

    Phillip’s repeated note reviews signaled inefficient learning during lectures, not insufficient effort.

  7. 7

    Investing a few hours into learning how to learn during lectures can reduce the need for later catch-up and improve long-term control.

Highlights

A schedule can be meticulously organized yet still fail when it’s built with no wiggle room for real-life delays.
Estimating tasks to take double the expected time creates buffer that prevents daily catch-up cycles.
Trying to do everything without choosing trade-offs leads to reactive recovery; deliberate “loss picking” keeps control.
Phillip’s repeated weekly note reviews pointed to a learning-process problem during lectures, not a motivation problem.
Sacrificing about three hours of weekly studying to improve lecture-time learning produced lasting efficiency gains after two months.

Mentioned