1. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 UW Majors Guide Design Process and Results Pei-Wen Chang Aaron Egaas Irvin MacQuarrie Daniel Podhola Ryan Prins Kathryn Tong Team Calder

2. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Calder is The Man! Performance in Art (Cirque Calder) Kinetic Sculpture (Mobile) Large Public Sculptures Had the “the most prolific and innovative artistic career of the twentieth century.” according to his website… Source: http://www.calder.org Overview: What we can learn about design: Inspiration can come from anywhere, be observant of your surroundings! A change in surroundings can positively influence your design Just create! Calder spent his entire life creating and designing. Practice makes perfect!

3. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Team Member Contributions Photo other image that “is” your team Photo Credit: Aaron Team MemberContribution Aaron & Danpresentation editor, prototype team, content types, visual design, photography Irvin & Pei-weninformation architecture, interactions, usability, organizational overview Ryan & Kathrynproject management, requirements, activities, report editors Group effortsthe triple, persona development, report draft, presentational slides

4. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Our Process Preparation Information Design Interaction Design Prototype Design

5. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Preparation for Design Questions we asked: What problem shall we pursue? –Strategic Design Who would benefit from a solution? –Persona Design How would they solve it? –Requirement Analysis

6. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Our Triple By delivering recommendations for a major that matched student interests to students we will be able to help them find their major faster because the service will contain pertinent information

7. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Our Persona Maria Sangria UW Student Yakima, WA “I just want an easy way to find a major on my own time, without having to wait in line at the Gateway center.”

8. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Major Requirements BossStudent Information Requirement About programs on campus Advisor contact information Listing of courses Related majors A timeline of steps for applying to a major Interest Survey Reverse course listing to related majors Related majors based on a class taken Presentation Requirement Professional Not intimidating Professional colors (ie no pink) List of suggested majors in order of suggestion Okay to have different look from what’s currently in use Not overly professional Ability to browse major List of suggested majors in order of suggestion Open extra information in a separate window Task Requirement Obtain feedback from users Open to all students Ability to schedule appointment w/ advisors Work in multiple browsers Keep technology in line w/ what is currently in place Remind me later option [Web advising – (boss doesn’t like)] Seamless technology

9. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Designing the information Information Architecture –Creation of our taxonomy Content Modeling –Defining our content

10. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Information architecture Brainstormed important words and phrases Created topic map centered around "major finder" Had two users complete a card sort Derived a taxonomy from the card sorts and the project requirements –Five top level hierarchies

11. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Content model Forming relationships between the words we developed during Brainstorm Prior work: UW’s Course Catalog Course Degree Program School

12. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Content Domain The information about majors on campus and what it takes to gain admission into these programs. This content also includes past classes and academic planning.

13. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Designing the interactions Tasks –Pulling tasks from prior labs to generate the top three Interactions –Putting the tasks together with functions

14. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Tasks Task 1: Look for pertinent information –Wanting to look for only the information that I need and nothing more Task 2: Input past courses and gain suggestions of one or more majors –Input your past courses and see what majors you could get into with them Task 3: Figure out what the degree requirements are for a specific major –Research the specific entry requirements for a particular major

15. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Interactions Created a site path diagram for the interactions Chose interaction of "Input past courses to get suggestion for major" Took in initial user state of confusion Detailed steps of the interaction Created a flow chart

16. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Designing the interface Putting the Pieces together

17. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Our prototype

18. The Information School at the University of Washington Demo

19. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair Usability Came up with a test plan Conducted usability testing for three interactions: –past courses, search, and browse Things that stood out: "guy with glasses" Encountered problems –user for first interaction had only taken three courses –user for third interaction didn't follow the expected path Recommendations –more extensive filtering system –look at changing location and titles for features further testing required

20. The Information School at the University of Washington INFO 440: Information System Design * Fall 2004 * Bob Boiko * MSIM Associate Chair You Should Know… What went right What went wrong What was insanely great Where we compromised How we fit a big project into a small time Next steps…