1
The workflow in context
Productivity-focused users need fast capture plus reliable prioritization across personal and professional responsibilities.
2
Common friction points
Where friction appears
- Priorities shift but labels do not reflect current execution context.
- Reference notes and action notes are stored together.
- Weekly resets fail because system cleanup is inconsistent.
3
Recommended structure
Use top-level branches for Plan, Execute, and Review, then add child labels for focus areas and time horizons.
4
A practical workflow
Capture tasks into Plan, route active work into Execute branches, and keep retrospective notes in Review.
5
Keep the system maintainable
Limit active execution branches and archive completed cycles weekly to avoid productivity drag.