This is a draft in progress.

Discussion about feedback and what components might emerge.

Feedback Definition



Problem description.


Sarah Windsor - Primary Persona
Scenarios to come.

Ed McClellan, Undergraduate
Scenarios to come.

Blue Sky Vision

Possible Components

Procedural/contextual help

Messaging and status indication in workflow:

Where is leaving tool/losing work an issue?

Best practices:

Design patterns

Summit Post-it Page

At the Fluid Summit, pain points represented on post-it notes were grouped into problem spaces (such as Feedback), then into (usually very high level) potential components such as the ones below. Each problem area was then rated as to whether it affected 1, 2, or 3/All of the Fluid applications (Sakai, uPortal, Moodle). Each potential component was then rated on the following matrix, which indicated how severe the pain point it helped solve was for users, as well as how frequently the pain point was encountered. It helped us determine how high a priority it was, with 1 being the highest priority and 3 being the lowest. Some of the components and pain points below also have indicators as to whether they related to (S)akai, (U)portal, or (M)oodle.

high severity



low severity




high frequency

low frequency

Procedural Guidance

1 / All
Also known as a "Wizard". Guiding a user through a multi-step series of interfaces to complete a task.

Empty State Orientation Helper

2A / All
Properly orient the user to a tool when it has no data (empty state). An example would be an inbox with no email.

Progress Indicator

2B / All
A status indicator for time to completion (for things like file upload).


1 / All
Display of messages to the user.

Contextual Help

1 / All
Help within the user's context.

Info Sharer

2B / All
The ability to share information entered through one tool with other tools.

RSS Aggregator

2B / All
Multiple RSS feeds displayed on a page.


1 / All
Sent notifications and the ability to manage and set preferences.

Print Preview

2B / All