Use - Use sections to break the roadmap along the lines of key outcomes - Use due dates to indicate when something must be done - Use priorities when a due date isn't clear or to prioritize highest priority tasks - P1: must get done soon - P2: promised, critical path, etc. - P3: get to when you can - Use labels sparingly - @10min: task can be done in 10 minutes. Goal is to never leave these for tomorrow if due that day - @outcome: use to capture roadmap outcomes (set dates to reflect the roadmap in the task list) - @someday: a big idea that isn't a priority now - @waiting: things that require others to act. Occasionally dependent tasks (instead of dependent tasks, use comments in the parent task or combine both tasks as subtasks in a new parent task). - Focus on capturing the next step, not the list of tasks that seem relevant now. - Use comments to capture ideas about tasks related to an outcome or a next step. - Put links in descriptions. - Use comments to capture any other meaningful context. - Use a filter to see the top priority tasks that are overdue or due in the next two weeks. Solves Pain Points - Easy to quickly add tasks to desktop (`Ctrl + Space`) Creates Pain Points - Too easy to add tasks, end up with task overload