emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christophe Schockaert <R3vLibre@citadels.eu>
To: Raymond Zeitler <zeitra@yahoo.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Tracking Interruptions -- Work Flow Question
Date: Sun, 13 Aug 2017 11:55:35 +0200	[thread overview]
Message-ID: <87mv73g5bc.fsf@artlab.createcnix.lan> (raw)
In-Reply-To: <1762394182.645329.1502589720701@mail.yahoo.com>


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] <---------------<<<<

  parent reply	other threads:[~2017-08-13  9:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1762394182.645329.1502589720701.ref@mail.yahoo.com>
2017-08-13  2:02 ` Tracking Interruptions -- Work Flow Question Raymond Zeitler
2017-08-13  2:47   ` Eric Abrahamsen
2017-08-13  9:25     ` Michael Welle
2017-08-13  9:44       ` Tim Cross
2017-08-13 21:29         ` Raymond Zeitler
2017-08-13 22:28           ` Tim Cross
2017-08-13 23:17             ` Bob Newell
2017-08-13 21:13     ` Raymond Zeitler
2017-08-13  9:55   ` Christophe Schockaert [this message]
2017-08-13 21:43     ` Raymond Zeitler
2017-08-17 10:07   ` Michal Politowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mv73g5bc.fsf@artlab.createcnix.lan \
    --to=r3vlibre@citadels.eu \
    --cc=emacs-orgmode@gnu.org \
    --cc=zeitra@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).