"Pain Point" Post-it Note Group Activity 

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.

high severity

1

2a

low severity

2b

3

 

high frequency

low frequency

File Manager (Priority 1 / Applicable to all)

Component Ideas 

Pain Points

Metadata / Tagging (Priority 2b / Applicable to all)

Component Ideas

Conditional Release (Priority 2a / Applicable to all)

Component Ideas

Pain Points

Link Manager (Priority 2b / Applicable to all)

Component Ideas

Pain Points

Content View (Priority 1 / Applicable all)

Component Ideas

Pain Points

List Navigational Actions / Views (Priority 1 / Applicable all)

Component Ideas

Pain Points

In-line file viewer (Priority 2b / Applicable all)

Component Ideas

Pain Points

Content Previewer - while I'm authoring (Priority 2b / Applicable all)

Document Creater (Priority 1 / Applicable all)

Group Breakout - fleshing out problem space

File Management Fleshing Out at Summit meeting

 Design Goals

 Next Steps