HCI Masters Project CourseHCI Masters Project Course

PSLC ProjectPSLC ProjectPhase 2 ReportPhase 2 Report

What the project is aboutWhat the project is about

Work Updates

Data CollectionData Collection

• We collected more data– CTAT Winter Workshop– More Contextual Inquiries

• 4 focus areas– high-level analysis tools (curves)– low-level drilling bits (logfiles

visualizations, Knight graphs)– Exporting function– Multi-user issues

• finding datasets of interest• access and permissions• social networking

ScenariosScenarios

• PSLC Primary Investigators (2)• PSLC Research Programmer• Student of PSLC PI• PSLC Member• Non-member Researcher/Grad student

Initial PrototypingInitial Prototyping

• Focused on one of the scenarios (Primary Investigator)

• Did sketches of ideas

• Consolidated ideas and made initial wire-frames

Lessons LearntLessons Learnt

• Need to have correct focus

• CIs may not tell you what the client wants.

• Informed data means more later on. Need context to understand early stuff

• Need to talk to all stakeholders.

• Conclusion: There are standard (curves) reports and we don't know how they work.

What’s Next

What’s Next: RefocusWhat’s Next: Refocus

• Invited client to affinity diagramming

• Organized design ideas

• Built shared understanding

• Got valuable feedback on idea groups, BUT

– Missing details on LearnLab analysis tools

– Needed to focus more on designing analysis tools

What’s NextWhat’s Next

• Identify highest priorities• Interview client stakeholders• Serialize research and prototyping• Split up the group into subteams

New Development PlanNew Development Plan

Development PlanDevelopment Plan

Four foci

1. High-level analysis tools

2. Low-level tools analysis3. Exporting function4. Multi-user issues

Why change course?

Need more data for about 8 analysis tools

Integrate and adapt 2 borrowed designs

Should be easy to design quickly

Development PlanDevelopment Plan

Serialize research and prototypingWhat is this?

1. Pick highest priority analysis tool or feature.2. Do an entire design/test/build cycle on it.3. Move on to next tool.

Development PlanDevelopment Plan

Interviews with client stakeholders

• CI data didn’t address focus– Didn’t see needs for client solution– Client solution not obviously applicable

• Lacked understanding of client solution– Analysis tools needed for collaboration– Need to understand analysis techniques. – Talking client stakeholders is fast

Development PlanDevelopment Plan

Serialize research and prototyping

• Prototype hard stuff early.• Concrete stuff required for June seminar• Client will be coding features• Work more closely with client• Build better partnership

Development PlanDevelopment Plan

Splitting up into sub-teams

• Spread resources• How it will work:

1. Pick a set of features or tools2. Assign one team to do R&D3. User testing by other team4. Rework and hand off final design to client5. Pick next feature set to work on

• Still working this out

Development PlanDevelopment Plan

Next actions

• Think-Aloud on existing prototype of an analysis tool• CI to gather data for an upcoming tool• More research on LearnLab analysis tools

Potholes We Ran Into(and How We Got Around them)

ProblemsProblems

• Methods approach exhausted– Solution: breakaway from data if it makes sense

• Getting requirements when clients are only current users of a feature– Solution: Use client stakeholders for CI’s

• Additional CI's adding marginal value– Solution: Prototype and test

FeedbackFeedback

• New development plan

• Soliciting requirements without hypothetical questions?

• Anything else you have comments on