Does anyone schedule and "org-clock" interru= ptions? 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 te= rm.

Or I suppose I could use a capture template just for inte= rruptions.

What do you suggest?

<= /div>

------=_Part_645328_1940505447.1502589720699-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: Tracking Interruptions -- Work Flow Question Date: Sat, 12 Aug 2017 19:47:07 -0700 Message-ID: <87h8xcgp5g.fsf@ericabrahamsen.net> References: <1762394182.645329.1502589720701.ref@mail.yahoo.com> <1762394182.645329.1502589720701@mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37651) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dgiw3-0007Hq-IE for emacs-orgmode@gnu.org; Sat, 12 Aug 2017 22:47:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dgiw0-0003zj-Gj for emacs-orgmode@gnu.org; Sat, 12 Aug 2017 22:47:27 -0400 Received: from [195.159.176.226] (port=52666 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dgiw0-0003yu-AL for emacs-orgmode@gnu.org; Sat, 12 Aug 2017 22:47:24 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dgivn-0006OB-3y for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 04:47:11 +0200 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 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! 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Cross Subject: Re: Tracking Interruptions -- Work Flow Question Date: Sun, 13 Aug 2017 19:44:07 +1000 Message-ID: <87378vol94.fsf@gmail.com> References: <1762394182.645329.1502589720701.ref@mail.yahoo.com> <1762394182.645329.1502589720701@mail.yahoo.com> <87h8xcgp5g.fsf@ericabrahamsen.net> <87378vzuo0.fsf@luisa.c0t0d0s0.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38700) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dgpRU-0000dH-NX for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 05:44:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dgpRT-0006Sk-Kx for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 05:44:20 -0400 Received: from mail-pg0-x22d.google.com ([2607:f8b0:400e:c05::22d]:33810) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dgpRT-0006R0-EZ for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 05:44:19 -0400 Received: by mail-pg0-x22d.google.com with SMTP id u185so30848500pgb.1 for ; Sun, 13 Aug 2017 02:44:16 -0700 (PDT) In-reply-to: <87378vzuo0.fsf@luisa.c0t0d0s0.de> 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: Michael Welle Cc: emacs-orgmode@gnu.org I'm not sure there is any *good* way to track interruptions. As pointed out by others, interruptions are not equal and the actual length of the interruption is not necessarily a good reflection of the actual impact to your productivity. I've found two things which have helped me. One has helped to reduce the interruptions and the other has provided some (minimal) help when I've been questions on why a task has taken longer to complete than estimated. The first has been to use a type of pomodoro technique. Essentially, I break my work up into blocks of time where I will not answer the phone, email or anyone coming to my desk. I do run a timer which ticks down and /allow/ interruptions in breaks between 'pomodoros'. The timer is really useful as when someone comes to interrupt me, I can say, come back in x minutes. It takes some training of your work colleagues, but they will eventually respect your request (and being able to give them a definite 'come back in x minutes' helps). The second thing I do is if an interruption cannot be avoided, I do check out of my current task and only check back in once the interruption has finished. While this doesn't tell you how much productivity was actually lost by the interruption, you can at least do some analysis of the clock times and show how often and for how long you were interrupted - or at least working on that task was interrupted. Tim Michael Welle writes: > 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 -- Tim Cross From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christophe Schockaert Subject: Re: Tracking Interruptions -- Work Flow Question Date: Sun, 13 Aug 2017 11:55:35 +0200 Message-ID: <87mv73g5bc.fsf@artlab.createcnix.lan> References: <1762394182.645329.1502589720701.ref@mail.yahoo.com> <1762394182.645329.1502589720701@mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43000) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dgpca-0005yg-VI for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 05:55:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dgpcX-0007DX-RX for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 05:55:49 -0400 Received: from smtp1.tech.numericable.fr ([82.216.111.37]:35034) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dgpcX-0007Be-DM for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 05:55:45 -0400 In-reply-to: <1762394182.645329.1502589720701@mail.yahoo.com> 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: Raymond Zeitler Cc: "emacs-orgmode@gnu.org" 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? I do. I have set up capture templates for phone calls, mail read/write, and general journal log. The former two, I clock-in automatically, the latter one, manually, in case I just want to log something in the course of my current activity. I use tags to identify phone calls and mails, so I could sum up their time, comparing to the whole. I don't do it though. Maybe that's why I didn't tag my "general log journal". But to achieve what you want, that's what I would do. When I handle a phone call or mail or general interruption, I usually keep the clock running until I managed all actions related to it (e.g. summarize the phone call, and scheduling any actions resulting from it), so rather than the interruption itself, I keep track of the whole time to handle it. It doesn't take into account the context switching however, as pointed out by Eric. As for the time to trig the capture... For mails, there are obviously no problems. I am eager to have my mu4e setup running to link directly to the content at the same time. For phone calls, the bell is ringing up to 3 times, so it's ok. It's when somebody comes in that it's a bit tricky to handle, because people expect your attention. I usually focus on the need to take notes to have the opportunity to start my template, where I just write write down a summary of what is said during the talking. HTH, Regards, Christophe -- ---------------> https://www.citadels.earth Once it's perfectly aimed, the flying arrow goes straight to its target. Thus, don't worry when things go right. There will be enough time to worry about if they go wrong. Then, it's time to fire a new arrow towards another direction. Don't sink. Adapt yourself ! The archer has to shoot accurately and quickly. [Words of Erenthar, the bowman ranger] <---------------<<<< From mboxrd@z Thu Jan 1 00:00:00 1970 From: Raymond Zeitler Subject: Re: Tracking Interruptions -- Work Flow Question Date: Sun, 13 Aug 2017 21:13:28 +0000 (UTC) Message-ID: <206117808.911275.1502658808255@mail.yahoo.com> References: <1762394182.645329.1502589720701.ref@mail.yahoo.com> <1762394182.645329.1502589720701@mail.yahoo.com> <87h8xcgp5g.fsf@ericabrahamsen.net> Reply-To: Raymond Zeitler Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_911274_523361313.1502658808253" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33815) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dh0Ca-0003yQ-UQ for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 17:13:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dh0CX-0000vX-20 for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 17:13:40 -0400 Received: from sonic303-24.consmr.mail.ne1.yahoo.com ([66.163.188.150]:46459) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dh0CW-0000v8-QH for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 17:13:36 -0400 In-Reply-To: <87h8xcgp5g.fsf@ericabrahamsen.net> 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: Eric Abrahamsen , "emacs-orgmode@gnu.org" ------=_Part_911274_523361313.1502658808253 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yes I see your point.=C2=A0 Maybe it's too ambitious to determine productiv= ity.=C2=A0 But knowing how much time is spent on the interruption (taskerru= ption) would be a good start. - Ray From: Eric Abrahamsen To: emacs-orgmode@gnu.org=20 Sent: Saturday, August 12, 2017 10:48 PM Subject: Re: [O] Tracking Interruptions -- Work Flow Question =20 Raymond Zeitler writes: > Does anyone schedule and "org-clock" interruptions?=C2=A0 I really need t= o 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.=C2=A0 Then I'd press "I" eve= ry 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! =20 ------=_Part_911274_523361313.1502658808253 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yes I see your point. Maybe it'= s too ambitious to determine productivity. But knowing how much time = is spent on the interruption (taskerruption) would be a good start.<= /div>

- Ray

= From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
<= b>Sent: Saturday, August 12, = 2017 10:48 PM
Subject:= Re: [O] Tracking Interruptions -- Work Flow Question

<= br>

Raymond Ze= itler <zeitra@yahoo.com> 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 Interruptio= n" in my todo.org (or an inter.org file) and schedule it every day. T= hen I'd press "I" every time I get interrupted and perhaps tag it with a sp= ecial term.

> Or I suppose I could use a capt= ure template just for interruptions.

> What do you suggest?

Seems to me the danger of interruptions is not how m= uch time they take

up, but how much time it takes= you to recover from them, and get back to

work. Much harder to clock!

------=_Part_911274_523361313.1502658808253-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Raymond Zeitler Subject: Re: Tracking Interruptions -- Work Flow Question Date: Sun, 13 Aug 2017 21:29:59 +0000 (UTC) Message-ID: <854362451.903910.1502659799512@mail.yahoo.com> References: <1762394182.645329.1502589720701.ref@mail.yahoo.com> <1762394182.645329.1502589720701@mail.yahoo.com> <87h8xcgp5g.fsf@ericabrahamsen.net> <87378vzuo0.fsf@luisa.c0t0d0s0.de> <87378vol94.fsf@gmail.com> Reply-To: Raymond Zeitler Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_903909_1714683948.1502659799510" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36726) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dh0SU-0003dB-HQ for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 17:30:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dh0SR-0002b6-B4 for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 17:30:06 -0400 Received: from sonic321-23.consmr.mail.ne1.yahoo.com ([66.163.185.204]:41124) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dh0SR-0002aJ-11 for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 17:30:03 -0400 In-Reply-To: <87378vol94.fsf@gmail.com> 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: Tim Cross , Michael Welle Cc: "emacs-orgmode@gnu.org" ------=_Part_903909_1714683948.1502659799510 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yes, I agree that it's difficult to assess productivity based solely on the= time I'd spend clocked into Taskerruptions. I came across one other question in this list about interruptions where the= poster was interested in following the pomodoro technique.=C2=A0 (There wa= s no reply.)=C2=A0 But that technique seems geared toward addressing "inter= nal" interruptions, like when I decide that the windows need washing when I= need to do the taxes.=C2=A0 (This after about 45 seconds of reading that w= ebsite.)=C2=A0 My interruptions are almost always what you addressed in you= r last paragraph; they're from people more important than me.=C2=A0 I almos= t never can say, "I'll get back to you."=C2=A0 Although I have taken to rop= ing off my cubicle with a stern "Do Not Disturb" sign on occasion. Just clocking them would be a great start.=C2=A0=C2=A0Maybe I'll figure out= that I can say, "I'll get back to you" in some cases. - Ray From: Tim Cross To: Michael Welle =20 Cc: emacs-orgmode@gnu.org Sent: Sunday, August 13, 2017 5:45 AM Subject: Re: [O] Tracking Interruptions -- Work Flow Question =20 I'm not sure there is any *good* way to track interruptions. As pointed out by others, interruptions are not equal and the actual length of the interruption is not necessarily a good reflection of the actual impact to your productivity. I've found two things which have helped me. One has helped to reduce the interruptions and the other has provided some (minimal) help when I've been questions on why a task has taken longer to complete than estimated. The first has been to use a type of pomodoro technique. Essentially, I break my work up into blocks of time where I will not answer the phone, email or anyone coming to my desk. I do run a timer which ticks down and /allow/ interruptions in breaks between 'pomodoros'. The timer is really useful as when someone comes to interrupt me, I can say, come back in x minutes. It takes some training of your work colleagues, but they will eventually respect your request (and being able to give them a definite 'come back in x minutes' helps). The second thing I do is if an interruption cannot be avoided, I do check out of my current task and only check back in once the interruption has finished. While this doesn't tell you how much productivity was actually lost by the interruption, you can at least do some analysis of the clock times and show how often and for how long you were interrupted - or at least working on that task was interrupted. Tim Michael Welle writes: > 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.=20 > > Regards > hmw --=20 Tim Cross =20 ------=_Part_903909_1714683948.1502659799510 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yes, I agree that it's difficult to a= ssess productivity based solely on the time I'd spend clocked into Taskerru= ptions.

I came across one o= ther question in this list about interruptions where the poster was interes= ted in following the pomodoro technique. (There was no reply.) = But that technique seems geared toward addressing "internal" interruptions,= like when I decide that the windows need washing when I need to do the tax= es. (This after about 45 seconds of reading that website.) My i= nterruptions are almost always what you addressed in your last paragraph; t= hey're from people more important than me. I almost never can say, "I= 'll get back to you." Although I have taken to roping off my cubicle = with a stern "Do Not Disturb" sign on occasion.

Just clocking them would be a great start.= Maybe I'll figure out that I can say, "I'll get back to = you" in some cases.

- Ray

From: Tim Cross <t= heophilusx@gmail.com>
To: Michael Welle <mwe012008@gmx.net>
Cc: emacs-orgmode@gnu.org
Sent: Sunday, August 13, 2017 5:45 AM
<= span style=3D"font-weight: bold;">Subject: Re: [O] Tracking Inte= rruptions -- Work Flow Question

I'm not sure = there is any *good* way to track interruptions. As
pointe= d out by others, interruptions are not equal and the actual length
of the interruption is not necessarily a good reflection of the a= ctual
impact to your productivity.

I've found two things which have helped me. One has helped t= o reduce the
interruptions and the other has provided som= e (minimal) help when I've
been questions on why a task h= as taken longer to complete than
estimated.

The first has been to use a type of pomodoro techni= que. Essentially, I
break my work up into blocks of time = where I will not answer the phone,
email or anyone coming= to my desk. I do run a timer which ticks down and
/allow= / interruptions in breaks between 'pomodoros'. The timer is really
useful as when someone comes to interrupt me, I can say, come bac= k in x
minutes. It takes some training of your work colle= agues, but they will
eventually respect your request (and= being able to give them a definite
'come back in x minut= es' helps).

The second thing I do is i= f an interruption cannot be avoided, I do
check out of my= current task and only check back in once the
interruptio= n has finished. While this doesn't tell you how much
prod= uctivity was actually lost by the interruption, you can at least do
some analysis of the clock times and show how often and for how = long you
were interrupted - or at least working on that t= ask was interrupted.

Tim

Mich= ael Welle writes:

> Hello,
>
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Raymond Zeitler <zeitra@yahoo.com> writes:
>>
>>> Doe= s anyone schedule and "org-clock" interruptions? I really need to
>>> quantify how much of a drain they are to my producti= vity.
>>>
>>> I thoug= ht 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 an= d perhaps tag it with a
>>> special term.
>>>
>>> Or I suppose I coul= d 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, f= or
> instance, sharpening pencils. Depending on the 'b= raininess' of the
> interrupted task add another 15 or= 30 minutes to the interruption
> account.
>
> Regards
> hmw

--
Tim Cross

<= /div> ------=_Part_903909_1714683948.1502659799510-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Raymond Zeitler Subject: Re: Tracking Interruptions -- Work Flow Question Date: Sun, 13 Aug 2017 21:43:50 +0000 (UTC) Message-ID: <182432611.922718.1502660630480@mail.yahoo.com> References: <1762394182.645329.1502589720701.ref@mail.yahoo.com> <1762394182.645329.1502589720701@mail.yahoo.com> <87mv73g5bc.fsf@artlab.createcnix.lan> Reply-To: Raymond Zeitler Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_922717_1097808882.1502660630478" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39332) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dh0jk-0001gs-T5 for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 17:47:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dh0jh-0008BA-Pp for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 17:47:56 -0400 Received: from sonic331-48.consmr.mail.ne1.yahoo.com ([66.163.190.229]:37715) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dh0jh-0008AH-9G for emacs-orgmode@gnu.org; Sun, 13 Aug 2017 17:47:53 -0400 In-Reply-To: <87mv73g5bc.fsf@artlab.createcnix.lan> 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: Christophe Schockaert Cc: "emacs-orgmode@gnu.org" ------=_Part_922717_1097808882.1502660630478 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yes, I like your setup with org-capture.=C2=A0 I think I can overcome the p= roblem of invoking the capture when someone pops in to complain that email = is down, for example.=C2=A0 I would use either AutoHotKey (I'm on Windows) = or bind a function key in Emacs to a taskerruption function for F2F issues.= =C2=A0 One or two keypresses (ALT-TAB F12), under those circumstances, woul= d not be considered rude in my environment. I used Planner for several years.=C2=A0 It had (has) a time-warp function s= o that the user could create content retroactively.=C2=A0 If all else fails= , I could schedule the taskerruption retroactively using a similar function= in org. - Ray From: Christophe Schockaert To: Raymond Zeitler =20 Cc: "emacs-orgmode@gnu.org" Sent: Sunday, August 13, 2017 5:56 AM Subject: Re: [O] Tracking Interruptions -- Work Flow Question =20 Raymond Zeitler writes: > Does anyone schedule and "org-clock" interruptions? I really need to quan= tify 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 tim= e 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? I do. I have set up capture templates for phone calls, mail read/write, and general journal log. The former two, I clock-in automatically, the latter one, manually, in case I just want to log something in the course of my current activity. I use tags to identify phone calls and mails, so I could sum up their time, comparing to the whole. I don't do it though. Maybe that's why I didn't tag my "general log journal". But to achieve what you want, that's what I would do. When I handle a phone call or mail or general interruption, I usually keep the clock running until I managed all actions related to it (e.g. summarize the phone call, and scheduling any actions resulting from it), so rather than the interruption itself, I keep track of the whole time to handle it. It doesn't take into account the context switching however, as pointed out by Eric. As for the time to trig the capture... For mails, there are obviously no problems. I am eager to have my mu4e setup running to link directly to the content at the same time. For phone calls, the bell is ringing up to 3 times, so it's ok. It's when somebody comes in that it's a bit tricky to handle, because people expect your attention. I usually focus on the need to take notes to have the opportunity to start my template, where I just write write down a summary of what is said during the talking. HTH, Regards, Christophe =20 ------=_Part_922717_1097808882.1502660630478 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yes, I like your setup with org-captu= re. I think I can overcome the problem of invoking the capture when s= omeone pops in to complain that email is down, for example. I would u= se either AutoHotKey (I'm on Windows) or bind a function key in Emacs to a = taskerruption function for F2F issues. One or two keypresses (ALT-TAB= F12), under those circumstances, would not be considered rude in my enviro= nment.

I used Planner for s= everal years. It had (has) a time-warp function so that the user coul= d create content retroactively. If all else fails, I could schedule t= he taskerruption retroactively using a similar function in org.

- Ray

From: Christophe Schockaert <R3vLibre@= citadels.eu>
To: Ra= ymond Zeitler <zeitra@yahoo.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org><= br> Sent: Sunday, August 1= 3, 2017 5:56 AM
Subject: Re: [O] Tracking Interruptions -- Work Flow Question

=

Raymond Zeitler w= rites:

> Does anyone schedule and "= org-clock" interruptions? I really need to quantify how much of a drain the= y are to my productivity.
> I thought I'd include a ge= neric "** TODO Interruption" in my todo.org (or an inter.org file) and sche= dule it every day. Then I'd press "I" every time I get interrupted and perh= aps tag it with a special term.
> Or I suppose I could= use a capture template just for interruptions.
> What= do you suggest?

I do.

I have set up capture templates for phone calls, mail read/write,= and
general journal log. The former two, I clock-in auto= matically, the
latter one, manually, in case I just want = to log something in the course
of my current activity.
I use tags to identify phone calls and m= ails, so I could sum up their
time, comparing to the whol= e. I don't do it though. Maybe that's why I
didn't tag my= "general log journal". But to achieve what you want,
tha= t's what I would do.

When I handle a p= hone call or mail or general interruption, I usually
keep= the clock running until I managed all actions related to it
(e.g. summarize the phone call, and scheduling any actions resultingfrom it), so rather than the interruption itself, I keep tr= ack of the
whole time to handle it. It doesn't take into = account the context
switching however, as pointed out by = Eric.

As for the time to trig the capt= ure... For mails, there are obviously no
problems. I am e= ager to have my mu4e setup running to link directly to
th= e content at the same time. For phone calls, the bell is ringing up to
3 times, so it's ok. It's when somebody comes in that it's a = bit tricky
to handle, because people expect your attentio= n. I usually focus on the
need to take notes to have the = opportunity to start my template, where I
just write writ= e down a summary of what is said during the talking.

HTH,
Regards,

Christophe