Basic Principles of Interface design
13 likes2,433 views
This document outlines the basic principles of user-centered design (UCD). It discusses how UCD prioritizes users by putting them at the center of design decisions through iterative testing and research. The goal is to optimize the user experience. Key aspects of UCD include discovering user needs through research, defining concepts based on personas, designing prototypes, and evaluating designs through usability testing to identify problems and continually improve the design.
Ad
More Related Content
What's hot (20)
Viewers also liked (20)
Ad
Similar to Basic Principles of Interface design (20)
Ad
Recently uploaded (20)
![Halstead’s_Software_Science_&_Putnam’s_Model[1].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/halsteadssoftwarescienceputnamsmodel1-250502175814-4c85707e-thumbnail.jpg?width=560&fit=bounds)
Basic Principles of Interface design
- 1. Principles of interface design BASIC PRINCIPLES OF INTERFACE DESIGN http://afflatus.me/wp-content/uploads/2015/03/Digital_Menu-by-Cosmin-Capitanu.jpg
- 3. User Centered Design is an iterative methodology that puts the user at the center of all design decisions The ultimate goal of UCD is to optimize a user's experience of a system, product, or process. The philosophy is to “fail fast” to uncover problem areas earlier using UCD methods instead of discovering the problems late in development stages of the project. What is UCD?
- 4. What is UCD?
- 5. Engeneering-driven design History: designed what was feasible and appropriate for the system not what users want and what was pleasure for them.
- 7. UCD BENEFITS
- 8. ITERATIVE DESIGN It is virtually impossible to design a user interface that has no usability problems from the start Iteration = to step through one design version after another. Conduct a usability evaluation (testing) for each version and revise the next one based on findings.
- 10. ITERATIVE DESIGN Repeat as necessary Design Prototype Test & Evaluate
- 11. Design without analysis won’t solve the right problem. DISCOVER / RESEARCH You need to know WHY they want to fire a gun.
- 12. Get know the users User perspectives: 1. Needs and wants 2. Goals, motivations, triggers 3. Obstacles and limitations 4. Tasks, activities and behaviors Understanding the perspective a user brings to a system enables us to design that system to meet their needs. DISCOVER / RESEARCH 5. Geography and language 6. Environment and gear 7. Work life and experience
- 13. How to do it? (Qualitative methods) • User interviews • Focus Groups
- 15. Learn from NUMBERS How to do it? (Quantitative) Questionars / surveys • Analytics • Clickheat
- 16. Questionars
- 18. CLICKHEAT
- 19. DEFINE / CONCEPT
- 20. clean up the messcreate personas DEFINE / CONCEPT
- 21. Fictional characters based on real user research WHY CREATE THEM? • We’re not always designing for ourselves • Personas help us to prioritize the design consideration • Build understanding and empathy - common shared understanding of the user group DEFINE / PERSONAS
- 25. Name and Intent Goals • From the user’s perspective (Wants and Needs) Behaviors and attitudes • How does this person make purchases, approach the Internet, etc. • What does this person think about your type of services, product etc. Scenarios • Detailed situations where your site could help PERSONA Ingredients
- 26. DESIGN!
- 27. DESIGN! Sketch a lot of different ideas, FAST! Then throw MOST of them away. Look at the big picture first - people see the forest before the trees.
- 28. WIREFRAME It states plainly and clearly what should go where. It’s just like an architectural blueprint of a house.
- 29. WIREFRAME • Communicate initial ideas • Stay focused on the right issues • Try design alternatives • Identify major usability issues early • Allow testing in design process Uses for wireframes
- 30. PROTOTYPE Any time during design cycle Early stages • Fewer resources spent • People are open to change Late stages • Require substantial work & resources • People are more resistant to change When to do prototyping
- 31. PROTOTYPE Evolution LOW-FI MED-FI HI-FI
- 35. Prototyping using a software
- 38. Design Studio A way to generate many ideas and solutions to a problem quickly through sketching, iteration, and critique.
- 39. Design Studio Collaborative and iterative workshop Place for active discussion over the design
- 40. Design Studio Why it works? • Combination of solitary and group work • Strict critique rules • Ideas come from everyone and anywhere • Brings the whole team together • Speeds design • Creates a shared understanding & ownership
- 41. Design Studio Flow Round #1 Round #2 Round #3
- 42. Design Phase Everyone can DRAW Don’t be afraid and shy! SKETCHING shouldn’t be perfect or pretty!
- 43. Critique Phase Critique Phase: YOU PRESENT, team members critique Green for Good ideas Red for Bad ideas ? for “not sure” - needs to be tested TEAM CAN ASK: Why? For whom? How? What?
- 44. PAPER Prototypes
- 45. TESTING Setup
- 46. TESTING paper prototypes •Pick someone to be the facilitator •Give user the intro and demonstration •Give user tasks one at a time •Pick someone to be the computer •Pick someone to be the user •Remaining people will be observers and note takers Let’s test your prototype
- 47. TESTING paper prototypes •Stays neutral and quiet during the testing session •Keeps neutral body language (poker face) •No grunting, sighing, etc. •No explaining •Have the same person play computer in every session The “computer”
- 50. EVALUATE! Make SURE the design WORKS Evaluation is not about SUCCESS. It is about FAILURE. Test EARLY and OFTEN!
- 51. USABILITY TESTING is the technique that Lets you check whether the design works for real users, diagnose problems and learn how to fix it.
- 52. STEP #1: Plan the test • Sketch / Paper prototype • HTML prototype • Old design • Competitor’s design • Your own final website EVERYTHING What to test?
- 53. STEP #1: Plan the test Recruit users ◦ Who is your target audience? - user profile Why to test with real users? Product managers, designer and developers are not typical users.
- 54. To identify a design's most important usability problems, testing 5 users is typically enough STEP #1: Plan the test How many users to test?
- 55. STEP #1: Plan the test Tasks tips 1) Don’t use industry jargon 2) Ask specific questions to get specific answers 3) Ask about firsthand experiences 4) Define the timeline You need to ask the right question in the right way. You want results you can trust.
- 56. Prepare Environment USABILITY LAB EXAMPLE
- 57. Usability LAB USABILITY LAB EXAMPLE
- 58. Usability LAB SIMPLE USABILITY LAB EXAMPLE
- 60. Usability LAB the environment should be as real as it is possible
- 61. Encourage participant to speak aloud Don't rescue participants when they get stuck Don't react negatively to mistakes Avoid your body language and voice reactions STEP #2: Run the test Don’t make the user feel guilty or dumb Key properties of a usability professional: CURIOSITY & HUMILITY
- 62. Go through your notes and identify common problems WRITE REPORT • summarize your findings • keep it simple • focus just on fixing 2-3 things STEP #3: Analyze findings
- 63. Modify design by findings STEP #4: Modify & repeat TEST AGAIN
- 64. Testing what’s obviously WRONG is a WASTE of time and money.
- 66. More about Usability: www.usability.gov Design Patterns that work: http://goodui.org Free WebExpo conference speeches: http://webexpo.cz/videa/en/ USEFUL LINKS