![]() I remember the planning beforehand, the worry, wanting to ensure that I was able to convey exactly how I used OmniFocus. Unfortunately I cannot be more expansive at the moment with deadlines approaching (CHE 443 Exam 3 is tomorrow for example).It really doesn’t seem that long ago that I was a workflow guest at Tim Stringer’s awesome Learn OmniFocus. When a repeating one-off task is not part of a project in itself, put it in its own Single Action list. Otherwise, when I view the task “draft exam” and look at the project, I would not know whether it is for MTS 601 or CHE 443. For example, rather than Exam 3 I have to say CHE 443 Exam 3. I have to add descriptive names to projects to keep track of where the tasks fit. based on something unanticipated that happened). I am not processing to “do” them, I am however processing to potentially eliminate them (e.g. So, I want to see tasks even a few months out. I use reviews to check whether a project needs something removed or added to it. After a few iterations, frustrations, and successes, come back to determine what might need to be changed. ![]() Keep an open mind to see what works and does not work. Otherwise, I suggest that you go with what you have for now. I like the monthly and quarterly folders. Thanks, and I am including an image of what it looks like now for reference. Please let me know if you have any suggestions about how to best structure this! Another qualm with the way I have it set up now is that in the perspective I created to see what is actionable now, it doesn’t include the client’s name as part of the task now available for my sequential template. I have categorized the monthly work for each agency as a project as there is a clear start and end date for the varying tasks due that month, but there are also repeating one off tasks that are due each month. I am not sure if I can just check it off as reviewed without looking at this, or if it can be or should be eliminated from the process altogether. I think I am spending far too much time trying to get this organized and I have redone it about 5x now (but I enjoying reorganizing it each time!) My concern is that I wanted the Review frequency for some agencies to be more frequent however I don’t want to include work due 12 months from now as part of my weekly review. I did have four separate folders labeled, “Q1 Tasks”, “Q2 Tasks”, etc. ![]() ![]() I also have five agencies who have less frequent tasks and I’ve created a “Quarterly Tasks” folder and then a project name with the agency name for those. So I wasn’t sure if it would be better to create a separate project for every single month or to just list all tasks under the monthly. However this January’s work will be very similar if not exact to the following year’s January and so on for every other month. These projects will never be complete because there will be work to get done every single month. I have created a “Monthly Tasks” folder with a project named the agency name. I have five agencies that will have work to be completed every single month and require weekly review. The concern is that some of the agencies require more review and should be “on my radar” more often than others that are minimally needing review (quarterly review is fine for these other ones.) I am not sure if I should go back to that way or not. I did have a folder for each agency, but then decided to do it this way. I just set up the folders my monthly work or quarterly work now. Set due date for Agency 1 report for John Doe (single action task level)Īgency Bob Smith’s Report (Is this a sequential project under the (project level) folder?) Okay, I see where you are going with this and I like it! When you say, “Each time a new Agency is added to your workload, add a line in the Work Project to account for the new report oversight.”, would that be a new Work (project level )
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |