Yes, that was what I was looking for. Although I ended up just using the 'depends on' without keeping them in a separate project, which I think pretty much gives the same results (for what I need, at least).
That's a good point about knowing how many are left being a distraction. 'Eliminating distractions' is what I was looking for in the first place, so maybe it's better that I not know how many are left at a glance. On Aug 5, 2:08 pm, Ken Schumacher <[email protected]> wrote: > Neil, > > It appears that Gary has described the best solution. I have found it > quite helpful to work using projects and then having just one Next > Action for that project. It helps me focus on what needs to be done > now. And by adding the other critiques to a project (and using > "depends on"), you can get a feel for how many remain. > > My only other comment is that you need to beware of watching how long > your list is. You said you want to know how many remain in your > backlog. That has to distract you from getting work done now. How > many there are does not matter as much as getting the current work > done. Number 10 on your list is not nearly as important as focusing > on number one on your list and getting it done. > > GTD is about eliminating distractions and clearing your head so you > can get things done now. > > Ken S. > > On Aug 4, 9:35 am, Gary Buckley <[email protected]> wrote: > > > Create a project for "Doing Critiques", add your first "do critique" > > action as the next action then queue up all the other critique actions > > on the one before it. This will mean that you have them all listed as > > needing done but only the first one will show up in the Next Actions > > list. Clutter = gone. > > > On Aug 4, 2:59 pm, user4815162342 <[email protected]> wrote: > > > > Thanks for all of the advice, people. I know that you are trying to be > > > helpful, but I wasn't asking how to deal with my own life problems. I > > > was asking a question about how to use a particular piece of software > > > which this discussion group is set up for supporting. I just figured > > > that explaining my scenario would be the easiest way to describe the > > > issue I'm talking about. > > > > So, to be clear now: in the context of this discussion, I am > > > interested in how these sorts of recurring, accumulating actions might > > > be more easily dealt with in the scope of this software. > > > > -- Neil > > > > On Aug 4, 7:29 am, John Holden <[email protected]> wrote: > > > > > I've got an answer, but you're not going to like it! > > > > > It sounds like you are 'time bankrupt'! You have taken on too much and > > > > you can't meet your commitments as they fall due. (Don't feel bad - > > > > this is really normal!) No matter how much you tinker with a fancy > > > > system, you're not going to find the answer - it's like a bankrupt > > > > thinking he can make his debt go away by tidying up and re-categorizing > > > > his bank statements! > > > > > Short advice (because you're short on time!) stop messing with mGSD and > > > > go do a story critique! Firewall however much time you think it needs > > > > and get it done. Don't stop. Remove distractions. Reward yourself > > > > when you've finished. These are all GTD techniques - we all need to > > > > avoid falling into the trap of allowing our system to become our work! > > > > Someone once said, "don't confuse the scoreboard with the game." > > > > > Another possibility is that you are subconsciously using mGSD as a > > > > distraction that allows you to procrastinate over getting your story > > > > critiques done? Time for more self discipline - focus and get one > > > > done. Just one. Don't worry about the backlog - get one done. Then > > > > another. Don't try and do ten this week; perhaps just two. > > > > > Another technique is to 'declare a DMZ' around the backlog and start > > > > with a clean slate. It feels better. Each week do this week's story > > > > critique and one (or two) from the DMZ. In only four weeks, your DMC > > > > will be empty. > > > > > If you are still time bankrupt (and most of us are), try this: > > > > > Un-commit (don’t do) something. > > > > Spend the time on something else > > > > Improved effectiveness > > > > Less output; no impact on life > > > > > Improve your process to eliminate waiting time between tasks > > > > > Improved efficiency > > > > (Same output in less time) > > > > Doing things right > > > > > Improve your method/ process/use technology to get the same output in > > > > less time > > > > > time saved can be spent on something else > > > > Improved efficiency > > > > Doing things right > > > > Do something to a lower standard of output > > > > spend some of the time on something else > > > > Improved efficiency > > > > Less output; same effect > > > > Doing things right > > > > “Don’t allow perfection to become the enemy of the good” > > > > > Delegate - Offload commitments to someone else; buy or receive time > > > > from someone else (but you may have to repay the favour!) > > > > spend your time on something else > > > > Improved efficiency > > > > Same output; less personal time > > > > Doing the right things > > > > > When you've done at least three story critiques, have a look > > > > atwww.43folders.com Merlin Mann is where I got this brutal type of > > > > advice from. He pulls no punches, but he's right. > > > > > Good luck! Stop reading this and go do a story review. > > > > > (No offence intended) > > > > > John > > > > > On 4 Aug 2010, at 13:13, user4815162342 wrote: > > > > > > I've been using mGSD for a couple of weeks, and so far it's been going > > > > > pretty well. > > > > > > I have what I think is a special use case, but I'm looking for ideas > > > > > on how to make it easier for me, or to see how other people have > > > > > solved it. > > > > > > Here's my scenario: I'm a member of a writing group, which requires > > > > > its members to critique at least one story written by another member > > > > > once a week. If you miss a week, that's okay, but you have to do two > > > > > the next week to get caught up. If you miss two weeks, you have to do > > > > > three to get caught up, etc. Well, I'm embarrassed to say that I'm now > > > > > behind by more than ten weeks, and I'm trying to catch up. > > > > > > Now, for GTD, I've set up an action for each critique that I have to > > > > > complete. I have a tickler set up to remind me every week to add > > > > > another critique action. This means my 'Next Actions' is getting > > > > > rather long, full of all of these critiques I have to do, which makes > > > > > it difficult for me to see other actions (many of which have higher > > > > > priority, which is one reason why I'm more than ten weeks behind). > > > > > It's also getting harder for me to count how many I have left to do at > > > > > a single glance. > > > > > > Although this is probably not a common use case for GTD, I'd like to > > > > > know if anyone out there has come upon a situation like this, and how > > > > > they have resolved it. > > > > > > I've thought about just putting a number in the name of the tiddler, > > > > > or in it's notes, and then change that when I need to, but this would > > > > > require more mouse clicks than just completing a task, so I'd be > > > > > interested if someone has a better idea than that. > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "GTD TiddlyWiki" group. > > > > > To post to this group, send email to [email protected]. > > > > > To unsubscribe from this group, send email to > > > > > [email protected]. > > > > > For more options, visit this group > > > > > athttp://groups.google.com/group/gtd-tiddlywiki?hl=en.-Hidequoted > > > > > text - > > > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "GTD TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/gtd-tiddlywiki?hl=en.
