Pebble+ student feedback and schedule

As a result of the work done for the ATLAS integration project, the issue of students having to use functionality embedded in a platform that was predominantly aimed at learning managers (Academics, Learning Designers etc.) was hi-lighted as an opportunity for improving the user experience.
Client
PebblePad
Year
2023
Timeline
4 weeks
Skills
Strategy
 / 
Research
 / 
Design
View prototype/website
View prototype/website
(CHALLENGE)

The PebblePad learning platform is made up of two main components. Pebble+ which is predominantly the domain of students, where they do their work, and ATLAS, which is the learning management component. Currently there are certain functions that a student needs to access that reside in ATLAS.

This creates a disjointed and often confusing experience for students when they find themselves in an alien environment that is primarily designed for other personas. The challenge was to remove the need for students to access core functionality in ATLAS and transfer this functionality to their native environment, Pebble+.

(GOAL)

The primary goal was simple, take students out of ATLAS. Totally remove the need for them to access core functionality in ATLAS. Keep them in Pebble+.

It was also our aim to update the functionality, streamline and simplify user journeys and present them using the new PebblePad design system. During the initial design phase of the ATLAS integration project, the cross-functional team identified scheduling and feedback as two student user journeys that would benefit from both a functional and UI update.

Feedback Widget

The goal for the 'Feedback Widget' was to enable students to receive and act upon all feedback quicker, creating a more efficient workflow for assessment. It would also help remove the need for students to access ATLAS.

Schedule Widget

The goal for the 'Schedule Widget' was to raise student awareness of deadlines and timelines, improve engagement, submission rates and overall academic outcomes. Again, it would help take students out of ATLAS.

As with the ATLAS integration work, high-level requirements for the work were defined. Again, these requirements would sit at the heart of all the proposed solutions and would align the solutions with the PebblePad design principles.

All solutions MUST BE:

- Simple to start
- Intuitive
- Scalable
- Helpful
- Consistent
- Concise
- Efficient
- Feel integrated
- Accessible

(RESULT)

The cross-functional design workshops generated a number of viable solutions. These were refined and I translated the sketched wireframes  into another hi-res click-thru prototype built with the PebblePad design system.

This prototype was presented internally to key stakeholders in the senior leadership, customer success, business development and product teams. The feedback was overwhelmingly positive. The prototype was then put through a user testing plan with students based in the UK and Canada. Again, feedback and results were very positive, with student users reporting that they found the functionality and presentation to be "very intuitive" "so easy to use" and "in-keeping with the Pebble+ interface" and that it was "such a relief that we don't have to go into ATLAS for this".


On the back of stakeholder reaction and positive user testing results, both the Feedback and Schedule Widgets were put through SuRICE scoring and planned into the product roadmap. Development for these two features in scheduled for Q2 and Q3, 2024.