teams to improve functionality and user experience

Teams to Improve Func1onality & User Experience

Daphne Ogle :: User Experience Designer Eli Cochran :: User Experience Developer

Jon Hays :: Instruc1onal Designer

Thursday, July 9, 2009

July 2009 10th Sakai Conference ‐ Boston, MA, U.S.A.

Working in Collabora1onTeams to Improve Func1onality & User Experience

2



Working in Collabora1on

We're here to talk about (and to get you to talk about) the collabora1on between

• Instruc1onal Designers• User Experience Designers

3



Why Collaborate?

• Faculty Support & Developments feels disconnected from the product development process.

• User Experience needs collaborators to deepen our understanding of users and to validate our solu1ons.

• Our skills and experiences are complimentary.

4



What do we hope to accomplish?

• Leverage each other's skills and investments

• Get beXer informa1on about our users

• Gain insight into each other’s prac1ces• Improve Sakai!

5



Who are we?Teams to Improve Func1onality & User Experience

6



University of California, Berkeley

• Faculty Support & Development Group• 2 frontline support • 3 instruc1onal designers• 1 administra1ve support

• 1 manager

• User Experience Group• 3 senior interac1on designers• 1 senior interac1on developer

7



Focus on User Needs

Are we really that different?

8

from ISO Standard for Human‐Centered Design

!"#$%&'($##"(&)*(

+,-.$/0#$1#*#"(

"#234$

5'21#-(-##12(

26#037#"(&,$0%)$.89(

,2#*(:()*4.$3;.%)$.8(

*#<,3*#-#$12

=$"#*21.$"(:(

26#03&'(1+#(0)$1#>1(

)&(,2#

56#03&'(1+#(,2#*(:(

)*4.$3;.%)$.8(

*#<,3*#-#$12

[email protected],.1#("#234$(

.4.3$21(

*#<,3*#-#$12

A*)",0#("#234$(

2)8,%)$2

!"#$%&'(

)*+,"+-.#&*(

/#.01232

42('5*+*(.(

6*+,"+-.#&*(

6+"70*-('5.'(

&.#(7*(2"08*$(71(

3#2'+%&9"#:

!"#$%&'(

;**$2(

/22*22-*#'

!"#$%&'(<"7(

/#.01232

4$*#9,1(

=*.+#3#>(

?".02

!5""2*(

;"#3#2'+%&9"#.0(

@"0%9"#2

Yes

No

Front‐End Analysis Model adapted from Dick & Carey’s Systema1c Design of Instruc1on



User Experience (UX)

9

Jesse James GarreX, hXp://www.jig.net/ia/


http://www.jig.net/ia/

http://www.jig.net/ia/


What UX brings to the collabora1on

• Empathic user researchers

• Design principles and paXerns

• Understanding of human behavioral paXerns

• Models: users, contexts, behaviors

• Tools to communicate requirements

• Knowledge of development process

• Product evalua1on techniques

10



Faculty Support & Development

11

End‐User Support

Help Desk

Documenta8on

Pedagogy Development

Consulta8on

Workshops

Users



What ID brings to the collabora1on

• Knowledge of Pedagogy and Learning Theories• Exper1se with Technologies used for Teaching• Tools for designing training/solving problems• assess needs• understand the context and constraints• design/recommend solu1ons

• evaluate results

• Rela1onships with real users (faculty, students, and staff)

12



Instruc8onal Designers: POV User Experience: POV

Support & foster effec1ve ways to use technology for teaching & learning

Support & foster effec1ve ways to use technology in context

Solve immediate frustra1on Understand immediate frustra1on

Find work‐arounds now Solve root problem long‐term

Make the most of Sakai as‐is Redesign Sakai to match needs

13

Common Goal: Support Users



What are we doing?Teams to Improve Func1onality & User Experience

14



What we are doing at Berkeley

• Design partners• UX designer as facilitator• UX “tag along” on T & S consults• Sharing informa1on /data

• Community building & requirements gathering

15



Design Partners

• Paired: research, modeling & design

• User tes1ng team• Shared understanding• Work products more effec1ve

16



UX Designer as Facilitator

• Leverage collabora1on ac1vi1es• Mul1ple perspec1ves and skills

• Feedback sessions early & olen• Knowledge sharing & dissemina1on

17



UX “tag along” on T&S Consulta1ons

• Mul1ple perspec1ves on the problem

• Iden1fy root problem & immediate work‐around

• Short & long term focus

• Capture user stories

18



Sharing Informa1on and Data

• User Research• User Tes1ng Results • Surveys• Data Logs

19



Community Building / Requirements

• Solicit community requirements

• Share thinking early & olen• Usability of informa1on we share

• Transparent process

20



Differing Perspec1ves

But we're really part of a much bigger community that also includes:

• End‐User Support• Developers• IT Staff• Project Managers

21




And don’t forget:

• Instructors• Students• Researchers• Staff• Administrators

22




• We all have a role in designing, developing and improving Sakai

• But we all have different perspec1ves• No one perspec4ve can get it right!

23




By u4lizing each others points of view we gain a richer three dimensional view of the Sakai user

24



DiscussionQ&A

25



Related presenta1ons this week

• Thursday 13:15 ‐ “How Users Can Influence Design & Development: Sharing Perspec1ves” Amann & Doherty

• Friday 12:00 ‐ “The Best Defense (Support) is a Good Offense (Design)” Doherty

26


teams to improve functionality and user experience

Education