Module 5 Notes
Module 5 Notes
Module 5
UX Design Guidelines:Using and interpreting design guidelines, Human memory
limitations, UX design guidelines & examples, Planning, Translation, Physical action,
Outcomes, Assessment, Overall
UX (User Experience) Design Guidelines, covering core principles and best practices that
apply across digital products like websites, apps, and software interfaces.
Step-by-Step Approach
Interpretation: Make key calls-to-action (CTAs) bold, larger, or more colorful than
surrounding text.
Adaptation: On a minimal UI, you might use spacing instead of heavy contrast.
Navigation Guideline
Accessibility Guideline
⚠⚠ Always document the why. Product managers, devs, or QA will likely ask.
1. Sensory Memory
3. Long-Term Memory
�Guideline:
Eliminate unnecessary elements. Design should be as simple as possible to meet user goals
efficiently.
� Example:
Google Search homepage – Minimal distractions, just the search bar and a couple of buttons.
�Guideline:
Design interfaces that allow users to recognize options rather than forcing them to recall
information from memory.
� Example:
Amazon's search autocomplete – Suggests previously searched terms and products to reduce
effort.
3. Provide Feedback
�Guideline:
� Example:
Instagram "like" animation – A heart icon fills instantly when tapped, showing the action was
successful.
4. Maintain Consistency
�Guideline:
� Example:
Apple's Human Interface Guidelines – Tabs, buttons, and swipe gestures behave the same
across all iOS apps.
5. Prioritize Accessibility
�Guideline:
Design for users of all abilities by following WCAG standards (e.g., contrast, keyboard
navigation, screen reader support).
� Example:
�Guideline:
Make it easy to find and understand how to move through the interface.
� Example:
Spotify's bottom navigation bar – Easily switches between Home, Search, and Library, always
visible on mobile.
�Guideline:
Use size, color, spacing, and layout to prioritize the most important information.
� Example:
Airbnb – Uses large imagery and bold titles for listings, with supporting info in smaller text
below.
�Guideline:
Prioritize mobile screens since many users will interact via phones.
� Example:
Twitter mobile app – Optimized interactions with thumb-friendly buttons, clear CTAs, and
vertical stacking.
�Guideline:
Prevent errors when possible, and make it easy to recover if they occur.
� Example:
Gmail's “Undo Send” – Gives users a few seconds to undo sending an email.
�Guideline:
� Example:
Slack channel settings – Basic options are shown first, with an "Advanced Settings" link for
more complex controls.
1.Planning
�Purpose:
�Activities:
Stakeholder interviews
Define user personas
Set business and UX goals
Identify key user tasks
Map out project scope and timelines
� Example:
Planning a ride-sharing app: Identify primary users (riders, drivers), goal (easy trip booking), and
pain points (wait time, unclear pricing).
2. Translation
�Purpose:
Translate user needs and goals into user flows, features, and structure.
�Activities:
� Example:
Convert user journey (open app → book ride → track ride) into screen flows and interactions.
3. Physical Action
�Purpose:
Design and build interactive elements that enable users to take action.
�Activities:
� Example:
Users tap ―Book Ride‖ button; app confirms ride with animation, shows real-time driver
location.
4. Outcomes
�Purpose:
What happens after the user’s action — both system response and user result.
�Activities:
� Example:
After tapping ―Pay,‖ the app confirms the transaction, sends a receipt, and updates ride history.
5. Assessment
�Purpose:
�Activities:
Usability testing
A/B testing
Analytics review (task success rate, drop-off points)
Heuristic evaluations
� Example:
Test shows users abandon ride booking at the payment screen. Redesign for simpler payment
flow.