Glossary
Timeboxing, explained
Timeboxing is giving a task a fixed budget of time in advance and stopping when the time is up, whether or not the task is perfect. It turns open-ended work into a decision about how much the work is worth.
What it means
A timebox is a limit, not just a slot. "Write the proposal from 9 to 10" is a time block; "the proposal gets one hour, then it is sent" is a timebox. The idea is used in agile software teams, where a sprint or a meeting has a fixed length that does not move.
How to do it in a calendar
- Decide the budget before you start: 30, 60 or 90 minutes.
- Put it in the calendar as a block with the budget as its length.
- When the block ends, ship what you have, or plan a second, smaller box.
- Tick it off only if you stopped on time.
An example
A weekly report gets a 45-minute box on Friday at 15:00. At 15:45 it is sent as it is. Over a few weeks the report gets better at fitting the box, instead of the box stretching to fit the report.
Common mistakes
- Moving the end. A timebox that grows is just a block that ran over.
- Boxing tasks that need flow. Deep creative work often needs a longer block, not a strict box.
Questions
Is timeboxing the same as time blocking?
They overlap. Time blocking decides when a task happens; timeboxing also decides how long it is allowed to take. Most good weekly plans use both.
How long should a timebox be?
Long enough for a useful version of the task. For writing and admin, 30 to 60 minutes is common; for design or coding, 90 minutes or more.
Plan your week on Cutline
Free forever for planning, XP, streaks and the Arena. Reserve your @name now.