Friday Conferences, 12/9

For conferences Friday we’ll meet one-on-one in HEAV 107 to discuss your Comprehensive Reflection draft.

Times:

10:20a-Emily

10:30–Liz

10:40–Rina

10:50–Brad

11:00–Megan

11:10–Kelsey

11:20-Natasha

Advertisements

Feedback 301

Prototype Testing

Professional web site designers often use a technique called usability testing to evaluate their work. Multiple books have been authored on the subject, and there are many approaches, but all involve structured observation—watching people actually try to use the web sites in question, seeing what happens, and revising accordingly. Here’s a very brief adaptation of this for our purposes:

  1. Develop a short list of three or four tasks you would like the users of your site (your audience) to be able to perform. What information should they be able to find and read, for example?
  2. Work with at least two partners,
  3. Perform a series of trials approaching each task:
    • One person should attempt to perform the task, speaking out loud as they do so — this is called think aloud protocol. “Okay, I’m supposed to find the examples which discuss group meetings. I’m going to use search. So, I’m looking for the search box…”
    • The site designer should help the person performing the task if necessary, gently prompting when necessary, and periodically reminding the test-user to keep thinking out loud—but otherwise trying to stay out of the way.
    • Person #3 should take notes. What can the test site user do successfully? Where do trouble spots occur? What things does the test-user say which are interesting?
    • If the test-user gets completely stuck on a task, ask me or someone from another group to perform the task as well. If two people have an issue, that points to the need for some rethinking.
  4. Rotate among yourselves so that everyone gets some feedback about their sites in the time allotted. Make sure to end testing with enough time to review the notes from your tests and create a list of revisions to follow.

Concept Pile

Here are some terms, in no particular order, to jog your memory and provide fodder for your reflection essay draft:

“This Is Water,” rhetoric, rhetorical situation, the classical rhetorical triad, logos, ethos, pathos, kairos, threshold concept, heuristic, exigency, rhetor(s), multiple audience(s), constraints, affordances, writing process, brainstorming, inventing, collaborating, conferencing, workshop, feedback, revising vs. editing, “SFDs,” “Navigating Genre,” old and new definitions of genre, genre awareness, genre features, conventions, formatting, medium, primary research, interviews, surveys, loaded questions, sample sets, observations, inductive vs. deductive inquiry, secondary research, library research, annotated bibliographies, plagiarism, evaluating sources, citations, signal phrases, credibility, authority, writing style, plain or practical style, academic style, description, rhetorical figures, persuasion, argumentation, argumentative structure, premise, conclusion, inference, deduction, induction, fallacies, enthymemes, implicit or assumed values and premises, tone, stance, diction, user-focused design, usability, iterative design, remediation, remixing, redesign, plagiarism, copyright, fair use, visual rhetoric, infographics, contrast, repetition, alignment, proximity, headings, access, typography, space, resumes, social media, digital environments, websites, frontloading, orientation, scanning, navigation, hyperlinks….what else?

Thursday Conferences, 12/1

For conferences Thursday we’ll review your Purdue Web interventions, recap the best practices from Lynch & Horton, and discuss how to apply these practices to your own website projects.

Groups & times:

10:30a–Rina, Elizabeth, Fitz, Amanda, Monica

1o:55a–Matt, Daniel, Brad, Katelyn, Natasha