1. Navigating Student Needs

2. Methods used Student Personas Needs identified Lessons learned

3. Method – sketching workshop

4. Method – “DOTs” exercise

5. Method – student lifecycle

6. Method – functional mindmaps

7. Methods – focus groups & card sorts OE student focus groups 5 x Student Services Initiatives proposals – Academic Commons, aka CalCentral – Communications Hub & Knowledge Base – Advising Toolkit – Bill Paying – Academic Planning Navigation card sorts

8. Student Personas Ben 3 rd year undergrad https://confluence.media.berkeley.e du/confluence/display/MYB/Ben+- +3rd+Year+Undergraduate+Student Sofia – freshman undergrad https://confluence.media.berkeley.e du/confluence/display/MYB/Sofia+- +Freshman+Undergraduate+Student Nicole graduate student https://confluence.media.berkeley.e du/confluence/display/MYB/Nicole+- +Graduate+Student

9. Needs – basic and many! Navigation – unify the online Berkeley experience Communications – More targeted messaging – Help me manage important tasks and events Academic life – Planning tools – Class tools The current student experience

10. Lessons Learned Create the big picture vision, then – Deliver useful functionality You can’t solve all problems ($, time, & resource constraints) – Identify & prioritize the high-value/high-impact solutions – Don’t recreate an existing solution – Address core campus needs, ex: teaching & learning “Push” vs. “Pull” services and UX design – “Push” key data, alerts, tasks, etc. – Help users navigate/”pull” information and access resources Students / Staff / Faculty – Share common needs and need to communicate – Create a single campus gateway, not 3

11. Looking to the future - Mobile “Pushing” alerts & key information to students