INFO 330 Class Project Do it for real

Overview of the Class Project Scope – Approximately the same as the sample project – Standard starting place Marketing analysis, project charter, personas – Org anal  User anal  Info analysis  Info/UI design Schedule – Week 4- intro – Week 5- Begin analysis – Week 8- Begin design, deliverable milestone – Week 10 – User testing

Teams I will assign you – Teams of 4 Peer eval – Each member evaluates all others – +/- 10% grade offsets – Details on the course site

Eval In-class presentations (10%)* – Engagement with assignment – Team participation – Professionalism Mock Job Interveiw (10%)* – Will judge the way an employer would Shows competency in the deliverable Professionally presented Final deliverable package (40%)* – Will judge the way an employer would Shows competency in the deliverable Professionally presented * Final percentages

Escape hatch If you have a better idea – Uses the same starting place – Is more advanced than what I propose – Covers the same scope Pitch me – Deliverables – Team (2 min 3 max) – Schedule

Scope Drill-down Project vision Heuristic eval of competitor’s tools – CarMax and two other companies User interview – Two users one persona Info flow design – Landing, flow, success Info analysis – Info types – Access structures Wireframing/ Templating User testing – Paper prototypes

Org analysis – Project vision Process 1.Listen to my presentation of the project 2.Study the materials I provide 3.Choose one user type 4.Craft a one paragraph description of 1.What the user wants 2.What the org wants 3.How you will make both successful Format of the deliverable you turn in – Project name – Team name: members – Project vision

Heuristic eval Process 1.Find or construct a suitable rubric Minimum of 30 criteria Cite sources and say which ones are original 2.Apply to at least 3 sites/tools The current Carmax tool – search/default.html?intcmp=START2012SEARCHL01Home_Page search/default.html?intcmp=START2012SEARCHL01Home_Page 2 other Web sites, Mobile Apps, client apps that do car selection 3.Collect data 1.Apply the rubric 2.Compile the results

Heuristic eval Format of the deliverable you turn in – Executive summary 2-3 paras that highlight your c hoices, problems and main results – Methods Brief step-by description of what you did – Results Opportunities to go beyond the competition Competitor strengths we should incorporate Current weaknesses to fix Use screenshots to illustrate – Data (appendix) Copies of the evals for each site Any extra screenshots not used in the results

User Interviews - Process 1.Find/develop an interview script that Validates/enhances persona Helps you develop a high level user journey – Reasons for drop-off – Criteria for moving toward goal Cite sources/ flag original questions 2.Perform script Find two users in one persona At least one session each with at least two team members present – Interviewer – Note taker/sketcher 3.Capture data Interview recording: audio only Interview notes Sketch of the high level user journey for each 4.Analyze data 1.Changes/ refinements to persona 2.Single combined user journey

User Interviews – Turn in Executive summary – See prior instructions Methods – See prior instructions Results – Revised persona – Single high-level user journey Relate to the user journey I presented Combines the data from both users Data (in appendix) – Everything you captured

Function and flow - Process Collect data – Three sites/tools – What car selection features are present Marked up screen shots Definitions of the functions – What is the decision making flow? Flowcharts for each showing Progress through info (not screens) Drop-off reasons Preferred actions Produce a single flow diagram that – Shows how people will Land, flow, and succeed – Uses the best of what you found – Includes functions that will need to be implemented to move the user forward – Uses the user journey flows you produced from the user interviews Produce a list of functions you will need to drive this flow – Name of function – Very basic algorithm – Should show up later in your wireframes

Function and flow – Turn in Executive summary – See prior instructions Methods – See prior instructions Results: Single Flow – Progress through stages (not screens, they will come later) – Drop-off reasons – Preferred actions Data (in appendix) – Everything you captured

Info analysis/Design – Process 1.Collect data – Three sites/tools – How are cars presented? Marked up screen shots Definitions – How are cars organized? Marked up screen shots At least one technique that is not “short loop” 2.Perform an analysis: Best of breed + original thinking – Car qualities – Navigation techniques – Functions

Info analysis/Design - Process 3.Create a database schema Model a car Model at least one other type of info that is important to track Model whatever you need to in order to support the navigation you propose Model whatever you need to support the functions you propose Pseudo queries for functions

Info analysis/Design – Turn in Executive summary – See prior instructions Methods – See prior instructions Results: Database schema – Intro: why you made the choices you did – Tables – Fields – Pseudo Queries Data (in appendix) – Everything you captured

Wireframes/ Templating - Process Produce a set of wireframe diagrams 1.Review your work to date 2.Create a small set of constraints that will guide your design decisions 3.For each major step in your flow, create a wireframe Layout of the screen – Label page areas Cars and other info items on the screen – Labels for users – Callouts to database tables and fields for developers Navigation – Global and local navs – Call out preferred next actions Functions – Show them on the wireframe – Enhance your list to specify what they need from the database – Basic algorithms – Pseudo queries

Wireframes/ Templating – Turn in Executive summary – See prior instructions Methods – See prior instructions Global design constraints Wireframe flow: Thumbnail wireframes showing – Expected progression with preferred next actions – Expected drop-offs with mitigations – This should closely relate to but be a different cut than the user journey user journey = mental state  mental state Wireframe = screen  screen Wireframes – Picture with callouts – Application of design constraints (as needed) Why this layout and areas Why these navigation areas? Why these functions Data (in appendix) – Everything you captured

User testing - Process 1.Schedule time with your two users 2.Show them the flows and wireframes you produced 3.Record the sessions 1.Notes 2.Audio 4.Analyze the results 5.Make a revision of your wireframes

User Testing – Turn in Executive summary – See prior instructions Methods – See prior instructions Results – Major insights and findings – Quotes as needed – Conclusions Revised Wireframes – New diagram – Summary of changes Data (in appendix) – Everything you captured