From: Raymond Zeitler <zeitra@yahoo.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Tracking Interruptions -- Work Flow Question
Date: Sun, 13 Aug 2017 21:13:28 +0000 (UTC) [thread overview]
Message-ID: <206117808.911275.1502658808255@mail.yahoo.com> (raw)
In-Reply-To: <87h8xcgp5g.fsf@ericabrahamsen.net>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
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.
- Ray
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Sent: Saturday, August 12, 2017 10:48 PM
Subject: Re: [O] Tracking Interruptions -- Work Flow Question
Raymond Zeitler <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 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!
[-- Attachment #2: Type: text/html, Size: 3233 bytes --]
next prev parent reply other threads:[~2017-08-13 21:13 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 [this message]
2017-08-13 9:55 ` Christophe Schockaert
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=206117808.911275.1502658808255@mail.yahoo.com \
--to=zeitra@yahoo.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.net \
/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).