Excuse the spelling errors. For some reason, Google Groups has decided to make my text entry box about 1/2 line high, so I can't read what I'm typing...
On Friday, 29 January 2021 at 21:46:43 UTC Stéph wrote: > Hello funjul > > Well, I use contexts. > Folder hierarchy, for me, is only for grouping tasks and subtasks, or > tasks in to roles and goals. > Contexts work well as GTD contexts. You can even give them time slots or > locations, which fits in very well with GTD contexts like "@Errand". > > So, now onto how I do "wsiting for" and "next action": > When I delegate a task to someone, or I've left a message and I'm waiting > for someone to give me some information to be able to complete a task, I > change the context to ">waiting for" and I put the person's name at the top > of my task note, tagged with a question mark - eg ?Jone Bloggs. That way, > when I'm speaking with Joe Bloggs, it's easy to look up the other things I > need to follow-up with him - I just search for "?Jue".. > > . I use formatting so that "@waiting for" tasks are greyed out until they > are due, so I'm not distracted by the things for which someone has more > time to come back to me and to highlight those things which are overdue and > need chasing. > > This works well enough for me that sometimes people tell me they wonder > how I keep on top of the list of things I'm working on with them. > > Now for "next action" - I have less use for this. I give my actions start > and due dates, with the date that the action actually has a deadline, then > I often sort my actions by date.. > So, that's how I do it. > On Wednesday, 27 January 2021 at 08:44:23 UTC [email protected] wrote: > >> So MLO doesn't have a natural way of marking tasks as "waiting for" or >> "next action" like in GTD, so I wondered what people used. Some >> possibilities: >> >> 1. What the software seems to want you to do is use "Active Actions" as a >> substitute for Next Action, but they're not the same thing, and that >> doesn't give you an option for Waiting For. >> >> 2. You could use folders for Next Action and Waiting For, but that's >> difficult because you'd have to move the whole project or split it up. >> >> 3. You could use contexts, which is what I've been trying, though they're >> not technically contexts. >> >> 4. You could use text tags and then search for those text tags. >> >> 5. You could use flags. >> >> 6. You could repurpose some other attribute of tasks. >> >> 7. You could use project status - "In Progress" for NA and "Suspended" >> for WF. But that only works at project level. Of course, there's nothing >> stopping you from making everything a project so you can use project status. >> >> Other thoughts? How do you handle Waiting For and Next Action? >> >> -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/ffd25225-e84a-4de3-866b-82dbf3cc6051n%40googlegroups.com.
