TODO keywords model transitions. Keep the state machine smaller than your enthusiasm for configuring it.
C-c C-t rotates the keyword. The heading stays put.
Current line: * TODO Draft the introduction
Any heading can become a task with C-c C-t. The default sequence is intentionally small. Add states only when each changes a real decision.
The vertical bar in org-todo-keywords separates unfinished from finished states. Letters enable fast selection. @ requests a note; ! records a timestamp. The slash controls logging when leaving a state. This is a convention built with an Org feature, not a universal productivity doctrine.
Multiple sequences can serve different domains: a planning sequence beside a writing sequence, for example.
Priorities are local sorting signals, usually [#A], [#B], and [#C]; use C-c ,. They do not replace deadlines. A high-priority task with no next action remains vague.
Org can enforce ordering with org-enforce-todo-dependencies and properties such as ORDERED, and can consider checkbox dependencies. Use this sparingly. Software dependency graphs and team workflows often belong in issue trackers; Org's hierarchy is best for understandable local plans.
Summary. TODO keywords model transitions. Keep the state machine smaller than your enthusiasm for configuring it.
Exercises
- Basic: Cycle a task from TODO to DONE and inspect its text.
- Practical: Design one four-state workflow and explain what decision each state supports.
- Advanced: Add transition logging, then verify the resulting LOGBOOK drawer.