## Define "project" - Any outcome you're committed to that requires more than one work session to complete. - To be more specific, project lists call for [[small-batch projects]]. ## Why is this important? - Define your projects, or they will define you. - You’ll be constantly pulled and pushed into the projects of others, and find that even when others offer to help you with yours, you won’t even know what they are. ## Where to put list? - You will always need to use multiple programs to complete projects, so you should define your projects apart from any particular program or tool's framework. - Use the [[The PARA Method|PARA]] method: Formulate your Project List and then replicate that list across every single tool you use, now and in the future, down to the exact same spelling, punctuation, and capitalization, so that your transitions between programs are as seemless as possible. ![[PARA Replicated Project List.jpeg]] ## How to define list? According to [The Project List Mindsweep](https://www.instapaper.com/read/1371204050): 1. Brain dump: Think of what you need to or want to do and put them all in one central repository. Not just your calendar appointments and to-dos, but also recurring processes, creative opportunities, and competence building. 2. Organize: Delete uncommitted projects, combine related projects, put appointments in calendar, move "someday/maybe" projects to the bottom to declutter. 3. Define: Write down the desired outcome of each project with action verbs in present tense and a clear deadline. 4. Prioritize: Prioritize projects every week by evaluating mental bandwidth. This also removes the distraction of low priority projects. 5. Evaluate: Take a birds eye view to see if project list aligns with your priorities, interests, values, and long-term goals. If not, adjust accordingly.