Spam detection software, running on the system "avery.infomotions.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see eric_morgan_at_infomotions.com for details. Content preview: Hi Kyle, If you turned your paper prototypes into non-interactive digital images -- just, say, a Google Draw document or even Paint, with boxes where you want them, menus arranged accordingly, headers footers etc. -- you could put them up as slides at a gathering and get user feedback that way, both via direct request, taking notes in a kind of seminar session, as well as (if you were willing to tweak your designs in response to feedback) a card sort. Either of these options would keep you from having to have a fully-functioning development version live prior to getting some kind of feedback. [...] Content analysis details: (1.3 points, 1.1 required) pts rule name description ---- ---------------------- -------------------------------------------------- 2.7 DNS_FROM_AHBL_RHSBL RBL: Envelope sender listed in dnsbl.ahbl.org [listed in lists.clir.org.rhsbl.ahbl.org. IN] [A] 1.0 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source [74.125.82.54 listed in dnsbl.sorbs.net] 0.0 T_HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail domains are different -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail domains are different -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
attached mail follows:
Hi Kyle, If you turned your paper prototypes into non-interactive digital images -- just, say, a Google Draw document or even Paint, with boxes where you want them, menus arranged accordingly, headers footers etc. -- you could put them up as slides at a gathering and get user feedback that way, both via direct request, taking notes in a kind of seminar session, as well as (if you were willing to tweak your designs in response to feedback) a card sort. Either of these options would keep you from having to have a fully-functioning development version live prior to getting some kind of feedback. Hope this helps! Best wishes, Jennifer Wright, MLIS Electronic Access Unit Technical Services Harlan Hatcher Graduate Library University of Michigan jennywri_at_umich.edu On Wed, Aug 31, 2016 at 9:48 AM, Kyle Breneman <tomeconqueror_at_gmail.com> wrote: > Apologies for cross-listing... > > I need some advice on user testing methods. I’ve embarked on a project to > redo our library website’s information architecture. I’ve sketched out a > new IA for the site which I want to test with users. Initially I thought > that I would just build out the new IA on our development server, then do > usability testing with users on the dev site. Now I’m realizing that will > be a lot of work, and making any changes once its built will also take > time. Is there a middle ground? Are there good ways to do some user > testing with paper prototypes? I want to get feedback on whether my > categories and labels are intuitive and meaningful. > > Kyle Breneman > > Integrated Digital Services Librarian > > University of Baltimore >Received on Wed Aug 31 2016 - 09:52:14 EDT