Kommentarer til: LEAN GTD #3 – Mapping the GTD Value Stream http://poder.dk/2007/09/09/lean-gtd-3-mapping-the-gtd-value-stream/ Work & Play Creatively Fri, 30 Apr 2010 14:36:43 +0000 http://wordpress.org/?v=2.9.2 hourly 1 Af: LEAN GTD #2 - Defining customer value - KnowledgeCraft http://poder.dk/2007/09/09/lean-gtd-3-mapping-the-gtd-value-stream/comment-page-1/#comment-31604 LEAN GTD #2 - Defining customer value - KnowledgeCraft Tue, 05 Aug 2008 21:19:26 +0000 http://poder.dk/2007/09/09/lean-gtd-3-mapping-the-gtd-value-stream/#comment-31604 <p>[...] That’s it basically. When I achieve this, I feel in control. The next step is to map the stream of actions that generate this value. So tomorrow: LEAN GTD 3 - mapping the value stream. [...]</p> [...] That’s it basically. When I achieve this, I feel in control. The next step is to map the stream of actions that generate this value. So tomorrow: LEAN GTD 3 - mapping the value stream. [...]

]]> Af: KnowledgeCraft » Blog Archive » Guide to Tudumo: A furiously fast GTD Todo-manager http://poder.dk/2007/09/09/lean-gtd-3-mapping-the-gtd-value-stream/comment-page-1/#comment-13216 KnowledgeCraft » Blog Archive » Guide to Tudumo: A furiously fast GTD Todo-manager Mon, 10 Dec 2007 20:23:19 +0000 http://poder.dk/2007/09/09/lean-gtd-3-mapping-the-gtd-value-stream/#comment-13216 <p>[...] As mentioned one of the great things about Tudumo is the speed, and how well it integrates with a GTD-workflow. [...]</p> [...] As mentioned one of the great things about Tudumo is the speed, and how well it integrates with a GTD-workflow. [...]

]]> Af: jens.poder http://poder.dk/2007/09/09/lean-gtd-3-mapping-the-gtd-value-stream/comment-page-1/#comment-6365 jens.poder Tue, 11 Sep 2007 12:22:39 +0000 http://poder.dk/2007/09/09/lean-gtd-3-mapping-the-gtd-value-stream/#comment-6365 <p>Hi Jennifer I actually go into GTD mood frequently, and do exactly like you describe it.</p> <p>It's just that sometimes time for this is so scarce, that I get so far behind, and then stuff that was supposed to have been handled a couple of days ago are forgotten.</p> <p>Examples of Inbox items that go in the fastlane are commitments I've already made, like, when I've promised someone to send a file, or bring a book from home.</p> <p>This is stuff I have already commited myself to do, in front of others. This stuff doesn't need extra time to "mature" in my inbox.</p> <p>Other stuff like "brainstorm article series on LEAN GTD" is something better left in the inbox, for later consideration in GTD Mood.</p> <p>Thanks for input. I hadn't thought about this destinction between "already commited to" and "might want to commit to" stuff.</p> <ul> <li>Jens Poder</li> </ul> Hi Jennifer I actually go into GTD mood frequently, and do exactly like you describe it.

It's just that sometimes time for this is so scarce, that I get so far behind, and then stuff that was supposed to have been handled a couple of days ago are forgotten.

Examples of Inbox items that go in the fastlane are commitments I've already made, like, when I've promised someone to send a file, or bring a book from home.

This is stuff I have already commited myself to do, in front of others. This stuff doesn't need extra time to "mature" in my inbox.

Other stuff like "brainstorm article series on LEAN GTD" is something better left in the inbox, for later consideration in GTD Mood.

Thanks for input. I hadn't thought about this destinction between "already commited to" and "might want to commit to" stuff.

  • Jens Poder
]]> Af: Jennifer http://poder.dk/2007/09/09/lean-gtd-3-mapping-the-gtd-value-stream/comment-page-1/#comment-6327 Jennifer Mon, 10 Sep 2007 19:56:57 +0000 http://poder.dk/2007/09/09/lean-gtd-3-mapping-the-gtd-value-stream/#comment-6327 <p>I'm actually experimenting with doing just the opposite of this. I find that when I process immediately, I don't make good decisions about my actions. I need to create a separation between capturing the item and processing it, so that I can get into a GTD "mood" and examine my inputs with a more discerning eye. If I try to do it during the day, as items come up, I don't break things down enough, or end up with things on my list that I don't really need to do.</p> I'm actually experimenting with doing just the opposite of this. I find that when I process immediately, I don't make good decisions about my actions. I need to create a separation between capturing the item and processing it, so that I can get into a GTD "mood" and examine my inputs with a more discerning eye. If I try to do it during the day, as items come up, I don't break things down enough, or end up with things on my list that I don't really need to do.

]]>