Re: Tracking Interruptions -- Work Flow Question

[Raymond Zeitler <zeitra@yahoo.com>]

[-- Attachment #1: Type: text/plain, Size: 2793 bytes --]

Yes, I like your setup with org-capture.  I think I can overcome the problem of invoking the capture when someone pops in to complain that email is down, for example.  I would use 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 environment.
I used Planner for several years.  It had (has) a time-warp function so that the user could create content retroactively.  If all else fails, I could schedule the taskerruption retroactively using a similar function in org.
- Ray

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

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   

[-- Attachment #2: Type: text/html, Size: 5185 bytes --]