Case Study
Part 1
Small Incremental Change
ANALYSIS PHASE
Vision from Stakeholders
-
Introduce the concept of educational badges.
-
Make them shareable.
Determine Desired Outcome:
1. Create a unified student experience
2. Introduce "Badging" concept. Make the badges social.
3. Design something students WANT to use and finish. Lessen the amount of groaning and angry tweets/instagrams from students
4. Design something for teachers of all technical skill levels, including those who struggle to use email
Research Users
Create Hypothesis
DESIGN PHASE
Badge Design
Badge Design
Badge Design
Interface Design
Interface Design
Interface Design
TEST AND LEARN
What happened?
A few of the reasons for the problem:
- Facebook and Twitter blocked at many schools (didn't realize the full extent to this)
- Users couldn't find the badges
- No interesting copy was added during implementation
- Why share? No incentive, social or otherwise.
- Not enough communication between teams to implement the project
... And now we iterate.
Part 2
Set the Vision
As part of the summer 2013 release, EverFi is looking to expand our entire K12 user base to use a single identity to access multiple learning platforms.
-
This approach will allow users to learn more about and access additional learning platforms
For school and districts, it will allow a single view of performance data across multiple platforms.
Define Goals
● Make engagement easier with a unified system - simplifies access to the learning platform and corresponding curriculum applications so that users don't have to enter the same information over and over again.
● Enable decision makers and high level stakeholders to better manage the success of the platforms at a school or district level so that they can see aggregated data when and where it’s convenient to them.
● Support future creation of teacher networking tools within the platform to supplement our on the ground schools team efforts and overall technical support model.
Define Assumptions
● All K12 learning platforms, except for current licensed AlcoholEdu for HS schools, are built and supported on our “Homeroom” system architecture for start of 2013 academic semester.
● Going forward, all K12 schools will have “viewing access” to all K12 learning platforms in order to be exposed to new products within the K12 “Assembly” suite of applications
● FUTURE: allowing users to login with using an additional ID, such as Facebook or Gmail.
Create User Stories/Personas
-
Student
-
Teacher
- Superintendant
- Sponsor
- Curriculum Director
- Principal
Conduct Focus Group
Determine User Performance Requirements
Simplified login page
Increased speed to register and log in to current account
Increased error messaging/tooltips
Guide user through login and registration process
DESIGN PHASE
Whiteboarding
Design Login User Flow
Design Registration User Flow
Wireframes
Wireframes
Wireframes
Higher Fidelity
Higher Fidelity
Higher Fidelity
Wireframe for Dashboard
First Draft of Dashboard
First Draft of Dashboard
Updated Dashboard
TEST AND LEARN
... AND THEN WE WILL ITERATE
My Design Process
By drewux
My Design Process
- 1,649