picking project teams & problem finding
DESCRIPTION
Picking Project Teams & Problem Finding. Jan 15, 2013. * Problem Finding slides from Prof. Tad Hirsch, UW Design. Hall of Fame or Shame?. Hall of Fame!. Good f lexible sort i cons change if save a house u nderstands “neighborhoods” Bad n o map legend? cluttered map s imilar icons. - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/1.jpg)
Prof. James A. LandayUniversity of Washington
CSE 440
USER INTERFACE DESIGN + PROTOTYPING + EVALUATION
Picking Project Teams &Problem Finding
* Problem Finding slides from Prof. Tad Hirsch, UW Design
Jan 15, 2013
![Page 2: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/2.jpg)
Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 2
Hall of Fame or Shame?
![Page 3: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/3.jpg)
• Good– flexible sort– icons change if save
a house– understands
“neighborhoods”• Bad
– no map legend?– cluttered map– similar icons
Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 3
Hall of Fame!
![Page 4: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/4.jpg)
Hall of Fame or Shame?
By Philippe Stark
Alessi Juicy Salif Citrus Juicer
Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 4
![Page 5: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/5.jpg)
Hall of Shame!Aesthetically pleasing but...
Does not perform it’s only function well: To make Juice.
Amazon review:You’ll get almost as much juice on the wall and counter as you do in the glass since the juice will spray in every direction.
An example of where beauty can overpower purpose
Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 5
![Page 6: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/6.jpg)
Prof. James A. LandayUniversity of Washington
CSE 440
USER INTERFACE DESIGN + PROTOTYPING + EVALUATION
Picking Project Teams &Problem Finding
* Problem Finding slides from Prof. Tad Hirsch, UW Design
Jan 15, 2013
![Page 7: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/7.jpg)
Outline
• Review
• Project teams
• Brainstorming & Problem Finding
Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 7
![Page 8: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/8.jpg)
Readings
• Fitts’ Law ?– time it takes a person to move a mouse to a
target is proportional to distance to target divided by target size
• e.g., buttons that are small or far away are harder to click on than buttons that are large or nearby
• What was NLS?– oNLine System
• Features of NLS?– mouse, groupware, client-server, windows,
version control, hypertext, 2d editing, context-sensitive help, …
Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 8
![Page 9: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/9.jpg)
Project Team Ideas
• Let’s hear 1 minute from each proposer
• At the end rank the top 4 projects you’d like to work on
• Don’t pick groups with your friends
• Groups will be online – problem finding assignment due this Thur (online
today)
Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 9
![Page 10: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/10.jpg)
Project Team Ideas
Winter 2013 10
1 Anti-distraction tool for students(Angela Liu)
2 To-do list/project planning(Fanny Luor)
3 Recipe sharing(Shahaf Nuriel)
4 Help people recycle (Chris Rovillos)
5 Time management/health app(Catriona Scott )
6 Exploration + discovery + creativity app(Janette Siu)
7 Collaborative grocery list (David Swanson)
8 Promote balance in users’ lives (Dian Hartono)
9 Grocery shopping based on meals(Peter Huss)
10 Help people find shared free time(Grace Jang)
11 Crowdsourced image search (Adam Kalman)
12 Music recommendations via crowdsourcing(Sheena Kapur)
13 Promote family interaction (Yousef Khwaja)
![Page 11: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/11.jpg)
Teams vs. Groups
• Groups– strong leader– individual
accountability– organizational purpose– individual work
products– efficient meetings– measures performance
by influence on others– delegates workWinter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 11
• Teams– shared leadership– individual & mutual
accountability– specific team purpose– collective work
products– open-ended meetings– measures performance
from work products– does real work
together
• Teams & good performance are inseparable– a team is more than the sum of its parts
![Page 12: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/12.jpg)
Keys to Team Success
• Common commitment– requires a purpose in which team members believe
• “prove that all children can learn”, “revolutionizing how we use energy in the home”, …
• Specific performance goals– comes directly from the common purpose
• “increasing the scores of graduates form 40% to 95%”– helps maintain focus – start w/ something achievable
• A right mix of skills– technical/functional expertise
(programming/design/writing)– problem-solving & decision-making skills– interpersonal skills
• Agreement– who will do particular jobs, when to meet & work,
schedulesWinter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 12
![Page 13: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/13.jpg)
Team Action Items
• Keep meeting & get used to each other• Figure out strengths of team members• Assign each person a role
– responsible for seeing work is organized & done
– not responsible for doing it themselves• Names/roles listed on next assign.
turned in
• Roles– design (visual/interaction)– user testing– development
– team manager (coordinate - big picture)
– documentation (writing)Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 13
![Page 14: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/14.jpg)
Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 14
Design Process: Exploration
Expand Design Space
• Brainstorming• Sketching• Storyboarding• Prototyping
Production
Design Refinement
Design Exploration
Discovery
![Page 15: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/15.jpg)
Wicked Problems
Ill-defined Complex, interrelatedMultiple stakeholders, differing perspectivesExample: Air pollution
No stopping ruleProblems are managed, not solvedExamples: Aging
Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 15
![Page 16: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/16.jpg)
Implications for Design
Solutions depend on how the problem is Framed… and vice-versa
Solutions are not optimal There’s no right or wrong… but there is better and worse
Every problem is uniqueCreative approaches are required
Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 16
![Page 17: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/17.jpg)
Approach
1. Explore the problem
2. Find a leverage point
3. Design an intervention
4. See what happens
5. RepeatWinter 2013 17
![Page 18: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/18.jpg)
Methods
Concept mapping
create a modelfind out what you already know
Ideation
explore a solution space
Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 18
![Page 19: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/19.jpg)
Concept mappingA technique for visualizing relationships between ideas
![Page 20: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/20.jpg)
Concept mapping
Process1. List 10-20 words associated with the topic2. Group them into named categories3. Start diagramming4. Add categories + examples5. Label the relationships6. Keep going until you lose momentum (and/or run
out of time)7. Highlight areas for further investigation
Outcomes8. A model (not definitive!)9. A few design directions
Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 20
![Page 21: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/21.jpg)
Step 1: List associated words
![Page 22: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/22.jpg)
Step 2: Group into Categories
![Page 23: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/23.jpg)
Step 3: Start Diagramming
![Page 24: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/24.jpg)
Step 4: Add Categories + Examples
![Page 25: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/25.jpg)
Step 2: Keep Going
![Page 26: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/26.jpg)
Step 2: And going…
![Page 27: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/27.jpg)
Step 2: Highlight Areas for further Investigation
![Page 28: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/28.jpg)
Step 8: Edit and Prioritize
![Page 29: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/29.jpg)
Next step: Research + Analysis
How big a problem is it? (market)
Whose problem is it? (stakeholders)
What’s already out there? (competition)
How are things done currently? (status quo)
How can they be improved? (innovation)Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 29
![Page 30: Picking Project Teams & Problem Finding](https://reader036.vdocuments.us/reader036/viewer/2022081422/56816769550346895ddc50bd/html5/thumbnails/30.jpg)
Next Time
• Gestalt Principles
• Remember to fill out and submit your project choices!!!!!!!!
Winter 2013 CSE 440: User Interface Design, Prototyping, & Evaluation 30