InfoCamp 2010: Exploring UX, Design, and Development in Libraries and Beyond

1. Saturday InfoCamp 2010
2. Sunday InfoCamp 2010
3. Tasks

1. Saturday InfoCamp 2010

1.1. Keynote: @walkingpaper: UX and Libraries

1.2. Session 1: @nickf: Mobile UX/IA

1.2.1. What is UX

What is the traffic document required for creating new products.

1.2.2. How do you do discovery

Know the business

1.2.3. What are the technical hurdles for mobile

1.2.4. How important is strategic design

Use sketching to show the interaction to determine how things should work.

How to demo functionality.

1.2.5. Don't use red in sketches

Use metal template sytems.

Design Commission

1.2.6. Show pictures of cats and dogs

1.2.7. Use the tools to make product development easy

1.2.8. Do not do IA without the Build process

Need to clarify gaps by going through the development together.

1.2.9. Create a feature as a team

1.2.10. Do not think of a hand-off as a completed project

1.2.11. Ensure that testing is built in

1.2.12. Set up a test harness

1.2.13. Put together analytics

1.2.14. Put together A/B by default

1.2.15. How do you select native vs. web

http://twitter.com/#!/lukew

1.3. Lunch: Value of User Testing

1.3.1. Use lean startup

1.3.2. Minimum viable product

1.3.3. Create something that demos

1.3.4. TODO Prototype first with mock data

1.3.5. Minimize testing as a task for QA

1.3.6. Don't use traditional 30 page functional specification documents

1.3.7. Use people to talk to get work done

1.3.8. List of things people need to do doesn't have priority

1.3.9. Define the goals for people

1.3.10. Don't use documentation

1.3.11. Layer in new functionality

1.3.12. Work with prototypes

1.3.13. If design is providing new UI (non-reuse UI) there is a failure

1.3.14. Product should be demoable and killable early

1.3.15. Process

1.3.15.1. Determine high level data consumption

1.3.15.2. Note the current business goal

1.3.15.3. Note the user goal

1.3.15.4. Determine 1 sentence summary

1.3.15.5. Do not define an implementation or UI

1.4. Session 2: Donald Brinkman: Big History, Deep Zoom, and Long Tail

1.4.1. Books: 2266, You are Not a Gadget, Vilem Flusser

http://en.wikipedia.org/wiki/2666_(novel)

You are Not a Gadget, Lanier

Vilem Flusser

Create

1.4.5. ChronoZoom: Interactive timescales of Cosmos, Earth, Life, Huma

http://www.youtube.com/watch?v=CDWKAAxL10Q

1.4.6. Zoom as the future of search

What could be done to position search results in some output?

1.4.7. Yearbooks search for showing the number of counts

Create a POC that shows visualization of yearbook pages that is interactive based on OCR.

Should be done without a specification.

1.4.8. Example: Roman history

1.4.9. David Christian

http://en.wikipedia.org/wiki/David_Christian_(historian)

Use part of a lecture, site, and promotion.

1.4.10. Using Big History in High School

The classic view of education.

http://matt.might.net/articles/phd-school-in-pictures/

1.4.11. Live Labs: Pivot

http://www.getpivot.com/

1.5. Session 2: Alternative: DAM

1.5.1. http://www.slideshare.net/TracyGuza/infocamp-seattle-dam

1.6. Session 3: @changeorder: Design a product

1.6.1. Create a yoga appliction

1.6.2. 10 minutes: Research and discussion

1.6.3. 10 minutes: Design prototype

1.6.4. 10 minutes: Use product and iterate

1.7. Session 4: UX Research for Mobile

2. Sunday InfoCamp 2010

3. Tasks

3.1. TODO Strategic UI Mission

3.2. TODO Create visualization of projects and technologies

What are the overlap between data on site, projects…

Core focus is data discovery and mining

Wireframes, comps, and functional specifications are not requirements.

Work closely with Product to determine

These are mostly Agile principles for product development.