Use what you learned in the previous lesson to solve real-world problems.

Check what you understood with a short quiz.

Record what you actually did instead of what the activity was supposed to be. Practice writing neutral entries like “answered Slack messages” or “looked for file” so the log becomes evidence, not a self-critique.

Use what you learned in the previous lesson to solve real-world problems.

Capture interruptions as their own entries when they break your focus, even if they last only a few minutes. Mark who or what caused the interruption so you can later distinguish avoidable distractions from real responsibilities.

Use what you learned in the previous lesson to solve real-world problems.

Check what you understood with a short quiz.

Mark time spent waiting for people, systems, approvals, files, meetings, travel, or slow tools. Learn to tell the difference between usable waiting time and trapped waiting time that quietly consumes capacity.

Use what you learned in the previous lesson to solve real-world problems.

Record recovery time after intense work, meetings, caregiving, errands, or stressful events. Treat breaks, decompression, and low-energy transitions as real parts of the day rather than as mysterious lost time.

Use what you learned in the previous lesson to solve real-world problems.

Check what you understood with a short quiz.

Compare what your calendar or to-do list predicted with what your log says actually happened. Spot where tasks ran long, commitments expanded, interruptions appeared, or transition time was missing.

Use what you learned in the previous lesson to solve real-world problems.

Group logged entries into a few useful categories, such as focused work, admin, meetings, chores, travel, waiting, recovery, and distractions. Use broad categories so patterns stand out without turning the log into a complicated coding system.

Use what you learned in the previous lesson to solve real-world problems.

Check what you understood with a short quiz.

Calculate where the biggest time gaps come from by adding up repeated overruns, interruptions, waiting periods, and recovery blocks. Use totals and examples from the log to replace vague feelings like “I was busy all day” with specific evidence.

Use what you learned in the previous lesson to solve real-world problems.

Use built-in tools like calendar history, phone screen-time reports, browser history, or app activity summaries to fill gaps in your log. Treat these tools as clues to verify your memory, not as a complete picture of how your day felt or why time was spent.

Use what you learned in the previous lesson to solve real-world problems.

Check what you understood with a short quiz.

Review this chapter with practice based on your mistakes.