2024-10-03 - UX/UI Working Group Meeting
- Asma Ahmed
- Sam Daitzman
Date
Oct 3, 2024
Discussion topics
Time | Item | Presenter | Notes |
|---|---|---|---|
10 mins | Quick updates on current projects |
| |
5 mins | Content Libraries relaunch design and implemented UX updates | @Sam Daitzman | Brief high-level updates/demo on content libraries relaunch. Will share some common workflows as they are currently implemented, a few weeks before code freeze. Please feel free to reach out for more detail, questions, or feedback. |
10 mins | Product proposals UX review | @Sam Daitzman | Review product proposals and identify any with UX/UI implications. We can assign some folks to quickly review some of these product proposals and report back next meeting. |
10 mins | Cross-platform notifications: shared workspace | @Sam Daitzman | Align on a shared plan for cross-platform notifications user experience. There are currently 3-4 separate teams working on notification improvements. I created a shared notifications workspace to collect some of those designs in one place. I’m hoping this can help us reach alignment on user experience across mobile, web, and email notifications. |
Meeting notes
Current Projects Discussion:
Updated the group on the ASU project, which is in the discovery phase, and other mobile projects that are progressing through the UX stage.
The content libraries project is moving quickly toward development, with a code freeze anticipated in a few weeks.
Content Libraries Preview:
A demonstration of the content libraries was given, highlighting features such as:
Creation and management of collections and components.
Advanced filtering tools for easier navigation.
A sidebar for library-level information.
Review of the Notifications Proposal:
Discussion regarding the notifications proposal, emphasizing the need for clarity before sharing the screen to avoid overwhelming participants.Notification Complexity and Grouping
The complexity of notifications across various channels (email, mobile push, etc.) was highlighted.
The importance of grouping messages was noted, referencing that too many notifications can reduce user engagement significantly.
Example: X's platform has experienced a notable drop in click-through rates when users receive more than a certain number of notifications.
Proposed Grouping Mechanism:
Notifications could be grouped based on course relevance and urgency.
Examples shared included:
A notification indicating unread replies to a single discussion post.
A summary notification for multiple discussion updates within a single course.
A combined notification for upcoming assignments across multiple courses, which could simplify user experience.
Database Overview for Notification Categories
There is a database that serves as a child page to the centralized multi-channel modifications proposal.
The database aims to categorize message types, levels, and routing details for both web and mobile notifications.
Status Indicators: Messages are categorized as "proposed" or "draft" to clarify their development stage.
Feedback Request: Attendees were encouraged to review the simplified view of the database and identify any expected messages that may be missing.
Event-Triggered Notifications Discussion
Additional Ideas:T he possibility of implementing event-triggered notifications instead of relying solely on date-based triggers was raised.
Examples of event-triggered notifications:
Course completion notifications.
Achievement notifications (e.g., certificate received).
Community engagement updates (e.g., failed assessments).
Connection to Course Updates: A discussion ensued about the potential for linking event-based triggers to course updates, enabling more timely and relevant communication with learners.