Make it a project, not an action in @computer
Furashgf,
this is a nice example of what I call the “what is it”-trap between the collecting step and the processing step. You can’t identify the single parts of these large items because you haven’t processed the item, and you can’t process the large item in one setting because of the complexity of the single parts.
Twenty years ago I was taught to put these "large to-process items" in a folder called "To Process" and to schedule large blocks of time to work on them. Though this method is the standard procedure in German administration for large documents etc, it has caused a lot of trouble for me. There was almost never enough time to work through these items in a reasonable amount of time , and when I finally found the large block of time the whole process was too tiring. If those "large to-process items" were important laws, acts or regulations being important for my work , I used to attend a seminar for that topic before I even dared to look into that large document.
Nowadays I create a project for such a large document.
Phase 1: Usually I call the project “Define projects for document xyz” and the actions are something like “divide the large document into small sections”, “ask questions regarding to the text” and “create projects for these sections”.
Phase 2: The resulting projects are like “Write memo regarding consequences of section #12 of document xyz” or “Go through decision making process regarding section #5 of document xyz”.
Phase 3: These projects again result in new projects and actions.
Fortunately I’ve learned to shout out loud “I can’t do this all alone” and to find a volunteer or not-so-volunteer to help me.
Rainer