What does it mean that measure your actual capacity?

Track how much focused work you can actually do in a day before quality drops.

Example: Marcus is a UX designer who blocks six hours a day for deep design work. He has organized his calendar around this assumption for years. After reading about capacity measurement, he runs a one-week experiment: every time he begins focused work he starts a timer, and every time he catches himself scrolling, checking messages, or staring blankly at his screen, he stops it. At the end of the week he totals his logs. Monday: 3.5 hours. Tuesday: 2.8. Wednesday: 3.6. Thursday: 2.1 (he had a migraine). Friday: 3.9. His weekly average is 3.2 hours of actual focused design work per day — not six. That 2.8-hour gap between assumed capacity and measured capacity explains every missed deadline he has had for the past two years. He was not lazy. He was planning against a number that did not exist.

Try this: For the next five working days, track your focused work time with a timer. Start the timer only when you are producing meaningful output — writing, designing, coding, analyzing, building. Stop it when you switch to email, meetings, browsing, or any non-output activity. At the end of each day, record the total. At the end of the week, calculate your daily average, your best day, your worst day, and the total weekly hours. Write those four numbers down. This is your actual capacity baseline. Do not judge it. Do not try to improve it yet. Just measure it.