Monthly Archives: October 2014

Th, 10/30: Proposals

Posted on by

1. Listen and evaluate another tech briefing: Go2Meeting (Alina & Tian). We’ll spend 10-15 minutes hearing from them and another 5-10 completing their evaluation form. Their deliverable is here.

2. Last-minute questions about the Instructions Project? This is due by midnight.

3. Slideshow: Proposals. Slides here.

4. Activity 1: RFPs. Browse the RFPs at grants.gov, find an example from your field, and skim the synopsis, full announcement and/or application materials to identify:

  • Investors — Who are they? Who do they represent?
  • Problem/need/goal — Why are they posting this RFP?
  • Objectives — What would a good proposal promise to do?
  • Solutions/Methods — How could might a proposal insure it keeps that promise? What must an applicant say about their qualifications, scheduling, resources, and capacity to manage?

5. Activity 2: Kickstarter. Browse the various projects on Kickstarter, find an example that interests you, and skim the page to identify:

  • Investors — Where & how does the maker address them?
  • Problem — What need or desire does this thing satisfy?
  • Solution — What is the thing and what does it promise to do?
  • Methods — What appeals does it make to insure it will keep those promises? What does the page say about the maker’s qualifications, scheduling, resources, and capacity to manage making this thing?

T, 10/28: The Feasibility Study

Posted on by

1. Listen and evaluate another tech briefing: Zoho (Tim & David). We’ll spend 10-15 minutes hearing from them and another 5-10 completing their evaluation form. Their deliverable is here.

2. Close up the Instructions Project. Your final deliverables for the Instructions Project are due Thursday before midnight. We’ll review the delivery requirements, the team evaluation form, and look at an example of a letter of transmission for the S.S. Save Wheezy instructions & usability report we viewed earlier in this unit.

3. Slideshow: What’s a feasibility study? Slides here.

4. Look at recent examples of feasibility studies IRL. Get into groups by major and pick a feasibility study to review from the list below. Ask yourselves the questions form the last slide above. Talk about this for 10-15 minutes and get ready to share.

Public admin/management:

–Bicycle Commuter Corridor Study from Syracuse Metropolitan Transportation Council

Engineering:

–Onondaga Lake Wastebeds Study from the NYDEC
–Kenilworth Park Landfill Site from the National Park Service
–Greenhouse Gas Management (NYC Dept of Environmental Protection)

Accounting or management:

–On Using CPA Firms from Auditor of Public Accounts, Virginia
–Enterprise Data to Revenue Project (California Franchise Tax Board)

Technology:

–Los Angeles County WiFi Feasibility Report from Los Angeles County

5. Look at examples from this class. These executive summaries were culled from more memorable final reports of previous semesters. Apply the same questions from the slides and come up with 2-3 ideas for your own project.

T, 10/21 & Th, 10/23: Usability testing

Posted on by

On Tuesday & Thursday you are testing your instructions in HBC 227. We also have two one tech briefing this week about a few Google apps:

  • Tuesday: Google Chrome apps and extensions (Ethan & Francisco)
  • Thursday: Advanced features of Google Docs (Evan & Lucas). Here is the Google Doc we can play around with:

http://goo.gl/lWksF8

 

Also on Tuesday, we’ll review my reflection on your mid-semester evals. As you might remember from my emails this weekend, I asked you to insert comments on this document before class. Specifically, we need to look at the proposed changes to the course, which are marked with a red star (✪). If we agree to the changes, I’ll start making them for Thursday.

Th, 10/15: Usability & mid-sem eval

Posted on by

Three tasks for today — two of which are carryovers from Tuesday…

1. Complete mid-semester evaluations.  I’ve done this with previous courses and found it be an effective way for all involved to reflect on our progress and make adjustments that we can all agree to. I will read all of your responses carefully, identify trends or patterns, and write a committal letter detailing changes we’ll make (which will need to be approved by you). To get started, visit this link or enter this URL into your browser:

http://goo.gl/7b8WBl

 

Answer the questions as fully as you can in the time allotted. (Or, if you find the co-writing process chaotic in Google Docs, you may answer the questions in a word processing program first and cut and paste them here.) You may also “like” your classmates’ responses by tallying this next to their answers or writing additional comments.

2. Review guidelines for making your own test. We’ll take a look at this handout, which is meant to help you think through the steps required for test design.

3. Analyze a usability report example and plan your tests. This is a very strong example of a usability report from  my Fall 2011 class and should give you an idea of what I’m looking for. Take a look at this, the handout above, and make a plan for the lab on Tuesday. As you do, consider:

  • Your objectives: What do you want to measure?
  • Your testers: Who are they? Who do they represent?
  • Your method: What kinds of tests do you want to run? How will they help measure your objectives? How many rounds of testing are you planning to do?
  • Your tools: What kinds of technology do you need to complete these tests?

T, 10/13: Usability

Posted on by

We’ve got four tasks for today:

1. Listen and evaluate first tech briefing:  Simple web design (Lincoln & Mark). We’ll spend 10-15 minutes hearing from Lincoln and Mark and another 5-10 completing their evaluation form. Again, not only do these forms count toward your participation grade, they count toward the presenter’s TB grade. I’ll walk you through the form one more time before Lincoln and Mark begin.

Here is their deliverable.

2. Listen to usability lecture. Slides are here. I’ll share definitions, examples, technologies, and methods for usability or user-experience (UX) testing.

3. Review guidelines for making your own test. We’ll take a look at this handout, which is designed to help you think through the steps required for test design.

4. Analyze a usability report example. This is a very strong example of a usability report from  my Fall 2011 class and should give you an idea of what I’m looking for. We’ll take a look at some of its strengths and raise questions moving forward.

For Thursday, read about usability testing in Anderson and take a look at this usability study about the iPad. Depending on what we got through today, I’ll give you some time with your team to discuss how you’d like to design your tests for next week.

T, 10/7: Webtexts & project planning

Posted on by

I’d like to start today by quickly reviewing what’s coming up, especially conferences on Thursday and Tech Briefings next week.

For the latter, I want to review four things:

  • You should have your deliverable ready at the start of your lesson
  • You have up to 15 min for your briefing; I time it. You will receive a notification from me at the 5 and 10 min. marks.
  • At the end of your briefing, the class has a few minutes to evaluate you in Google Forms, but may also choose to write notes throughout the briefing and complete the online form later.
  • Evals go to me for advisement; I judge some of your participation grade with this in mind.

After that, we have three tasks:

1. Looking closer at instructions as webtexts: Part I. In the last part of class on Thursday, each group looked at a different DIY instructions site.

  1. Team 1: All Recipes
  2. The Awesome Team (Name): wikiHow
  3. Minions: Instructables
  4. Francisco & The Girls: DIY Network

Take a few minutes to regroup and chat about your answers to these questions:

  • How are the instructions organized? What does the parts list look like? How are the pages designed? How do users navigate from one page/frame/screen/layer to another?
  • Describe and evaluate the visual elements — formatting, images, videos, etc. — in terms of font, arrangement, size, perspective, clarity, etc.
  • Describe and evaluate the text – the actual words — in terms of language used for action (verbs, verbs, verbs), sequence (order of steps), manner (how something is done), and purpose (why something is done).

2. Looking closer at instructions as webtexts: Part II.

On Thursday I also asked you to try to make or do something from one of these sites  (or somewhere similar), paying attention to what worked well with the instructions and what did not. Tell us about how this went:

  • How could these instructions be improved?
  • What would happen if they were rewritten in a different medium?
  • If there’s a comment section, how did folks add to the experience?

3. Working with Teams. The reading for today (“Project Planning and Tracking”) outlined some strategies for mapping a project with a team and checking in with it. Use this Google Doc as you meet with your group and apply the readings (be sure to save your own copy first!). Ultimately by the end of the class, I want the project manager from each group to send me an email briefing me on:

  • Your chosen host for your webtext and your reasons
  • Your project plan, addressing scope, assumptions, requirements for success, tasks + schedule, and the kinds of ways you’ll track your progress throughout the next few weeks

Th, 10/2: Intro to the Instructions Project

Posted on by

We got our eye on four tasks today:

1. Letters are due tonight. Any last minute questions about these? A few reminders:

  • Please send me your letters and ad in one email. This is so that (a) I don’t lose your stuff, and (b) I don’t get twice as many emails as necessary.
  • Send me your 2 letters as doc or docx files — I don’t want pdfs and I don’t want Google Docs. This is so I can comment on these quickly and consistently.
  • Also attach your job ad as a legible doc, pdf, or png file. I won’t comment on these but I do want to know the context for your letter.
  • Name the files with your last name first and the assignment (i.e. Barrow_jobad.pdf).

Also, are you signed up for a conference?

2. The Instructions Project. We’ll quickly review the requirements for this assignment and look at some examples from previous students. These examples are not meant to be models to emulate, but should give you a rough idea of what’s possible (or at least what might be considered in the ballpark) for this unit.

3.Time to build. I’ll give you about 40-45 minutes of class time to meet with your group and come up with some ideas for your prototype. You certainly don’t have to decide on a design today, but this is a chance for you to entertain and evaluate some ideas. While branding isn’t really part of this project, you should consider the idea of your design enough that it makes sense conceptually to your audience (or imaginary customers).

4. Looking closer at instructions as webtexts. In the last part of class today, I’d like each group to look at a different DIY instructions site.

  1. Team 1: All Recipes
  2. The Awesome Team (Name): wikiHow
  3. Minions: Instructables
  4. Francisco & The Girls: DIY Network

You can handle this task as you see fit. If almost everyone has a laptop, though, you may look at different pages and compare designs. Or you might all choose one to discuss. No matter what you decide,  be prepared to discuss the following questions after 10-15 minutes:

  • How are the instructions organized? What does the parts list look like? How are the pages designed? How do users navigate from one page/frame/screen/layer to another?
  • Describe and evaluate the visual elements — formatting, images, videos, etc. — in terms of font, arrangement, size, perspective, clarity, etc.
  • Describe and evaluate the text — the actual words — in terms of language used for action (verbs, verbs, verbs), sequence (order of steps), manner (how something is done), and purpose (why something is done).

For Tuesday, I’d like you to try to make or do something from one of these sites  (or somewhere similar). It shouldn’t be too complicated and it certainly shouldn’t cost you anything. You could make a sauce, fix a door that sticks, or mix a cocktail (21 and up, of course). As you do, notice what works well with the instructions and what doesn’t. How could these instructions be improved? What would happen if they were rewritten in a different medium? If there’s a comment section, how do folks add to the experience? Come to class ready to share your experience!