From: Eduardo Mercovich <eduardo@mercovich.net>
To: Karl Voit <news1142@Karl-Voit.at>
Cc: emacs-orgmode@gnu.org
Subject: Re: Just sharing another orgmode use: usability tests
Date: Wed, 02 Aug 2017 22:26:03 -0300 [thread overview]
Message-ID: <87pocdqw5w.fsf@biologica.mercovich.net> (raw)
In-Reply-To: <2017-08-02T17-01-37@devnull.Karl-Voit.at>
Hi Karl.
>> + automatic task clocking, including automated time stamping of
>> every observation.
> You seem to use headings for any events.
> If list items does the trick as well, you can take a look at
> timers
> for doing the clocking thing:
> http://orgmode.org/manual/Timers.html
Totally agree, that's exactly what I use now. :)
Lists are used inside each task, at 1 item per (short)
observation.
>> + observation tagging (there are repeating patterns of use or
>> interaction problems or sources that you could catch on the
>> fly, so any observation could be related to those common
>> issues).
> You already mentioned templates. I'd go with yasnippets for that
> as well.
Sorry I wasn't clear, I meant more the use of tags related to
common observed patterns mark and select after (with sparse tree)
those in which that pattern or issue is relevant. Great to group
things (tasks, observations, etc.) related to the same issue.
>> + automatic filling of User/task-results-and-time matrix (the
>> most fundamental metric of usability tests).
> Wow, this would be great.
Yes, but for that I have to learn Lisp. ;)
I'm starting with "An Introduction To Programming in Emacs Lisp"
by Robert J. Chassell. Just minutes a week sadly, but this is what
I can do now. :)
In the document structure we have:
* Users,
** Pre-task interview
** tasks (with TODO states as indicators of success|failure|so-so;
maybe we can use properties).
- each one with one or more timer entry
- so total task time is the last item timer value,
** Post-task interview
To make the User/task-results-and-time matrix we'll have to walk
the hierarchy and get for each User the sequence of tasks, and of
each, the success (or not), time and tag (issue) related and put
that in the results matrix.
Since I couldn't find other references about orgmode used for
usability, I am organizing an informal workshop to share this
experience next week with 10 people or so from the usability
community in Buenos Aires.
If someone is interested, we can arrange another in English after
this 1st one. ;)
Best regards...
--
eduardo mercovich
Donde se cruzan tus talentos
con las necesidades del mundo,
ahí está tu vocación.
(Anónimo)
next prev parent reply other threads:[~2017-08-03 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 20:08 Just sharing another orgmode use: usability tests Eduardo Mercovich
2017-08-02 15:03 ` Karl Voit
2017-08-03 1:26 ` Eduardo Mercovich [this message]
[not found] <8d18331fde644aa79d32d60d720a8d10@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-06-16 8:25 ` Eric S Fraga
2017-06-16 14:19 ` Eduardo Mercovich
[not found] ` <e24c85840a894ce9bbe7c0b56cfc1d53@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-06-17 13:37 ` Eric S Fraga
2017-06-18 22:21 ` Eduardo Mercovich
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=87pocdqw5w.fsf@biologica.mercovich.net \
--to=eduardo@mercovich.net \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@Karl-Voit.at \
/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).