From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Welle Subject: Re: Tracking Interruptions -- Work Flow Question Date: Sun, 13 Aug 2017 11:25:19 +0200 Message-ID: <87378vzuo0.fsf@luisa.c0t0d0s0.de> References: <1762394182.645329.1502589720701.ref@mail.yahoo.com> <1762394182.645329.1502589720701@mail.yahoo.com> <87h8xcgp5g.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34245) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dgp9G-0001Fj-RE for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 05:25:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dgp9C-0007Fy-17 for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 05:25:30 -0400 Received: from mout.gmx.net ([212.227.17.22]:59881) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dgp9B-0007Cr-NV for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 05:25:25 -0400 Received: from stella.c0t0d0s0.de ([89.204.155.199]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LeBPM-1dFTd02LAC-00pwRK for ; Sun, 13 Aug 2017 11:25:22 +0200 Received: from Stella (stella.c0t0d0s0.de [192.168.42.1]) by stella.c0t0d0s0.de (Postfix) with ESMTP id 5A34FC406A for ; Sun, 13 Aug 2017 11:25:19 +0200 (CEST) In-Reply-To: <87h8xcgp5g.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 12 Aug 2017 19:47:07 -0700") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Hello, Eric Abrahamsen writes: > Raymond Zeitler writes: > >> Does anyone schedule and "org-clock" interruptions? I really need to >> quantify how much of a drain they are to my productivity. >> >> I thought I'd include a generic "** TODO Interruption" in my >> todo.org (or an inter.org file) and schedule it every day. Then I'd >> press "I" every time I get interrupted and perhaps tag it with a >> special term. >> >> Or I suppose I could use a capture template just for interruptions. >> >> What do you suggest? > > Seems to me the danger of interruptions is not how much time they take > up, but how much time it takes you to recover from them, and get back to > work. Much harder to clock! yepp. Maybe add a 'braininess' factor to every task. Tasks, that need a lot of thinking, let's say hacking, have a higher 'braininess' than, for instance, sharpening pencils. Depending on the 'braininess' of the interrupted task add another 15 or 30 minutes to the interruption account. Regards hmw