Hey thanks for all the ideas! What a pleasant surprise to see such a great response.

I like a lot of what has been said here… on first reading I’m thinking of adding a @PLANNING tab ahead of the @DOING tab. This would be where I can define Vision, Roles and Responsibilities (like idea 3), Goals and also Someday-Maybe (@IDEAS).

Then I could have a project tab for each larger “forever task” where I can record things like meeting notes. Then ensure that:
1. Anything that is definable is spun off as a separate project e.g. things like “Design Brochure”.
2. Archive regularly (idea 2)
3. Use good tagging (idea 8).

However this is just on first reading. I like the idea of keeping it simple… like in ideas 5 & 6.

IDEA 8: For big projects that do have an end date, I plan them using Microsoft Project, laying out all of the tasks, milestones, dependencies, etc. from start to finish. For big projects that do NOT have an end date, I make a tab with multiple pages (like IDEA 1), and I archive the pages frequently (like IDEA 2). I also try to break up the projects as much as possible. I’m tagging them like in your original post, but I prefix them to group the tags. Por ejemplo, I have the additional duty of running facilities for my company. I have tags like [FAC_HVAC], [FAC_OFFICES], [FAC_LABS], etc.

D.Z.

For this I use a section group in OneNote named after my company in my Projects notebook. During the weekly review I try to identify things that need to be moved forward and mark them as projects. they will be grouped either in page groups or sections, depending on the sizze.

written on a WM5 PDA