SAS Profile
Role: Research and Design
Screen to work from
The Ask
Develop a personalized profile for SAS users that displays information related to the individual user’s SAS activity. The enhanced profile screen is needed to display information related to Community and Interactive Calendar updates, and courses taken in the PD Center that meet specific training requirements. This profile screen also needed to highlight information added to the RSS feed to allow teachers easy access to those messages.
Pain Points
The tool was scarcely used. The Preferences section took up a large section of the screen and didn't display the preferences selected. The user's information was hidden inside the SAS Profile button, which also doubled as an edit button. The screen had no other functionality. The chat button on the footer went over part of the navigation making it difficult to read or click.
Research
During user interviews, I learned the most prominent sections they were interested in seeing were (1) the user's information and PD courses, and (2) the RSS feed and Interactive Calendar.
After some iteration, I made sure those sections would be visible before the fold and could be interacted with minimal scrolling.
Enhancements Made
I designed a dashboard that prominently displayed Professional Development courses taken and allowed users to download their transcripts. As requested I added an RSS feed and a way to subscribe to it easily. I wanted to bring a more modern look to the page that still kept in line with the style of the portal.
As a profile page, it was important to display the user information on the screen and add edit functionality.
I added an alert highlight for the interactive calendar and the communities section so the user can be notified when an update has been made.
I moved the Preferences section to a less prominent place on the screen and displayed the preferences selected by the user.
Lessons Learned
Before finishing the development of this screen I should add rollovers to the links. Even though the buttons should work as they currently do in the portal I should have created rollovers to make sure the engineers did not think these would work differently. I need to make a note of that in the handoff.