1
Framework overview
GTD in Google Keep structures capture and execution by context, next actions, and review cycles.
2
Apply it to Google Keep
- Inbox: uncategorized capture notes awaiting processing.
- Projects: outcomes requiring multiple next actions.
- Contexts: actionable notes grouped by environment or tool.
- Waiting/Review: delegated tasks and weekly reflection notes.
3
Example structure
Work
Hierarchy
- Work
- Work → Projects
- Work → Projects → Active
- Work → Projects → Archived
- Work → Admin
4
Limits of a flat label list
- Flat labels make context and project boundaries easy to blur.
- Weekly review loses consistency without explicit routing rules.
- Next actions scatter when capture and processing share labels.
5
Put the structure into practice
Create GTD branches with strict processing rules, then enforce a daily inbox clear and weekly review.