sakai tools designing a user-centered sakai tool sakai tools team rob lowden, daphne ogle
TRANSCRIPT
Sakai ToolsDesigning a User-Centered Sakai Tool
Sakai Tools Team
Rob Lowden, Daphne Ogle
June 8, 2005 2
Agenda
• Tools Team Update
• User-centered design (UCD)
• “Deep Dive” – IDEO Video
• UCD and Sakai Tools
• CSS and skinning Sakai
June 8, 2005 3
Tools Team Update
• TTeam– Past 18 months– Next 6 months– To infinity and beyond
TTeam UpdateUCD
IDEO
Problem Statement
Research
Modeling
Requirements Definition
Framework Definition
Design
Development Support
CSS
June 8, 2005 4
Why User-Centered Design (UCD)• Successful adoption
– Users choose to use Sakai– NO need for "excessive" training
and support staff
• Usable– Easy to use / Intuitive– Meet basic user needs– Doesn’t cause more work
TTeam Update
UCDIDEO
Problem Statement
Research
Modeling
Requirements Definition
Framework Definition
Design
Development Support
June 8, 2005 5
Suggested UCD Process
Cooper Consulting, www.cooper.com
TTeam Update
UCDIDEO
Problem Statement
Research
Modeling
Requirements Definition
Framework Definition
Design
Development Support
June 8, 2005 6
IDEO Video• Tweak process
• Multi-disciplinary team
• “Fail often in order to be successful”
• Feedback early and often
• Watch users at work in their world
• Don’t be constrained by current systems
TTeam Update
UCD
IDEOProblem Statement
Research
Modeling
Requirements Definition
Framework Definition
Design
Development Support
June 8, 2005 7
Problem Statement
• Problem– The problem of…
• Affects– Affects…
• Impact– The impact of which is…
• Successful Solution– A successful solution would provide (benefit
of successful solution)
Menlo Innovations, www.menloinstitute.com
TTeam Update
UCD
IDEO
Problem Statement
Research
Modeling
Requirements Definition
Framework Definition
Design
Development Support
June 8, 2005 8
Legacy Tool Refactor Problem Statement
• Problem– Many Sakai legacy tools are unintuitive and not aligned with style
guide– Limited amount of time & resources available between end of
January and Sakai 2.0 release.• Affects
– Affects faculty, students, staff and researchers in higher education
• Impact– The impact of which is that Sakai end users have to spend a lot
of effort to use the tools and have an inconsistent mental model of the how Sakai works
• Successful Solution– A successful solution would provide:
• Users a consistent interaction model across tools so expectations are met (e.g. how do I navigate, what is a link and what’s not, where certain types of actions can be found, etc).
• Change all legacy tools across system at the same level in given time
TTeam Update
UCD
IDEO
Problem Statement
Research
Modeling
Requirements Definition
Framework Definition
Design
Development Support
June 8, 2005 9
Research
• User Research– Observe users in the field – Interview users and stakeholders– Utilize existing user data
• Support issues• Logs• Surveys• Etc…
– Design and usability principles
TTeam Update
UCD
IDEO
Problem Statement
ResearchModeling
Requirements Definition
Framework Definition
Design
Development Support
June 8, 2005 10
Modeling
• Personas
• Persona Map
• Scenarios / Activity Diagram
TTeam Update
UCD
IDEO
Problem Statement
Research
ModelingFramework Definition
Requirements Definition
Design
Development Support
June 8, 2005 11
Personas
TTeam Update
UCD
IDEO
Problem Statement
Research
ModelingRequirements
Definition
Framework Definition
Design
Development Support
June 8, 2005 12
Persona MapTTeam Update
UCD
IDEO
Problem Statement
Research
ModelingRequirements
Definition
Framework Definition
Design
Development Support
June 8, 2005 13
Scenarios/Activity Diagrams
• Scenario– System use in story form
• Activity Diagram– Same use in diagram form
• Includes context of work
• More “real” than task flow
TTeam Update
UCD
IDEO
Problem Statement
Research
ModelingRequirements
Definition
Framework Definition
Design
Development Support
June 8, 2005 14
Requirements Definition
• Use Case Diagrams
• Use Case Matrix
• High-level requirements doc
TTeam Update
UCD
IDEO
Problem Statement
Research
Modeling
Requirements Definition
Framework Definition Design
Development Support
June 8, 2005 15
Use Case Diagram
TTeam Update
UCD
IDEO
Problem Statement
Research
Modeling
Requirements Definition
Framework Definition
Design
Development Support
June 8, 2005 16
Use Case MatrixUse Case Frequency Matrix
This matrix describes which actors use which use case, and whether a particular use case is hourly (H), daily (D), weekly (W), monthly, (M) or yearly (Y). Edge cases (E) mean the use case will be performed very infrequently, if ever.
Actor A
Actor B
Actor C
Use Case #1
Use Case #2
Use Case #3
Use Case #4
TTeam Update
UCD
IDEO
Problem Statement
Research
Modeling
Requirements Definition
Framework Definition
Design
Development Support
June 8, 2005 17
Framework Definition
• Information architecture
• Navigation characteristics
• Use case detail
• Style guide
• Tool interoperability
TTeam Update
UCD
IDEO
Problem Statement
Research
Modeling
Requirements Definition
Framework Definition
Design
Development Support
June 8, 2005 18
Design
• Task Flows
• Site Diagrams
• Mock-ups
TTeam Update
UCD
IDEO
Problem Statement
Research
Modeling
Requirements Definition
Framework Definition
DesignDevelopment Support
June 8, 2005 19
TTeam Update
UCD
IDEO
Problem Statement
Research
Modeling
Requirements Definition
Framework Definition
DesignDevelopment Support
June 8, 2005 20
TTeam Update
UCD
IDEO
Problem Statement
Research
Modeling
Requirements Definition
Framework Definition
DesignDevelopment Support
June 8, 2005 21
Development Support
• Functional specifications
• Relentless communication
• User testing
TTeam Update
UCD
IDEO
Problem Statement
Research
Modeling
Requirements Definition
Framework Definition
Design
Development Support
June 8, 2005 22
Conclusion
• Big picture understanding of UCD
• UCD for final core release
• Establish UCD as best practice for future of Sakai
• What would be helpful for December conference?
TTeam Update
UCD
IDEO
Problem Statement
Research
Modeling
Requirements Definition
Framework Definition
Design
Development Support